04-22-2014 12:12 AM
We have Symantec Backup Exec 12.5 Rev. 2213 installed on Windows Server 2003 R2 with SQL & files backup jobs defined.
The destination for backup jobs is NAS device. Was wandering what happens if server running Symantec Backup Exec fails completely and we have only files on NAS device available. How would we restore then?
Regards,
Drazen
04-22-2014 12:44 AM
1) load the OS on a new machine
2) load BE on the new machine
3) connect the NAS to the new machine
4) inventory and catalog the B2D folder on the NAS.
5) restore the C: drive and the system state, and then reboot
At this stage you would get back your old media server.
04-22-2014 12:46 AM
The answer depends on whether you backup up the Catalogs and Data folder (along with the Backup Exec database) and whether or not you have reasonably similar hardware and a working IDR bootable CD with a recent .DR file
If you have all the above you use IDR to recover the operating system and then possibly recover the latest catalogs and Backup Exec database as a separate stage once the IDR recovery has completed.
If you do not have any of the above then the solution would be manually re-install the operating system and Backup Exec, add in your NAS storage and run Inventory and catalog jobs.
There are of course middle options if you have some of the above items.
BTW as a general recommendataion you should look to update your software as not only is Backup Exec 12.5 already in the end-of-life countdown and not being patched but Windows 2003 is in a similar state.
04-22-2014 01:21 AM
Thank you for your quick answers.
We do have Backup Exec database and whole Symantec folder (including Catalogs and Data) backed up.
How does that change/simplify our recovery options then?
The hardware might or might not be similiar.
Regards,
Drazen
04-22-2014 01:27 AM
Having a backup of the Data and Catalog directories will help you to recover BE itself. You would be able to get back your old job settings, etc.
If your hardware is different, then you would have to load the OS and install BE and then replace the Data and Catalog directories to get back your old job settings. There is no way to completely recover the server because of lack of drivers in your backups.
04-22-2014 12:32 PM
04-22-2014 07:06 PM
04-22-2014 10:18 PM
Additionally, open a cmd and browse to the Backup Exec directory. Run the following command:-
beserver.exe -console
You may either post/pm the output which could help us find out the cause of the error.
Additionally, does the VM have the same name as that of the original media server ? If not, this could be a reason for the service failure when you imported the Data & Catalogs.
04-23-2014 02:09 AM
if the name of the server changes from where the BEDB comes from to where it is now being loaded you do have to take addtional steps as you are in effect doing a migration and not a DR if the servername is different.
04-24-2014 01:06 AM
VM could not connect to database instance since i've renamed VM *after* Backup exec was installed.
There is reg key to fix this:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Server Name
I've tried renaming the VM before Backup Exec was installed and that resolved the issue.
Also, since I was also interested in scenario where Data&Catalogs folders would not be available, NAS was inventoried and cataloged and restoration of data was successfull. Thank you all for your help!
Regards,
Drazen
04-24-2014 01:32 AM
sorry but there are server names inside the database as well as in the registry
Step 5 ion this document priovided tyeh SQL commands
http://www.symantec.com/docs/TECH67296