- Posts: 1
- Liked: never
- Joined: Aug 28, 2014 12:38 pm
- Full Name: Paul Jenkins
The problem is that Veeam has no way of knowing that files on shared data-stores belonging to servers outside of the current scope are required and not garbage.
I'd really like to see this problem addressed, as quickly as possible.
This was reported to Veeam Support in Case #00604751.
- Veeam Software
- Posts: 6413
- Liked: 611 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
I see your concern; but, it`s not typical to have 2 vCenters sharing one datastore. Could you explain why you decided to go for such type of configuration?
The reason why Garbage Files Report shows more files than you expected as garbage is in report`s logic. The report shows an overview of storage consumed by all files that do not belong to VMs registered in VI inventory. For instance it helps to find VMs which were removed from inventory, but not deleted from datastore.citpaj wrote:The problem is that Veeam has no way of knowing that files on shared data-stores belonging to servers outside of the current scope are required and not garbage.
In your case, if you choose one of VCs in the scope, Veeam One will report all not related to the VC files as garbage, including VMs of the second VC and vice versa.
If you choose all VI, which contains 2 VCs sharing same datastore, Veeam One will first check all datastores(one in your case) of the first VC for garbage files, then all datastores(same one in your case) for garbage files.
For cases where single datastore is not shared by several VCs, the Garbage Report doesn`t have that kind of problem.
So once again, let me ask why have you decided to use one datastore by 2 VCs? You can split it into 2 parts, and avoid the issue.
Users browsing this forum: No registered users and 2 guests