Backup Policy Process Number: Designer: Date:

Siddhartha
Patwardhan
CUSTOMER Reviewer: Date:

Process Owner: Ver #: Ver Date Approver: Date:

SAN Team 1.2

Back Up Policy Document

Issue V.1.2

Page 1
 Backup Policy Process Number: Designer: Date:
Siddhartha
Patwardhan
CUSTOMER Reviewer: Date:

Process Owner: Ver #: Ver Date Approver: Date:

SAN Team 1.2

Table of Contents
KEY Backup Summary Points.......................................................................................................................2
I. Backup Process using EMC Networker................................................................................................3
1. Application Name – CRM.................................................................................................................3
2. Application Name – BRM.................................................................................................................4
3. Application Name – AIA...................................................................................................................5
4. Application Name – OSM.................................................................................................................6
5. Application Name – ASAP...................................................................................................................7
6. Application Name – Mediation........................................................................................................8
7. Application Name – EPayment........................................................................................................9
8. Application Name – Notification....................................................................................................10
9. Application Name – POS................................................................................................................11
10. Application Name – DMS...........................................................................................................12
11. Application Name – Exchange...................................................................................................13
12. Application Name – BI...............................................................................................................14
13. Application Name – BMC Remedy.............................................................................................15
14. Application Name – BMC Patrol.................................................................................................16
15. Application Name – KIOSK.........................................................................................................16
16. Application Name – RA-FMS......................................................................................................16
17. Application Name – Domain Controller.....................................................................................17
18. Application Name – LDAP..........................................................................................................18
19. Application Name – Portal.........................................................................................................18
20. Application Name – ERP............................................................................................................19
II. Cases logged with EMC support to troubleshoot backup failures.....................................................20
III. Backup Process using HP – Ignite...................................................................................................21
IV. Glossary.........................................................................................................................................24

Page 2
 Backup Policy Process Number: Designer: Date:
Siddhartha
Patwardhan
CUSTOMER Reviewer: Date:

Process Owner: Ver #: Ver Date Approver: Date:

SAN Team 1.2

KEY Backup Summary Points

1. Backup Strategy involves a mixture of Full & Incremental Backups taken to

Virtual Tape Library (VTL) (EMC DL3D) using EMC Networker backup
application. Daily backups are followed by subsequent replication of data
(Cloning) to physical tapes using Scalar i500 library.

2. All backups follow a retention policy of 30 days on VTL which is available

online for restore. Data past 30 days is sent to offsite tapes. Current
retention of offsite tapes is infinite as their retention policy decision is
being awaited from CUSTOMER.

3. Some Unix server file systems are backed up using HP Ignite imaging
software to obtain a base copy or image of the entire server for Disaster
restore of UNIX OS. This image backup, backs up the OS local file system
only (excluding attached storage), once a month, and stored on storage
array with a retention of 2 months due to space constraints on VTL.

4. Backup failures if any, are troubleshoot by backup team and if needed EMC
support is involved by logging ticket with them. Few cases with brief
description is included in the document.

Page 3
 Backup Policy Process Number: Designer: Date:
Siddhartha
Patwardhan
CUSTOMER Reviewer: Date:

Process Owner: Ver #: Ver Date Approver: Date:

SAN Team 1.2

I. Backup Process using EMC Networker

1. Application Name – CRM

Schedule
What is backed up
Sun Mon Tue Wed Thurs Fri Sat Time
CRM Database                
/
app/oracle/admin/scripts/r
manbak_in1.sh (alonsum1) INC INC INC INC INC INC SKIP 2:00
/
app/oracle/admin/scripts/r
manbak_wf.sh(alonsum1) SKIP SKIP SKIP SKIP SKIP SKIP FULL 2:00
/
app/oracle/admin/scripts/r
manbak_arc.sh(alonsum1) FULL INC INC INC INC INC INC 1:30
CRM Application                
/crmgtw (crmgtw cluster) INC INC INC INC INC INC FULL 23:30
/siebelfs (siebelapp “) INC INC INC INC INC INC FULL 23:30
                 
CRM Filesystem                
alonwin1 (CRM front end) INC INC INC INC INC INC FULL 23:00
alonwin2 (CRM front end) INC INC INC INC INC INC FULL 23:00
alonwin3 (CRM front end) INC INC INC INC INC INC FULL 23:00
alonwin4 (CRM front end) INC INC INC INC INC INC FULL 21:30
alonmon1 (CRM front end) INC INC INC INC INC INC FULL 2:30
alonmon2 (CRM front end) INC FULL INC INC INC INC INC 3:30

INC : Incremental Backup

FULL : Full Backup

PS : The databases mentioned in table are scripts for Oracle backup. Full backup,
Incremental backup and Archive backup of Oracle have different scripts. Hence
Full backup is run only once for full backup script and skipped other days.
Incremental is skipped on the day of full backup and Archive Logs backup has to
be run Full once a week and incremental on rest of the days
alonsum1 & alonsum2 are Oracle RAC. Backup can be taken by any of 2 nodes.

Page 4
 Backup Policy Process Number: Designer: Date:
Siddhartha
Patwardhan
CUSTOMER Reviewer: Date:

Process Owner: Ver #: Ver Date Approver: Date:

SAN Team 1.2

II. Glossary

INC Incremental Backup

FULL Full Backup
VTL Virtual Tape Library
TIME Start time of the backup

Page 5