Hi all,
after v11 upgrade, sometimes I happened to notice the corruption of the .vbm file when the space on the repository runs out.
I opened the Case # 04770441, the solution was to delete/rename the corrupted .vbm and run the job again.
Is this a normal behavior? Has anyone else had the same problem?
I don't remember that with previous versions the same thing happened in case of running out of space on the repository ..
Thanks
Marco S.
-
- Veeam Legend
- Posts: 351
- Liked: 36 times
- Joined: Oct 24, 2016 3:56 pm
- Full Name: Marco Sorrentino
- Location: Ancona - Italy
- Contact:
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: VBM corruption
Hi Marco,
Basically, it's one of the most frequent causes of metadata corruption in all versions. But why does your repository run out of space? I'd be focused on this issue, maybe you should consider the Scale-Out Backup Repository to avoid problems with free space.
Thanks!
Basically, it's one of the most frequent causes of metadata corruption in all versions. But why does your repository run out of space? I'd be focused on this issue, maybe you should consider the Scale-Out Backup Repository to avoid problems with free space.
Thanks!
Who is online
Users browsing this forum: Majestic-12 [Bot] and 77 guests