SAP HANA Backup and Recovery

SAP HANA Backup and Recovery
SAP HANA
Backup and Recovery (Overview, SPS08)
Andrea Kristen, SAP HANA Product Management
October 2014
Public
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
2
Agenda
Backup
Recovery
Database copy
Tool support and certification
What‘s new?
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
3
Backup
SAP HANA Backup and Recovery
In-memory data and persistent storage
In-memory computing is safe: The SAP HANA database holds the bulk of its data in memory for
maximum performance, but still uses persistent storage to provide a fallback in case of failure.
During normal operation of the database, data is automatically saved from memory to disk at regular
savepoints. Additionally, all data changes are captured in the log. The log is saved from memory to
disk after each committed database transaction.
After a power failure, the database can be restarted like any disk-based database and returns to its
last consistent state by replaying the log since the last savepoint.
Time
1
Savepoint:
Data is written
to disk (data area)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
2
After each COMMIT,
log is written
to disk (log area)
3
Power failure
Public
5
SAP HANA Backup and Recovery
Why backups?
While savepoints and log writing protect your data against power failures, this does not help when the
persistent storage itself is damaged or a logical error occurred.
Backups are required
 To protect against disk failures
 To make it possible to reset the database to an earlier point in time
They are also useful for other scenarios such as database copy.
Backups are carried out while the database is running, users can continue to work normally.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
6
SAP HANA Backup and Recovery
Memory  disk  backup
Data backups
SAP HANA database
 Contain the current payload of the data volumes (data
and undo information)
 Manual (SAP HANA studio, SQL commands), or
scheduled (DBA Cockpit)
Memory
Savepoint
Data Area
(disk)
COMMIT
Log Area
(disk)
Data Backups
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Log backups
 Contain the content of closed log segments; the
backup catalog is also written as a log backup
 Automatic (asynchronous) whenever a log segment is
full or the timeout for log backup has elapsed
Log Backups
Public
7
SAP HANA Backup and Recovery
Terminology
Data
 Data area = all data volumes
 1 data volume per service with persisted data
(per node)
Data Area
Redo log
Data
Volume
Log Area
Log Volume
Log
Volume
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Log
Segment
 Log area = all log volumes
 1 log volume per service with persisted data
(per node)
 Log volume contains log segments
– Number of pre-formatted log segments is
configurable
– Log segments are closed when they are full, or the
log backup timeout has elapsed
– After a log segment has been successfully backed
up, it is released for overwriting
Public
8
SAP HANA Backup and Recovery
Data backup: synchronization of multiple nodes
SAP HANA automatically handles the
synchronization of the data backup across nodes
 no user interaction for synchronization required!
Master
Name
Server
 All services that persist data are backed up
– E.g. master name server, index servers
Index
Server
 Global data backup savepoint for these services
– Synchronized across all nodes and services
Savepoint
– Transactions are paused very briefly
Savepoint
– Savepoint is kept until the backup is finished for all
services. If a page is changed during the backup, it is
written to a different location (shadow page concept)
 Data marked in the savepoint is read from the data
volumes and written to the backups
Synchronized
backup savepoint
– Parallelization: one backup stream per service,
double buffer technology for reading from the volumes
and writing to the target
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Name
Server
Name
Server
Index
Server
Index
Server
Savepoint
Savepoint
Parallelization
Backup
Public
9
SAP HANA Backup and Recovery
Options for backups: File system
Backups to the file system




For both data and log backups
E.g. to an NFS share
For information on file systems: SAP Note 1820529
Data backups triggered/scheduled using SAP HANA
studio, SQL commands, or DBA Cockpit, log backups
written automatically (unless disabled)
SAP HANA
studio
hdbsql
Create backup
SAP HANA
Database
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Backup
Storage,
e.g. NFS
Public
10
SAP HANA Backup and Recovery
Options for backups: Backint
Backups to 3rd party backup server
 For both data and log backups
 “Backint for SAP HANA” API can be implemented by a
3rd party backup agent (certification required)
 Provides functions for backup, recovery, query, delete
 3rd party backup agent runs on the SAP HANA server,
communicates with 3rd party backup server
 Backups are transferred via pipe
 Direct integration with SAP HANA:
– Data backups to Backint can be triggered/scheduled
using SAP HANA studio, SQL commands, or DBA
Cockpit
– Log backups are automatically written to Backint (if
configured)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA
studio
hdbsql
Create backup
SAP HANA
3rd Party
Backup Agent
3rd Party
Backup
Server
Public
11
SAP HANA Backup and Recovery
Options for backups: Storage snapshot
Storage snapshots as backups
SAP HANA also supports the creation of storage
snapshots, which can later be used for recovery
1. Prepare the database for the storage snapshot,
using HANA Studio, SQL commands, or the storage
tool (if implemented).
Technically, this creates an internal backup snapshot
(same as for a normal data backup)
2. Using the storage tool, create a storage
snapshot of the SAP HANA data area
3. Confirm the storage snapshot as successful, using
either HANA studio, SQL commands, or the storage
tool (if implemented).
An entry including the external backup ID is written to
the backup catalog.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA
studio
hdbsql
Storage
Tool
Prepare database
Confirm storage snapshot
SAP HANA Database
Internal snapshot
Data Area (Disk)
Create storage
snapshot
External
Storage
Public
12
SAP HANA Backup and Recovery
Backup information in SAP HANA Studio
You open the backup overview tab by doubleclicking Backup in the Systems view in SAP HANA
studio
 Progress information on currently running data backup,
