ZDLRA implementation at CFM

Transcription

1 October 04, 2017 ZDLRA implementation at CFM Presented by Gabriel Nitulescu Project Leader CFM

2 Who Are We? Fundamental research applied to financial markets CFM invests in Science, Technology and Finance 25 years of experience in managing trading systems A rational process that produces robust Trading Algorithms Proprietary software able to execute & control large volumes of data 180 People Offices in Paris, London, New York, Tokyo CFM

3 Data Protection Desired Architecture DB_A_frep_00 DataGuard DB_A_frcn_00 FREP Archived logs backup Database backup FREP Archived log backup database backup Backup FREP Backup FRCN CFM

4 Workload Characterization CFM

5 Legacy Data Protection Strategy Oracle Best Practices Disk to Disk to Tape Daily to Disk RUN { RECOVER COPY OF DATABASE WITH TAG 'UPDATABLE'; BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'UPDATABLE' DATABASE; BACKUP DEVICE TYPE SBT ARCHIVELOG ALL NOT BACKED UP ; } Weekly to Tape RUN { BACKUP DEVICE TYPE SBT RECOVERY AREA; } +DATA +RECO MAA Best Practices Architecture Two Independent Data Centers with Data Guard No special procedures in case of disaster or maintenance Production Impacts Large FRA size (1,7 DB Size) High CPU Utilization During Backup High Bandwidth Utilization for Weekly Backups BD_A DB_B Image copy 24 TB 38 TB Inc0 5 TB 12 TB Inc1 0.3 TB 0.2 TB Archives / day 3 TB 1 TB Flashback logs / day 1 TB 0.3 TB CFM

6 Why ZDLRA? Technical advantages (Virtual Full & Real-Time Redo Transport) Reduce CPU required for backup => no more backup window => sizing => licenses Backup & Recovery performances Financial Aspects (Lower TCO) Zero Data Loss Recovery Appliance Lower Cost than Primary Storage (FRA on Production Server) > Savings of 40% CFM

7 OEM implementation White Paper Deploying the Zero Data Loss Recovery Appliance in a Data Guard Configuration OEM based implementation Minimize downtime CFM

8 Enrolling Protected Databases Enrolling Primary Protected Database with Recovery Appliance SQL> exec DBMS_RA.ADD_DB (db_unique_name=> 'PRODOMR_FREP_00', protection_policy_name => 'CFM_003_DAYS', reserved_space=>'51g'); SQL> exec DBMS_RA.GRANT_DB_ACCESS (db_unique_name => 'PRODOMR_FREP_00',username => 'vpccfm'); SQL> select DB_UNIQUE_NAME,DBID,DB_KEY from ra_database ORDER BY DB_UNIQUE_NAME; Repeat for Standby Protected Database with Recovery Appliance SQL> exec DBMS_RA.ADD_DB (db_unique_name=> 'PRODOMR_FRCN_00', protection_policy_name => 'CFM_003_DAYS', reserved_space=>'51g'); SQL> exec DBMS_RA.GRANT_DB_ACCESS (db_unique_name => 'PRODOMR_FRCN_00',username => 'vpccfm'); SQL> select DB_UNIQUE_NAME,DBID,DB_KEY from ra_database ORDER BY DB_UNIQUE_NAME; DGMGRL> switchover to 'prodomr_frcn_00'; rman target catalog RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN> show all; RMAN configuration parameters for database with db_unique_name PRODOMR_FREP_00 are: CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET; CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%u' PARMS "SBT_LIBRARY=/u01/app/oracle/product/ /dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/wallet credential_alias=zfrep00_catalog')"; CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FRCN_00' CONNECT IDENTIFIER 'PRODOMR_FRCN_00_DR'; CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FREP_00' CONNECT IDENTIFIER 'PRODOMR_FREP_00_DR'; CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO 'SBT_TAPE'; [oracle@<db_server_frep>]$ rman target /@PRODOMR_FRCN_00_DR catalog /@zfrcn00_catalog RMAN> register database; database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN> show all; RMAN configuration parameters for database with db_unique_name PRODOMR_FRCN_00 are: CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET; CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%u' PARMS "SBT_LIBRARY=/u01/app/oracle/product/ /dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/wallet credential_alias=zfrcn00_catalog')"; CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FRCN_00' CONNECT IDENTIFIER 'PRODOMR_FRCN_00_DR'; CONFIGURE DB_UNIQUE_NAME 'PRODOMR_FREP_00' CONNECT IDENTIFIER 'PRODOMR_FREP_00_DR'; CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO 'SBT_TAPE'; DGMGRL> switchover to 'prodomr_frep_00';

