MphasiS – Backup And Recovery Guideline

Version 1.0

17 August 2010
Confidentiality Notice/Disclaimer
This 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 arvind.narsing@mphasis.com
Business Phone 080-40049128
Backup and Recovery Guideline 1.1

Amendment Record
Published/ Section /
Version Author
Revised Date Nature of Change
Backup and Recovery Guideline 1.1

Table of Contents
2.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
Backup and Recovery Guideline 1.1

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

<<Name To be
DB backup, of reviewed
restore and Server every
Ilangovan
recovery Bhanu team quarter or
document Prakash contact> on need
Reddy Arvind N Sudheeran K > basis

<<Name To be
of reviewed
Application <<Name of Server every
backup document << Name of <<Name DM and team quarter or
TechLead/Project <<Name of Tech Business contact> on need
Lead >> of PM>> Lead>> contact>> > basis

To be
<<Name <<Name
Application reviewed
of of
Dependency & every
dependent <<Name of Server
Interface quarter or
<< Name of application DM and team
document on need
TechLead/Project <<Name owner>> Business contact>
basis
Lead >> of PM>> contact>> >

1
Backup and Recovery Guideline 1.1

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

2
Backup and Recovery Guideline 1.1

2.2. Document Contents

Name Comments

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
DB backup, restore 3) List details of recovery steps , test plan and test scripts to verify the restored
and recovery backup
document 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”)

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
Application backup
document
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.

1) List all required dependencies

2) List contact points, restores details of the respective dependencies
Application 3) List details of recovery steps , isntallation steps, test plan and test scripts to
Dependency & verify
Interface document

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

Backup_RecoveryTe
mplate.xlsx

3
Backup and Recovery Guideline 1.1

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.

Comments
File Responsible
Name/ID
System(s) Level Frequency Schedule Individual/Org

<< Such as << Such as

<< Name(s) "Daily" or "Last Friday << Organization or
<< Name or To be
of the file << Such as "Weekly" or of the week individual
identifier reviewed and
system(s) "Full" or "When " or responsible for
associated with audited every
included in "Incremental" modified" "Monday" or performing this
the backup quarter or on
this backup >> >> "As backup procedure
procedure >> need basis
>> required" >>
>>

