N4 "Data Recovery Service in fault state. Runtime data not protected." [Solved]
I recently was tasked with upgrading a site that had a bunch of old AX Jaces to new Jace 8000's. I ran the migration, which ended up being more problematic than I had anticipated because apparently some old Honeywell modules don't like to go from 3.8 to 4.11. So, 3.8 -> 4.4, then 4.4 -> 4.11.... Anyway, everything seemed to be going fine then a month or so later I get a call about an error showing up on the bottom of Workbench that says "Data Recovery Service in fault state. Runtime data not protected." after quite a bit of searching I found the solution.
In the Niagara Community there is an article that talks about this problem.
"There's a very old issue where certain Lonworks network variables, that should be non-critical weren't flagged as non-critical. And there's an action on the Lonworks network to fix it. You should be aware that when people upgrade older systems, it's not uncommon to encounter this issue. System Integrators may still be using personal palette files today, that still contain Lon network variables that don't have the non-critical flag set. Unfortunately, we cannot distinguish between the case where we didn't set the non-critical flag when it was created by software, from the case where a person intentionally turned it off. So, it's necessary that System Integrators invoke the Set Nvs Non-Critical action themselves. This will set all NVs non-critical in the station's Lonworks Network. Old versions of Niagara AX exist where that action throws an exception. To support those old versions, we used to distribute a program object that does what the action is supposed to do. But we don't support those old versions of AX anymore."
Not all of the Jaces were showing this error. However, when looking at the Data Recovery Service in the running stations the bars representing data being stored were filling up fairly quickly. After running the action on the Lon Network the the data rate on the bars slowed down considerably. After rebooting the Jace's with the error the problem was solved.
TLDR: Right click on the LON Network and go to actions -> Set Nvs Non-Critical.
I recently was tasked with upgrading a site that had a bunch of old AX Jaces to new Jace 8000's. I ran the migration, which ended up being more problematic than I had anticipated because apparently some old Honeywell modules don't like to go from 3.8 to 4.11. So, 3.8 -> 4.4, then 4.4 -> 4.11.... Anyway, everything seemed to be going fine then a month or so later I get a call about an error showing up on the bottom of Workbench that says "Data Recovery Service in fault state. Runtime data not protected." after quite a bit of searching I found the solution.
In the Niagara Community there is an article that talks about this problem.
"There's a very old issue where certain Lonworks network variables, that should be non-critical weren't flagged as non-critical. And there's an action on the Lonworks network to fix it. You should be aware that when people upgrade older systems, it's not uncommon to encounter this issue. System Integrators may still be using personal palette files today, that still contain Lon network variables that don't have the non-critical flag set. Unfortunately, we cannot distinguish between the case where we didn't set the non-critical flag when it was created by software, from the case where a person intentionally turned it off. So, it's necessary that System Integrators invoke the Set Nvs Non-Critical action themselves. This will set all NVs non-critical in the station's Lonworks Network. Old versions of Niagara AX exist where that action throws an exception. To support those old versions, we used to distribute a program object that does what the action is supposed to do. But we don't support those old versions of AX anymore."
Not all of the Jaces were showing this error. However, when looking at the Data Recovery Service in the running stations the bars representing data being stored were filling up fairly quickly. After running the action on the Lon Network the the data rate on the bars slowed down considerably. After rebooting the Jace's with the error the problem was solved.
TLDR: Right click on the LON Network and go to actions -> Set Nvs Non-Critical.
