Discover Best of Show März 2016, Düsseldorf

Transcription

1 Discover Best of Show März 2016, Düsseldorf

2 Agenda 2

3 Agenda StoreOnce and Preparation SQL Backup Prerequistes Backup and Optimization Oracle Backup Prerequistes Backup and Optimization Copy to Tape Optimization / Recommendation SA Enablement Workshop Important Links 3

4 Transform to a hybrid infrastructure Protect your digital enterprise Enable workplace productivity Empower the data-driven organization

5 Transform to a hybrid infrastructure Protect your digital enterprise Protect your most prized digital assets whether they are on premise, in the cloud or in between. Enable workplace productivity Empower the data-driven organization

6 SQL/Oracle Backup to StoreOnce 6

7 Preparation before you begin Create devices to be used for the backup Verify communication using filesystem backup to StoreOnce Separate data types and create several data stores (e.g. Store_SQL, Store_ORA, Store_ESE, ) StoreOnce 6500 Federated Stores will be created using StoreOnce UI Single-Node Create stores using Data Protector B2D device Tape Library Gateway Tape Drive Physical Storage Library Slots Gateway 1 (MA host 1) Gateway 2 (MA host 2) Gateway 3 (MA host 3) B2D device Physical Storage 7

8 SQL Backup 8

9 SQL Server integration architecture SM - Data Protector Session Manager: Backup Session Manager during backup and Restore Session Manager during restore. Backup API or VDI - SQL Server VDI, the backup interface introduced with SQL Server. MA - Data Protector General Media Agent. 9

10 Different ways to back up the MSSQL instances Zero Downtime Backup / Instant Recovery VDI VSS Transportable backup VSS writer / VDI (virtual device interface) Single Instance Cluster Always On Not a complete list 10

11 Prerequisites SQL integration License to use the SQL Server integration SQL Server correctly installed and configured, SQL Server is available For supported versions, platforms, devices see latest support matrices at MS SQL Integration component installed on every SQL Server Availability Group - every availability group replica must have the MS SQL Integration component installed Cluster - all nodes as Data Protector cluster-aware clients, Data Protector Inet service on all nodes run under a Windows domain user account (with cluster administrator rights) Configure the Data Protector Inet service user impersonation for all cluster nodes Security Policy privileges for this user: Impersonate a client after authentication and Replace a process level token 11

12 Prerequisites SQL integration (continued) The user account to be used must have appropriate SQL Server permissions for running backups and restores SQL Server must be online during configuration Make sure that the SQL Server Browser service is running. Configuration must be performed for every SQL Server instance separately For availability group configurations you must first import the availability group listener as a virtual client by selecting Virtual Host in the Clients context. More information can be found in the integration guide (HPE Data Protector 9.05 Integration Guide) 12

13 Creating the SQL backup specification Adding new Backup In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications, right-click MS SQL Server, and click Add Backup. 13

14 Creating the SQL backup specification Selecting the Template In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications, right-click MS SQL Server, and click Add Backup. In the Create New Backup dialog box, select the Blank Microsoft SQL Server Backup template. Click OK. 14

15 Creating the SQL backup specification Selecting the Client and Database In Client, select the SQL Server system. In Application database, select or specify the name of the SQL Server instance. Click Next. 15

16 Creating the SQL backup specification Specifying the user account W2K8: account specified in the Client selection page Other: account under which the Inet service (SQL Server) is running Windows domain user account (preferred option) SQL Server user account 16

17 Creating the SQL backup specification Settings for an Availability Group For an availability group configuration, you can also provide a port number used by the availability group listener. The default is

18 Creating the SQL backup specification Selecting the Client and Database Select the databases, file groups, or data files you want to back up. For an availability group backup specification, you can expand the availability group listener to display availability group replica clients and the databases belonging to the selected availability group. 18

19 Creating the SQL backup specification Selecting the Devices and Media Pools Select the devices. Click Properties to set the media pool and preallocation policy. The device concurrency is set to 1 and cannot be changed. To create additional backup copies (mirrors), specify the desired number by clicking Add mirror/remove mirror. Select separate devices for each mirror. Click Next. 19

20 Creating the SQL backup specification Backup Options Select backup options. Click Next. 20

21 Creating the SQL backup specification Backup Options Define Pre-exec or Post-exec scripts, set session ownership Modify Protection depending on your needs Set SQL Server specific options 21

