DRserversap

8/6/2019 DRserversap

1/20

Disaster Recovery/Site Recovery Management Solution

Disaster recovery solution

using virtualization technology

THE DISASTER RECOVERY PROJECT IIAT SAP CO-INNOVATION LAB TOKYO


2/20


3/20

contents

4 Disaster Recovery Solution forSAP ERP, and at a Lower Cost

4 Importance o DR (DisasterRecovery) measures to ensurebusiness continuity

4 DR solution or backbone

systems using virtualizationtechnology

4 Joint demonstration tests bysix companies atSAP Co-Innovation Lab Tokyo

5 Key elements o the testenvironment

6 Veriication scenario

7 Establishing the ServerEnvironment

7 Server + VM (Virtual Machine)

environment 8 Intel Xeon 5500 seriesprocessor

9 Dramatic evolution improvesvirtual environment perormance

10 Establishing the StorageEnvironment

10 Replication using NetAppSnapManager or MicrosotSQL Server

11 Setting the transer interval,taking veriication into

consideration11 Controlling the storage

environment rom the serverside

11 Perormance in an FCoEenvironment veriied

12 Advanced architecture oNetApp

13 Establishing the NetworkEnvironment

13 Cost reduction by FCoEprotocol

13 Connections to the server andstorage

14 WAAS, the WAN accelerationsolution

14 Using WAAS to achieveeective use o bandwidth

15 Key points or establishing anetwork environment

16 Disaster Recovery in a VirtualEnvironment

16 Failover in a virtual environment16 Mock disaster response, to

test recovery plans as oten as

desired17 Major unctions o the SiteRecovery Manager

18 Disaster Recovery PotentialUsing VirtualizationTechnology

18 DR measures using virtualiza-tion technology that beneitsrom an advanced technologicalenvironment

18 Eective use o the DR site:Improving the value o IT assets


4/20

Disaster recovery solution

for saP erP, anD at a lower cost

SIX COMPANIES PERFORM JOINT DEMONSTRATIONTESTS AT SAP CO-INNOVATION LAB TOKYO

Importance of DR (DisasterRecovery) measures to ensurebusiness continuity

Today, IT systems play a critical role inalmost all companies. System malunc-

tions caused by natural disasters suchas earthquakes and typhoons, orhuman-caused disasters such asterrorism and hacking, may lead toimmeasurable damage to business op-erations. Japan is an earthquake-pronecountry, so maintaining the integrity oIT systems is vital in ensuring thesuccess o any BCP (Business Conti-nuity Plan). Eective DR (DisasterRecovery) capacity is increasingly acompliance issue as well.

Normally, DR solutions involve install-ing the same hardware environment ata remote DR site as that used by thesystem at the operation site, synchro-nizing data by replication. This kind osolution is typically expensive. On theother hand, inexpensive solutions stillhave a disadvantage: they requirecomplicated operations and diicultchangeover procedures ater adisaster.

The operation o a backbone system,which should be one o a companysmost important IT assets, may serious-ly impact on the entire businessprocesses o the company. As a result,many companies hesitate to adopt aDR solution.

DR solution for backbone systemsusing virtualization technology

DR solutions using virtualization tech-nology are now attracting attention asan option to solve these issues.

Virtualization technology can reducethe number o physical servers, and isalso eective or DR solutions requiredor a backbone system. The technologylets users obtain virtual images at theoperation site regularly, and replicatethose images at the DR site, reproduc-ing the operation site environment.Virtualization technology releasesusers rom the need to maintain hard-ware with the same physical environ-ments at both the operation site and

the DR sites. In other words, users areable to create a lexible systemenvironment at a lower cost.

Joint demonstration testsby six companiesat SAP Co-Innovation Lab Tokyo

In July 2008, SAP Japan establishedSAP Co-Innovation Lab Tokyo in

collaboration with its partners andcustomers, to carry out collaborativeresearch and develop various solutionsor the Japanese market. In Septembero the same year, SAP Japan, VMwareInc, NetApp K.K. and Intel Corporationsuccessully carried out Phase I odemonstration tests o the DR Solu-tion, using virtualization technology.

During the subsequent Phase II o theDisaster Recovery Project, demonstra-

