The move of the client indexes is pretty straight forward. Read esg66605 - How to move a Client File Index to an alternate location
As for the server database and indexes, it depends on what your goal is. If you have no need to keep a history of data that has been backed up at hand.
Keep in mind that there is no need to scan the information from the media if you do not need it.
To move the servers information, follow the steps in esg55147 - How to reconstruct an existing environment at an alternate site
You can also review the steps in the Disaster Recovery Guide for the version of NetWorker you are using.
NOTE: Whenever performing these type of actions, it is important to review the documentation through before starting so you have an understanding of the steps before you perform them.
Also, be sure you have a valid backup of the NeWorker environment in the event that something unexpected occurs.
Mark_Bellows
240 Posts
0
September 7th, 2011 12:00
The move of the client indexes is pretty straight forward. Read esg66605 - How to move a Client File Index to an alternate location
As for the server database and indexes, it depends on what your goal is. If you have no need to keep a history of data that has been backed up at hand.
Keep in mind that there is no need to scan the information from the media if you do not need it.
To move the servers information, follow the steps in esg55147 - How to reconstruct an existing environment at an alternate site
You can also review the steps in the Disaster Recovery Guide for the version of NetWorker you are using.
NOTE: Whenever performing these type of actions, it is important to review the documentation through before starting so you have an understanding of the steps before you perform them.
Also, be sure you have a valid backup of the NeWorker environment in the event that something unexpected occurs.
Good luck!
Mark