Backup Restore Template

MphasiS – Backup And Recovery Guideline

Version 1.0

17 August 2010

Confidentiality Notice/DisclaimerThis document is disclosed only to the recipient to whom this document is addressed and is pursuant to a relationship of confidentiality under which the recipient has obligations to confidentiality. This document constitutes confidential information and contains proprietary information belonging to MphasiS Corporation. The confidential information is to be used by the recipient only for the purpose for which this document is supplied. The recipient must obtain MphasiS Corporation written consent before the recipient or any other person acting on its behalf, communicate any information on the contents or the subject matter of this document or part thereof to any third party. The third party to whom the communication is made includes individual, firm or company or an employee or employees of such a firm and company.The recipient, by its receipt of this document, acknowledges that this document is confidential information and contains proprietary information belonging to MphasiS Corporation and further acknowledges its obligation to comply with the provisions of this notice. The contents of this document are provided in commercial confidence, solely for the purpose of evaluating whether the contract should be awarded to MphasiS. The information contained in this document represents the views and opinions of MphasiS on the issues discussed, as of the date of publication. Due to the dynamic nature of the industry and the technology that it depends upon, MphasiS makes no warranty as to the long term accuracy of the assessments made herein. Copyright © MphasiS Corporation. All rights reserved. All product and company names mentioned herein are trademarks or registered trademarks of their respective owners.

Backup and Recovery Guideline 1.1

Document Control

Application Delivery

Contact Arvind Narsing

Address

Email [email protected]

Business Phone 080-40049128

mailto:[email protected]


Amendment Record

Published/ Revised Date

Version AuthorSection /Nature of Change


Table of Contents2. DATA BACKUP AND RECOVERY......................................................................................................- 1 -

2.1. RASCI MATRIX................................................................................................................................- 1 -2.2. DOCUMENT CONTENTS.......................................................................................................................- 3 -

3. BACKUP SCHEDULE.............................................................................................................................- 4 -

4. BACKUP PROCEDURES........................................................................................................................- 4 -

5. RECOVERY PROCEDURES..................................................................................................................- 7 -

6. RECOVERY TEST AND REVIEW HISTORY...................................................................................- 8 -

6.1. RECOVERY PLAN HISTORY:...............................................................................................................- 8 -

7. APPENDIX...............................................................................................................................................- 11 -

7.1. RELATED DOCUMENTATION.............................................................................................................- 11 -7.2. HARDWARE CONFIGURATION...........................................................................................................- 12 -7.3. DISK CONFIGURATION......................................................................................................................- 12 -7.4. SERVER NETWORK CONFIGURATION...............................................................................................- 13 -7.5. DATABASE DETAILS.........................................................................................................................- 13 -7.6. FIREWALL..........................................................................................................................................- 13 -

8. COMMUNICATION AND DECISION MAKING PROTOCOLS...................................................- 14 -

8.1. CONTACTS ( LIST DOWN ALL CONTACTS WHO IS REQUIRED FOR RESTORE AND RECOVERY ACTIVITY).......................................................................................................................................................- 14 -8.2. ESCALATION MATRIX........................................................................................................................- 14 -

9. ISMS reference document.........................................................................................................................- 14 -


1. Introduction

This document is intended to be a guideline based on which all application owners need to prepare detailed documentations for their respective applications to ensure smooth backup & recovery process of the applications and databases managed by the CIO-Apps team.

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.

2. Data Backup and Recovery

1. Ensure data capture cycles (daily, weekly or monthly) match the RPO (recovery point objectives) requirements specified by business. In addition ensure that the actual data (database, flat files, system cache, DB log files, program files) backed up is the correct range to ensure the restored data will provide the fully restored systems needed to meet the RPO’s

2. Ensure application setup and related configuration files required to make the application up and running are backed up for point in time recovery.

3. Ensure backup/restore documentation is maintained and tested to ensure recovery of systems.

2.1. RASCI MATRIX

Name Responsible Approved Support Informed Consult Comments

DB backup, restore and recovery document

IlangovanBhanu Prakash Reddy Arvind N Sudheeran K

<<Name of Server team contact>>

To be reviewed every quarter or on need basis

Application backup document << Name of

TechLead/Project Lead >>

<<Name of PM>>