22 Creating the SQL backup specification Backup Options (continued) Backup type Concurrent streams Fast direct mode Check database integrity SQL backup compression Exclude from backup Pre-exec, Post-exec Description Specify the number of concurrent data streams for backup The maximum (default) value is the number of selected backup devices, for SQL Server supports only one data stream per device. Select this option for critical production SQL Servers that require fast backup with minimum impact on their performance. This option can only be used with locally connected devices and the same block size. Select this option to verify the SQL Server data integrity before backup. If the check fails, backup completes with warnings. Specify how Data Protector should handle the Microsoft SQL Server backup compression. Specify this option to exclude specific databases from backup Specify a command with arguments or a script (filename) that will be executed on the SQL Server system after backup. 22

23 Creating the SQL backup specification Scheduling the Backup Schedule the backup. For Backup types see table on next slide. 23

24 Creating the SQL backup specification SQL Server online backup types Backup type Full database backup Transaction log backup Differential database backup Copy-only database backup Description Includes all data regardless of the changes made after the last backup. Uses fewer resources than database backups, so can be created more frequently. By applying transaction log backups, you can recover the database to a specific point in time. Records only changes made to the database since the last full database backup. A copy-only full backup is an independent full backup, which never truncates the transaction logs and does not affect an SQL Server restore chain. 24

25 Creating the SQL backup specification Saving the Backup Save the backup specification, specifying a name and backup specification group. Use speaking names for the backup specifications. 25

26 Running the backup 26

27 SQL Backup Summary The backup was done using the default settings Default setting for the Load Balancing and Min/Max option - 1/5 Concurrent streams defaults to 1 1 stream used to back up the data to StoreOnce Overall speed might be too slow for larger databases Device Locking: Depending on DP version and used device - five devices might be locked, even if only one stream was used for the backup (see omnidbutil -show_locked_devs) 27

28 Optimization Omnirc recommended settings: OB2IPCKEEPALIVE = 1 OB2IPCKEEPALIVETIME = 900 OB2IPCKEEPALIVEINTERVAL = 60 Omnirc optional settings (may increase overall performance) OB2SQLBLOCKSIZE OB2SQLMAXTRANSFERSIZE 28

29 Optimization Streams / Compression Increase streams to back up with higher performance Disable compression to achieve better dedupe ratio Devices Increase the Max value equal to streams Select one gateway only Server Side Deduplication Source Side Decuplication Target Side Deduplication 29

30 Optimization Compare the performance Backup Job default settings 1 stream Backup Job optimized settings 20 streams 30

31 Oracle Backup 31

32 Oracle Server integration architecture SM - Data Protector Session Manager: Backup Session Manager during backup and Restore Session Manager during restore. RMAN - The Oracle Recovery Manager. Data Protector MML - The Data Protector Oracle integration Media Management Library, which is a set of routines that enables data transfer between the Oracle Server and Data Protector. Backup API - The Oracle-defined application programming interface. IDB - The Data Protector Internal Database where all the information about Data Protector sessions, including session messages, objects, data, and used devices and media, is written. MA - Data Protector General Media Agent. 32

33 Different ways to back up the Oracle databases Zero Downtime Backup / Instant Recovery BackupSet Proxy Transportable VSS using oravss writer Normal Oracle RMAN Single Instance Cluster RAC Data Guard Not a complete list of all backup types 33

34 Prerequisites Oracle integration License to use the Data Protector Oracle integration Oracle Server correctly installed and configured For supported versions, platforms, devices, see the latest support matrices at Oracle Server software installed, and Oracle target database open or mounted. If the Oracle recovery catalog database is used, ensure that it is properly configured and open. Oracle net services properly configured and running for the Oracle target database and the recovery catalog, if you use it. Oracle Real Application Clusters (RAC): Each node must have a dedicated disk for storing archive logs. Such disks must be NFS mounted on all other RAC nodes. 34

35 Prerequisites Oracle integration Identify the Oracle database user that will be used by Data Protector for backup. This user must have the SYSDBA privilege granted. You need to provide these user accounts when you configure the Oracle database. In cluster environments, ensure to add he following users to the Data Protector admin or operator user group: OSDBA user for all physical nodes, and OSDBA user for the virtual server (applicable for HPE Serviceguard clusters) Collect the information to configure the integration: Oracle Server home directory Login information to the target database Optionally, login information to the recovery catalog database Optionally, login information to the standby database More information can be found in the integration guide (HPE Data Protector 9.05 Integration Guide) 35

36 Oracle integration Backup types Online backup of a whole database or parts (tablespaces) Online incremental backup (Oracle differential incremental backup 1 to 4) Offline backup of a whole database Backup of Archived Redo Logs only Backup of the Oracle database recovery catalog Backup of the Oracle control files Backup of recovery files residing in the flash recovery area: full and incremental backup sets control file autobackup (SPFILE included if used) archived redo logs datafile copies, control file copies Flashback logs, the current control file, and online redo logs are not backed up. In Oracle Data Guard environment, backup of standby database 36

