![]() We may decide 99GB are available, but that's not correct. It uses its cache considering the size of VMs currently being backed up.įor instance, in 15 minutes we will try to assign resources for a new task, the meanwhile first one only created storage and started writing into it, having taken only 1GB for now. While there is at least 1 active task Veeam does not update for free space information. Veeam now thinks 95GB is available on this extent. Requested free space for its full backup will be 5GB (50% of VM size). When resources for backup of a certain VM are assigned, we check the space it will take. Veeam caches free space information from the database. This issue is related to the logic of how Veeam calculating space available on SOBR extents. ![]() ![]() Will see tomorrow if these settings have some affect. I removed some old backup from the storage as well. ![]() I got this reply from support - I also added the registry in the KB2282 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |