| Author |
Message
|
| dellv |
 Posted: Tue Mar 17, 2009 8:01 pm Post subject: What is DR? |
 |
|
Newbie
Joined: 17 Mar 2009
Posts: 8
|
| can anybody explain DR instructions for the Server?(Abrivate DR) |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Tue Mar 17, 2009 9:38 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
DR = Disaster Recovery. ie. What to do if critical application and infrastructure components fail. There should be a DRP = Disaster Recover Plan for your organisation.
_________________
Glenn |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Mar 18, 2009 5:16 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| You may also come across the abbreviation BCP (business continuity plan) that seems to be the buzzword flavor of the month in all the CIO magazines so expect to see it in a meeting near you soon! |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Mar 18, 2009 5:32 am Post subject: Re: What is DR? |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| dellv wrote: |
| can anybody explain DR instructions for the Server?(Abrivate DR) |
In some shops it is called as Contingency plan. If something goes wrong with existing infrastructure, the traffic will be routed to contingency(DR) center or servers.
Thanks. |
|
| Back to top |
|
|
| Pavan Kumar PNV |
| Posted: Wed Mar 18, 2009 6:08 am Post subject: |
|
|
Acolyte
Joined: 03 Feb 2007
Posts: 66
|
you can read more on how this is achieved in MQ by reading the HACMP manuals
_________________
_____________
Pavan Pendyala
http://pavanz.blogspot.com |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 18, 2009 6:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Pavan Kumar PNV wrote: |
| you can read more on how this is achieved in MQ by reading the HACMP manuals |
If you happen to be on the platform that uses HACMP. If not, it's the manual for SecureGuard or one of the other...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 18, 2009 6:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In fact, HACMP is not a Disaster Recovery solution at all.
It's a High Availability solution.
DR usually requires multiple physical locations, separated by a considerable distance. Trying to span that "space" with most HA solutions will lead to pain and lots of time in conference rooms with executive managers. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 18, 2009 6:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
A more broad definition of DR: The ability to restore normal (business) operation following an outage - to the extent that the organization is willing and able to do so.
Sounds political, yes? It is. I've worked at shops where the directive was "Just back up everything." Of course, you can't really back up everything unless you know where everything is. There is also a knee in the expense curve beyond which management may/may not be willing to go to guarantee no outages. There is an enormous range of possibilities between no DR at all, and no outages.
The above definition deliberately leaves out any/all detail (hardware, software, network, data, etc.) because these are determined by how much or little management comits to DR.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 18, 2009 7:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
In fact, HACMP is not a Disaster Recovery solution at all.
It's a High Availability solution.
|
Doh!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Mar 18, 2009 3:58 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
A more broad definition of DR: The ability to restore normal (business) operation following an outage - to the extent that the organization is willing and able to do so.
Sounds political, yes? It is. I've worked at shops where the directive was "Just back up everything." Of course, you can't really back up everything unless you know where everything is. There is also a knee in the expense curve beyond which management may/may not be willing to go to guarantee no outages. There is an enormous range of possibilities between no DR at all, and no outages.
The above definition deliberately leaves out any/all detail (hardware, software, network, data, etc.) because these are determined by how much or little management comits to DR. |
The DR capability should also be tested on a regular basis (say once a year) to ensure that it actually works and the DRP is correct in every detail. Normally this would be done out of business hours, as the main facility is completely taken off line, and the DR site is brought up for testing. Its a given fact that some business data may be missing or duplicated at the DR site, so application restart and recovery is an interesting exercise.
These days, good HA solutions are beginning to make traditional DR obsolete.
Business Continuity (BC) encompasses both HA and DR.
_________________
Glenn |
|
| Back to top |
|
|
|
|
