Restore function broken: Apps do not work correctly after full restore

OK, more info.

I was able to do a restore as long as I chose Custom and checked everything but  "Share Access", then hand-installed the shares and set everything up: permissions, services, etc.. Not fun.

Looks like Restore>Share Access locks up both Transmission and Sickrage, in both cases never doing the "configuration" part of the App installation as a result.

Reinstalling apps from scratch MIGHT work if you did it from a .deb file, because it's broken in the Apps>Available Apps installation, at least for Transmission & Sickrage. Those 2 relatively simple packages not installing stopped me, so I didn't even look at things like github, osticket, surveillance, prestashop, etc. 

Repeat: NOT fun.

And certainly broken. 

I take your point about the apps mount point. but since this is by long-ago setup Netgear standard, mission-critical operations like a configuration backup and restore should work flawlessly, especially since it's practically the only way to come back from hardware failure of the unit in question. And if I was restoring to a replacement unit, it would be a brand-killer if a restore killed apps, as this one seems to do. IT departments I've worked in would junk and ban hardware if they couldn't restore to replacement hardware.

Instead, I have to use RSS (potentially breaking warranty) and dive in "behind the curtain" to find out some of what's going on, and it certainly seems as if there's SOMETHING important not being done right. Especially if I can see stuff in the config directory broken right away, broken so badly that there's no web interface, not solvable by a remove & reinstall, and as near as I can tell not fixable without tarballing over files from the original unit. 

I confess, I could not recommend a ReadyNAS product based on this.

QNAPs are already off my list, for just this reason.

Synology units are not known for having this problem.

I never had a Config Restore kill an add-on in old RAIDiator, and I was running a few.

Logs available. I'd sure like to do what I can to help ReadyNAS people to fix this problem. I was just lucky in that this was a backup to an active unit.

Hope this helps! Now just to wait until the 1st resync is done, to start the slow, painful "add disk, resync, rsync" back to see if I get the full array availaible this time.