Planning for space required for SAP HANA backups

Before Data Protection for SAP HANA sends data to Tivoli® Storage Manager, it notifies the Tivoli Storage Manager server of the amount of data that is going to be sent. This enables the Tivoli Storage Manager server to select the appropriate storage pool that accommodates this specific amount of data.

About this task

Through the backint SAP HANA interface, Data Protection for SAP HANA does not know the amount of data that is due to be sent by SAP HANA. It is assumed that half of the memory size is to be transferred. If the system has 1 TB RAM, then the estimated size for the backup object is assumed to be 512 GB. For the data that is stored by the SAP HANA indexserver this number is close to the value for a fully used system. For other SAP HANA services like nameserver or statisticserver, the value is much smaller. Typically the backups of these services are several MB only, and a backup can result in a storage pool that is intended for large objects being used.

Procedure

To avoid backing up small items to the next storage pool in line, the required size of the first storage pool should be at least half the size of the appliance memory multiplied with the number of sessions (SESSIONS, MAX_SESSIONS) that are simultaneously sending files. If you use the maxsize parameter for the first storage pool, make sure it is at least half the size of the appliance memory.
Another option is to use Virtual Tape Library for backups.