ANL. All other databases and scientific experiment databases would be unrecoverable (there are no offsite backups). Recovery Point Objective (RPO) (RPO is defined as the maximum interval of data loss since the last backup that can be tolerated and still resume the business process) RPO objectives are currently not formally defined. Need to work with Service Owners / Customers to determine objectives. Estimates based on current backup/restore parameters : ½ to 2 business days depending on availability of restore services, database size and – number of databases that need recovery. Off-site restored data may be as much as 7 days old (from backups currently copied off-site once per week). Recovery Team In this section describe the other services, roles, and responsibly required for recovering this service. Service/Role/Function Responsibility Dependencies Expected Response Time Network Services Service Owner Network connectivity / Reference SLA/OLA DNS service DocDB 4312 Network Attached Service Owner Must be able to connect Reference SLA/OLA Storage to and access SAN, NAS 4311 and AFS data volumes Virtual Server Hosting Service Owner We must be able to Reference OLA DocDB access working Virtual 4612 Machines Facilities Service Owner Data center, power, Reference OLA environment 4594 Backup and Restore Service Owner We must be able to get Reference OLA DocDB our databases restored 4315 from backups IT Server Hosting Service Owner We must be able to 4-8 business access working
ANL. All other databases and scientific experiment databases would be unrecoverable (there are no offsite backups). Recovery Point Objective (RPO) (RPO is defined as the maximum interval of data loss since the last backup that can be tolerated and still resume the business process) RPO objectives are currently not formally defined. Need to work with Service Owners / Customers to determine objectives. Estimates based on current backup/restore parameters : ½ to 2 business days – depending on availability of restore services, database size and number of databases that need recovery. Off-site restored data may be as much as 7 days old (from backups currently copied off-site once per week). Recovery Team In this section describe the other services, roles, and responsibly required for recovering this service. Service/Role/Function Responsibility Dependencies Expected Response Time Network Services Service Owner Network connectivity / DNS service Reference SLA/OLA DocDB 4312 Network Attached Storage Service Owner Must be able to connect to and access SAN, NAS and AFS data volumes Reference SLA/OLA 4311 Virtual Server Hosting Service Owner We must be able to access working Virtual Machines Reference OLA DocDB 4612 Facilities Service Owner Data center, power, environment Reference OLA 4594 Backup and Restore Service Owner We must be able to get our databases restored from backups Reference OLA DocDB 4315 IT Server Hosting Service Owner We must be able to access working 4-8 business
Database%20Hosting-Service%20Continuity%20Plan-2012-09-08.docx