No HANA point in time retore possible if time lies after the last log backup.

Hi @dcvadmin 

Was “Initialize log area” option selected during the restore?

Please unselect “Initialize log area”  option and rerun the restore

https://documentation.commvault.com/2022e/expert/22526_faqs_sap_hana_idataagent_01.html

Initialize Log Area Option

When you select the Initialize Log Area option, the software only replays the log entries from the backup when it is required. The following are the most common scenarios when you use the option:

Note: Consider your environment when you choose the option.

• When you have a corrupt catalog

• When the log area is not usable

• When you perform a database copy or a system copy

Data Only Restore

The following are the most common scenarios when you use the option:

• When the catalog is corrupted

• When you do not want to replay the logs

Point-in-Time Catalog Restore

The following are the most common scenarios when you use the option:

• When the most recent catalog backup is corrupted

• When you perform multiple restore operations with the Initialize Log Area option

Regards,

Gowri Shankar 

Hi @dcvadmin 

Do you mean even with “Initialize log area” disabled, the recover to PIT after the last log backup isn’t working?

Is restore to latest time working and using the most recent logs?

Thanks,

Sunil

Hi @dcvadmin 

Would you mind running the same test from HANA studio or cockpit and see if it’s using the locally available logs for recovery?

Commvault generates the same recover syntax and HANA requests for the required logs. I believe this isn’t a vendor side issue, but would like to double check by running recovery from HANA studio.

Thanks,

Sunil

Hi @dcvadmin 

Ah.. I got it. Snapshot backup can be restored only through Commvault UI. I was thinking it’s a streaming backup.

Are you doing snap revert or non-revert restore?

Thanks,

Sunil-

I now understand why this behavior is. For hardware revert we always Initialize log area whether or not it’s selected in the GUI. We have had customer issues when data and log paths are on same volume and when snap revert is done the log area is also overwritten and can’t be used for recovery.

But for restore without hardware revert selected, we don’t Initialize log area.

Thanks,

Sunil

Hi Frank,

Can you raise a support ticket to relax this? We can leave it to the user whether or not to Initialize log area. We may have to run some more tests in the lab though.

Thanks,

Sunil

@Sunil : please please leave this decision to the customer! If necessary with a demand / a hint to dangers if the log area is on the same volume as the data area

@Sunil :

1.) even if the customer had not used “hardware reverse” (till now), it is extremly necessary that there is an option to init or not to init the log area (as I metioned maybe with a warning that the log area should not be on the data volume). Restore from SnapShot via hardware revert is by far faster than restore via copy from mounted snapshot (like the actual choosen way) and there should be a way for PiT recovery to a nearly actual time (maybe only one table was droped by mistake and the customer don’t want to loose all other changes since the last log backup).

2.) I don’t understand why you see in the logs that the option “init log area” was activated. Our customer who tested the restore nows, that this is wrong for a PiT recovery with time < last log backup (note: he uses the html GUI and not the java GUI). What else can be the reason for not be able to perform a PiT < last log Backup?

Best regards and thanks for your help !!

Frank