Rajesh Gupta Best Practices for SAP BusinessObjects Backup & Recovery Including High Availability and Disaster Recovery Session #2747

Transcription

1 Rajesh Gupta Best Practices for SAP BusinessObjects Backup & Recovery Including High Availability and Disaster Recovery Session #2747

2 Introduction Rajesh Gupta - rajgupta@deloitte.com Solution Network SAP Lead, Deloitte Consulting LLP Rajesh is a lead SAP HANA/NW/BASIS & OS/DB Certified Consultant Over 21+ years of consulting experience with around 15+ years in SAP and over 6 Year as Oracle DBA. SAP HANA Distinguished Engineer ASUG HQ - Enterprise Architecture SIG Group Community Facilitator This presentation should not be interpreted as a representation about or endorsement of any third party products, including SAP software

3 Learning Points Proven methodology for mitigating project risk using a robust backup and recovery strategy. Best Practice for setting up High Availability and Disaster Recovery for production system. Minimize the disaster effects on the daily operations so that the environment can resume critical business functions quickly.

4 What We ll Cover Best Practices for Considering Availability Backup and Recovery Strategy High Availability Clusters A Fault-Tolerant Architecture Disaster Recovery Wrap-up

5 BOBJ Business Intelligence platform SAP BusinessObjects Business Intelligence platform is a flexible, scalable, and reliable solution for delivering powerful, interactive reports to end users via any web application intranet, extranet, Internet, or corporate portal. Delivers tangible benefits that extend across & beyond the organization. Integrated suite for reporting, analysis, and information delivery. Increase end-user productivity & reduce administrative efforts

6 BusinessObjects BI Suite Single BI Platform which provides Authentication and Security A Common Semantic Layer Report and document scheduling and delivery

7 SAP BusinessObjects BI Architecture

8 Business scenarios for implementation Every organization has unique requirements, implementation of the BI platform should be tailored to your needs: Single-machine deployment - for demo or other nonproduction usage Multiple-server deployments - production deployments Client-server configurations - ensure the security

9 Single vs Multiple-server deployments Single-machine NETSCALER Multiple-server TOMCAT CMS SQL DB FS Rep TOMCAT CMS Database Server SQL DB FS Rep FS Rep MA FS Rep FS Rep

10 Redundancy of SAP BusinessObjects Redundancy in an SAP BusinessObjects environment can be achieved by few major categorizations of redundancy: Backup and Recovery Failover High Availability Disaster Recovery

11 Why Backup and Recovery Plan? A backup and recovery plan consists of making copies of data which may be used to restore the original content in the event of data loss. Preserve your data - You're prepared for any type of data loss or disaster, because you can recover your data quickly whenever and wherever you need it. Diminish monetary losses due to database failures and systems downtime Reduce risk and maximize security by storing data offsite, offline and out of reach in a secure location The plan aims to minimize the disaster effects on the daily operations so that the environment can resume critical business functions quickly.

12 Types of backups System backup This is typically a backup of your entire server, OS, and all, bit for bit. Typically, a full backup is taken once a week, with an incremental backup taken daily. This certainly varies from organization to organization. Database backup This is a backup taken of a specific database at a specific time. This is a backup of the database structure and its contents. It doesn t necessarily include the OS files. Directory backup These are files or folders or directories that are of special importance and are backed up on a periodic basis separate from any other backups. Often these are done more frequently, multiple times a day.

13 Backup option Cold backup Needs downtime as CMS, FRS will be stopped Assures accurate system snapshot, as no user is in and transactions can occur during the backup Suitable for complete system backup Hot backup No downtime of the system Can t be assured as accurate because users may still accessing the system. Suitable for partial backup

14 What to backup? It is always recommended to back up BusinessObjects system on a daily basis for all the below components unless otherwise they are modified. CMS tables and Audit tables File Repository Server Database Connections Custom applications (java/.net code)

15 What to consider? Solid backup and recovery strategy in place. Where do we keep our backups? Can we easily recover from data loss due to any type of failures? How often the backup needs to be taken on BO content? How much time is taking to complete the backup process? How long the downtime of the system if it is the cold backup? Testing of database recovery process?

16 Things to be ready before backup Ensure that there are no scheduled reports and Federation jobs running during the backup process time window. Users must be communicated regarding the backup process so that they can plan their report schedules, etc. For hot backup it is always suggested to run the Repository Diagnostic Tool to make sure the CMS and FRS are in sync.