tion tests using up-to-date technologywere carried out jointly by six compa-nies, with Cisco Systems (a network

1. Minimizing investment costs byintegrating disaster recovery plat-orms through virtualization.

2. Establishing a disaster recoveryplatorm using VMwares DR

solution and NetApps storagetechnology. Achieving seamlesschangeover in case o a disaster,including reliable data protectionand tests/rehearsals.

3. Improving the perormance o vir-tual environments using serverswith Intel Xeon 5500 seriesprocessors

4. Allowing the seamless transitionsacross dierent IA platorms byIntel Virtualization Technology.

5. Establishing a network platormwith the latest communicationprotocol, FCoE (Fibre Channelover Ethernet), to ensure a simplesystem environment with integrat-

ed I/O.6. Speeding up replication or the DR

site, using Ciscos WAN optimiza-tion solution.

7. Examining a scenario under whichthe disaster recovery platorm iseectively used during normaloperations, without lowering oper-ation site perormance throughapplication o disaster recoverymeasures.

Key points of the Disaster Recovery Phase II Project ofSAP Co-Innovation Lab Tokyo

4


5/20

vendor) and Zacatii Consulting (a com-pany with broad experience in DRsolutions) as new participants. Phase IIo the project builds on the success oPhase I, by separating the operationand DR sites. During Phase I the DR

solutions or SAP ERP were locatedhypothetically in the same laboratory,using VMwares virtualization techno-

logy, NetApps storage technology andIntels server platorm.

Key elementsof the test environment

Continuing rom Phase I, which veriiedthat transactions at the operation sitewere correctly relected in the DR site

in a hypothetical environment, the ol-lowing test environment was designedor Phase II (See Figure 1), based onZacatii Consultings experience andtaking actual business purposes intoconsideration;

At the operation site, two IA (IntelArchitecture based) servers running

Operation site (Tokyo) DR site (Osaka)

CiscoNexus5020

CiscoNexus5020

CiscoMDS9222i

CiscoMDS9222i

IA Server(Intel Xeon5500 series)



NetAppFAS3170

NetAppFAS3040

CiscoCatalyst3750E

VC +SRM

VC +SRM

CiscoCatalyst3750E

RouterWAAS

RouterWAAS

1GE 1GEWAN

FC 4G FC 4G

10GbE 10GbE

FCoEFC 4G FC 4G

FCoE

10GE 10GE

Application environment

SAP ERP on SQL Server 2005

Server environment

Tokyo

IAServer(IntelXeon5500series)IAServer(IntelXeon5300series)

Osaka

IAServer(IntelXeon5500series)

Storage environment

NetAppFAS3170(Tokyo) NetApp FAS3040 (Osaka)

NetAppSnapManager or Microsot SQL Server 5.0

NetAppSnapDriveforWindows6.0.1SnapMirror

Virtual environment

VMwareESX3.5Update4&Update3

VMwarevCenterSiteRecoveryManager 1.0 Update 1

VMwarevCenterServer2.5

Network environment

CiscoNexus5020DataCenterSwitchCiscoCatalyst3750EL2/L3SwitchCiscoMDS9222iFCSwitchCiscoWAE-7371

(WAAS:Wide Area Application Services)

OS

Microsot Windows Server 2003 (x64)

Figure 1: Configuration of verification environment

5


6/20

VMware ESX are installed, to complywith the assumption that more thanone system is running. At the DRsite, virtual machines are integratedinto one IA server to minimize costand achieve an environment assum-

ing a many-to-one serverconiguration.

At the operation site, an Intel Xeon5500 series processor-based server,designed or improved virtualizationperormance, and a server based onolder generation Intel Xeon 5300series processors, were used. At theDR site, an Intel Xeon 5500 seriesprocessor-based server was installedto veriy that the data could be syn-

chronized and that business could becontinued in the environment with di-erent mixed platorms.

Synchronization was carried outsimultaneously at the operation andDR sites, using NetApps storagetechnology. It was conirmed that thealigned data was transerred withoutinterrupting the system.

A simple network environment wasestablished by integrating FC (Fibre

Channel) and Ethernet networksbetween the server and the storagesystem using the latest FCoE (FibreChannel over Ethernet) networkprotocol.

Packets were compressed using theWAN acceleration solution WAAS(Wide Area Application Services), byCisco Systems WAE-7371, toimprove data transer perormance.

The operation site was located inTokyo and the DR site in Osaka,500km away. The sites were con-nected by a VPN, which providescost beneits.

Verification scenario

During Phase II o the project, veriica-tion o the technologies supplied byeach partner and conirmation o theresults o the entire project were con-

ducted based on the design and verii-cation scenario o Zacatii Consulting.

RPO1 and RTO2

