Video Screencast Help

NBU restore and placeholders

Created: 30 Jul 2013 • Updated: 02 Aug 2013 | 3 comments
This issue has been solved. See solution.


I think I know the answer to this but wanted some confirmation. We had a file server fail yesterday and I was asked if we could reinstall the FSA agent before all of the shares are restored from NBU to allow users to access the data that is now back in one of the shares. I would think this would be fine but was not sure if NBU had any verification process that might recall some of the data being restored from backup and I was sure someone out here could confirm if there would be any issues with starting FSA up for the newly restored shares while the remaining are being laid down from NBU? Generally, we stop the FSA services for a full share restore but this one is a bit different.

We are running EV 9.0 SP4R1



Operating Systems:

Comments 3 CommentsJump to latest comment

GabeV's picture

If you installed the FSA agent before restoring the data, you might want to exclude the NBU application using this TN:

I do not think that restoring a placeholder would make a recall from the EV side, but just in case, I'd use the TN above. Also, stopping the FSA services should be sufficient.

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

Arjun Shelke's picture

I will rather suggest completing the restore job before you start up with FSA stuff. If anything goes wrong with the restore then it will be difficult for you to fix the situation. And even support team, may require more time to help you with that situation.

Either complete the restore first or log a case with Support to let them understand the environment properly and provide you with responsible suggestion.

Vikes 2's picture

We decided to wait for the restore to complete, better safe than sorry.