Windows Forum

Ask something
Discussion Locked

Backup Windows 2k server

0 helpful
5 replies

by gregori65

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am confused on how I should take my steps in case I might need to rebuild my windows 2K server. My office has only one w2k server with the exchange 2k installed. I use Veritas 6.0 as backup software installed on a separate media server by which I perform a full backup everyday. Now, if my w2k server crasches, do I need to reinstall the operating system before I full restore it?

Thank you for your help.

5 replies

by simpsonite

Typically, yes. You will need to make sure you are doing a full backup of your server, including systemstate. I usually use the Windows Backup component to occasionally backup the systemstate to a local file and then backup the whole system including the file. you will need to install to an altermnate directory, apply patches and service packs to bring you up to the same level, reinstall BackupExec and restore. If you are not using the exchange agent for Backup Exec, you will need to backup Exchange seperately.

Hope this helps, respond if you need more info.

by gregori65

Ok, so I undersatand that I have to backup data files, profiles, home directory, storage groups, mail boxes as well as systemstates (registry and active directory...)but why do I need to backup the operating system if I have to reinstall it anyway?
your help has been appreciated

by cg it

I think actually doing a reinstall from backups is a better method of learning than just getting theory of why its best to backup everything. That's where a test network comes in. Try a reinstall from a full backup on the test network without reinstalling the O/S and see what happens. You'll be surprised. Next try a reinstall from a full backup with reinstalling the O/S. You'll be surprised again. Do a directory service restore from a backup[ I assume your W2K server is your DC] and see how it runs. Disaster recover is a pain in the butt even with backups but backups make the process less like pulling teeth.

by cg it

I'll add this. One of the biggest reasons for backing up everything is that if you try to recreate from scratch after a disaster, you lose the global catalog, SIDs, ACLs user profiles, stuff like that. workstations will have to rejoin the domain and then user profiles will be different which makes users boo you in the hallway and throw paperwads at you.

by cg it

users boo and throw paperwads at IT people as a matter of course so thats not a biggee in and of itself, but I honestly recommend that you get yourself a test network [ a server and a workstation] and do recovery simulations.

This discussion is closed to new replies.