Backup Policy

(1 week Cycle)

SAP System ID

IPP

SAP Component SAP ERP

Release

ERP 6.0 EHP4 701 KER

DB System

ORACLE 10.2.0.4

Customer

Incepta Pharmaceuticals Limited,

40, Tejgaon I/A, Dhaka, Bangladesh.

Implementation
Partner
Telephone
Fax

Zensar Technologies, Hyderabad

Prepared by

Jagan Mohan. S

+91 40 40230000
+91 40 40230333

Doc Version
No.
Doc Creation
Date
Installation
No.

Approved by

SAP
Customer No.

18/08/2010
0020399609
0000737402

ZensarOBT Technologies, 2010

This document contains proprietary information of Zensar Technologies. No part of this document may be
reproduced, stored, copied, or transmitted in any form or by means electronic, mechanical, photocopying or
otherwise, without the express consent of Zensar Technologies

2010 Zensar Technologies

Page 1 of 7

Project Number: SAP-2010-246

Backup Policy
(1 week Cycle)

Backup Policy

Hostname

Sat

Sun

Mon

Tue

Wed

Thu

Fri

Fortnight

IPPProductio
n Server

DB online
+
Day End
Archive
Log
(separate
Tape)

DB online
+
Day End
Archive
Log
(separate
Tape)

DB online
+
Day End
Archive
Log
(separate
Tape)

DB online
+
Day End
Archive
Log
(separate
Tape)

DB online
+
Day End
Archive
Log
(separate
Tape)

DB online
+
Day End
Archive
Log
(separate
Tape)

DB offline
+
Day End
Archive Log
(over write
after
15days)

OS Backup
(fortnight separate
Tape)

IPDDevelopm
ent server

DB Offline

IPTQuality
Server

DB Offline

OS Backup

IPSSolution
Manager

DB Offline

OS Backup

2010 Zensar Technologies

OS Backup

Page 2 of 7

Project Number: SAP-2010-246

Backup Policy
(1 week Cycle)

Options considered for Backup (Production):

Day End Archive Log:

1 week (6 Days)
Total Tapes required 6 Nos
The first LTO will be overwritten only after 7th day

Database

1 week (7 Days)
Total Tapes required 8 Nos (Fridays Offline Backup)
The first LTO will be overwritten only after 7th day

OS Backup:

Every alternate week end (Friday)

Total Tapes required 2 Nos

Backup of T & D

Every Friday ----- 4 Nos

OS Backup:

Every alternate week end (Friday)

Total Tapes required 4 Nos

Backup of Solution
Manager

Every Friday ----- 2 Nos

OS Backup

Every alternate week end (Friday)

Total Tapes required 2 Nos

Note:

An Offline Backup is taken after shutting down SAP

An Online Backup is taken while SAP is Running
Archive log backup is taken while SAP is Running

SAP Strongly recommends using a Backup cycle of at least 4 weeks

The more backups are available in case of recovery, the better we
are protected against physical tape errors and logical database errors

Recommended:

2010 Zensar Technologies

Page 3 of 7

Project Number: SAP-2010-246

Backup Policy
(1 week Cycle)

For a Database Recovery, use the same software / tools that used for
Backup
Ensure Spare Backup Media is available for any emergency

Responsibility & Media Required

Production Server
Online Backup
Offline Backup
Day End Archive Log
OS Backup
Dev & Test Server
Offline
OS Backup
Solution Manager
Offline
OS Backup
Spare tapes
Total No of Media Required

Qty
6
2
6
2

Responsibility
Incepta
Incepta
Incepta
Incepta

4
4

Incepta
Incepta

2
2
7
35

Incepta
Incepta

Disaster recovery scenarios with Adopting Backup Policy:

Everyday midnight 23:59hrs Database Online Backup will be scheduled on Production

Server.
At the end of Online Database Backup Day End Offline Archive Log Backup will be
scheduled. This backup will backup all the archive log files and will delete the files from
the disk
In the event of Database crash or corruption, and there is no Disk Corruption (offline
redo log files), Data can be recovered till the last Offline Archive log available on the Disk.
(Previous day online backup + Day end Archive log backup + Archive log available on
disk)
In the event of Database crash or corruption along with Disk corruption (offline redo log
files), data can be recovered till the last Offline Archive log backed up to the tape in (DB
Online + Day end Archive log backup)

Example:

Assuming Backup media is good, Database online Backup completed successfully + Day
end Archive log Backup Completed successfully and hard disk is not crashed.
Database is crashed in the next day 14:00hrs after the backup.
Previous days online backup + Day end archive logs + available offline archive logs on the
disk

2010 Zensar Technologies

Page 4 of 7

Project Number: SAP-2010-246

Backup Policy
(1 week Cycle)

Approx data loss could be for the data for which the Offline Archive logs are not yet
generated to the disk.

2010 Zensar Technologies

Page 5 of 7

Project Number: SAP-2010-246

Backup Policy
(1 week Cycle)

Number Priority

Action
Deadline Person Responsible
Description

Issue
Type

Priorities: 1 (very high), 2 (high), 3 (medium), 4 (low).

DRAFT:
=====
Day End Redo log (Save and Delete)
Full Online Full Database

Full Offline Full Database

Important Notes
Note Number

Description

Note: All recommendations provided in this report are based on our experience only.
OS folders to be backedup on daily basis till golive and after golive weekly basis

Till gilive - Daily

/usr/sap/trans
/sapmnt/<SID>(eg. IPD,IPQ,IPP,IPS) Monthly
/usr/sap/<SID>(eg. IPD,IPQ,IPP,IPS) Monthly

2010 Zensar Technologies

Page 6 of 7

Project Number: SAP-2010-246

Backup Policy
(1 week Cycle)

After golive Weekly

/usr/sap/trans
/sapmnt/<SID>(eg. IPD,IPQ,IPP,IPS)
/usr/sap/<SID>/DVEBMGS(nn) (nn
10
20
30
50
/usr/sap/<SID>/SYS/gen
/usr/sap/<SID>/SYS/src

2010 Zensar Technologies

system number
Development
Quality
Production
Solution Manger)

Page 7 of 7

Project Number: SAP-2010-246