37 Creating the Oracle backup specification Adding new Backup In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications, right-click Oracle Server, and click Add Backup. 37

38 Creating the Oracle backup specification Selecting the Template In the Context List, click Backup. In the Scoping Pane, expand Backup Specifications, right-click Oracle Server, and click Add Backup. In the Create New Backup dialog box, select the Blank Oracle Backup to create a backup without predefined options, or use a different template with predefined options. Click OK. 38

39 Creating the Oracle backup specification Templates types Template Archive Archive_Delete Database_Archive Database_Switch_Archive Database_Switch_Archive_Del Direct_Database SMB_BackupSet_Database SMB_Proxy_Database Whole_Online Whole_Online_Delete Description Backs up archived redo logs. Backs up archived redo logs, deletes them after the backup. Backs up database and archived redo logs. Backs up DB, switches online redo logs + backs up archived redo logs. Backs up database, switches online redo logs, backs up archived redo logs and then deletes archived redo logs. Backs up database and controlfile. Backs up DB and control file in ZDB mode using proxy-copy method. Backs up DB and control file in ZDB mode using backup set method. Backs up database and archived redo logs. Backs up DB and archived redo logs, and deletes archived redo logs. 39

40 Creating the Oracle backup specification Selecting the Client and Database In Client, select the Oracle Server system. In a cluster environment, select the virtual server. In Application database, select or specify the name of the Oracle database. Specify the User and group/domain options (Unix, Linux, Windows 2008). Ensure that this user has been added to the Data Protector admin or operator user group and has the Oracle database backup rights. Click Next. 40

41 Creating the Oracle backup specification Configuring Oracle databases The pathname of the Oracle Server home directory (example Windows: C:\oracle\product\11.2.0\db_1) Specify the login information to the primary database (SYSDBA privileges) Services = net service name for the primary database 41

42 Creating the Oracle backup specification Configuring Oracle databases Select Use target database control file OR Use recovery catalaog Oracle Data Guard and if you intend to use standby database specify the login information 42

43 Creating the Oracle backup specification Selecting the Oracle database objects Select the databases objects to be backed up. For example, a single tablespace can be separately selected for backup, but for a complete online backup of the database, the ARCHIVELOGS must also be selected. The archived logs can reside in the flash recovery area. In this case, if you select the FLASH RECOVERY AREA to be backed up, you do not need to select also ARCHIVELOGS. 43

44 Creating the Oracle backup specification Selecting the Devices and Media Pools Select the devices. Click Properties to set the device concurrency, media pool and preallocation policy. To create additional backup copies (mirrors), specify the desired number by clicking Add mirror/remove mirror. Select separate devices for each mirror. Click Next. 44

45 Creating the Oracle backup specification Backup Options Select backup options. Click Next. 45

46 Creating the Oracle backup specification Backup Options Define Pre-exec or Post-exec scripts, set session ownership Modify Protection depending on your needs Set Oracle-specific options 46

47 Creating the Oracle backup specification Backup Options (continued) Backup type Disable recovery catalog auto backup Disable Data Protector managed control file backup Back up standby database RMAN Script Pre-exec, Post-exec Description By default, Data Protector backs up the recovery catalog in every backup session. By default, Data Protector backs up the Data Protector managed control file in every backup session. Oracle Data Guard: This option is applicable if the database is configured with the standby connection. By default, RMAN backs up the database files and archived redo logs on the primary system. Select to enable backup of database files and archive logs on standby system. You can edit the Oracle RMAN script section of the Data Protector Oracle backup specification. Specify a command or RMAN script that will be started by ob2rman.pl on the Oracle Server system before the backup (pre-exec) or after it (post-exec). RMAN scripts must have the.rman extension. 47

48 Creating the Oracle backup specification Scheduling the Backup Schedule the backup. 48

49 Creating the Oracle backup specification Scheduling the Backup With Oracle full and incremental level 0 backups all data blocks per datafile are backed up. With Oracle incremental backup (level 1 or higher), only the data blocks that have changed since a previous backup are backed up. The difference between a full backup and an incremental level 0 backup is that the incremental 0 is a base for subsequent incremental backups. Oracle incremental backups can be differential or cumulative. By default, Data Protector performs Oracle differential incremental backups. 49

50 Creating the Oracle backup specification Saving the Backup Save the backup specification, specifying a name and backup specification group. Use speaking names for the backup specifications. 50

51 Running the backup 51

52 Oracle Backup Summary The backup was done using the default settings. Because of the default settings the Load Balancing and Min/Max option 1/5 was used. As a result 5 streams were used to backup the database. The overall speed for the backup might be too slow for larger databases. The backup specification is not optimized to back up the data to StoreOnce 52

