Re: Backup best practices...
- From: "Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxxx*a*m>
- Date: Sun, 3 Feb 2008 07:36:36 -0800
Let's skip your personal server and concentrate on the production servers for your customers. Like myself it sounds like you are a one person shop. What will happen to your customers if you are on holiday in Hawaii and one of their servers has a meltdown? You have done them a great disservice by not having a tested, documented plan to restore their backup. They should be able to do this without you present if possible. If you are like me most of your customers are small business' who count on you to keep their computers running. Some of them would suffer a serious financial blow if their computers were unavailable for a week. How would you feel if one of them went out of business because of you?
Now to get back to your system. Implement a backup system as close to your customer's as is possible. Try several different bare metal restores until you know how to do it without thinking. Try restoring to a new hard drive. Try restoring to a new server. Try restoring from an old backup then recovering current data from a newer backup. Once you can do this document the process for your server. Now spend some time at your customer's sites documenting how they would do it and give them the documentation.
I'm sorry if this sounds like a rant. Selling your customers a solution without a tested, documented plan to restore their data is irresponsible. It will come back to haunt you. Here is a link on using supported procedures to backup and restore a SBS server.
http://www.microsoft.com/downloads/details.aspx?familyid=487736f8-f6f5-436d-a82d-0c8d66e2a634&displaylang=en
--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca/phpBB2/
"Rosewood" <rosewood@xxxxxxxxxxxxxxxxxxxx> wrote in message news:AE3F2BC8-4AD8-48E3-AC02-0F5D0518629C@xxxxxxxxxxxxxxxx
On my personal server, I received a SMART alert telling me that the primary drive is failing. Because this server is my personal one, used only by me for me, I never invested in really sexy hardware for it. If the (sole) primary drive failed tomorrow, outlook would still have all of my emails. My documents would still be available offline.
So my question is: What is the best practice for backup for SBS2003? For me, a perfect backup would be one that is easy to restore and restores everything. All settings for IIS, Exchange, the AD, etc. All the mailboxes would come back, etc. and all w/ minimal effort (or at least very well documented effort).
On all of my production servers, the main drive is in RAID so there is always a live mirror and I use the built in NTbackup to an external drive that most of the time is swapped out weekly for an offsite backup. However, I've never had to actually restore anything since I've started using 2003. So I figured now would be a good time to make sure I'm knowledgeable on the best practices on the backup, and the recovery side of things.
Thanks
.
- Follow-Ups:
- Re: Backup best practices...
- From: Rosewood
- Re: Backup best practices...
- Prev by Date: Re: Specific user account denied access to programs on log in
- Next by Date: Re: Windows Activation when converting installation to a VM
- Previous by thread: Re: Backup best practices...
- Next by thread: Re: Backup best practices...
- Index(es):
Relevant Pages
|
Loading
