The document discusses various backup methodologies for SAP systems running on VMware ESX virtualization. It outlines 5 options: 1) network backup, 2) VCB scripted backup, 3) self-service backup via SAN RDM, 4) self-service backup via NAS, and 5) Powersnap. For each option, it highlights advantages and limitations, and considerations regarding off-site backup, predictable times, offloading resources, enabling system copies, and cost-effectiveness. It concludes that fitting functional requirements, organization, and least implementation time are key factors to consider.

1. SAP on ESX – Backup Methodology
M. Daniels
December 8th 2009

2. SAP on ESX: Backup Challenges
What is the impact for backup is SAP runs virtualized?
» Considerations:
» Off Site Backup
» Predictable backup and restore times
» Offloading CPU and network
» Enable homogeneous system copies
» Cost-effectiveness
» SAP DB Classifications:
» Small <250GB
» Medium >250GB < 1,5TB
» Huge >1,5TB
» Context
» A service provider with shared storage, backup, compute and SAP services.
2 MaartenDaniels@Gmail.com

3. Option 1 – Network Backup
High Lights Limitations Considerations
 BR Backup integrated with Networker or  Network Bandwidth  Off Site Backup
Commvault  Predictable backup and restore times
 CPU
 Offloading CPU and network
 Data transfer via network to back-up
server offsite  Enable homogeneous system copies
 Cost-effectiveness
 Small SAP Instances Data files and Redo
SAP DB
Backup
SAP AS
Client
OS OS
SAP DB SAP AS Off site
ESX
Virtual Machine
VMWARE
File Systems
Cost Drivers
 GB on Tape
 #Sap Instances
3 MaartenDaniels@Gmail.com

4. Option 2 – VCB Scripted Backup
High Lights Limitations Considerations
 BR Backup integrated with Networker or  Off Site Backup
Commvault via VCB.  Maintainability and ownership  Predictable backup and restore times
 Offloading CPU and network
 Customized and complex backup
scripting. (Ownership SAP admin) Redo Log (network)
 Enable homogeneous system copies
 Cost-effectiveness
 Shift in responsibilities (RACI) SAP DB
Backup
SAP AS
 Data transfer via SAN for datafiles Client
OS OS
 1 VCB Server per ESX farm. SAP DB SAP AS
ESX
Mount SAN Snapshot
SAP Backup script
VCB server
VMWARE SAN Backup Datafiles
VMFS Filesystem
Cost Drivers
 GB on Tape
 VCB Server
 Software

Off site 
Time for Script
#SAP Instances
4 MaartenDaniels@Gmail.com

5. Option 3 – Self Service Backup via SAN RDM
High Lights Limitations Considerations
 Simular to Oracle RAC with ASM  CPU Bottleneck on ESX  Off Site Backup
appraoch. Assigned datastore for  Predictable backup and restore times
datafiles and redo. DBA can organize  RDM limitations on ESX
 Offloading CPU and network
and is responsible.
 Enable homogeneous system copies
 Remote SAN storage (SOD – Storage BR Backup Tooling
 Cost-effectiveness
on Demand) via Raw Device Mapping Self Service
Backup
Restore
(RDM) SAP DB
Backup Backup SAP AS
Client Store
 Full control with BR-Backup OS OS
 Paradigm Shift
ESX
Storage via raw device mapping
 Data transfer via SAN for datafiles
Virtual Machine
VMWARE
File Systems
Off site
Cost Drivers
 SOD – AC GB’s
SOD –
Low Cost
SATA
SOD Business Class
5 MaartenDaniels@Gmail.com

6. Option 4 – Self Service Backup via NAS
High Lights Limitations Considerations
 Simular to Oracle RAC with ASM  CPU Bottleneck on ESX  Off Site Backup
appraoch. Assigned datastore for  Predictable backup and restore times
datafiles and redo. DBA can organize  RDM limitations on ESX
 Offloading CPU and network
and is responsible.
 Enable homogeneous system copies
 NAS storage NFS ( FileStorage On BR Backup Tooling  Cost-effectiveness
Demand - FSOD) Self Service
Backup
Restore
SAP DB
 Off-Site Copy using NDMP Volume Backup Backup Any other
SAP AS
Dumps Client Store VM
OS OS OS
 Full control for SAP with BR-Backup
NDMP SAN
ESX
FSOD via NFS
 Data transfer stays inside one bubble at
one location. Off site
Virtual Machine
VMWARE
 Paradigm Shift File Systems
FSOD
 Self Service enhancements with
snapshots, deduplication
Share
SnapShots.1.2.3.4.5.6.7
Cost Drivers
Self Service
ASIS Dedupe
Low Cost SATA
 GB on Tape
 NAS share can be exported to various  GB on SAN or NAS
VM’s for homogenious system copies SOD Business Class (dedup)
6 MaartenDaniels@Gmail.com

7. Option 5 – Powersnap
High Lights Limitations Considerations
 Over 1.x TB use this; don’t bother with  Complexity of Setup  Off Site Backup
VMWARE.  Predictable backup and restore times
 Offloading CPU and network
 Cerfitied on EMC and Networker
 Enable homogeneous system copies
 Always full Clone  Cost-effectiveness
 High End Solution.
Cost Drivers
 Servers to connect
 GB R1 / R2 BCV
 Servers to Backup
 GB on Tape
 CBS Powersnap
 CBS SAN Connection
7 MaartenDaniels@Gmail.com

8. SAP on ESX: Backup Challenges
» Fit to functional requirements
» Organisation
» Least time to implement
8 MaartenDaniels@Gmail.com

9. SAP on ESX: Backup Challenges
» Netwerk backup has limitation with regards to volume, duration and network
bottleneck.
» VCB backup is possible, requires custom scripting. Unclear on how to script it
application aware.
» Raw Device Mapping. (Identical to Oracle RAC setup with ASM). Pardigm Shift.
Homogeneous system copy to be validated.
» NAS self service infrastructure.
» Powersnap / SRDF; not for Virtualized environments.
» Other options: Use RAC database on dedicated hardware met SAN backup.
Challenge here is to share among customers and the required base load for to
leverage cost.
9 MaartenDaniels@Gmail.com

10. For more information please contact:
Maarten A. Daniels
maartendaniels@gmail.com
This presentation is shared on SlideShare for discussion purposes.