Author 
To ensure recoverability of the SAP HANA database, you want to check if the required data and log backups are present and undamaged.
Reason and Prerequisites
- You use an SAP HANA database Revision 64 or higher.
- To protect business operations after system failures, database backups are created manually or automatically at regular intervals. However, recoverability of the database can only be ensured if all necessary backups are present and undamaged during the recovery process. Before starting a recovery, you can, therefore, check whether all backups are available and undamaged.
Solution
By calling hdbbackupdiag with the --check option, you can verify if the available backups are suitable for recovering the HANA database at a particular time. The backups used may be present in any directory in the file system or in an external backup tool.
The hdbbackupdiag tool determines which backups are required to comply with the required point in time and checks whether these backups are available and accessible. It then executes the following checks:
For backups that were written to the file system:
- - the file is contained in the file system either at the location to which it was written or at a location specified by a search path
- - the current operating system user has read authorization for the file
- - the file is large enough to accommodate the usable load stored at the start of the file
- - the file's backup ID corresponds to the backup ID specified in the backup catalog
For backups written to an external backup tool:
- - the backup is contained in an external backup tool
Note the following: The hdbbackupdiag tool does not check the content of the backups for consistency. To check individual backups for consistency, you can use the program hdbbackupcheck
Call hdbbackupdiag --check
hdbbackupdiag --check [options]
Options:
-d : Specify the directory in which you are searching for the backup catalog. If this option is not available, a search is carried out for the latest version of the backup catalog in the current directory and, if necessary, in the directories specified with --logDirs and in the external
backup tool.
-c : Specify a file name for the backup catalog
-i : Specify a backup ID for a data backup: this ID should be used as the basis for recovery. If this option is not available, you can use the most recent suitable data backup.
-u "YYYY-MM-DD HH:MM:SS": Specify a time in UTC as the recovery target. If this option is not available, the most recent possible point in time is used.
--dataDir : Specify a directory in which to execute a search for data backup files. If this option is not available, a search is only carried out for the data backup files in the paths noted in the backup catalog.
--logDirs : Specify a comma-separated list of directories where a search is executed for log backup files. If this option is not available, a search is only carried out for the log backup files
in the paths noted in the backup catalog.
--useBackintForCatalog: If this parameter is specified, a search is also carried out in the third-party backup tool for the most recent version of the backup catalog.
--backintDataParamFile : Specify a parameter file for accessing data backups via an external backup tool
--backintLogParamFile : Specify a parameter file for accessing log backups via an external backup tool If this parameter is not specified, the parameter file used for accessing the data backups is also used here.
Bear in mind that all directories must be specified as absolute paths.
This restriction does not apply to file names like, for example, in the case of the --backintDataParamFile option.
hdbbackupdiag --check: mode of operation
The program searches for the most recent version of the backup catalog in the directories specified in the command line and also, if necessary, in the external backup tool. From the backup catalog found, the system determines which data
and log backups are required for a recovery, taking into account the specified options. The above-mentioned checks are executed for these backups.
The program indicates which backup catalog is used, which backups are required for the necessary recovery and for which backups the checks were either successful or failed.
If the checks for all backups required for the recovery were successfully completed, the return value of the program is 0; otherwise, the value 1 is returned.
For example:
All backups are written to the default paths in the file system and are still available there:
> hdbbackupdiag --check -d $DIR_INSTANCE/backup/log
using newest backup catalog /usr/sap/IW2/HDB02/backup/log/log_backup_0_0_0_0.1371126898275
using backup catalog 1371126898275 from file /usr/sap/IW2/HDB02/backup/log/log_backup_0_0_0_0.1371126898275
Backup '/usr/sap/IW2/HDB02/backup/data/COMPLETE_DATA_BACKUP_databackup_0_1' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/data/COMPLETE_DATA_BACKUP_databackup_1_1' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/data/COMPLETE_DATA_BACKUP_databackup_2_1' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/data/COMPLETE_DATA_BACKUP_databackup_3_1' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/data/COMPLETE_DATA_BACKUP_databackup_4_1' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/log/log_backup_1_0_481920_492928' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/log/log_backup_2_0_524224_641600' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/log/log_backup_3_0_709376_710272' successfully checked.
Backup '/usr/sap/IW2/HDB02/backup/log/log_backup_4_0_1235008_1369728' successfully checked.
> echo $?
0
More Details Refer Snote :1873247
