Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
promises. The definition of business continuity spans from toleration of hours of downtime<br />
during business hours to zero downtime, 24 hours a day, 365 days/year, which is a wide range<br />
that your organization needs to define.<br />
The foundation of an <strong>IBM</strong> zEnterprise solution to support business continuity is the Parallel<br />
Sysplex cluster. DB2 and z/OS support Parallel Sysplex. The software described in this<br />
section aids in building a continuous SAP service.<br />
z/OS software supporting an SAP high availability solution<br />
The basic System z solution is the introduction of a DB2 shared member on Parallel Sysplex.<br />
This cluster solution ensures that the SAP database service continues when a part of the<br />
cluster is down. <strong>IBM</strong> DB2 10 for z/OS is the major building block for this solution.<br />
One major point of failure is the SCS. For a highly available SAP system, the SCS must be<br />
able to replicate to a standby SCS instance. This Central Services Instance Replication is<br />
often called the replicated enqueue server. Because replication is an SAP SCS service,<br />
automation tools are needed to detect an outage of SCS and to switch over to the backup<br />
service, and if possible, inflight of a transaction. z/OS uses the following <strong>IBM</strong> software<br />
applications for automation:<br />
► Tivoli NetView for z/OS (5697-ENV)<br />
► Tivoli Systems Automation for z/OS (or equivalent third-party software)<br />
Documentation and sample scripts for Tivoli Systems Automation are available from <strong>IBM</strong>.<br />
If you choose an equivalent product, you must configure and test the product with SAP.<br />
The SAP Business Suite 7 reference architecture for System z describes the combined<br />
solution of Parallel Sysplex with DB2 data sharing and Central Services Instance<br />
Replication managed by the Tivoli products. For more technical details and scenarios, see<br />
the Business Continuity for SAP on <strong>IBM</strong> System z, SC33-8206-04.<br />
z/OS software for SAP disaster recovery solutions<br />
This section lists proven <strong>IBM</strong> software products that can help to create disaster recovery<br />
solutions. Selecting the right solution for your purpose is not a trivial task and is subject to<br />
specific HA and disaster recovery assessments and system design.<br />
Consider the following solutions:<br />
► <strong>IBM</strong> Tivoli Storage Productivity Center for Replication<br />
► z/OS HyperSwap Manager<br />
► Geographically Dispersed Parallel Sysplex (<strong>IBM</strong> GDPS)/Peer-to-Peer Remote Copy<br />
(PPRC)<br />
Disaster recovery solutions are beyond the scope of this book.<br />
Final planning checklist<br />
Before you proceed with preparations of your system, verify that you have all the required<br />
information by following this self-assessment checklist:<br />
� Choose your installation scenario by working with your SAP Basis consultant and following<br />
the SAP Master Guide for SAP NetWeaver (for SAP NetWeaver 7.3) at:<br />
http://service.sap.com/installnw73<br />
� Plan your SAP system landscape with the SAP Basis consultant. Follow the SAP Technical<br />
Infrastructure Guide for SAP Systems Based on SAP NetWeaver at:<br />
https://cw.sdn.sap.com/cw/community/docupedia/tig<br />
Appendix B. Planning, preparing, and implementing the SAP landscape 167
Change language