with information on the services included in the backup
 Last successful data backup
– Start/end time, duration, size, and throughput
– To display more detailed information on this data
backup, click More Information
 Information on open snapshot
Buttons for
 Canceling running data backup
 Starting backup
 Displaying backup.log file
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
13
SAP HANA Backup and Recovery
Backup configuration in SAP HANA Studio
Backint
 If a 3rd party backup tool is installed, it is displayed
automatically
 (optional) Specify vendor-specific parameter files
Data backup
 Default settings for data backups to the file system
 Destination, maximum file size
 You specify the destination type (file or Backint) when
executing the data backup
Log backup
 Default settings for log backups
 Destination type (file or Backint), destination, backup
interval
 Log backups are carried out automatically unless
disabled
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
14
SAP HANA Backup and Recovery
Creating a data backup
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
15
SAP HANA Backup and Recovery
Creating a storage snapshot
Creating a snapshot
1. In the Systems view in SAP HANA studio, right-click on the system and choose Storage Snapshot...
Then choose the Prepare option.
Alternatively, you can use the SQL command:
BACKUP DATA CREATE SNAPSHOT COMMENT ‘snapshot_test’
2. Using the storage tool, create a storage snapshot of the SAP HANA data area
3. In SAP HANA studio, confirm the successful storage snapshot and enter the external snapshot ID.
Alternatively, you can use the SQL command:
BACKUP DATA CLOSE SNAPSHOT BACKUP_ID 3456789 SUCCESSFUL 'storage_id_12345‘
Storage snapshots are listed in the backup catalog. You can either display the backup catalog in SAP
HANA studio, or query it using SQL (system view M_BACKUP_CATALOG).
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
16
SAP HANA Backup and Recovery
Backup catalog
The backup catalog provides detailed information on data backups, log backups and storage
snapshots, for example start/end time, duration, size, and throughput
The backup catalog is stored within the SAP HANA database, and also backed up as part of the log
backup (even in log mode OVERWRITE). This allows for offline access to the backup catalog during
recovery.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
17
SAP HANA Backup and Recovery
Backup lifecycle management (I)
Deleting old backups may be required in order to manage your backup storage space or to
fulfill regulatory deletion requirements
You can delete old backups
 From the backup catalog (logical view)
 Physically (from disk and/or from a 3rd party backup server via the Backint interface)
There is an audit event which you can enable to create an entry in the audit trail whenever a backup is
deleted using this function.
The deletion functionality is available both in SAP HANA studio (see next slide) and on the command
line (SQL commands)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
18
SAP HANA Backup and Recovery
Backup lifecycle management (II)
Prerequisite
 BACKUP ADMIN system privilege
1. In the Systems view in SAP HANA studio, doubleclick Backup and open the Backup Catalog tab
2. Right-click on a data backup in the list and select an
option:
o Delete the selected data backup only
o Delete backups (both data and log backups) that are older
than the selected data backup
3. Choose whether you want to delete the entry in the
backup catalog only, or whether you want to also
physically delete the backup (from the file system or if
available from the 3rd party backup tool)
4. Review your settings before starting the deletion by
pressing Finish
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
19
Recovery
SAP HANA Backup and Recovery
Backups during normal database operation
Time
1
Data backups/
storage snapshots
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
2
Log backups
3
Most recent
entries from
log area
4
Failure
Public
21
SAP HANA Backup and Recovery
Recovery options
C
B
A
Time
(A) To the most recent state
 Uses the specified data backup or storage snapshot
+ subsequent log backups
+ entries that are still available in the log area (if it was not destroyed by the failure)
(B) To a point in time in the past
 Uses the specified data backup or storage snapshot
+ subsequent log backups
+ entries that are still available in the log area (if it was not destroyed by the failure)
(C) Using a specified data backup or storage snapshot (without log replay)
 Uses the specified data backup or storage snapshot, but no log backups
 All log entries that still exist in the log area are deleted, no log will be replayed
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
22
SAP HANA Backup and Recovery
Starting a recovery
In the Systems view in SAP HANA studio, choose
Backup and Recovery  Recover System... from
the context menu of the database and enter the
credentials of the SAP HANA operating system
user <SID>adm
Caution: For a recovery, the SAP HANA database
will be shut down
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
23
SAP HANA Backup and Recovery
Recovery to the most recent state (option A)
You can use either a data backup (from the
file system or Backint), or a storage snapshot
as the basis for the recovery
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
24
SAP HANA Backup and Recovery
Recovery to a point in time in the past (option B)
You can use either a data backup (from the
file system or Backint), or a storage snapshot
as the basis for the recovery
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
25
SAP HANA Backup and Recovery
Recovery using a specified data backup or storage snapshot (option C)
You can use either a data backup (from the
file system or Backint), or a storage snapshot
as the basis for the recovery
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
26
SAP HANA Backup and Recovery
Recovery phases
After the initial collection of system information for
the recovery, the recovery wizard shows the
following phases:
 Phase 1: Data recovery
