UNSOLVED
NetWorker Disaster Recovery Resolution Path
The purpose of this discussion is to help with Disaster Recovery from the Preparation to the actual Recovery. To the extent you prepare for a DR, your recovery will be more successful.
We will talk about NetWorker SERVER disaster recovery roadmap (not a client). This provides an aid to disaster recovery planning. It does not provide detailed step-by-step disaster recovery instructions.
For a successful DR of the NetWorker server, you must meet the following minimum requirements:
• Back up the bootstrap regularly, at least once per 12 hours.
• Back up the server OS configuration regularly.
• Back up the CFI for all clients. A separate, dedicated backup for all client indexes can be performed before or after a bootstrap.
• Monitor, record and store information of each bootstrap backup in a separate physical location from the NetWorker server.
• Use a dedicated pool for bootstrap backups.
• Clone the bootstrap backups.
• Record and maintain the connectivity and details of the SAN, IP and all storage components.
In a situation of a total loss you can recover your backup server from the media with a "sanner" and a "nsrdr -B" commands .Also a bootstrap record will show you what media to use for complete (index,mm,res)recovery of your server.
There is no need to install the same OS or computer configuration.The only thing you need is the same server name as the original.
This is not the procedure of course only some pointers.
Best Regards.
Alexey
I used to keep a basic image of the backup server. So, it is not a must to backup the OS. One requirement is the server name stay the same. (If it is long name, keep it as long name).
To make DR quicker, I dump the mm out to UNC path periodically. Same for res.
crazyrov
6 Operator
•
1319 Posts
775
0
Posted January 21st, 2015 05:00
I don't believe a backup of the Backup server's OS is required for a successful DR, also the part of having dedicated pool for bootstrap backups is also not that impacting on a DR.