9 CLI Backup Scripts RMAN Backup Job Scripts $ cat backup_inc_l0.rman run { backup device type sbt tag 'INCFOREVER' cumulative incremental level 0 filesperset 1 section size 64g database plus archivelog not backed up filesperset 32;} Level 0: One time $ cat backup_inc_l1.rman run { backup device type sbt tag 'INCFOREVER' cumulative incremental level 1 filesperset 1 section size 64g database plus archivelog not backed up filesperset 32;} Level 1: Daily RMAN Backup Job Output $time rman target /@PRODOMR_FREP_00_DR catalog /@zfrep00_catalog cmdfile=backup_inc_l1.rman log=backup_inc_l1_${oracle_sid}.`date +"%Y%m%d%H%M%S"`.log & allocated channel: ORA_SBT_TAPE_1 channel ORA_SBT_TAPE_1: RA Library (ZFREP) SID=47483A6E3C363BB5E053345B430A24E2 $time rman target /@PRODOMR_FRCN_00_DR catalog /@zfrcn00_catalog cmdfile=backup_inc_l1.rman log=backup_inc_l1_${oracle_sid}.`date +"%Y%m%d%H%M%S"`.log & channel ORA_SBT_TAPE_1: RA Library (ZFRCN) SID=480AB266A1C90E9EE0533E5B460A5440 skipping archived logs of thread 1 from sequence to 43535; already backed up Actual OEM limitation CFM

10 CFM Data Protection Architecture with Recovery Appliance efrcn00-vm01 efrep00-vm01 DataGuard DB_A_frcn_00 CFM 2017 backup FREP FREP backup DB_A_frep_

11 CLI real time redo: Redo Transport Authentication Using a Password File Data Guard Concepts and Administration 6 Redo Transport Services > Redo Transport Authentication Using a Password File SQL> create user vpccfm identified by xxxxxx; SQL> grant sysoper to VPCCFM; SQL> select * from V$PWFILE_USERS; USERNAME SYSDB SYSOP SYSAS SYS TRUE TRUE FALSE VPCCFM FALSE TRUE FALSE SQL> ALTER SYSTEM SET redo_transport_user = 'VPCCFM' SCOPE=SPFILE; SQL> ho scp orapwd${oracle_sid} SQL> shutdown immediate; All standby databases SQL> startup; SQL> show parameter redo NAME TYPE VALUE redo_transport_user string VPCCFM Same User for Redo Transport and Backup (VPC) CFM

12 Enable Real-Time Redolog Shipping Updating DGMGRL Configuration Configuring Log Archive Destination to RA DGMGRL> add recovery_appliance ZFREP as connect identifier is 'ZFREP00_CATALOG'; DGMGRL> enable recovery_appliance ZFREP; DGMGRL> add recovery_appliance ZFRCN as connect identifier is 'ZFRCN00_CATALOG'; DGMGRL> enable recovery_appliance ZFRCN; DGMGRL> show configuration; Configuration - prodomr_dg Protection Mode: MaxPerformance Members: prodomr_frep_00 - Primary database prodomr_frcn_00 - Physical standby database zfrep - Backup appliance zfrcn - Backup appliance No cascade redo FREP SQL> alter system set log_archive_dest_4='service=zfrep00_catalog VALID_FOR=(ALL_LOGFILES, ALL_ROLES) ASYNC DB_UNIQUE_NAME=zfrep' scope=both FRCN SQL> alter system set log_archive_dest_4='service=zfrcn00_catalog VALID_FOR=(ALL_LOGFILES, ALL_ROLES) ASYNC DB_UNIQUE_NAME=zfrcn' scope=both sid='*'; Confirming Configuration SQL as rasys@zfrcn00 > select DB_UNIQUE_NAME, NZDL_ACTIVE, SPACE_USAGE/1024 as SPACE_USAGE_TB, DISK_RESERVED_SPACE/1024 as DISK_RESERVED_SPACE_TB, round(deduplication_factor,2) from RA_DATABASE order by DB_UNIQUE_NAME; DB_UNIQUE_NAME NZD SPACE_USAGE_TB DISK_RESERVED_SPACE_TB ROUND(DEDUPLICATION_FACTOR,2) PRODOMR_FRCN_00 YES CFM

13 CFM Real-Time Data Protection Architecture with Recovery Appliance efrcn00-vm01 efrep00-vm01 DataGuard FREP backup backup Real time Redo Shipping FREP CFM 2017 Redo Shipping DB_A_frcn_00 DB_A_frep_

14 CFM Real-Time Data Protection with Recovery Appliance & Data Guard Broker efrcn00-vm01 efrep00-vm01 DataGuard FREP backup backup Real time Redo Shipping FREP Real time Redo Shipping DB_A_frcn_00 DB_A_frep_00 * RDBMS >= * RDBMS >= Active far Sync CFM

15 Backup Elapsed Time & Resource Usage DB Size = 12TB RMAN Backup Channels = 8 CFM

16 Results 1 of 2 CFM

17 Results 1 of 2 CFM

18 Results 2 of 2 CFM

19 Results 2 of 2 CFM

20 Summary Positive Results Improvements Needed Technical: Minimized Backup Window Offloaded Database Server CPU Increased Recovery Performance o Virtual full backup, Compression Ability to implement the desired architecture Better OEM integration More Detailed Documentation More Oracle University Courseware Improved Support Skills Price: Lower TCO Reduce impact of CPU for backup => licenses «User TB» on RA vs FRA Project: Implementation is less complex than first impression CFM