Entire job failing for one missing vm

[didier-hosteur]

Hi,

I have a veeam server backuping one big vcenter 5 server.
Rather than backuping all the vcenter then adding vms to exclude list, i manually check vm to be backed up.
When my admin system removes vm (on purpose) the entire job fails but only that lissing vm should be failing.

Any idea how i could fix that ? Giving that i really need not to use the exclude list (vm are added automatically to vcenter all day, not all to be backed up).

Thanks !

[Gostev]

Hello - the job should not be failing in this case, only missing VM should. Other VMs should be backed up normally. If you are not seeing this, please open a support case. Thanks!

[yizhar]

Hi.

I suggest that you consider using VMware folders in vcenter, then configure Veeam to backup by folder.
Instruct VMware admins to create VMs in the appropriate folder.
For example, a "test" or "dev" folder will have different backup jobs if any,
while "production" (or more specific folder if you like) will be selected for regular backups.

Yizhar

[didier-hosteur]

Hi,

The job failing only shows the one VM not found, which it realizes when creating VM list then does not proceed the other VMs.
I thought of vmware folders but not quite something i want to setup.

I guess I'll have to open a support case.. But i think this behavior is a mess

[foggy]

Sure, the most efficient way to address issues like that is opening a case with our technical team. It would be much appreciated if you could update the thread on the results of the investigation. Thanks.

[Vitaliy S.]

When my admin system removes vm (on purpose) the entire job fails but only that lissing vm should be failing.

Do you possibly mean that the job status has a failed status? Can you please open the corresponding job session and check what the protection status for other VMs?

[didier-hosteur]

Hi,

Sorry, i was on vacation.

Here are two screenshots. On the first you can see they are many other objects in the job.

[foggy]

In fact there is only one VM in the job (sds-135...), according to the screenshot.

[veremin]

Also, the screenshots contain information about retries only.

From the information given, the whole situation seems to be expected - the only VM that hadn’t been backed up successfully fell into job retries. Because VM wasn’t backed up even during retries, retries finished with the “Failed” status.

Thanks.

[didier-hosteur]

I just feel so dumb :/

I'm deeply sorry for having asked such a dumb question, really ^^'

I didn't take under advisement that it was showing the 3rd retry, meaning on first try the other VMs in the job went fine.

Thank you very much for your time and again.. sorry

[veremin]

You’re welcome. Glad to hear that the whole situation has been finally clarified, and that today you can enjoy backup/replication functionality without any issues. Thanks.