<<Name of Tech Lead>>

<<Name of DM and Business contact>>



Application Dependency & Interface document

<< Name of TechLead/Project Lead >>

<<Name of PM>>

<<Name of dependent application owner>>

<<Name of DM and Business contact>>



1


(Note: Use the sheet “RASCI MATRIX” in the attached template)

2


2.2. Document Contents

Name Comments

DB backup, restore and recovery document

1) List complete details of backup ( files, level, frequency schedule dependencies, tool used e.g. RMAN or SQL backup, HP Data protector)

2) List details of tapes , location , contact person of Infra team

3) List details of recovery steps , test plan and test scripts to verify the restored backup

4) List details of dependencies to be restored

Note: List all files required to recover the application until last point of failure(Note: Use the sheet “DatabaseBackup”,”Restore”, “DatabaseRecovery” in the attached template “Backup_RecoveryTemplate.xlsx”)

Application backup document

1) List details of all files required to be backed up

2) List details of tapes , location , contact person of Infra team

3) List details of recovery steps , installation steps, test plan and test scripts to verify the restored backup

4) Media details ,License keys

Note: List all files required to recover the application until last point of failure(Note: Use the sheet “ApplicationBackup”,”Restore”, “ApplicationRecovery” in the attached template “Backup_RecoveryTemplate.xlsx”)

File system backup is recommended for application files and VSS for source code . VSS server backup to be taken on daily basis to ensure code is available in case of VSS server crash.

Application Dependency & Interface document

1) List all required dependencies

2) List contact points, restores details of the respective dependencies

3) List details of recovery steps , isntallation steps, test plan and test scripts to verify

Note: List all files required to recover the application until last point of failure

3


3. Backup Schedule

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.

Name/ID File

System(s) Level Frequency Schedule Responsible

Individual/Org

Comments

<< 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 week " or "Monday" or "As required" >>

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

To be reviewed and audited every quarter or on need basis

(Note: Use the sheet “BackupSchedule” in the attached template)

4. Backup Procedures

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

(Note: Use the sheet “BackupLog” in the attached template)

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 FullIncrementalOther (explain):

Frequency (Cycle)

Daily (Sunday through Saturday)Weekdays (Monday through Friday)WeeklyMonthlyQuarterlyAnnuallyWhen files are modifiedOther (explain):

4


Retention

_N____ backup cycles (enter the number of cycles to retain)ForeverOther (explain):(Person responsible for backup should get the required information from Server Team)

E.g For Oracle ERP Quarter ending tapes has to be preserved, whereas as for other transactional system past quarter tapes can be overwritten

Storage Location/ID

OnsiteOffsiteNotes (describe storage identifier, storage location etc):

Backup Medium

E.g Virtual Tape

Hard disk 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 >>

5


6


5. Recovery Procedures

The Recovery Log is used to track the actual executions of the 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 Function << 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 etc associated with the backup

tape used for this recovery >>

Procedures

<< Detailed steps for executing the recovery

7


procedures, including login, file locations, executables to run, parameters to use, expected messages or results, verification of results >>

8


6. Recovery Test and Review History

Note:For critical 1 application recovery drill be carried out every 3 months and for Criticality 2,3 applications drill will be carried out every 6 months to start with .

Test/Walkthrough Date Responsibility Success(Y/N) Remarks

6.1. Recovery Plan History:

9


10


11


7. Appendix

Refer Appendix section for sample doc and related details which should be part of Master document for respective application which can used as handy reference or be part of respective documents in section 2.2 . The below section lists down details as an example of what all details every application owner needs to capture.

7.1. Related Documentation Application Document Definition

Payroll

Folklore Web application installation guide

Payroll

Desktop application (Folklore) installation guide

Payroll

Desktop application (Interface) installation guide

Payroll SAP payroll input file download guide

DB restoration

Back-up team will provide the DB backup. The same would be restored in DB Server by Server Team according to the attached document.

PayrollPassword List (To be maintained in a DVD)

VSS (with restricted access) will be maintained at the DR site. A copy of the executables along with password list will be written to a DVD and maintained in the Fire Safe zone at the DR site.

12


7.2. Hardware Configuration

The table below details the Minimum configuration required to setup the Prod environment