17 Recovery process in Business Objects Regardless of whether a cold or hot backup, recovery process should be simple and clear-cut. The high level sequence of steps to be followed for recovery process as specified below. Stop all Business Objects services. Restore the backup of the CMS and Audit database. Configure the all the ODBC sources to point to the restored database and report source. Restore the Input and Output File Repositories (FRS) Start all Business Objects services.

18 High Availability & Disaster Recovery Service level agreement with the business dictate the Failover and High availability requirement and also the requirements for disaster recovery. Designing this type of architecture depend on various variables Budgets The recovery time objective (RTO). The recovery point objective (RPO) As part of a BOE HA and Disaster recovery plan: Implement redundant servers in a backup system, which mirrors the primary system If the primary system goes down, still the disaster recovery system is available

19 Failover and High Availability A highly available application absorbs fluctuations in availability, load, and temporary failures in the dependent services and hardware. Avoid single points of failure. Failover capabilities implies that a redundancy exists within an environment so that it may be able to actively swap to another running server without interruption to the user The application continues to operate at an acceptable user and systemic response level as defined by business requirements or application service level agreements.

20 Active / Passive what it mean? Failover: active/passive : A second server, whether physical or virtual, is mirrored to the active node but not started or actively handling requests. In addition, database, file store, and web tier components have similar capability of cold swapping processes. High availability: active/active: Both node/server are actively fulfilling requests. This also implies that other components of the architecture, such as the web tier, database tier, and file store, can function despite either software or hardware failure within the environment.

21 Topologies - Failover and High Availability Active-Passive Failover Active-Active Failover Bi-directional Failover Shared Recovery Sites Production Production Production Recovery Recovery Production Dedicated resources for recovery Leverage recovery infrastructure for test/dev Production applications at both sites Each site acts as the recovery site for the other Many-to-one failover Useful for Remote Office / Branch Office

22 Fail-over using cluster Fail-over functionality can be achieved by using the clustering technology provided by the OS vendor (e.g. Windows or AIX). Using the server manager, you can configure following components using a cluster name Job Server, Access Server, SNMP

23 Fail-over using Windows cluster for DS Windows clustering is supported for Data Services 4.2 Windows clustering with DS 4.2 is only for the clustering of Job Servers. Data Services Management Console component is NOT supported with Windows clustering. You must create a Windows cluster before you install the software This is NOT a load balancing solution It must be an active-passive configuration

24 Disaster recovery Come with higher budget as this has a backup plan to recover SAP BusinessObjects in some other location in case of disaster This backup strategy will either call for mirrored servers in the backup data center or a strategy to quickly recover from backup to alternate servers in that backup data center. The mean time to recovery is dictated by the mission criticality of business intelligence in your organization compared to the size of your deployment to be recovered.

25 Triple Insurance/Coverage for availability Virtualization decoupled from hardware Or HANA HA cluster for resiliency against hardware. System replication Software based Active Synchronous Replication across metro DC. This provides fast switch times as data can be preloaded into the secondary instance. Long distance (Geo) coverage using system replication (Async) or Storage replication (Recover point) Primary Secondary Geo Primary * Server Dat a Lo g Synchronous System Replication Seconda ry (Active, Preloade d) Dat a Lo g Asynchronous System Replication Tertiary 85% H/W Leveraged for other systems Dat a Lo g

26 Key Learnings Understand the enterprise resources to achieve redundant environments. Fully comprehend the budget available. Weigh the pros and cons of virtualization to achieve redundancy. Verify the required availability standards in the event of a failure. Create a plan that carefully communicates how to manage failures. Test the failure scenarios in your environment Develop an annual validation plan.

27 Where to Find More Information SAP Data Services 4.2 Installation Guide for Windows. SAP Note High availability and load balancing with Data Services / Data Integrator SAP Note Is Windows clustering supported with Data Services 4.2? SAP Note How to delete a SIA Node SAP Note How to Delete server references in the CMS SAP Note How to delete a SIA from the CCM SAP Note Backup and restore BusinessObjects Enterprise XI 3.x / BI 4.x system from one environment to another environment

28 STAY INFORMED Follow the ASUGNews team: Tom Chris Craig

29 SESSION CODE 2747