Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Data Warehouse Disaster Revcovery Options Expand / Collapse
Author
Message
Posted Thursday, November 15, 2012 12:31 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, December 25, 2014 8:04 PM
Points: 7,141, Visits: 12,768
You skipped Step 1. Please define your RTO and RPO, then you can start to evaluate your options. If your RPO is 24 hours then Simple Recovery Model with nightly FULL backups could be enough. If your RTO is 30 minutes then FULL recovery model with Mirroring or Log Shipping will probably make more sense.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1385310
Posted Thursday, November 15, 2012 3:58 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 5:40 PM
Points: 4,263, Visits: 4,311
RTO, RPO?



For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1385388
Posted Thursday, November 15, 2012 4:10 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, December 25, 2014 8:04 PM
Points: 7,141, Visits: 12,768
RTO > Recovery Time Objective: the duration of time and a service level within which a business process must be restored after a disaster (or disruption) in order to avoid unacceptable consequences associated with a break in business continuity, i.e. how long can the system be unavailable while databases are being recovered.

RPO > Recovery Point Objective: the maximum tolerable period in which data might be lost from an IT service due to a major incident, i.e. how many seconds worth of data can the business tolerate losing.

Business Continuity implies the resumption of normal operations, however inevitably it means the prospect of the business itself surviving the disaster. You can Bing or Google to dig up some current stats about how many business completely go under after they lose a non-trivial amount of their proprietary business data.


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1385390
Posted Thursday, November 15, 2012 6:14 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 5:40 PM
Points: 4,263, Visits: 4,311
Thanks.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1385408
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse