No storage snapshot in Veeam B&R after 3PAR failover

No storage snapshot in Veeam B&R after 3PAR failover

Recently I had a strange behavior when creating 3PAR snapshots in Veeam Backup&Replication after a site-failover (Peer-Persistence) occurred. Snapshot-jobs stop with error, backup-jobs using 3PAR integrated snapshots jobs are still running because they  failed over to NBD. Snapshot-jobs were configured using secondary 3PAR for snapshots too – see more information here.

Management console showed the following error for snapshot-jobs:
VM VM name does not meet the requirements for storage snapshot based jobs

Because the job worked fine until the failover event, this error is strange. Even the log file of the snapshot-job does not show much more:

[11.07.2019 09:34:13] Error VM VM name does not meet the requirements for storage snapshot based jobs at Veeam.Backup.Core.CViSanSnapshotOnlyJobPerformer.ExecuteTask(IVmBackupTask task)
[11.07.2019 09:34:13] Error VM VM name does not meet the requirements for storage snapshot based jobs (System.Exception)
[11.07.2019 09:34:13] Error at Veeam.Backup.Core.CViSanSnapshotOnlyJobPerformer.ExecuteTask(IVmBackupTask task)
[11.07.2019 09:34:13] Error Processing VM name
[11.07.2019 09:34:13] Error VM VM name does not meet the requirements for storage snapshot based jobs (System.Exception)
[11.07.2019 09:34:13] Error at Veeam.Backup.Core.CViSanSnapshotOnlyJobPerformer.ExecuteTask(IVmBackupTask task)
[11.07.2019 09:34:13] Error VM VM name does not meet the requirements for storage snapshot based jobs (System.Exception)
[11.07.2019 09:34:13] Error at Veeam.Backup.Core.CViSanSnapshotOnlyJobPerformer.ExecuteTask(IVmBackupTask task)

I tried to:

  • Rescan 3PARs in Veeam console.
  • Create a new snapshot-job for one VM – with secondary 3PAR.
  • Removed secondary 3PAR from snapshot-job.
  • Rebooted hardware proxy server – used for snapshot backups.

Nothing worked. Luckily the solution was quite simple:

  • Rescan vCenter in Veeam console!

After this, snapshot-jobs worked again without any issues! I hope this saves some time for troubleshooting.

Leave a Reply

Your email address will not be published. Required fields are marked *