53 Optimization Omnirc recommended settings: OB2IPCKEEPALIVE = 1 OB2IPCKEEPALIVETIME = 900 OB2IPCKEEPALIVEINTERVAL = 60 Omnirc optional settings (may change the behavior during backup) OB2_DPMCTL_SHRLOC ORA_ASM_HOME ORA_ASM_LCL_INSTANCE OB2CATPATH OB2_ORACLE_RC_USER OB2_ORACLE_ASM_OSUSER Zero Downtime Backup: ZDB_ORA_INCLUDE_CF_OLF, ZDB_ORA_INCLUDE_SPF, ZDB_ORA_NO_CHECKCONF_IR, ZDB_PRESERVE_MOUNTPOINTS, ZDB_MOUNT_PATH,... 53

54 Optimization Compression / Encryption Disable Oracle compression / encryption / optimization to achieve better dedupe ratio RMAN> CONFIGURE BACKUP OPTIMIZATION OFF; RMAN> CONFIGURE ENCRYPTION FOR DATABASE OFF; Concurrency / Streams / Channels Increase devices / streams / channels to back up with higher performance Better deduplication (next slide): filesperset 1 maxopenfiles 1 54

55 Example Oracle Script backup database 55

56 Example Oracle Script backup archive (1) 0 Post-exec POSTEXEC "Archive2_ORACLEDB_DB1.cmd" -on_host "cell.server" 56

57 Example Oracle Script backup archive (2) 57

58 Optimization Compare the performance Backup Job default settings 5 stream Backup Job optimized settings 15 streams 58

59 Other Recommendations Incremental Backups: when planning for incrmental backups and to reduce backup time for large databases consider to enable Oracle Change Block Tracking. Use the Oracle recovery catalog as central repository for your databases. Other usefull commands can help to reclaim space on StoreOnce (Houesekeeping): To clean obsolete backups run the commands (RMAN script): list backup summary; DELETE NOPROMPT OBSOLETE; DELETE NOPROMPT EXPIRED BACKUP; DELETE NOPROMPT EXPIRED COPY; To synchronize recovery catalog and StoreOnce media (RMAN script): CROSSCHECK BACKUPSET; CROSSCHECK COPY; Archive Save + Archive Second Copy and Delete 59

60 Best Practice for Oracle Backup and Recovery Database in ARCHIVELOG mode for online backup and point in time recovery RMAN parameter FILESPERSET 1 will improve deduplication ratio Use Block Change Tracking for incrementals backups (configure in Oracle) Backup policy: Weekly full and daily incremental to reduce compute, bandwidth and storage usage Daily backups of the control file (key component) Daily backups of parameter file, tnsnames.ora, and listener.ora Archived redo logs are backed up as necessary ALLOCATE CHANNEL to multiplex backup streams improve backup thoughput No Oracle encryption / compression / optimization 60

61 Copy to Tape 61

62 Copy to Tape Keep in mind Do not copy to tape using Data Protector Post Backup copy Best Practise to separate backup, replication, copy to tape and housekeeping for StoreOnce Backup Replication Housekeeping Start of Replication Window Spare Time for future growth or Physical Tape Offload Housekeeping Window Limitation for SQL/DP regarding streams and devices (see QCCR2A61217 and QCCR2A58718) When combining several SQL backup into one copy job 62

63 Copy to Tape Settings Copy only protected objects to prevent re-copying alread processed objects Copy only objects not copied so far or with number of copies less than X When using replication to copy from first StoreOnce to second StoreOnce you would select 1 When copying objects to tape after replication has been finished you would select 2 Select timeframe or no time limit 63

64 Copy to Tape Settings Select library filter to prevent copying from tape to tape (depending on settings in object filter) Try to avoid several libraries into one copy job 64

65 Copy to Tape Settings Reset or change retention after successfull copy on StoreOnce Keep or change retention after successfull copy on Tape Library 65

66 Questions and Answers 66

67 References 67

68 HPE StoreOnce Links StoreOnce StoreOnce VSA webpage Free 1TB VSA: Oracle RMAN Plug-in download SAP Plug-in download SEM Plug-in download SQL Plug-in download StoreOnce demo StoreOnce Sizer tool BURA compatibility matrix RMC webpage RMC download RMC documents Get Protected Guarantee webpage 68

69 HPE StoreEver Links HPE Tape Storage Systems home page HPE StoreOpen and LTFS HPE Tape Storage Compatibility HPE TapeAssure HPE ESL G3 Library LTO technology home page HPE StoreEver Tape Presentations, Sales Tools HPE StoreEver Tape News 69

70 Thank you Daniel Braun - daniel.braun@hpe.com Mobile