- Service Provider
- Posts: 96
- Liked: 6 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
Previous: 2 x ESXi hosts > Server w/ vCenter > Veeam backup job > Veeam copy job
Now: 2 x ESXi hosts > vCenter appliance > Veeam backup job > Veeam copy job
i.e. only change is that we replaced the server with an actual vCenter appliance.
The result is that the copy job considered the VMs in the same source to be "new" and created duplicates in an inflated VIB which completely filled up the copy job repo.
I "deleted VM data from backup" to clean up the copy job chain. This freed up enough space for increments but not inflated increments because of duplicate "new" VM copy data.
Please advise what I need to do to prevent this from happening when I enable the copy job.
- Veeam Software
- Posts: 18555
- Liked: 1606 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Users browsing this forum: Google [Bot], Majestic-12 [Bot] and 13 guests