Re: Backups, ASR and Disastor Planning
- From: "kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Feb 2008 13:09:20 -0700
Larry Struckmeyer wrote:
Good catch Kevin.
So, Chris: if all is normal, then all is normal. If the
computer/user is refused or challenged, you can try the reset command
as shown in the article. If that does not work, then use the
wizards to remove the computer account, disjoin the workstation from
the domain, then still using the wizards, recreate the account and
run //connectcomputer.
Just to make it clear this is *not* something for *any* DC, SBS included.
This applies only to *member* servers and workstations. Also, this is not
something 'typical' for the occasional recovery using last nights backup.
....but for DR planning and when older backups enter into the picture
(images, monthly fulls, etc) it's nice to have some expectations that this
can pop up especially for the less experienced or 'backup' admin.
For planning, backups (system state, images) 0-30 days, condition #1 in the
article is an increasing probability (3.33% increase each day). After 30days
its almost certain, if the Computer account passwords are being changed on
schedule.
After 30 days condition #2 becomes the same increasing likelyhood. After 60
days, it too is almost certain.
"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:OoQk2GCaIHA.1132@xxxxxxxxxxxxxxxxxxxxxxx
Larry Struckmeyer wrote:
Unless you withdrew from the domain, nothing should change. Every
thing should be like it was.
Servers (Non DCs) change their Computer$ account password
periodicaly (30 day by default) so, the older the restored backup
the more likely it is you might run into an outdated computer$
account password. The following describes this and recovery;
http://support.microsoft.com/kb/295049/en-us
"Chris White" <ChrisWhite@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E028228B-F465-4C85-A6C0-646582CAA2E3@xxxxxxxxxxxxxxxx
- Sorry, additional question...
Whats the proper way to rejoin a user to the domain after running
through restoring the server. Obviously I dont want to run the
/connectcomputer wizard as the user and computer accounts already
exist. So what do I need to
do or run on the clients/server in order to rejoin them to the SBS
box? Cheers.
--
Chris White
United Kingdom
"Chris White" wrote:
Haha true true.
Unfortunatly that person would probably be my father. He's a
director here
but sometimes shares this wonderful IT burden with me (8 Servers
and 40 users).
Anyway, I want to write a plain and simple disaster recovery plan
and stick
to it. I want people to know what to do if this should ever happen
or god forbid somethin happens to me.
So i am in the process of taking care of our company in this
respect. I work
here out of passion more than money, I want to see the company
grow and be
successful. We've recently had a boom which was un-expected,
taking us from
300GB of data up to about 1TB with work increasing nicely. This is
all very
good but obviously I need to take care of risks my end in terms of
recovery.
I will have Shadow Copies working nicely when our backup server
has more SATA TB disks installed. At the moment its mostly DFS
Replica's with Failover
enabled covering the file stuff.
Anyway, thanks for the help. I will use the document to shape the
recovery
document.
--
Chris White
United Kingdom
"Teneo" wrote:
Are you saying someone at the office can restore when you are
away.... Cool
you have another IT person...lol
"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote
in message
news:OS%23GSK$ZIHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
Hi Chris:
The official MS document and real world experience don't differ
much. Install the Windows Portion of SBS, stop, add the Service
Pack needed to
bring your Windows to previous levels, and restore from your
backup.
http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d62bcc9/BKU_BkupRstr.doc
Or, image with one of the commercial / freeware products.
--
Larry
"Chris White" <ChrisWhite@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:BCEC9F94-B15E-4116-A195-E974E2C8CBC3@xxxxxxxxxxxxxxxx
Hi all,
I am just completing my disaster recovery routine for the
server room in
case i'm not around. Its bad enough being the one and only IT
guy in this
company but I need to make a plan for disaster recovery should
anything
happen when i'm away.
Now, the following is currently in place...
SBS2003 Full Backup to Local Hard Disk x 3 (3 Days Worth of
Full Backups)
Backup File Copied to Seperate Backup Server and Taken Offsite.
However, the one thing that always made me curious was the ASR.
How to
properly implement this into the design and, in the event of a
total HDD
failure on the SBS Operating System HDD, how to go about
getting it all
back
up and running.
Whats the best steps to recovery assuming the following...
1. The SBS HDD has totally died and is down completely.
2. Backups are available on seperate local HDD installed in SBS
Server
Cheers and thanks in advance.
--
Chris White
United Kingdom
--
/kj
--
/kj
.
- Follow-Ups:
- Re: Backups, ASR and Disastor Planning
- From: Chris White
- Re: Backups, ASR and Disastor Planning
- References:
- Re: Backups, ASR and Disastor Planning
- From: Larry Struckmeyer
- Re: Backups, ASR and Disastor Planning
- From: Teneo
- Re: Backups, ASR and Disastor Planning
- From: Chris White
- Re: Backups, ASR and Disastor Planning
- From: Chris White
- Re: Backups, ASR and Disastor Planning
- From: Larry Struckmeyer
- Re: Backups, ASR and Disastor Planning
- From: kj [SBS MVP]
- Re: Backups, ASR and Disastor Planning
- From: Larry Struckmeyer
- Re: Backups, ASR and Disastor Planning
- Prev by Date: Re: Exchange SBS R2 Max Size Problem
- Next by Date: Re: Exchange SBS 2003 R2 Exchange SP2 Upgrade
- Previous by thread: Re: Backups, ASR and Disastor Planning
- Next by thread: Re: Backups, ASR and Disastor Planning
- Index(es):
Relevant Pages
|