RPO (Recovery Point Objective) wasveriied or 2 to 3 hours, and RTO (Re-covery Time Objective) was veriied or2 to 4 hours. RPO and RTO are bothimportant indicators o the degree obusiness continuity. Targeted compa-nies are middle-sized or larger compa-nies, including retail businesses and ECbusinesses o small-sized companies

that require a shorter RPO and RTO.

ReplicationData was replicated using NetAppsstorage management sotwareNetApp SnapManager or MicrosotSQL Server and data replicationsotware SnapMirror every 60 min-

utes, to synchronize with the DR sitewhile processing 5,000 to 10,000transactions/hour with two virtualmachines or ERP (host servers usingIntel Xeon 5500 series processorsand Intel Xeon 5300 series proces-sors) at the operation site.

Business restart after a disaster(Failover)VMwares VMware vCenter SiteRecovery Manager (SRM), which man-

ages and automates DR, is activated ithe system at the operation site isstopped during the transaction. Thetests conirmed normal operations oSAP ERP on the virtual machine at theDR site, and the correct relection otransaction data o SAP ERP until theend o the synchronization.

1. RPO: An indicator that represents the timing or requency o capturing backup data. Used in backing up and restoring operation veriications during thedisaster recovery process.

2. RTO: An indicator that represents the time required or recovery o an inormation system, rom the moment a disruption is caused by a system ailure ordisaster, until restoration to an agreed-upon service level. Used in BCP or DR operation veriication.

6


7/20

Server + VM (Virtual Machine)environment

The server conigurations at the opera-tion site (in Tokyo) and the DR site (inOsaka) are as described below (See

Figure 2). It was assumed that the twophysical servers at the operation siteand one physical server at the DR sitewere all running beore the new envi-ronment was established. The scenariocalled or the addition o a server withIntels latest processor platorm at boththe operation site and DR site, therebyestablishing a new DR site using thevirtualization technology. It was veriiedthat a lexible DR site could be estab-lished with dierent server

environments.

Operation siteThree physical servers were installed atthe operation site. Two o them haveVMware ESX installed, and the otherhas VMware vCenter Server (vCenterServer) and VMware vCenter Site Re-

covery Manager (SRM) installed tomanage the virtual environment in anintegrated manner.

