SAP HANA Database Backup and
Recovery (New and Changed)
A number of enhancements and new features have been added to SAP
HANA backup and recovery as of SAP HANA 2.0 Platform SPS 00.
ENHANCEMENTS FOR LOG BACKUPS
Using SAP HANA, all the log segments of a service, which are ready
to be backed up at the same time, can be written to a single log backup
to improve performance. For each log backup, you can specify a
maximum file size.
As well as file-based log backups, third-party tools also support this option
for log backups.
Details: Writing Multiple Log Segments to a Single Log Backup.
Log backups can be triggered by events in SAP HANA 2.0.
By default, a log backup is created as soon as a log segment fills up, or
when the service-specific timeout for a log segment has been reached for
that segment.
A log backup can also be specified to be created only if a service-
specific timeout has been reached, if you prefer that option.
As well as file-based log backups, third-party tools also support this option
for log backups.
There is more information on the website: Related Information allows you
to set the Interval Mode for Log Backups
ENCRYPTION AND BACKUP AND RECOVERY
Data encryption is supported in SAP HANA 2.0's persistence layer.
When it comes to encryption root keys, the database administrator must
make sure they've been copied and stored somewhere safe. It's important
for a database administrator to import the root keys before performing a
recovery.
There is more information on the website: Notables: SAP HANA Backups
and Encryption, Root Key Backup, and Import Backed-up Root Keys in
Related Information.
LOCATION OF THE BACKUPS OF THE BACKUP CATALOG
Unlike the backup catalogue, the location of log backups is configured
separately.
To recover SAP HANA, you must specify the path to the backup catalogue
before you can proceed.
More information: Backup Catalog Backup Destination Information
SAP HANA MULTITENANT DATABASE CONTAINERS
Using a data backup of a SAP HANA single-container system, it is now
possible to restore a tenant database from a SAP HANA backup.
There is more information on the website: When copying a database with
Backup and Recovery, Please take note of the following: SAP HANA
Multitenant Database Containers & Backup, SAP HANA Multitenant
Database Containers and Recovery in Related Information are important to
note.
EXTENSION NODE FOR BUSINESS WAREHOUSE
With SAP HANA 2.0, the extension node for Business Warehouse can be
used to recover the database.
Details: SAP HANA Recovery and Data Temperature: Business
Warehouse Extension Node in Related Information
SAP HANA ON IBM POWER SYSTEMS: RELEASE
COMPATIBILITY
Only IBM Power Little Endian (LE) systems are supported by SAP HANA
2.0.
SAP HANA 2.0 backups are compatible with both supported hardware
platforms (Intel and IBM Power). It is possible to restore SAP HANA 2.0
from backups created with SAP HANA 2.0 on either an Intel-based or an
IBM Power-based platform.
You can restore SAP HANA 2.0 to both Intel-based and IBM Power-based
systems using backups created with SAP HANA 1.0 SPS 10 or later
running on an Intel-based system. IBM Power-based backups created with
SAP HANA 1.0 cannot be used to restore SAP HANA 2.0.
Important Notes about SAP HANA on IBM Power Systems
SAP HANA COCKPIT (CHANGED)
It's now possible to use a new and improved SAP HANA cockpit.
With the change to the SAP HANA recovery and backup procedures using
SAP HANA cockpit, the guide has been updated.
Additionally, you can find more information in Related Information about the
following topics: SAP HANA System Administration (New and Changed)
and Schedule Data Backups (SAP HANA Cockpit).
