Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Legato Restore of NT 4 sp6 Client

Status
Not open for further replies.

revdark

MIS
Mar 21, 2001
9
CA
Good Afternoon,

I am currently running into trouble with restoring a server (to identical hardware.

The client is running NT 4 SP6, and the Legato Version is 6.11.

The legato server is also NT4 SP6a Version 6.11

The restore works up until the point that the system has to be re-booted. After this is done, the system just keeps rebooting in an endless loop. As soon as the logon splash screen appears, it vanishes and the system reboots.

Has anyone encountered this before, and if so, was there a solution?

Thank you,
Shayne Dark
 
One thing to check would be the size of thr page file. It needs to be at least the size of the amount of RAM + the size of the registry. Make sure the you have the right size before rbooting the machine.
 
Good Morning,

Thanks for the idea, but the pagefile is 3760mb, with the physical memory being only 2560mb I cannot imagine that the registry has swollen to the better part of a Gb.

The Virtual Memory settings on the machine were set identically to the original before the restore was attempted.

Any other thoughts on the matter?

Best Wishes,
Shayne Dark
 
We've done restores of legato clients to both identical and non-identical hardware here. After you drop the system state onto the new client and you have to reboot, try putting the NT4 CD back in and doing an inspect/repair on your NT system files(Helps if you have an ERD handy). Since you are booting, you can probably skip the repair on boot sector/startup files/ .When the repair completes reboot the box, and once you get in reapply SP6a. Having identical hardare is really a beautiful thing.

Hope this helps,

Larry
 
We had this problem in the case when Harddisk partioning
has been changed before restore. We had a hidden partition,
therefore boot partition was 1, not 0. new configuration
had first partition as boot partition

Solution was not to recover boot.ini, since there is an
entry pointing to the boot partition number.

hope this helps

Wilfried
 
I had this happen a lot whist testing for DR in my test lab.

It came down to the way I built NT on the machine before the restore.

How are U building NT on the machine before the restore is started.

FernandezD
At your service.
Unix systems Admin
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top