.

DR Plans - Best Practices?

<<

lorddicranius

User avatar

Sr. Member
Sr. Member

Posts: 448

Joined: Thu Mar 03, 2011 3:54 am

Post Tue Apr 19, 2011 12:44 pm

DR Plans - Best Practices?

I just had a curious question as to how other companies plan their DR in regards to recovering failed servers.  What are the best practices when it comes to this?

Example: a server is backed up to hard drive on another server on-site (copy #1).  This backup server then archives copies of all the backups to a hard drive that can be taken off-site (copy #2).  Then this backup server also syncs to another server at a remote location (copy #3).  The idea of creating another backup that can be taken off-site (just in case the hard drive that was archived to fails) is being tossed around now.

That's one backup on-site, 2 copies that are physically walked out of the building, and one synced to a remote location.  Where does one draw the line? ???
GSEC, eCPPT, Sec+
<<

R3B005t

Newbie
Newbie

Posts: 43

Joined: Wed Mar 09, 2011 9:03 am

Location: NVA/D.C.

Post Tue Apr 19, 2011 1:27 pm

Re: DR Plans - Best Practices?

Well there are a few different strategies.  We employ several, we have an alternate out of state DR site that contains the following.  We have a LUND with our core servers that replicates across the wan, we have secondary bes servers set up with replication, our exchange environment is clustered with nodes existing at multi-sites.  We also have routine nightly and weekly backups that are stored off sight at a secure location.  Did I mention that we also have client machines doing differential backups.
<<

dynamik

Recruiters
Recruiters

Posts: 1119

Joined: Sun Nov 09, 2008 11:00 am

Location: Mile High City

Post Fri May 06, 2011 8:09 pm

Re: DR Plans - Best Practices?

This is what risk assessments are for. It doesn't sound like there is really a plan, course of action, or any formalized process. What are your ultimately trying to achieve? What is the impact of lost data and/or downtime? You're just going to be grasping at straws if you don't sit down and figure out what you're really trying to achieve. Who knows, you may even find a better way of doing what you need to when you start brainstorming...
The day you stop learning is the day you start becoming obsolete.
<<

Triban

User avatar

Hero Member
Hero Member

Posts: 620

Joined: Fri Feb 19, 2010 4:17 pm

Post Sun Jun 19, 2011 10:07 pm

Re: DR Plans - Best Practices?

The big question is... If something fails, can you bring it back up?  How long can you be down before it hurts business?  What systems are you replicating?  Are you hoping to restore from bare metal?  Is there any virtualization in use on the network?  Ok, so that is more than one question.  But like dynamik recommended, you need to have a formal risk assessment done before planning your DR.  That will make it much easier if you know what needs to be up in a certain amount of time.  Then you are spinning your wheels on less critical systems.

And of course testing testing testing, once you have the plan in place.  Its no good if you don't test.
Certs: GCWN
(@)Dewser
<<

lorddicranius

User avatar

Sr. Member
Sr. Member

Posts: 448

Joined: Thu Mar 03, 2011 3:54 am

Post Mon Jun 20, 2011 2:18 am

Re: DR Plans - Best Practices?

Thanks for the tips guys.  Some great questions that I need to be thinking about.  To do list: risk assessment.
GSEC, eCPPT, Sec+

Return to Other

Who is online

Users browsing this forum: No registered users and 2 guests

.
Powered by phpBB® Forum Software © phpBB Group.
Designed by ST Software