Veeam 9.5.0.1922
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.
Thanks!
-
- Veteran
- Posts: 316
- Liked: 48 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
- Location: Kannapolis, North Carolina, USA
- Contact:
-
- Veteran
- Posts: 316
- Liked: 48 times
- Joined: Apr 07, 2015 1:53 pm
- Full Name: James Wilmoth
- Location: Kannapolis, North Carolina, USA
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Copy job creating duplicates
Hi James, not only do copy jobs get affected but regular backup jobs as well, since VM IDs are changed upon migration to a new vCenter Server. You should either perform an in-place upgrade or use native migration assistant. Thanks!
Who is online
Users browsing this forum: No registered users and 23 guests