Sid_F
asked on
Backing up and restoring a full windows sbs server
I am currently using veritas backup exec sbs to backup windows 2000 sbs and windows 2003 sbs on several sites.
If a server crashes what is the best way to restore it fully. Recently a server crashed and I had to rebuild the server and restore the data the problem was I also had to dis-join all the pc's from the domain and re-join them again as the sid was different. I have looked into veritas disaster recovery but most of the time the image doesnt' fit on a cd making it difficult to restore as well as having to ensure the dr file is going through ok each day also a server with the same hardware is not always avaliable
Is there a simple method for backing up/restoring full system image. Symantec live state utility seems good but I would have to run it along side veritas so this would not work cost wise for a small business environment
If a server crashes what is the best way to restore it fully. Recently a server crashed and I had to rebuild the server and restore the data the problem was I also had to dis-join all the pc's from the domain and re-join them again as the sid was different. I have looked into veritas disaster recovery but most of the time the image doesnt' fit on a cd making it difficult to restore as well as having to ensure the dr file is going through ok each day also a server with the same hardware is not always avaliable
Is there a simple method for backing up/restoring full system image. Symantec live state utility seems good but I would have to run it along side veritas so this would not work cost wise for a small business environment
Make sure you select the shadow copy components when making the backups. These contain all the active dir components and user accounts etc. These should also be restored first to have AD running again.
Exactly the problem (i.e. one problem) I see with Backup Exec. Acronis true image claims to be better, just boot from CD, and restore entire drive from remote network drive, but Im not sure it is any easier, and means more money. This is why a ghost image of an entire drive duplicated to another is faily foolproof (only SID needs to be refreshed), but it is a nuisance to shut down the server to ghost it all the time. None of the image programs seem to realize, the only easy way is a HDD clone, not an image.
ASKER
Sorry, failed to mentions its veritas version 10, the o.s is 2000/2003 sbs not windows nt
ASKER
Scratchboy, What do you mean by only needs SID to be refreshed, do you mean a new SID?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just follow Veritas recommendations and don't join new mini-OS into domain, read here: http://seer.support.veritas.com/docs/241149.htm
"Also, when installing the parallel install of NT, join a workgroup and not a domain. This allows to recover your original security information descriptor (SID) through Backup Exec, so re-establishing trust relationships with all domains will not be required. If recovering from an entire hard disk failure, use Windows NT setup to partition and format the new disk during installation. Format the partitions with the same file system as before the failure."