on 2024 Oct 30 6:34 AM
Hi
Running command below for a HANA 2.0 SPS07 on RHEL 8.6 to check recoverability:
python hdbrecovercheck.py checkPointInTimeReachable -D <SID> -b --backintCatalogParamFile /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/param --backintDataParamFile /usr/sap/<SID>/SYS/global/hdb/opt/ hdbconfig/param --backintLogParamFile /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/param -t "2024-10-27 12:00:00"
29.10.2024 15:27:32 INFO: ==== hdbrecovercheck.py started at 2024-10-29 14:27:32 UTC) (local time: 2024-10-29 15:27:32 CET) = ===
29.10.2024 15:27:32 INFO: Checking backup consistency (untilTime=2024-10-27 12:00:00, backupCatalogPath=None, logBackupPaths= None, dataBackupPaths=None, backintVersion=None, useBackintBackupCatalog=True, backintCatalogParamFile=/usr/sap/<SID>/SYS/global/hd b/opt/hdbconfig/param, backintDataParamFile=/usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/param, backintLogParamFile=/usr/sap/<SID>/SYS /global/hdb/opt/hdbconfig/param, ignoreDeltaDataBackups=False, database=<SID>)
29.10.2024 15:27:32 INFO: Calling hdbbackupdiag -v -t -B -u 2024-10-27\ 12:00:00 --useBackintForCatalog --backintCatalogParam File /usr/sap/<SID>/SYS/global/hdb/opt/hdbconfig/param --databaseName <SID>
29.10.2024 20:09:09 INFO: Successfully checked backup files required for recovery:
COMPLETE_DATA_BACKUP_databackup_0_1/SAP_108511444_12308240
COMPLETE_DATA_BACKUP_databackup_2_1/SAP_108511444_12308240
COMPLETE_DATA_BACKUP_databackup_3_1/SAP_108511444_12308240
COMPLETE_DATA_BACKUP_databackup_3_2/SAP_108511444_12308240
COMPLETE_DATA_BACKUP_databackup_3_3/SAP_108511444_12308240
COMPLETE_DATA_BACKUP_databackup_3_4/SAP_108511444_12308240
log_backup_3_0_4237773075136_4237840183872/SAP_108511444_12308443
log_backup_3_0_4237840183872_4237907284800/SAP_108511444_12308896
log_backup_3_0_4237907284800_4237974393664/SAP_108511444_12309219
29.10.2024 20:09:09 INFO: Point in time 2024-10-27 12:00:00 reachable via backup per volume ID:
29.10.2024 20:09:09 INFO: 2: {'Reachable': None, 'MaxLogPos': 1773975235, 'MaxTimestampReachable': 'unknown (timestamp cannot be determined for a data backup)'}
29.10.2024 20:09:09 INFO: 3: {'Reachable': True, 'MaxLogPos': 4237974393664, 'MaxTimestampReachable': '2024-10-27 13:1 1:33'}
29.10.2024 20:09:09 INFO: Checking whether point in time 2024-10-27 12:00:00 is reachable in log area (if required)
29.10.2024 20:09:09 ERROR: hdbrecovercheck.py checkPointInTimeReachable got unexpected error -
Traceback (most recent call last):
File "hdbrecovercheck.py", line 1573, in main
externalResult, internalResult = args.func(
File "hdbrecovercheck.py", line 193, in checkPointInTimeReachable
internalResult["logArea"] = self._checkLogArea(database=database,
File "hdbrecovercheck.py", line 1012, in _checkLogArea
databackupMaxLogPosPerVolumeId, persGuidPerVolumeId, guidsFromLogBackupsPerVolumeId, lastRedoLogPosPerVolumeId = self._ext ractGuidsFromBackups(backupsPerVolumeId=backupsPerVolumeId)
File "hdbrecovercheck.py", line 1076, in _extractGuidsFromBackups
assert databackupMaxLogPos is None or backup["RedoLogPosition"] > databackupMaxLogPos
AssertionError
29.10.2024 20:09:09 INFO: ==== hdbrecovercheck.py finished at 2024-10-29 19:09:09 UTC) (local time: 2024-10-29 20:09:09 CE T) ====
We use 3rd party backup tool Commvault and reason why we check recoverability, is because we face huge timestamp differences between our point-in-time timestamp and actual point-in-time restore timestamp.
Best regards
Bert
Request clarification before answering.
User | Count |
---|---|
30 | |
22 | |
16 | |
8 | |
7 | |
7 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.