Rajan Arora (Deloitte) SAP Business Objects Backup and Recovery Scenarios and Best Practices Session # 3233

Transcription

1 Rajan Arora (Deloitte) SAP Business Objects Backup and Recovery Scenarios and Best Practices Session # 3233

2 AGENDA Overview Key Learnings What to Backup Type of Backup s Restore Scenario s Best Practices Lessons Learned Q&A

3 OVERVIEW Handling Backup & Restore with SAP Business Objects can be very challenging if not configured correctly. This session will share the best practices based on lessons learned during the designing & implementation of backup strategy for SAP BI. Following are some of the highlights of the session: Available and Recommended Approaches Common Issues during Backup & Recovery of SAP Business Objects

4 KEY LEARNINGS Back Up and Recovery concept of SAP Business Objects Backup/Restore types and procedures for SAP Business Objects Best Practices for SAP Business Objects Backup/Recovery Plan

5 WHAT TO BACKUP ODBC DSNs Configuration files Local Audit Log File (if Enabled) Custom applications and code (Optional)

6 TYPE OF BACKUP s Cold Backup Needs downtime - CMS, FRS need to be stopped Less chances of data loss No changes can occur during the backup Hot Backup No downtime of the system More chances of data loss Data can be changed during the backup Suitable for complete system backup Suitable for Partial Backup Content Backup Server Backup Can be restored on different Hardware Includes Operating system as well Fast and can be scheduled frequently Slow and expensive applications and data stored on local drives Need Application Downtime for consistency Incremental Backup Full Backup Capture only changes since last back up Captures every byte Faster and Robust Require Long System Downtime and Slow Complex restore process Easy to restore

7 TYPE OF BACKUP s Most appropriate backup for your organization will depend on answers to following questions: How often do you need to backup your content? How much time exists to complete the backup? Do you require high availability of the BOE system? How frequently will you restore?

8 RESTORE SCENARIO s Full System Restore is the most basic type. A full restore assumes that the entire server, database or file system was lost and only a full restore will bring it back to life. Temporary Restore is restoring to a new location and using an import wizard/promotion management to restore missing or corrupted objects to the production deployment. Business Intelligence Archive files (BIARs) Restore is used for partial restore of the CMS database or input/output FRS.

9 RESTORE SCENARIO s Recovery Process Note the Cluster Key and Administrator password of the source system For Partial Recovery you need to import the content to be restored from a BIAR file using Import Wizard/Promotion Management In some cases, Recovery SIA needs to be created and cluster key needs to be changed Run the Repository Diagnostic Tool in order to remove any inconsistencies between File Repository Servers and (recovered) system database.

10 BEST PRACTICES Recommended Backup Strategy: Backup Weekly Daily Operating System Backup File System/FRS Backup Database/Repository Backup (Full) (Full) (Cold) (Incremental) (Hot) (Hot) Custom Code Backup BIAR Backup

11 BEST PRACTICES For hot backup always run the Repository Diagnostic Tool to make sure the CMS and FRS are in sync. FRS and CMS backup s should be started as near to simultaneously as possible, but the FRS backup should never start before the CMS backup. Ensure that there are no scheduled reports/ Federation jobs running during the backup process time window Do not run promotion management or LCM during backup window

12 BEST PRACTICES Hot Backup Maximum duration needs to be longer than the actual time it takes to back up your repository It is good to have NAS (Network attached Storage) as source Input and Output repository. This will help in automatic incremental backup s of FRS.

13 LESSONS LEARNED BOBJ Backup is responsibility of both server administrator and BOBJ Administrator After DB restore you need to delete all source server entries from Database manually before starting the BI services (SAP Note: ) Promotion Management tool times out when adding large number of objects while performing Backup using BIAR file. Solution is to use command line LCM tool Do not add all objects in one job while performing BIAR file backup. It can cause issue during selective restore

14 LESSONS LEARNED In cluster/distributed installation take additional servers also in consideration for Backup Strategy Hot Backup will require additional space in repository server as it creates new backup file instead of overwriting Good Cold Backup integrity requires proper sequence for shutting down Business Object Services and backup kick off.

15 Q&A

16 STAY INFORMED Follow the ASUGNews team: Tom Chris Craig

17 SESSION CODE 3233