-
- Veteran
- Posts: 531
- Liked: 58 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
Choosing an individual VM in backup copy
Folks,
I have a backup job that backs up several VMs in VMware, and I have a Legacy backup copy job that backs up only one of those VMs, in order to produce a GFS chain for that VM only.
Now I have upgraded the backup chain for the source backup job, and now I get a warning in the Legacy backup copy job saying:
"Legacy backup copy jobs do not support new backup chain format of the source backup.
Please recreate a backup copy job and map your existing backup files to the new job."
The problem is, that when I create a new backup copy job, I don't have the option to choose only one VM to backup, I can only choose a backup job or a repository as the source. I don't remember how I managed to create a backup copy job with only one VM, because it was a long time ago. Perhaps that option existed back then?
Is there any way to continue the GFS backup copy chain in a new backup copy job? Or do I have to create a new source backup job for only this VM, and then create a new backup copy job, and choose that new backup job as the source? And then remove the old backup copy job and let the existing GFS chain be orphaned?
Kind regards,
PJ
I have a backup job that backs up several VMs in VMware, and I have a Legacy backup copy job that backs up only one of those VMs, in order to produce a GFS chain for that VM only.
Now I have upgraded the backup chain for the source backup job, and now I get a warning in the Legacy backup copy job saying:
"Legacy backup copy jobs do not support new backup chain format of the source backup.
Please recreate a backup copy job and map your existing backup files to the new job."
The problem is, that when I create a new backup copy job, I don't have the option to choose only one VM to backup, I can only choose a backup job or a repository as the source. I don't remember how I managed to create a backup copy job with only one VM, because it was a long time ago. Perhaps that option existed back then?
Is there any way to continue the GFS backup copy chain in a new backup copy job? Or do I have to create a new source backup job for only this VM, and then create a new backup copy job, and choose that new backup job as the source? And then remove the old backup copy job and let the existing GFS chain be orphaned?
Kind regards,
PJ
-
- Veeam Software
- Posts: 2346
- Liked: 555 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Choosing an individual VM in backup copy
Hi Per!
For limiting what gets copied by the Backup Copy jobs, use the exclusion options: https://helpcenter.veeam.com/docs/backu ... clude.html
As for continuing, it depends on the Backup Copy mode; for the latter two cases, a new backup set will be made for the Backup Copy, but for first it should auto-remap. The old chain will go to Orphaned Backups and Background Retention will handle retention.
For limiting what gets copied by the Backup Copy jobs, use the exclusion options: https://helpcenter.veeam.com/docs/backu ... clude.html
As for continuing, it depends on the Backup Copy mode; for the latter two cases, a new backup set will be made for the Backup Copy, but for first it should auto-remap. The old chain will go to Orphaned Backups and Background Retention will handle retention.
David Domask | Product Management: Principal Analyst
-
- Veteran
- Posts: 531
- Liked: 58 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
Re: Choosing an individual VM in backup copy
The old Legacy backup copy job used the "Periodic copy" mode and a single metadata file.
What happens if I create a new backup copy job, choose the source backup job, exclude all VMs except the VM in question, and then click on "Map backup" and point it to the existing GFS chain?
What happens if I create a new backup copy job, choose the source backup job, exclude all VMs except the VM in question, and then click on "Map backup" and point it to the existing GFS chain?
-
- Veeam Software
- Posts: 2346
- Liked: 555 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Choosing an individual VM in backup copy
In the case of Periodic mode upgrades, the previous chain will not be possible to continue (i.e., no mapping to the previous chain) as noted in the User Guide:
So the old chain will still be usable for restores and will be handled by Background Retention, but the new job will start its backup set anew.Veeam Backup & Replication will start a new backup chain in the required format and will place the backups used for mapping to the orphaned node and retain them according to the background retention. For more information on when the background retention applies, its limitations and considerations, see Background Retention.
David Domask | Product Management: Principal Analyst
-
- Veteran
- Posts: 531
- Liked: 58 times
- Joined: Jun 06, 2018 5:41 am
- Full Name: Per Jonsson
- Location: Sweden
- Contact:
Re: Choosing an individual VM in backup copy
Yes, I did that, and the old GFS chain went orphaned, and a new chain was created with one full backup in it.
Thank you!
PJ
Thank you!

PJ
Who is online
Users browsing this forum: Baidu [Spider], Semrush [Bot] and 33 guests