The virtual machines or ERP (ERP#1)and or the other applications (AD#1)were installed on a high-spec serverwith the latest Intel Xeon 5500 seriesprocessor.

The other server has an older genera-tion Intel Xeon 5300 series processorto permit continuous use rom theexisting environment. On that server,the virtual machine or ERP (ERP#2)was installed.

DR siteTwo physical servers were installed atthe DR site. One o them is or the VC+ SRM server, the other is a high-specserver with an Intel Xeon 5500 seriesprocessor and VMware ESX. The serv-ers integrate the three virtual machines(ERP#1, ERP#2 and AD#1) managedby VMware ESX at the operation siteinto one host machine at the DR site.

establishing the server environment

LATEST SERVER PLATFORM SUPPORTSA STRONG VIRTUAL ENVIRONMENT

Operation site DR site

VC + SRM

Windows

VC + SRM

Windows

VMware ESX1 VMware ESX2 VMware ESX3

AD

#2

Windows

ERP#1

Windows

ERP#2

Windows

AD replication

Storage replication (SnapMirror)

VM

VM

ERP#1

Windows

ERP#2

Windows

AD

#1

Windows

Figure 2: Server + VM environment

AD: Microsot Active Directory

7


8/20

Synchronization methodAD#1 in a virtual machine automaticallytransers the changes to others by Ac-tive Directory Replication Technologies.The virtual machines or ERP (ERP#1and ERP#2) synchronize data using

NetApps storage unction (SnapMirrorand SnapManager or Microsot SQLServer).

Intel Xeon 5500 series processor

The processor or the server releasedby Intel in March 2009, the Intel Xeon5500 series processor, was used atthe operation and DR sites or the

demonstration tests. It was veriied thatthey achieved more eective disasterrecovery in the VMware virtualenvironment.

The Intel Xeon 5500 series processoris a completely revamped microarchi-tectural version developed rom theormer Intel Core Micro Architecture.The new version represents the core

design technology o the processor,and eatures next-generation micro-architecture code-named Nehalem.The Intel Xeon 5500 series processorhas our cores and supports the dualsocket platorm. The ormer FSB (ront-

side bus) was replaced with the asterQPI (QuickPath Interconnect) to con-nect the processor with the chipsets. Itaccesses memory directly and morequickly by using the memory controllerembedded in the processor.

In addition, the processor has IntelIntelligent Power Technology to reducethe power consumption o the core

0

5

10

15

20

25

Figure 3: Results of VMmark benchmarkFor details on the test environment, please visit www.vmware.com/products/vmmark/results.html.

Intel Xeon 5400series processor(Operating frequency:3.16 GHz)

Intel Xeon 5500series processor(Operating frequency:2.93 GHz)

Figure 4: Virtualization performance test for SAP ERPFor details, please visit http://download.intel.com/business/software/testimonials/downloads/xeon5500/sap_virtualization.pdf

Intel Xeon 5300series processor

DellPowerEdge2950IIIVMwareESXv3.5.0

VMmark v1.08.47@6tiles2sockets8cores8threads

Intel Xeon 5500series processor

DellPowerEdgeR710VMwareESXv4.0

VMmark v1.123.55@16tiles2sockets8cores16threads

8
http://www.vmware.com/products/vmmark/results.htmlhttp://www.vmware.com/products/vmmark/results.htmlhttp://download.intel.com/business/software/testimonials/downloads/xeon5500/sap_virtualization.pdfhttp://download.intel.com/business/software/testimonials/downloads/xeon5500/sap_virtualization.pdfhttp://download.intel.com/business/software/testimonials/downloads/xeon5500/sap_virtualization.pdfhttp://download.intel.com/business/software/testimonials/downloads/xeon5500/sap_virtualization.pdfhttp://www.vmware.com/products/vmmark/results.htmlhttp://www.vmware.com/products/vmmark/results.html


9/20


10/20

establishing the storage environment

TRANSFERRING THE VIRTUAL ERP MACHINE DATATO THE DR SITE EVERY 60 MINUTES

Replication using NetAppSnapManager for Microsoft SQLServer

The LUN (Logical Unit Number) in thestorage has the structure described

below. When NetApps storagemanagement sotware (NetApp SnapManager or Microsot SQL Server) isimplemented, the local backup unctiono the storage, Snapshot, creates abackup image o the virtual machinedata using very little data, and the repli-cation tool SnapMirror transers the

data to the DR site. At the DR site,the dierential backup system o thestorage saves the backup data or theprevious seven sessions. The methodand scheduling or synchronizing withthe DR site depends on the eature o

the LUN as described below (See Fig-ure 5).

OS area and system areaThe data in the OS area and systemarea are not changed except when thesystem is updated or a security patchis applied. Thereore, SAP ERP and

SQL servers are stopped to replicatedata or the DR site only when anychanges are made to the system.

UserData areaThe logs and databases in the

UserData area are replicated to the DRsite online using SnapManager orMicrosot SQL Server. A command isperormed every 60 minutes to transerthe backup data to the DR site.

Operation site

DR site

VM

VM

OS area

VMFS

OS

OS area

VMFS

OS

VMFS

OS

System area

RDM

EXEC

System area

RDM

EXEC

RDM

EXEC

UserData area

RDM RDM

Tran-Log Database

UserData area

RDM RDM

Tran-Log Database

RDM RDM

Tran-Log Database

SnapManagerfor SQL

SnapMirror SnapMirror

Snapshot Snapshot

SnapManager for SQL

Figure 5: Storage configuration and synchronization method

10


11/20

Setting the transfer interval,taking verificationinto consideration

Ater transerring data to the DR siteby SnapMirror, it is required to veriy

whether the data saved on the disc hasno errors and conorms to the appropri-ate standards. In the demonstrationtests, the interval between backup datatransers was set at a relatively shortperiod o 60 minutes, and veriicationprocedures were omitted. In the actualoperation environment, the intervalbetween transers should be deter-mined taking a possible longer veriica-tion time into consideration, due to thestorage coniguration and data

eatures.

Controlling the storageenvironment from the server side

SnapManger or Microsot SQL Serveris used together with SnapDrive orWindows, a tool or automating storagemanagement. Snap-Manager orMicrosot SQL Server is a datamanagement tool specializing in backupand recovery together with SQL Serv-er, and a kind o command center o

SnapDrive or Windows. It acquiressnapshots, creates clones, and re-stores backup data using SnapDrive orWindows unctions.

The special unction o SnapManageror Microsot SQL Server is to controlthe storage environment rom theserver side. Virtualization o the serverrenders the storage/server boundaryunclear. SnapManager or MicrosotSQL server enables users to carry out

backup on the server side something

that previously could be carried outonly on the storage side and allowsthe server or database administrator touse storage unctions such as backingup and restoring without any proes-

sional knowledge. Thereore, in anactual operation situation, the server ordatabase administrator is expected tobackup or restore data.

Performance in an FCoEenvironment verified

SnapDrive or Windows supports FCand iSCSI as a standard. In this conig-uration, the FCoE connection was alsotested. The storage (NetApp FAS

series) was tested while operating the

application in an environment where itwas connected with the data centerclass switch NEXUS 5020, using FCvia FC switch MDS 9222i. The serverwith an Intel Xeon 5500 series pro-

cessor was connected with Nexus5020, using FCoE. The result was note-worthy, because although many con-nection test results using only FCoEwere reported by vendors, ew tests atthe application level had been conduct-ed. It is also expected to reduce TCO(total cost o ownership) during thetransition period when changes aregradually made or the server to usethe FCoE connection, with the storageretaining the FC connection.

Figure 6: Overview of general data management solution supplied by NetApp

Storage infrastructure

Database SuiteDatabase collaborative management sotwareSnapManager for Microsoft SQL Server 5.0

Data ONTAPSingle architecture or multi protocols and purposes

Server Suite

Server collaborative management sotwareSnapDrive for Windows 6.0

General

m

anagement

software

Storage

software

functions

Shared storageresource pool

VirtualizationvolumeFlexVol

Data protectionSnapshot

SnapMirror

VirtualreproductionFlexClone

Enhancingstorage eiciency

Thin ProvisioningDe-dupe

FAS2000 FAS3000 FAS3100 FAS6000 V-series

Storage or multi protocolsCollaboration with storages

o other manuacturers

11


12/20

Advanced architecture of NetApp

SnapshotSnapshot, one o the basic DataONTAP unctions, acquires onlinebackup images during system opera-

tion. The most advantageous eaturesinclude its excellent space eiciency,no deteriorated writing perormance,and lexible operation per volume unit,which make it possible or the user toobtain backups very oten, and to sig-niicantly reduce recovery time.Snapshot obtains only metadata blocksat a certain point in time, rather thanmaking a physical copy o the entirevolume or backup. Thereore, it hasnone o the deteriorated perormance

that is seen in the Snapshot thatadopts the so-called copy-out method.Implementation can be conducted pervolume and the obtained Snapshot im-age is saved separately in the hiddendirectory in each volume. Acquisitionand recovery o Snapshot does notaect the other volumes, and operationrules or each volume can be deter-mined lexibly.

SnapMirrorSnapMirror is a backup unction apply-

ing Snapshot. It transers only changeddata blocks to the destination ater theirst 0 level transer (whole data trans-er o the targeted volume). One spe-cial eature o SnapMirror is that ittransers data as i a ull copy image oreach transer is being saved, eventhough only the dierential data istranserred ater the irst transer.

In this test, backup images or the pre-vious seven sessions were saved, butthe data used was not seven times theoriginal the images were saved usingmuch less data. In addition, SnapMirrorcan make rapid transers by LAN or

WAN, since it uses less network traicby transerring only the dierentialdata. For the data transer channel,users can use IP networks and also FCnetworks.

FlexCloneFlexClone instantly creates a clone othe disc volume within the storage. Itapplies Snapshot technology to make abackup only or dierential data blocks.It is able to instantly create a clone by

copying only logical data, without mak-ing a physical copy (thus, similar toSnapshots approach). In act, it cancreate a clone using only 10% o theoriginal amount o data when creating aclone, which means that the sameamount as that o the original is not re-quired or creating clones. Data copiedby FlexClone is readily available orreading and writing, while copied datacreated by Snapshot was or read only.This allows the user to conduct dier-ent kinds o tests using clones.

12


13/20

Cost reduction by FCoE protocol

One o the special eatures o the dem-onstration tests was the participation oCisco Systems, which made it possibleto establish a network platorm using

the latest network technology, FCoE(Fibre Channel over Ethernet). FCoE isa protocol to connect interaces withFC and Ethernet connections, or whichstandardization is promoted. It does notrequire separate inrastructures orLAN and SAN, and integrates I/O. The10Gbps connection makes a broad-band environment available.

The reason or using FCoE in the dem-onstration test was to handle the I/Otraic, which increases with virtualiza-tion. When a server is virtualized,multiple virtual machines run on onephysical server, so the traic amount

or each physical server is increased.As the number o virtual servers in-creases, LAN, SAN and server traicincreases, leading to more complicatedwiring and overloaded operations. Thedemonstration tests thereore exam-ined ways to reduce cables, switchesand interaces, by establishing a net-work environment using the FCoE pro-tocol. This would lead to less networkmanagement and lower costs, includingless power consumption (and thereore

greener IT operations).

Connections to the server andstorage

Each physical server is connected witha Cisco Nexus 5020 data center classswitch, using FCoE. The Cisco Nexus

5020 is connected with NetApps stor-age using FC via a Cisco MDS 9222iFC switch. The connection betweenthe switch and the storage was testedor multiplexing by virtualizing the SAN,using the VSAN (Virtual SAN) unctiono the Cisco MDS 9222i while main-taining its independency. A Cisco Cata-lyst 3750E was used or the Ethernetswitch, and connected with a CiscoNexus 5020 using 10GB Ethernet.Between the operation and DR sites,

the cost-eective option o a VPN wasused.

establishing the network environment

OPTIMAL I/O INTEGRATION FOR DRFOR THE SAP SYSTEM, AND OPTIMIZED WAN

NetAPPFAS

BenchmarkDriver

VC + SRM

CiscoCatalyst3750E

CiscoWAE-7371(WAAS)

Cisco MDS9222i

Cisco Nexus 5020

c1/17 c1/18

c2/1

Eth1/13

Eth2/1

Eth2/2

1GE 1GE 1GE 1GE

Eth1/14

c2/2

NetAPPFAS

VC + SRM

CiscoWAE-7371(WAAS)

Cisco MDS9222i

IA Server(CPU: Intel

Xeon 5500series,

CNA: EmulexLP21000M)


Xeon 5300series,



Xeon 5500series,


Cisco Nexus 5020

c2/1

Eth1/13

c2/2

VPNRouter

VPNRouter

WAN

FCoE

10GB

1GB

FC 4G

Figure 7: Network environment

CiscoCatalyst3750E

13


14/20

WAAS, the WAN accelerationsolution

In the demonstration tests, CiscoSystems WAN acceleration solutioncalled WAAS was used to enhance the

eiciency o transerring data betweenthe sites. WAAS technology is used toachieve the same perormance as aLAN, but on a WAN. The amount odata to be sent to the WAN is reducedby combining DRE (Data RedundancyElimination), which optimizes bandwidthon WANs based on data redundancyand data compression. In addition,WAN throughput is improved by TFO(Transport Flow Optimization), whichoptimizes TCP traic. Delays are re-

duced to achieve eective use o band-width, using technologies such as look-ahead, alternative protocol andcaching.

Using WAAS to achieve effective

use of bandwidth

According to the Network Traic Sum-mary Report or WAAS, perormancemeasured in the test environment re-sulted in 4.92 times greater eectivecapacity in Osaka, and 5.64 timesgreater in Tokyo. The bandwidth usagerate was over 80% at both sites, prov-ing that bandwidth was used moreeectively than beore adopting WAAS(See Figure 8).

Storage replication is also accelerated.Beore adopting WAAS, the through-puts to send SAP ERP data rom theoperation site to the DR site were60.04 (KB/sec) and 61.82 (KB/sec) orthe data area, and 101.84 (KB/sec) or

the log data. Ater adopting WAAS,they were 228.20 (KB/sec), 219.26(KB/sec) and 248.45 (KB/sec) 2 to3.5 times aster (See Figure 9).

Figure 8: Results of Network Traffic Summary ReportAccording to the Network Traffic Summary Report for WAAS, effective capacity was 4.92 timesgreater in Osaka and 5.46 times greater in Tokyo. The bandwidth is used more efficiently,

with a usage rate of more than 80% at both sites.

14


15/20

Key points for establishing anetwork environment

The demonstration tests show thatenvironments where switches andadapters were previously needed or

both LAN and SAN can be integratedby establishing a connection rom theserver and the storage to FCoE, withNIC and HBA being consolidated withCNA (Converged Network Adapter).Management eiciency can also beimproved by using VLAN and VSAN invirtualization. Furthermore, the 10Gbps environment permits the develop-ment o the virtual environment andimproves the perormance o VMwareVMotion and SRM.

In addition, it was proven that eveninexpensive WAN connections canachieve satisactory perormancethrough the use o WAAS. In act,a very cost-eective environment cannow be established or DR strategies,

which were previously ignored becauseo ormerly high running costs and thecost-boosting distance between thesites.

Figure 9: Results of tests for improved throughput by WAASBy adopting WAAS, the time required for replicating the storage was2 to 3.5 times shorter for both data and log areas

0

50

100

150

200

250

KB/sec

Beore adopting WAAS

Ater adopting WAAS

Data area 1

60.04

228.20

Data area 2

61.82

219.26

Log

101.84

248.45

Storage area

15


16/20

Disaster recovery

in a virtual environment

VMware vCenter Site Recovery Manager (SRM)AUTOMATES DISASTER RECOVERY

Failover in a virtual environment

I the system must be shut down due toany disaster at the operation site, thesystem should be ailovered at therecovery site to restart business opera-

tions immediately. However, this is verydiicult to do in conventional DR envi-ronments, because the server must beconnected with an external storagedevice or the recovery process mustbe carried out manually by an adminis-trator. There are many cases where therecovery process remains untested,since much time and work are requiredto prepare an updated DR plan to meetthe daily demands o a changing sys-tem environment.

To resolve these issues, VMwarevCenter Site Recovery Manager (here-inater SRM), which automates disasterrecovery in a virtual environment, wasused in the demonstration tests to veri-y both the seamless connection withthe storage and the automation o therecovery process. SRM is a newsolution released in June 2008. Thedemonstration tests were an excellentopportunity to test SRMs perormancein a remote environment.

In the demonstration tests, a server orSRM was installed at both the opera-tion site and the recovery site, so thati the operation site ailed a virtualmachine with the same conigurationcould take over at the recovery site.The data accessed by the virtualmachine at the recovery site uses thebackup volume replicated by NetAppsSnapMirror. The test was automaticallystarted by pressing the recovery button

o the SRM on the vCenter Server, and

proper restoration was veriied. SRMworks with NetApps storage whenthe SRMs DR plan is implemented,SnapMirror is stopped automaticallyand the SRM starts the virtual machineautomatically by calling up the data

rom the recovery volume, according tothe recovery plan prepared in advance.

The results show that a ast and eec-tive ailover can be successullycarried out under various environmentswith a dierent number o servers atthe operation site and recovery site.RTO was about 1 hour, much less thanthe targeted time o 2 hours. This testwas implemented in an environmentwith a minimum number o virtual

machines (two physical servers at theoperation site and one at the recoverysite). The greater the number o serv-ers installed, the greater the beneitsrom automation. Thereore, SRM maybe one o the most optimal solutions inenvironments where rapid disasterrecovery is required.

Mock disaster response, to testrecovery plans as often as desired

SRM includes a unction to conductdrills to test the entire recovery pro-cess. Using the Snapshot unction o

the storage, users can conduct drills asrequently as they want by connectingthe virtual machine to an isolated testnetwork without interrupting the actualenvironment. Conventional DR systemsinvolve a complicated process to carryout recovery tests, and sometimes im-pact negatively on actual business op-erations. With such a conventionalsystem, many companies do not haveenough time to carry out recoverytests, and avoid them because o the

associated business risk. In somecases, additions or changes are madeto the system ater recovery test com-plications, making managers reluctantto conduct another recovery test. SRMlets users conduct automatic testsusing the recovery plan at any timewithout interrupting on-site operations,

Recovery site

VMware Infrastructure

vCenter ServerSite Recovery

Manager

Virtual machine

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

Server

Operation site

VMware Infrastructure

vCenter ServerSite Recovery

Manager

Virtual machine

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

VC +SRM

Windows

Server ServerServer

Figure 10: VMware vCenter Site Recovery Manager concept

16


17/20

while maintaining a highly reliable re-covery environment.

In the demonstration tests, a clonevolume o the recovery data saved inthe DR storage system was created

instantly, using NetApps FlexClone.The recovery plan and the test scenariowere implemented in separate testenvironments. Ater completion o thetest, the test environment was com-pletely restored to original pre-testconditions. The test results were savedin the vCenter Server, allowing or easyveriication.

Major functions of the SiteRecovery Manager

Automated failover Running the recovery plan with a

single touch o a button using theVCenter Server

Automatically replicating data storeor recovery

Implementing or stopping a user-deined script during the recoveryprocess

Reconiguring the IP address o the

virtual machine to match the networkconiguration o the ailover site

Managing and monitoring theimplementation o the recovery planusing the vCenter Server

Achieving test with no downtime Conducting recovery tests using the

SnapShot unction o the storagedevice, without aecting data to bereplicated

Connecting the virtual machine with a

separate network or testingpurposes Automatically conducting tests o the

recovery plan

Customizing recovery plan implemen-tation, in accordance with the testscenario

Cleaning up the test environmentautomatically ater test completion

Disaster recovery management Detecting and displaying the virtual

machine to be protected using thereplication unction o the storagedevice

Creating and managing the recoveryplan directly rom the vCenter Server

Saving, displaying and exporting testresults and ailover implementationresults rom the vCenter Server

Figure 11: Button to run the recovery plan Figure 12: Screen to run the recovery plan

17


18/20

Disaster recovery Potential using

virtualization technology

TARGETING EFFECTIVE USE OF THE DR SITE

DR measures using virtualizationtechnology that benefits froman advanced technologicalenvironment

Many results were obtained rom this

project, proving that virtualization tech-nology is eective or DR measuresapplied to an SAP ERP system. DRmeasures using virtualization providegreat beneits during operation, includ-ing quick recovery in case o a disaster,and the ability to conduct mock disas-ter drills while operations at the actualsite continue running. These variousadvantages contribute to the reductiono TCO.

These positive results are certainlyoptions or SAP users who need toensure both business continuity and di-saster recovery, and who havedepended on the reliability o a less e-icient physical environment toimplement DR measures, or who havepostponed the adoption o the DRsolutions because o the cost. Virtual-ization can also be applied to ERP in anSaaS environment promoted by SAP,and in establishing a private cloudenvironment achieved by advances in

virtualization technology. Virtualizationtechnology is also developing at theoperational level, taking actual businessneeds into consideration.

Effective use of the DR site:Improving the value of IT assets

Future challenges or our researchinclude inding ways to eectively usethe DR site as part o daily business

operations. Ater all, it is especiallydiicult or small and medium-sizedcompanies to obtain a return on invest-ment when installing IT assets thatwould only be used or disaster recov-ery measures.

In this respect, SAP Co-Innovation LabTokyo is studying a detailed scenario inwhich a DR site could also be usedeectively during daily business opera-tions. For example, it may be possible

to establish a development or test envi-ronment using data replicated to theDR site, without stopping synchroniza-

tion rom the operation site, or to useas a test instance employing the actualbusiness data by creating a replicationby FlexClone only o the data volume oSQL Server out o the synchronizedvolume and attaching it to another SAP

instance. SAP Co-Innovation Lab Tokyowill continue to conduct demonstrationtests to examine issues springing romthe needs o a variety o companies.

Our recent demonstration tests cov-ered the process until ailover at theDR site, and did not test ailback to theoperation site. In the uture, the Lab willtest environments that are more realis-tic rom a business perspective, takinginto consideration ailback procedures

that also include overseas sites.

1. A low-cost disaster recoveryplatorm can be established byvirtualization

2. Smooth ailover using VMwaresDR solution and NetApps storage

technology was achieved3. An Intel Xeon 5500 series

processor improves perormancein a virtual environment

4. I/O is integrated through FCoE5. Speeding up replication or the DR

site, using Ciscos WAN optimiza-tion solution.

6. A DR site can be established even

with an inexpensive WAN, usingthe WAAS WAN optimizationsolution

Benefits Proven by Phase II of the Disaster Recovery Projectof SAP Co-Innovation Lab Tokyo

18


19/20


20/20

50xxx xxx (YY/MM)20YY by SAP AG.All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP Business ByDesign, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks orregistered trademarks o SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects,Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and otherBusiness Objects products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks oBusiness Objects S.A. in the United States and in other countries.Business Objects is an SAP company.

All other product and ser vice names mentioned are the trademarks o theirrespective companies. Data contained in this document ser ves inormationalpurposes only. National product specications may vary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its afliated companies (SAP Group) or

normational purposes only, without representation or warranty o any kind,and SAP Group shall not be liable or errors or omissions with respect to

the materials. The only warranties or SAP Group products and services arethose that are set orth in the express warranty statements accompanyingsuch products and services, i any. Nothing herein should be construed asconstituting an additional warranty.

www.sap.com/contactsap

2009 by SAP AG.All rights reser ved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP Business ByDesign, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or regis-tered trademarks o SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, CrystalReports, Crystal Decisions, Web Intelligence, Xcelsius, and other BusinessObjects products and services mentioned herein as well as their respectiveogos are trademarks or registered trademarks o Business Objects S.A.n the United States and in other countries. Business Objects is an SAPcompany.

All other product and service names mentioned are the trademarks o their

respective companies. Data contained in this document serves inormationalpurposes only. National product specications may vary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its afliated companies (SAP Group) ornormational purposes only, without representation or warranty o any kind,and SAP Group shall not be liable or errors or omissions with respect tothe materials. The only warranties or SAP Group products and services arethose that are set orth in the express warranty statements accompanyingsuch products and services, i any. Nothing herein should be construed asconstituting an additional warranty.

DRserversap

Documents

Transcript of DRserversap