Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Backup and Recovery Design Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

Contents

= Overview

The Backup and Recovery Design task produces a deliverable that describes how and when backups of the system will be performed and how those backups will be recovered in case of system failure. forfait sosh rio b and you portabilité du numéro calcul IMC rio orange

Example 1 - Backup Recovery plan for assets and content at a Bank

Listed below are example Backup Recovery plan for assets and content at a Bank:

Introduction

This document is intended to be a complete backup recovery process of the assets and content stored and managed by the Client.

This document is not intended to be a complete business continuity or disaster recovery plan. It is only a plan for regular backups of files and for restoration or recovery of files from regularly scheduled backups after an outage has occurred. It does not include plans for the restoration or recovery of facilities, hardware, or services after an outage.

Backup Strategy

<< Current overall strategy for backing up systems and files >>

The following schedule lists each of the detailed backup procedures included in this backup and recovery plan. It also indicates the frequency and schedule for each backup and shows who is responsible for each backup.

Backup Schedule


Name/ID
File System(s)
Level

Frequency

Schedule
Responsible Individual/Org.

<< Name or identifier associated with the backup procedure >>

<< Name(s) of the file system(s) included in this backup >>

<< Such as "Full" or "Incremental" >>

<< Such as "Daily" or "Weekly" or "When modified" >>

<< Such as "Last Friday of the month" or "Monday" or "As required" >>

<< Organization or individual responsible for performing this backup procedure >>

           
           

Backup Procedures

The Backup Log is used to track the executions of the following backup procedures.

Name/ID

<< Name or identifier associated with this backup procedure >>

Description /Purpose

<< Description or purpose of this backup, such as "Daily incremental backup of modified partitions" >>

File System(s)

<< Name(s) of the file system(s) included in this backup >>

Level Circle one:
Full
Incremental
Other (explain):
Frequency (Cycle) Circle one:
Daily (Sunday through Saturday)
Weekdays (Monday through Friday)
Weekly
Monthly
Quarterly
Annually
When files are modified
Other (explain):
Retention Circle one:
_____ backup cycles (enter the number of cycles to retain)
Forever
Other (explain):
Storage Location/ID Circle one:
Onsite
Offsite
Notes (describe storage identifier, storage location, storage vendor):
Backup Medium Circle one:
Tape
CD
Other (describe):
Procedures

<< Detailed steps for executing the backup procedure, including login, file locations, executables to run, parameters to use, expected messages or results, verification of backup results >>

 
 
 

Recovery or Restoration Strategy

Systems or data can be destroyed or corrupted in some cases due to errors, outages, or intentional disruptions. Sometimes only a specific file or file system must be recovered or restored from backups after an outage. Major outages or disruptions may require restoration of most or all of the files from backups. The following sections of this document describe procedures for both minor and major restorations of files from backups.

Recovery or Restoration of an Particular File or File System

In most cases, if a particular file or file system is corrupted or destroyed, only that file or file system needs to be restored from the backups. One of the Recovery Procedures that follow can be used to recover or restore a particular file or file system.

Recovery or Restoration after a Major Outage

If a major outage, such an outage caused by a natural or manmade disaster, has occurred, you may need to restore many or all of the files and file systems. Such major restorations require proper timing and sequencing due to business priorities and file dependencies. The following is a plan for restoration or recovery of all files from regularly scheduled backups after a major outage has occurred. If you need to restore many, but not all of the files, you can use portions of this plan paying close attention to sequencing noted in the Schedule for Recovery/Restoration after a Major Outage and predecessors or dependencies listed in each individual recovery procedure.

<< Please fill in the current procedures for restoration of files after a major outage >>

The following table lists the recovery procedures that are included in the plan for restoration of files after a major outage. It also indicates the timeframe within which each restoration should occur, the priority or sequence of restorations, and who is responsible for each restoration.

Schedule for Recovery/Restoration after a Major Outage


Restoration Timeframe
Restoration Sequence/
Priority
Recovery Procedure
Name/ID


File System(s)
Responsible Individual/
Organization

<< Such as "Within 24 hours" or "Within 30 days" >>

<< Sequence or priority of this restoration >>

<< Name or identifier associated with the recovery procedure >>

<< Name(s) of the file system(s) included in this backup >>

<< Organization or individual responsible for performing this recovery procedure >>

         
         

Recovery Procedures

The Recovery Log is used to track the actual executions of the following recovery procedures.

Name/ID


<< Name or identifier associated with this recovery procedure >>

Conditions for Use


<< Description of the conditions or circumstances under which this recovery procedure should be used >>

Purpose/Results


<< Description of the purpose or expected results of using this recovery procedure >>

File System(s)


<< Name(s) of the file system(s) that will be restored >>

Responsible Individual or Organization


<< Name(s) and emergency contact information such as phone, pager, and cell phone >>

Prerequisites/
Dependencies


<< Description of any prerequisites that must be performed before this procedure is executed and/or any dependencies related to this procedure >>

Associated Backup Procedure(s)


<< Name(s) or identifier(s) of the procedure(s) that create the backup(s) that will be used by this recovery procedure >>

ID(s) of Backup(s) Used


<< Such as tape ID and storage vendor name associated with the backup tape used for this recovery >>

Procedures


<< Detailed steps for executing the recovery procedures, including login, file locations, executables to run, parameters to use, expected messages or results, verification of results >>

 
Wiki Contributors
Collapse Expand Close

View more contributors