Solved

Best Practices - Full Restore of SBS 2003 onto a new array

Posted on 2007-04-06
5
331 Views
Last Modified: 2010-04-18
I'm looking for the best practices way to back up and restore SBS 2003 to a new hard drive array on the same server it's currently running on.  I've had success in the past using the Windows backup to take a full system backup, installing SBS on the new array, and then doing a restore from the full backup.  This last one we did failed and the machine bluescreened after the restore.  We ran out of time and couldn't run a repair on the restored OS (would have probably fixed the problem) but we had to roll back.  I found two things that I didn't do that may have caused it.  
1. We didn't make the C & D partitions the exact same size as they were on the old array, and
2. We didn't bring the newly installed OS up to the same Service Pack as what was running on the old array before I ran the restore.
We would much prefer to do this as a bare-metal restore but the only product I know that will do that is Symantec Backup Exec - System Recovery and we can't spend a $1K just for this restore.  Microsoft says that the blue screen is caused by the hardware change and 97% of the time can be be fixed by running a repair.

I need to know how you guys and most large enterprises are doing this to establish what the best practice should be for our organization.  Your thoughts and recommendations are greatly appreciated.
0
Comment
Question by:changjia
5 Comments
 
LVL 16

Accepted Solution

by:
glenn_1984 earned 500 total points
ID: 18867937
0
 
LVL 22

Expert Comment

by:Olaf De Ceuster
ID: 18868164
Re:
1: Size of partitions (as long as they are large enough) does not matter. If you had Drives C and D it will be easier if you recreate them on the new array.
2: SP levels have to be the same otherwise you are doomed.
3: Make sure USB drives are disconnected while doing restore.
Hope that helps,
Olaf
0
 
LVL 8

Expert Comment

by:Brain2000
ID: 18873193
Restores can be very messy, and every situation can warrant a different approach.  For example, our company has terrabytes of data, and can take up to 48 hours to restore all of the data we host.  So bare metal restore is not an option (or we're in big trouble).  We keep a warm standby that is within a week or two ready to go.  On our production machines, we run mirrored drives and clusters.  So if a computer completely dies, an entire other server is ready to take over and continue on.

Let's look at your situation, which doesn't sound too bad.  If you don't want to make the investment in Veritas just yet, another option might be to take a fresh hard drive that is the same size as the existing one in the SBS server, then install that hard drive into the SBS server, taking out the existing drives.  Install the same operating system, put on the service pack, and then remove the hard drive and stick it in a closet (or a safe place).

Then, on the day that you need to do a full restore, pull that hard drive out of the closet, boot up, run the restore, and you're done.

If a restore method is imperative that it work, then be proactive about it and try the method before you buy into it.  Even with Veritas, try the bare metal restore before you rely on it.  The reason for that is even Veritas bare metal restore fails half of the time, unless you did it just right.  Or didn't have a certain service pack installed.  Or had a patch installed.  etc...  It's better to be proactive and find that you have a restore problem, and get that problem resolved, before you need to actually do a restore for real.
0
 

Author Comment

by:changjia
ID: 18909580
glen_1984,

The tech republic article was very helpful.  As a matter of fact we brought in the author as a Subject Matter Expert to consult for a few hours on our server upgrade.

Thanks.
0
 
LVL 16

Expert Comment

by:glenn_1984
ID: 18917346
Glad it worked.
I could have used him last week.
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

How to fix error ""Failed to validate the vCentre certificate. Either install or verify the certificate by using the vSphere Data Protection Configuration utility" when you are trying to connect to VDP instance from Vcenter.
Storage devices are generally used to save the data or sometime transfer the data from one computer system to another system. However, sometimes user accidentally erased their important data from the Storage devices. Users have to know how data reco…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now