RE: VM vs Data Guard for DB redundancy

From: Dave Morgan <oracle_at_1001111.com>
Date: Fri, 22 Jul 2016 08:38:12 -0600
Message-ID: <57922FD4.2070602_at_1001111.com>



> From: "Mark W. Farnham" <mwf_at_rsiz.com>
> Date: Wed, 20 Jul 2016 08:41:05 -0400
>
> Excellent point.
>
>
> … And the whole topic needs to be evaluated in the context of the business continuation needs both locally (ranging from a blown disk to a site disaster) and regionally (ranging up to earthquakes, floods, and terrorism). Fine slicing to minimize license costs *probably* pales in comparison to the insurance value of doing things “right” to support business continuation, and that requires building a specific plan for a specific business. Amongst VMware, Dataguard, Delphix, Mladen’s company’s stuff, AXXANA, and more, first you build a comprehensive plan for the whole business, then you construct a few possible alternatives to support the technological infrastructure component (that includes getting back your data and getting the database up and running and accessible, but also includes the entire stack of access out to the actual users.) The business also has to plan (one possible example) how to get enough order entry clerks relocated to an ar
 ea where
cell phone service and
> wifi has been restored. And so forth.

Exactly, I once purchased a $100 1TB USB consumer disk to mirror redo logs in a poor mans hot backup scenario.

Archive logs have already been transferred, if there's a problem grab the USB drive, cross the street, plug it into the hot backup and roll forward. 30-60 minute downtime instead of 4-8 hours.

At that time, the next level, redo logs mirrored to a remote array, where the client is now, was $250,000.

Horses for the courses as they say.

Dave

>
>

-- 
Dave Morgan
Senior Consultant, 1001111 Alberta Limited
dave.morgan_at_1001111.com
403 399 2442
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jul 22 2016 - 16:38:12 CEST

Original text of this message