System Recovery The following sub-sections define the process and procedures necessary to restore the system to a fully operational state after a service interruption. Each of the sub-sections starts at a specific system state and ends up with a fully operational system. PECS is designated as Routine Support for disaster recovery. This level of support will acquire replacement processing capacity after an AITC disaster declaration. The recovery time objective (RTO) is that it will be operational when the AITC resumes regular processing services or no later than 30 days after a disaster declaration. Data will be restored from the last backup (recovery point objective (RPO)). System backups of the vapredbs1 server are performed on the following basis; Full backups are performed on Sundays and kept for one month. This means that at any time, there should be four full backup tapes available for each server. Tapes are normally dispatched offsite on Mondays. Differentials are run for the remainder of the week to capture daily changes. Differential results are sent offsite on Mondays. Oracle RMAN is the application used to perform full backups of the PREP database every Tuesday and Saturday morning. The tapes are retained offsite for one month. RMAN is also used to back up archive logs and the control file database to tape daily and are also retained offsite for a month. The full database backups run for about 40-45 minutes. The archive log backups are shorter, which run about 25-30 minutes. This section provides procedures for recovering the application at the alternate site, while Section 5.0 describes other efforts that are directed to repair damage to the original system and capabilities. Backup procedures are also defined in this section. Procedures are outlined for each team required to complete the recovery. Each procedure should be executed in the sequence it is presented to maintain efficient operations. The Team Leader or designee will provide hourly recovery status updates to the Austin Service Desk (ASD). Restart After Non-Scheduled System Interruption This are identical to those found in Section 3.1, Administrative Procedures. section’s instructions Software is recovered from images stored on the SAN. The same recovery procedures listed in ACP 4.1 should be followed for a return to original site restoration. An alternate site would need comparable equipment installed and would need to be able to boot from SAN for successful execution of this plan.
System Recovery The following sub-sections define the process and procedures necessary to restore the system to a fully operational state after a service interruption. Each of the sub-sections starts at a specific system state and ends up with a fully operational system. PECS is designated as Routine Support for disaster recovery. This level of support will acquire replacement processing capacity after an AITC disaster declaration. The recovery time objective (RTO) is that it will be operational when the AITC resumes regular processing services or no later than 30 days after a disaster declaration. Data will be restored from the last backup (recovery point objective (RPO)). System backups of the vapredbs1 server are performed on the following basis; Full backups are performed on Sundays and kept for one month. This means that at any time, there should be four full backup tapes available for each server. Tapes are normally dispatched offsite on Mondays. Differentials are run for the remainder of the week to capture daily changes. Differential results are sent offsite on Mondays. Oracle RMAN is the application used to perform full backups of the PREP database every Tuesday and Saturday morning. The tapes are retained offsite for one month. RMAN is also used to back up archive logs and the control file database to tape daily and are also retained offsite for a month. The full database backups run for about 40-45 minutes. The archive log backups are shorter, which run about 25-30 minutes. This section provides procedures for recovering the application at the alternate site, while Section 5.0 describes other efforts that are directed to repair damage to the original system and capabilities. Backup procedures are also defined in this section. Procedures are outlined for each team required to complete the recovery. Each procedure should be executed in the sequence it is presented to maintain efficient operations. The Team Leader or designee will provide hourly recovery status updates to the Austin Service Desk (ASD). Restart After Non-Scheduled System Interruption This section’s instructions are identical to those found in Section 3.1, Administrative Procedures. Software is recovered from images stored on the SAN. The same recovery procedures listed in ACP 4.1 should be followed for a return to original site restoration. An alternate site would need comparable equipment installed and would need to be able to boot from SAN for successful execution of this plan.
prec_6_1_tg_r0717.docx