Restore Points Missing

[ec.bryantu]

Hi, we have a Veeam setup with Exagrid at our main site and DR site. Right now the main site does all the backup jobs and saves to Exagrid and then the two Exagrid appliance replicate data between eachother. We have Veeam setup at the DR. At the DR site, I thought that I would be able to rescan the backup repository that was created and it would show all the restore points that have been replicated from the main site. But on some servers I am only seeing 1 restore point from like 2023. Any ideas why this might be happening?

[david.domask]

Hi Eric,

First, I must note that we don't have support for the Exa=>Exa replication, so please be prepared that we may be inhibited by this lack of integration with it.

The rescan process imports backups based on the .VBM file (backup metadata), so I'm guessing there must have been issues either with the replication not getting the VBM files correctly or something during the rescan/import.

I would advise open a Support Case and let Support review the logs. Use the 3rd radio button to export logs from the Veeam server itself, and note the name of the DR Exagrid repository. We need logs from the DR Veeam server where you attempted the import from. Mention that the focus is why the repository rescan did not import backups from the Exagrid, and support can check the debug logs and see what our rescan process encountered.

Please share your case number here once created, thanks!

[ec.bryantu]

Opened a case already (07600376). I also opened one with Exagrid and they confirmed site to site replication is working as expected. Seems to be a Veeam issue. I will work on getting logs uploaded.

[ec.bryantu]

Looks like when I Rescanned it today it found more files. Why does Veeam not provide a way to schedule a Rescan of backup repository at a DR site?

[david.domask]

Hi Eric,

Glad to hear some more files are appearing, perhaps it has to do with timing on the replication. While I understand your point on a scheduled rescan, please keep in mind that the storage <> storage replication you're using isn't integrated with Veeam -- with other means of maintaining secondary copies, Veeam is aware of the copy process and thus tracks the DR copies as well.

Thank you for sharing the case number, however, I don't see logs on the case currently -- I can see that some items got skipped during the rescan, so I think it's best to continue with Support and review what the challenges on the rescan import were.

I would strongly advise however using a supported method for the DR copies such as our Backup Copy Job. While I understand the benefits of the storage level replication, without proper integration it's expected to have challenges as you have two technologies unaware of each other that may have conflicting behaviors.