Template.xlsx
(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.

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

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

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

/Purpose backup of modified partitions" >>
File System(s) << Name(s) of the file system(s) included in this backup >>

Full
Level
Incremental
Other (explain):
Frequency Daily (Sunday through Saturday)
(Cycle) Weekdays (Monday through Friday)
Weekly
Monthly
Quarterly
Annually
When files are modified

4
Backup and Recovery Guideline 1.1

Other (explain):
_N____ backup cycles (enter the number of cycles to retain)
Forever
Other (explain):
(Person responsible for backup should get the required information
Retention 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
Onsite
Storage
Offsite
Location/ID
Notes (describe storage identifier, storage location etc):
E.g Virtual Tape
Backup
Medium Hard disk
Other (describe):
<< 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 >>
Procedures

5
Backup and Recovery Guideline 1.1

6
Backup and Recovery Guideline 1.1

5. Recovery Procedures

RecoveryLog.xlsx

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 << Name(s) and emergency contact information such as
Function phone, pager, and cell phone >>

Prerequisites/ << Description of any prerequisites that must be

Dependencies performed before this procedure is executed and/or any
dependencies related to this procedure >>

Associated Backup << Name(s) or identifier(s) of the procedure(s) that

Procedure(s) create the backup(s) that will be used by this recovery
procedure >>

ID(s) of Backup(s)
<< Such as tape ID etc associated with the backup tape
Used
used for this recovery >>

<< Detailed steps for executing the recovery

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

7
Backup and Recovery Guideline 1.1

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:

RecoveryTest_Templ
ate.xls

8
Backup and Recovery Guideline 1.1

9
Backup and Recovery Guideline 1.1

10
Backup and Recovery Guideline 1.1

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 - EDB Folklore Web application installation guide

Installation Manual.pdf

Desktop application (Folklore) installation

Payroll Folklore Payroll
guide
Installation Guide.pdf

Desktop application (Interface) installation

Payroll Payroll Interface
Installation file.doc guide

Payroll ftp file download SAP payroll input file download guide
process .doc

Back-up team will provide the DB backup. The

same would be restored in DB Server by
DB restoration Restore a Database
backup.doc Server Team according to the attached
document.
VSS (with restricted access) will be
maintained at the DR site. A copy of the
Password List (To be
Payroll executables along with password list will be
maintained in a DVD)
written to a DVD and maintained in the Fire
Safe zone at the DR site.

11
Backup and Recovery Guideline 1.1

7.2. Hardware Configuration

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

Server Name Proposed Server Process # of CPU Speed Memory Storage(

Model or Type CPU’s (GB) GB)

MphasiS-Pay2
HP DL580 G5/ Intel 2-Dual 3.40 GHZ
(Application 16 640
Dell PE6850 Xeon Core Dual core
Server)
MphasiS-Pay3 HP DL580 G5/ Intel 2-Dual 3.40 GHZ
4 750
(Database Server) Dell PE6850 Xeon Core Dual core
Desktops (To run
Four desktops with minimum Configuration of Pentium 4 CPU, 512 MB RAM,
Folklore - payroll)
80 GB HDD, running Windows XP, MS-Office, Dot Net Framework 2.0.
application

7.3. Disk Configuration

Disk Configuration
Server Name
# Disks RAID Level Drive Label/Usage Size
C: 12 GB
2x 72GB RAID 1
MphasiS-Pay2 E: 680 GB
(Application Server)
6x 146GB RAID 5 D: 55 GB

C: / Program files 21 GB
2x 72GB RAID 1
MphasiS-Pay3 D: / Payroll Interface 47 GB
(Database Server)
6x 146GB RAID 5 E: / Backups & Logfiles 680 GB

Four Desktops
C: & D: Standard MphasiS
(To run Folklore - N/A N/A 180 GB
corporate OS images
payroll application)

Three Desktops
C: & D: Standard MphasiS
(For technical N/A N/A 80 GB
corporate OS images
Support)

Enterprise
Windows
edition x64 Local WPS Gold Disk
Server 2003
(W) SP1
Folklore (E- Local WPS /
Local WPS / Fire Safe Zone at the
Payroll Web NA Fire Safe Zone
DR site*
Setup) at the DR site*
Local WPS / Fire Safe Zone at the
MphasiS-Pay2 JAVA 64 bit NA
DR site*
(Application Server)
Local WPS / Fire Safe Zone at the
Tomcat 6 NA
DR site*
Adobe Local WPS / Fire Safe Zone at the
8 NA
Reader DR site*
MS office
(Word, 2003 Local WPS Gold Disk
Excel)
MphasiS-Pay3 Windows Standard Local WPS Gold Disk

12
Backup and Recovery Guideline 1.1

Disk Configuration
Server Name
# Disks RAID Level Drive Label/Usage Size
Edition x86
Server 2003
(W) SP1
(Database Server) Enterprise
SQL Server
Edition Plus Local WPS Gold Disk
2000
SP4
Professional
Windows XP Edition (w) Local WPS Gold Disk
SP2
Desktop Folklore Local WPS /
Local WPS / Fire Safe Zone at the
Desktop NA Fire Safe Zone
(To run Folklore DR site*
Setup files at the DR site*
payroll application) Local WPS / Fire Safe Zone at the
Local WPS /
Interface DR site*
NA Fire Safe Zone
Desktop
at the DR site*
Setup files

7.4. Server Network Configuration

Server Name(s) Software Version Media location License Key
MphasiS-Pay2
255.255.255.224 172.16.100.176/
(Application N/A 192.100.45.110
/ 192.100.45.97 172.16.100.67
Server)
MphasiS-Pay3 255.255.254.0/ 172.16.100.176/
N/A 172.16.101.201
(Database Server) 172.16.100.2 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 Product/Usage
Inbound – F/W to Server
Outbound – Server to F/W
8080 TCP Both Payroll Application
8082 TCP Both Payroll Application
1433 TCP Both Database

13
Backup and Recovery Guideline 1.1

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 Secondary
Number Contact Number
Sanjiv Kumar Shrivastava Group tzydns@eds.com 9916162196
Manager

8.2. Escalation Matrix

Escalation Leaders Department Contact Details Contact Number

9. ISMS reference document

EPRO-CRO-013_Bac
kup and Restoration Procedure.doc

14