Case Support Number: 07886415
I'm facing an issue where I’m unable to delete obsolete and duplicated restore points stored in a Performance Tier repository.
During the investigation, I noticed that the obsolete/duplicated restore points are marked with the GFS flag, while the current points in the backup chain are not. Because of this, the system is not allowing the removal of those restore points, even though they should not be retained according to the job’s configuration.
A repository rescan has already been performed, and the job/session logs show the deletion task as "successful", but the .VBK and .VIB files are never actually removed from disk.
We urgently need to remove these obsolete restore points to free up space on the local disk repository.
Questions:
Is there any known workaround for this behavior?
Could this be related to metadata inconsistency introduced after a vCenter migration?
Is there a recommended procedure to force synchronization and properly remove GFS-flagged points that should not be retained?
Any help or guidance from the community or Veeam engineers would be greatly appreciated.
Thank you.
-
claudiohipolito
- Influencer
- Posts: 10
- Liked: 1 time
- Joined: Jan 16, 2025 12:50 pm
- Full Name: Claudio Hipolito nunes
- Contact:
-
Mildur
- Product Manager
- Posts: 11047
- Liked: 3038 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Unable to Delete Obsolete/Duplicated Restore Points in Performance Tier Repository (GFS Flag Issue)
Hi Claudio,
Welcome to the forum.
It’s best to continue working through your existing support case rather than starting a parallel investigation here.
If the issue is urgent, you can manually delete the VBK files and their related VIBs from the file system, then perform a repository rescan. Keep in mind that on Fast Clone–enabled repositories, the reclaimed space may be less than expected.
Best regards,
Fabian
Welcome to the forum.
It’s best to continue working through your existing support case rather than starting a parallel investigation here.
If the issue is urgent, you can manually delete the VBK files and their related VIBs from the file system, then perform a repository rescan. Keep in mind that on Fast Clone–enabled repositories, the reclaimed space may be less than expected.
Best regards,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot], Google [Bot], pybfr and 34 guests