
This means that the yearly backups we keep for some years are useless. Seems fine.īut if we are truly not able to restore from a new BE server. Backups ran according to schedule again to.

My new BE installation saw all the servers etc etc. Make some changes in SQL database and done. I only had to copy a Data and Catalog folder.
Symantec backup exec 2014 manual manual#
I had found a manual on Symantec site to do this and also contacted Symantec by phone.
Symantec backup exec 2014 manual upgrade#
This for a Windows upgrade from 2008 to 2012 R2. Since there would probably be references to my old BE server.įunny thing is. So if BE looks at GUID's no luck on a new BE installation restoring a compleet server. But storage devices probably work with GUID's to. I assume GUID's are not only in the SDR files. That could work.īut since i saw that SDR files already work with GUID numbers.

What if i make a new BE server with same specs etc. This basically means that if your BE server crashes. I'm not going to contact Symantec anymore. At this point I am becoming curious if it is even possible!ĮDIT: Thanks for the responses. So, if anyone has experience with this scenario. Which in case of Fire or whatever would no longer exists. i see only references to my production BE server. There is a option in BE to store catalog information with the backup set. When trying to restore backup from BE server (LAB). So nice feature for your live environment. SDR needs to be enabled at least to perform this action from production BE server. P2V from Windows backup straight to ESX host. From there trying to restore from backup sets. VM (From BE connected to a ESX host of vCenter and backup entire VM) Backups where made to "Backup To Disk" Device.

I duplicated backup sets (Windows Backups) from tape. In my lab environment i pretend that everything is burned to the ground. P2V from Windows backup straight to ESX host.īUT. From that original BE server where the backups are made from no problem doing any type of restore: So we are running BE2014 to backup 24 Production servers. I'm really curious if anyone here had run up to the same problem.
