Log backups
Archived logs for databases contain committed transaction data. This transaction data can be used to run a database recovery when you are running a restore operation. Using archive log backups enhances the recovery point objective for your data.
Ensure that you select the Enable Log Backups option to allow point in time recovery when you set up a backup job or service level agreement (SLA) policy. When selected for the first time, you must run a backup job for the SLA policy to activate log archiving to IBM Storage® Protect Plus on the database. This backup creates a separate volume on the vSnap repository, which is mounted persistently on the SAP HANA application server. The backup process updates the configuration parameters basepath_logbackup, and basepath_catalogbackup in the global.ini configuration file, which is in the persistence section of the target SAP HANA instance. Both parameters will be updated to the NFS mount point of the vSnap volume.
- log_mode is set to normal
- log_backup_using_backint is set to false
- enable_auto_log_backup is set to yes
The vSnap volume is kept mounted on the SAP HANA application server unless the Enable Log Backup option is cleared and a new backup job is run. During a disable log backup, the mentioned parameters will be reset to their previous values.
Truncating archive log backups
IBM Storage Protect Plus automatically deletes older transactional logs after a successful database backup. This action ensures that the capacity of the log archive volume is not compromised by retention of older log files. These truncated log files are stored in the vSnap repository until the corresponding backup expires and is deleted. The retention of database backups is defined in the SLA policy that you select. For more information about SLA policies, see Defining a Service Level Agreement backup job.
IBM Storage Protect Plus does not manage the retention of other archived log locations.