Server Name Proposed Server Model

Processor Type

# of CPU’s

CPU Speed Memory (GB)

Storage(GB)

MphasiS-Pay2 (Application Server)

HP DL580 G5/ Dell PE6850

Intel Xeon

2-Dual Core

3.40 GHZ Dual core

16 640

MphasiS-Pay3 (Database Server)

HP DL580 G5/ Dell PE6850

Intel Xeon

2-Dual Core

3.40 GHZ Dual core

4 750

Desktops (To run Folklore - payroll) application

Four desktops with minimum Configuration of Pentium 4 CPU, 512 MB RAM, 80 GB HDD, running Windows XP, MS-Office, Dot Net Framework 2.0.

7.3. Disk Configuration

Server NameDisk Configuration

# Disks RAID Level Drive Label/Usage Size


2x 72GB RAID 1C: 12 GB

E: 680 GB

6x 146GB RAID 5 D: 55 GB


2x 72GB RAID 1C: / Program files 21 GB

D: / Payroll Interface 47 GB

6x 146GB RAID 5 E: / Backups & Logfiles 680 GB

Four Desktops

(To run Folklore - payroll application)

N/A N/AC: & D: Standard MphasiS

corporate OS images180 GB

Three Desktops (For technical Support)

N/A N/AC: & D: Standard MphasiS

corporate OS images80 GB


Windows Server 2003

Enterprise edition x64 (W) SP1

Local WPS Gold Disk

Folklore (E-Payroll Web Setup)

NALocal WPS / Fire Safe Zone at the DR site*

Local WPS / Fire Safe Zone at the DR site*

JAVA 64 bitLocal WPS / Fire Safe Zone at the DR site*

NA

Tomcat 6Local WPS / Fire Safe Zone at the DR site*

NA

Adobe Reader

8Local WPS / Fire Safe Zone at the DR site*

NA

MS office (Word, Excel)

2003 Local WPS Gold Disk

13


Server NameDisk Configuration

# Disks RAID Level Drive Label/Usage Size


Windows Server 2003

Standard Edition x86 (W) SP1

Local WPS Gold Disk

SQL Server 2000

Enterprise Edition Plus SP4

Local WPS Gold Disk

Desktop

(To run Folklore payroll application)

Windows XPProfessional Edition (w) SP2

Local WPS Gold Disk

Folklore Desktop Setup files

NALocal WPS / Fire Safe Zone at the DR site*


Interface Desktop Setup files

NA



7.4. Server Network ConfigurationServer Name(s) Software Version Media location License Key


N/A255.255.255.224/ 192.100.45.97

192.100.45.110172.16.100.176/ 172.16.100.67


N/A255.255.254.0/ 172.16.100.2

172.16.101.201172.16.100.176/ 172.16.100.67

7.5. Database Details

Parameters Remarks

Server IP 172.16.100.201

Instance Name(Payroll) mphasis-pay3

Database Name FINSOURCE

MBFL

MBPO

MSIPL

Database Version SQL Server 2000 Enterprise Edition SP4

Compatible

Database Control URL http://localhost:1158/em/console/logon/logon

7.6. Firewall

The following ports need to be opened at the firewall in DR site for proper functioning of the Native Domain Authentication system.

Port Protocol Direction

Inbound – F/W to Server

Outbound – Server to F/W

Product/Usage

8080 TCP Both Payroll Application

8082 TCP Both Payroll Application

1433 TCP Both Database

14

http://localhost:1158/em/console/logon/logon


8. Communication and decision making protocols All concerned stakeholders will be informed through email. Corporate communication (In-touch) will be used to inform wider business audience. EASE support help desk will be used to inform the users in case of down time Conference bridge will be setup for the duration till DR activity is completed successfully

8.1. Contacts ( List down all contacts who is required for restore and recovery activity)

Name Role Email ID Primary Contact Number

Secondary Contact Number

Sanjiv Kumar Shrivastava Group Manager

[email protected] 9916162196

8.2. Escalation Matrix

Escalation Leaders Department Contact Details Contact Number

9. ISMS reference document

15

mailto:[email protected]

Date post:	21-Nov-2014
Category:	Documents
Upload:	arvindn
View:	336 times
Download:	13 times

Backup Restore Template

Documents