– using data backup or snapshot
 Phase 2: Log recovery
– using log backups and/or log that is still available in
the log area
 Phase 3: Restart
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
27
SAP HANA Backup and Recovery
Recovery steps when using a storage snapshot
1. Using the storage tool, transfer the storage
snapshot to the data area of the SAP HANA
database
2. Using SAP HANA studio or the command line,
recover the database using the storage snapshot
as basis (available in the recovery wizard)
SAP HANA
studio
Storage
Tool
cmd
Recover database
Note: All recovery options are available, including
point-in-time recovery using log backups/log from the
log area
SAP HANA Database
Internal snapshot
Data Area (Disk)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Transfer storage
snapshot
External
Storage
Public
28
Database copy
SAP HANA Backup and Recovery
Database copy (I)
You can carry out database copies using SAP HANA’s standard backup/recovery functions
A typical use case would be to create a copy of your production system for tests on a smaller QA
system. Note: If the target system has less resources, e.g. less CPU and RAM, performance cannot be
expected to be the same as in the source system.
Options for database copy
 Using data backup or storage snapshot + log backups of the source database
 This allows you to restore the database to a point in time after the data backup or storage snapshot
 Using only data backup or storage snapshot of the source database
 This restores the content exactly as of the point in time of the data backup or storage snapshot
Copying from a larger (m nodes) to a smaller system with fewer hosts (n nodes) is supported for
database copies using data backups. You will need to configure (m-n) additional index servers in the
target database. Note: This is currently not supported when using storage snapshots.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
30
SAP HANA Backup and Recovery
Database copy (II)
Using data and log backups – source and target databases may have different number of hosts
Node n
Node 2
Node 2
Index Server
Node 1
Node 1
Index Server
Index Server
Index Server 1
Index Server 1
Index Server 2
Source database
with n nodes
(e.g. PROD)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Data backup
+ log backups
(optional)
Target database
with 2 nodes
(e.g. QA)
Public
31
SAP HANA Backup and Recovery
Database copy (III)
Using snapshot and log backups – source and target databases must have same number of hosts
Node n
Node n
Node 2
Node 2
Index Server
Index Server
Node 1
Node 1
Index Server
Index Server
Index Server 1
Index Server 1
Source database
with n nodes
(e.g. PROD)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Snapshot +
log backups
(optional)
Target database
with n nodes
(e.g. DEV)
Public
32
Tool support and certification
SAP HANA Backup and Recovery
SAP tool support for backup and recovery
SAP HANA studio
DBA Cockpit
hdbsql/command Line
Backup
Recovery
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
34
SAP HANA Backup and Recovery
Backint Certification
Certification is an installation prerequisite for backup tools using the “Backint for SAP HANA” interface.
 SAP Note 1730932 (Using backup tools with Backint)
 Announcement of the certification process
Certified tools (as of 2014-10-13)
Vendor
Backup Tool
Support Process (SAP Notes)
Commvault
Simpana 10.0, Hitachi Data Protection Suite 10 (via Simpana Backint interface)
1957450
EMC
Networker 8.2, Interface for Data Domain Boost 1.0
1999166, 1970559
HP
Data Protector 7.0 and 8.1
1970558
IBM
Tivoli Storage Manager for Enterprise 6.4
1913500
SEP
Sesam 4.4
2024234
Symantec
NetBackup 7.5
1913568
Online listing of certified tools: Application Development Partner Directory
 Enter the search term HANA-BRINT and click on a partner name  ”SAP Certified Solutions” for further details
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
35
What‘s new?
SAP HANA SPS08
SAP HANA Backup and Recovery
What’s new in SAP HANA SPS08?
New Backint certifications (after SPS07)
 Commvault, HP, EMC, and SEP
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
37
More information
SAP HANA Backup and Recovery
More information
SAP HANA documentation
Available on the SAP Help Portal
 SAP HANA Administration Guide,
“Backing Up and Recovering the SAP HANA Database”
 SAP HANA Technical Operations Manual
SAP HANA website
 Backup/recovery overview presentation
Important SAP Notes




1642148: FAQ: SAP HANA database backup and recovery
1730932: Using backup tools with Backint
1869119: Check backup integrity
For further notes on backup/recovery, see HAN-DB-BAC
Backint for SAP HANA certification
 Certification announcement and description
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Public
39
Thank You!
Contact information:
Andrea Kristen, SAP HANA Product Management
andrea.kristen@sap.com
© 2014
2014 SAP
SAP SE
AGor
oran
anSAP
SAPaffiliate
affiliatecompany.
company.All
Allrights
rightsreserved.
reserved.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising