General discussion

Locked

Creating/Updating an NT 4.0 Server ERD

By wcbattey ·
When I try to create and Emergency Recovery Disk (ERD) or update an existing one using the rdisk utility the [3.5" HD 1.44 Mb] floppy diskette formats okay and the process of copying ER data to the floppy begins without incident. However, a short while later the copying stops and a message appears stating that all the information could not be copied to the floppy because the disk is full, and that "... the remaining data has been copied to the hard drive." This occurs when I try to make an ERD on either of my servers.

I do not believe that having the information copied to the hard drive will help me if I ever need to restore NT using boot and ER disks.

I have looked at a few reference books for NT 4.0 Server, but none of these books even mentions that this situation can arise.

I would like to hear from anyone who knows of [the cause and] a solution that I can use to successfully create an ERD for each of my Dell PowerEdge 2400 servers.

Thanks

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Creating/Updating an NT 4.0 Server ERD

by DKlippert In reply to Creating/Updating an NT 4 ...

The Repair folder is full, you must sacrifice such files as Sam and Security.
MS has a procedure to follow in just this case.
Type the following in the address box of IE:

MSKB Q130029

Collapse -

Creating/Updating an NT 4.0 Server ERD

by wcbattey In reply to Creating/Updating an NT 4 ...

Poster rated this answer

Collapse -

Creating/Updating an NT 4.0 Server ERD

by TTrinh In reply to Creating/Updating an NT 4 ...

Instead of having to "sacrifice" some important files, there is another way to save the whole thing:

You mention having 2 servers. run the command RDISK /s- under command promtp, and your whole registry is saved to c:\winnt\repair folder (in compresed form). Save this whole folder to your second server, under REG1_bk, for examle. This will allow you access to the reg in case server 1 is messed up. Do the same for server2 to save to server1.

To uncompress those files, just use the expand command. When server1 is sick, install a second instance of NT on server1, then connect that instance to your net work and copy the bk reg to server1 and uncompress and replace files in c:\winnt\system32\config with the bk files.

Tuan

Collapse -

Creating/Updating an NT 4.0 Server ERD

by wcbattey In reply to Creating/Updating an NT 4 ...

Very helpful! I adopted the recommendation offered by this contributor

Collapse -

Creating/Updating an NT 4.0 Server ERD

by wcbattey In reply to Creating/Updating an NT 4 ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums