search

HCL-TECH-SOFTWARE / domino-backup

Configuration files for HCL Domino Backup integration with other backup solutions.
https://opensource.hcltechsw.com/domino-backup/
Apache License 2.0
5 stars 4 forks source link

Cannot delete file - File not found #25

Open Aemmer opened 2 days ago

Aemmer commented 2 days ago

Dear all

We are testing backup with VEEAM on Domino 12.0.2 FP4 running on Windows Server 2016. The logs in Domino Backup still shows the hourglass but the backup jobs on the VEEAM side are completed and we are able to restore databases. But we get for each database a log entry "Cannot delete file - File not found" 27.11.2024 23:32:00 Backup: Started 27.11.2024 23:32:00 Backup: Pruning backups 27.11.2024 23:32:00 Backup: FileDelete: [c:\backup\nsf\DomTest\SNAP\20241119223206\activity.ntf] Cannot delete file - File not found 27.11.2024 23:32:00 BackupVSS: Domino Agent VSS Freeze Event received 27.11.2024 23:32:00 Backup: FileDelete: [c:\backup\nsf\DomTest\SNAP\20241119223206\admin4.nsf] Cannot delete file - File not found 27.11.2024 23:32:00 Backup: FileDelete: [c:\backup\nsf\DomTest\SNAP\20241119223206\admin4.ntf] Cannot delete file - File not found

How are the settings for the configuration in Domino Backup for using VEEAM and to get rid of this entries?

Examples of log: grafik

grafik

27.11.2024 23:32:12 Backup: BackupNode: [DomTest], BackupName: [default], Translog Mode: [CIRCULAR], Backup Mode: [SNAP] 27.11.2024 23:32:12 Backup: LastBackupTime: 26.11.2024 23:25:35 27.11.2024 23:32:14 Backup: Starting backup for 263 database(s) [SnapShotMode] 27.11.2024 23:32:15 Backup: Ready for VSS Snapshot 27.11.2024 23:32:15 BackupVSS: DominoVSSWriter::OnFreeze Domino in Freeze Mode after 14 seconds! 27.11.2024 23:32:19 Backup: VSS Post Snapshot status reached after 3 seconds! 27.11.2024 23:32:19 BackupVSS: Sending unfreeze to Domino Backup 27.11.2024 23:32:19 Backup: Capturing changes in 263 database(s) [SnapShotMode] 27.11.2024 23:32:20 Backup: VSS Snapshot Backup finalized 27.11.2024 23:32:20 BackupVSS: DominoVSSWriter::OnPostSnapshot Post backup changes applied after 0 seconds. 27.11.2024 23:32:28 Backup: 27.11.2024 23:32:28 Backup: --- Backup Summary --- 27.11.2024 23:32:28 Backup: Previous Backup : 26.11.2024 23:25:35 27.11.2024 23:32:28 Backup: Start Time : 27.11.2024 23:32:12 27.11.2024 23:32:28 Backup: End Time : 27.11.2024 23:32:20 27.11.2024 23:32:28 Backup: Runtime : 00:00:07.204 27.11.2024 23:32:28 Backup: 27.11.2024 23:32:28 Backup: All : 263 27.11.2024 23:32:28 Backup: Processed : 263 27.11.2024 23:32:28 Backup: Excluded : 0 27.11.2024 23:32:28 Backup: Pending Compact : 0 27.11.2024 23:32:28 Backup: Compact Retries : 0 27.11.2024 23:32:28 Backup: Backup Errors : 0 27.11.2024 23:32:28 Backup: Not Modified : 0 27.11.2024 23:32:28 Backup: Delta Files : 0 27.11.2024 23:32:28 Backup: Delta applied : 0 27.11.2024 23:32:28 Backup: 27.11.2024 23:32:28 Backup: Total DB Size : 29.1 GB 27.11.2024 23:32:28 Backup: Total DeltaSize : 0.0 Bytes 27.11.2024 23:32:28 Backup: Data Rate : 4'134.7 MB/sec 27.11.2024 23:32:28 Backup: --- Backup Summary --- 27.11.2024 23:32:28 Backup: 27.11.2024 23:32:28 Backup: Finished

Thank you for any help! Th. Aemmer

Daniel-Nashed commented 2 days ago

We need your detailed configuration on the Veeam side to understand what is going on. The underlying problem is very likely the problem we are currently working on with Veeam. Domino Backup VSS requires Auto Recovery snapshots to also store the delta files on the Veeam side.

This works well for the following cases:

  1. Using the backup agent on the machine (also on Vsphere)
  2. Using Vsphere storage assisted snapshots with VMware tools

What currently does not work is the Veeam application aware processing and we are researching with Veeam what is happening.

The VMware tools approach requires dependent disks, which is not a configuration every server has or can have depending on your requirements.

The snapshot is a normal snapshot without Auto Recovery where the changes are merged into the snapshot. That's really required here to make it a true VSS consistent Domino backup snapshot.

In addition we would need to look into your prune configuration. The DXL file shipped for the Veeam integration does not need any prune file operations, because all prune operations are performed by Veeam on their repository.

Please make sure you are using the standard DXL file available for the 12.0.2 configuration with VSS writer.

From what I see in the backup logs you are lucky that you are not getting any delta files, because the snapshot is no Auto Recovery snapshot.

Side note:

Your Windows 2016 server should not cause any trouble here. But please not it isn't supported any more. Like Windows 2018 and R2 are not supported any more.

Today you should really running on Windows 2022. I am currently testing with Windows 2025, which is just released and will be supported in Domino 14.5 next year.