Problem with Arcserve DR and NT BDC

[PaulC245]

We have encountered a problem, fortunately in testing. We use Arcserve 6.5 with the Disaster Recovery Agent. In the past we have conducted successful tests to restore the BDCs in our Branch Offices. We tried testing again recently and we can not get the servers to boot. The message says that the file \\winnt\system32\config\SYSTEM is missing or corrupt. Arcserve refuses to restore the registry files SYSTEM and SOFTWARE. It also fails to restore most of the drivers, and a number of DLLs. We can only find this out after replacing the missing files one by one and rebooting to find the next one. The Emergency Repair process fails to recover these files even though we have a current ERD.

The files are backed up, we can merge the tape on another machine and restore the files individually. If we try to restore the entire WINNT folder, those files will not restore.

We don't believe we have run a test since upgrading to NT Service Pack 6a.

Has anybody encountered this problem? Is there a way around it?

Thanks

Paul

 

[monkeylizard]

I hat eto point out the obvious (Since I'm sure you've thought of this) but try removing SP6a and going back to whatever you used before. Try it then. If it works, then it's a pretty sure bet that AS6.5 doesn't play well with NT's SP6a.

If this is the case and you NEED Sp6a, you'll have no choice but to upgrade AS6.5 to 6.61 or 2000.

Fill us in on how this goes and I may have some better ideas. Monkeylizard
-Isaiah 35-

 

[ARCserveGuru]

Quick question,

Have you followed this documentation?

http://support.ca.com/techbases/asnt/16046.html

guru - brightstor@hotmail.com

 

[PaulC245]

Hi Guys,

Thanks for the ideas. We are going to try building a server using SP4 or 5 and see if we can restore it. Then upgrade to 6a and see what happens.

As for the documentation from CA, we will use that if we have to. We have used that here in our home office successfully. We purchased the Disaster Recovery package because it's supposed to do it in one step. It worked before we had SP6a. It's difficult to walk one of our branch people through an install of NT and the registry editing on the phone. CA support has offered little help and we wanted to see if anyone else had run into this.

Thanks,

Paul