Hi Veeam,
We have a headache around failures we cant do anything about regarding SureBackup.
Scenario:
We have upgraded OS on several VM's. Old VM's got NIC dettached and a backup has run. Now we get errors every runbecause VM's has no NIC assigned.
As SureBackup takes action from latest restorepoint in chain, and the present possibility to exclude VM's from present VM's in the job we have no otherway to come around this other than waiting retention policy out (1 year and surebackup runs every week) or upgrade backup chain to move backup data from chain (for now upgrading backup chain is not an option).
Feature Request is therefor to exclude on present backups in the chain, and not only from VM's in the job.
Thanks
-
- Service Provider
- Posts: 15
- Liked: 2 times
- Joined: Feb 15, 2021 8:31 am
- Full Name: RH
- Contact:
-
- Veeam Software
- Posts: 2325
- Liked: 554 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: FR - List for exclusions based on backups on disk for job in questions
Hi Rh,
Just to make sure I get your request correctly, the situation is:
1. VMs were upgraded and as a result, the NIC got removed from these VMs
2. A backup was taken when the VM did not have a NIC
3. Surebackup now fails because of this
Is it intentional that these machines do not have a NIC? Or will it be re-attached later?
I'm just having a little trouble understanding the difficulty, as if you're re-attaching the NIC later, once a backup is done with the NICs re-attached, everything should work as expected, but I think I'm not quite getting the scenario correctly, so can you perhaps elaborate?
Also, I'm not sure I understand in full why temporarily excluding the VMs from the Surebackup job is not an option right now, but I suppose once you clarify I'll be better able to advise on this also.
Just to make sure I get your request correctly, the situation is:
1. VMs were upgraded and as a result, the NIC got removed from these VMs
2. A backup was taken when the VM did not have a NIC
3. Surebackup now fails because of this
Is it intentional that these machines do not have a NIC? Or will it be re-attached later?
I'm just having a little trouble understanding the difficulty, as if you're re-attaching the NIC later, once a backup is done with the NICs re-attached, everything should work as expected, but I think I'm not quite getting the scenario correctly, so can you perhaps elaborate?
Also, I'm not sure I understand in full why temporarily excluding the VMs from the Surebackup job is not an option right now, but I suppose once you clarify I'll be better able to advise on this also.
David Domask | Product Management: Principal Analyst
-
- Service Provider
- Posts: 15
- Liked: 2 times
- Joined: Feb 15, 2021 8:31 am
- Full Name: RH
- Contact:
Re: FR - List for exclusions based on backups on disk for job in questions
You are correct.
Issue is that OLD VM that got NIC deleted/dettached is now deleted from environment, and last backup was done of the VM without a NIC.
I cannot exclude VM's from the list of backups on disk, but only for VM now present in the job list.
I can show you issue on a session if you like.
Issue is that OLD VM that got NIC deleted/dettached is now deleted from environment, and last backup was done of the VM without a NIC.
I cannot exclude VM's from the list of backups on disk, but only for VM now present in the job list.
I can show you issue on a session if you like.
-
- Lurker
- Posts: 1
- Liked: 1 time
- Joined: Dec 07, 2018 11:42 am
- Full Name: Manuel Knörr
- Location: Germany
- Contact:
Re: FR - List for exclusions based on backups on disk for job in questions
Hi,
following up here, even though the thread is from earlier this year.
We have similar problem with surebackup of single VMs in big backupjobs. I would like to exclude all other VMs that have been part of the job. At the moment, we can only exclude VMs that are configured in the job right now.
Since some of our VMs have been decommisioned from production, we removed them from the backupjob.
However, because of retention policies there still are backups of those VMs linked to the job in our repository.
Because I can not exclude them, SureBackup will always check them.
Therefore we would need to exclude VMs based on the backups in the job instead of the current job configuration.
following up here, even though the thread is from earlier this year.
We have similar problem with surebackup of single VMs in big backupjobs. I would like to exclude all other VMs that have been part of the job. At the moment, we can only exclude VMs that are configured in the job right now.
Since some of our VMs have been decommisioned from production, we removed them from the backupjob.
However, because of retention policies there still are backups of those VMs linked to the job in our repository.
Because I can not exclude them, SureBackup will always check them.
Therefore we would need to exclude VMs based on the backups in the job instead of the current job configuration.
Who is online
Users browsing this forum: Ahrefs [Bot], Baidu [Spider], Bing [Bot], Semrush [Bot] and 72 guests