Networker

Re: [Networker] KATRINA disaster recovery

2005-09-06 17:39:41
Subject: Re: [Networker] KATRINA disaster recovery
From: Albert Eddie Contractor AFRPA/ESS <Eddie.Albert AT AFRPA.PENTAGON.AF DOT MIL>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Tue, 6 Sep 2005 17:33:05 -0400
Has anyone heard from the original author?

A. I hope he is ok and B. I would like to get his absolute REAL WORLD
review of what they did to recover the data. Whether the backup plan
they had worked, what it was, what they would have changed, etc.

Basically a lessons learned.

Semper Fidelis, /ALE


> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Dave Mussulman
> Sent: Sunday, August 28, 2005 6:46 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Possible disaster recovery
> 
> Browning, David wrote:
> 
> >Well, I really hope this isn't necessary, but as I write 
> this email, I 
> >am facing the possibility of having a destroyed data center at this 
> >time on Monday.  We have evacuated, with an incredible 
> number of backup tapes.
> >
> >What I was wondering, is there anything that I can do from a remote 
> >location to speed up recovery time - such as copying the 
> media database to another
> >remote computer, or copying the bootstrap.   Is there such a 
> way as to run a
> >bootstrap to a disk, or maybe a directed recover of the bootstrap?
> >
> >I have probably 18-24 hours to do some things from this remote 
> >location, before we will lose connectivity to the data 
> center (my assumption).
> >
> >I gladly welcome any ideas at this point. 
> >
> >  
> >
> As was already mentioned; don't rely on a bootstrap or index 
> restores (although in this case, saveset restores are what 
> you're going to want to do.)  Shutdown the existing networker 
> server, archive the nsr directory with something else (tar, 
> ntbackup, etc.) and copy that to your new DR backup server.  
> It should mimic at least the OS/software level as the 
> production server; matching hardware is best.
> 
> If you have that, and you have the media, you can start 
> restoring to DR systems.  IOW, you don't have to wait until 
> you find out the original system was harmed/affected.  Get 
> the DR systems up, but off the network
> - and if you need to move it into service, it's ready to go.  
> You can at least do that for fulls and high level 
> incrementals.  If you find out you need to replace a 
> production system, only the last incrementals you have need 
> to be restored.  (The fulls are usually the time-sinks.)
> 
> In that same vein, if you can copy live data from the 
> production system to the DR system, do that and don't 
> necessarily even worry about an older restore.
> 
> Good luck and Godspeed,
> 
> Dave
> 
> To sign off this list, send email to 
> listserv AT listserv.temple DOT edu and type "signoff networker" in 
> the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any 
> problems wit this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or via RSS 
> at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Networker] KATRINA disaster recovery, Albert Eddie Contractor AFRPA/ESS <=