Re: Looking for feedback for DR plan
- From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
- To: hrp@xxxxxxxxxx
- Date: Fri, 18 Apr 2014 11:44:57 -0500
As described, I would have to say that the time required is infinite since
you dont have enough data to determine the information you need for DR.
Just writing and testing scripts can take weeks to months depending on how
complex they are. The same applies to the testing plan. You just dont have
enough information. If I absolutely had to come up with a time estimate
from the information provided, I would say somewhere between 12 and 36
months, and make it clear that was pretty much a wild guess.
On Fri, Apr 18, 2014 at 11:14 AM, Henry Poras <hrp@xxxxxxxxxx> wrote:
> OK guys, just looking for some opinions and feedback here. We have a minor
> disagreement at work and I am trying to see where you weigh in. I’ll try to
> present this in as unbiased a manner as possible.
>
> The main question is how long should it take to roll out a DR environment
> given:
>
> -
>
> we currently have a physical standby running
> -
>
> no knowledge of RPO or RTO
> -
>
> incomplete knowledge of type of application connections to DB
> -
>
> incomplete knowledge of number of applications connecting to DB
> -
>
> incomplete knowledge of upstream and downstream feeds/connections to DB
> -
>
> unknown whether failover requires failover of entire application stack
> or not
> -
>
> homegrown failover scripts (currently being used in another
> environment) are being proposed
> -
>
> no testing plan in place as of yet.
>
>
> How much time would you allocate to getting this up and running? Any other
> comments on this proposal?
>
> Thanks.
>
> Henry
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Other related posts:
