VEEAM - VM No longer appearing in backup job

[CHiLL]

For some reason, our staff file server VM started to fail backing up on Wednesday last week. Previous job reports had been showing warnings on disk space (less than 10% remaining), which was rectified on Friday, but the job still completed sucessfully. However on Thursday, the backup completed but the verification failed with the error:

Failed to perform backup file verification Error: The network path was not found. Failed to read data from the file [\\10.22.11.98\Veeam_Backups\SJW-STAFF\SJW-STAFFD2019-09-25T220135.vbk]. Agent failed to process method {Signature.FullRecheckBackup}.

 

Then the job failed it's rety with the following similar error:

Failed to perform backup file verification Error: The network path was not found. Failed to read data from the file [\\10.22.11.98\Veeam_Backups\SJW-STAFF\SJW-STAFFD2019-09-25T220135.vbk]. Agent failed to process method {Signature.FullRecheckBackup}.

Nothing to process. All machines were excluded from task list.

 

Then the job finished with a warning on Friday with the following:

Backup location [\\10.22.11.98\Veeam_Backups] is getting low on free disk space (2.0 TB free of 21.3 TB).

Nothing to process. All machines were excluded from task list.

 

When I select the job in VEEAM, the VM doesn't appear in the VM list at the bottom (next to where the job log appears). However if I go into the properties of the job and go to select the VM - it is there in the list, with a size listed. If I press recalculate, the size refreshes. When I press Finish, the VM still doesn't appear in the VM list.

 

No changes have been made to that job this calendar year and the backup files (we use reverse incremental, .vbm, .vbk and .vrb files) do appear in the backup directory. I've performed a rescan of our infrastructure, but that's not made a difference.

 

I'm going to restart the server in a couple of hours, once a file copy completes, to see if that helps. Otherwise I'm at a loss. I could remove the VM from the job and re-add it in, but that'd create another chain. Not the end of the world, but for space reasons, I'd like to avoid that if I can.

 

We are using VEEAM 9.5.4.2753, with no active support contract at present.

Edited September 30, 2019 by CHiLL

[kmount]

Hello,

 

On the job where you see it in the list - look at the exclusions - https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_excludes_vm.html?ver=95u4

 

I have seen disks/VMs land in here that leads to this confusion - though mostly on a copyjob/replication.

 

Cheers,

 

Kim

[CHiLL]

Hello,

 

On the job where you see it in the list - look at the exclusions - https://helpcenter.veeam.com/docs/backup/vsphere/backup_job_excludes_vm.html?ver=95u4

 

I have seen disks/VMs land in here that leads to this confusion - though mostly on a copyjob/replication.

 

Cheers,

 

Kim

Thanks for the response. The exclusion list on the VMs tab is empty. The Disks tab lists the VM and under 'Disks to process' states 'All disks'. The Templates tab is set to backup templates and exclude them from incremental backups.

[kmount]

That looks alright then there - it may simply show up when you run the job again (as opposed to a retry) - it reads to me as its frozen it out on the retry - the retry then completes but remarks all vms processed (Except the excluded one).

 

A fresh run of the job should bring it in.

[CHiLL]

It appears to be working now, I'll check it in the morning, after tonights scheduled job.

 

Here's what I did;

- Recaclulate the VM size in the properties of the job

- Re-scan the backup infrastructure

- Disabled the job, adjusted the start time, enabled the job

- Disabled the job, adjusted the start time back to normal, enabled the job

- Restarted the Veeam service

 

I then started the job and the VM appeared in the list again. I cancelled the job before it mounted the VM and will wait for it to run as scheduled this evening. I don't know if it was a specific one, a combination of, all of or even none of the above that did the trick...but here's hoping!