Am attempting to create a disaster recovery plan for our firm. I have had no success restoring my current backup to a new server using the method described in the documentation(BSOD every time). Are there other issues of which I am not aware? [sig][/sig]
I am doing exactly the same thing as you, and have also been getting lots of BSOD's.
So far the only thing that I think may have affected my restore, was that the original copy of NT was installed into a WINNT40 directory, whereas the new installation was just WINNT. There may be a path embedded in the registry files that are restored, that causes problems.
Additionally, I noticed on the Veritas site, that someone asked a similar question, but in relation to using the IDR option. One of the comments by Veritas was, that you couldn't restore a multi-processor installation of NT to a new machine which only has one processor. For one of my servers, this is the case.
However, it still failed when I tried to restore a uni-processor machine.
If I have any luck, or find any further information, I'll let you know.
My %systemroot% is correct, but I am attempting to restore a dual-processor machine to a uni-processor, so that is probably my problem.
I am now experimenting with just restoring the security from the prior installation, then reinstalling the applications from CD, then restoring the data from backup.
I will be watching the forum thread recently posted as to alternatives to Backup Exec. Creating a backup app that can restore only the applicable registry settings in cases like this will obviously be a difficult task, but whoever is able to make it work should be able to write their own ticket.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.