I would like to know about the behavior when a job with storage snapshot coordination and a job without storage snapshot coordination (Hotadd mode) are executed at the same time for the same VM.
For example, let's assume that we have the following environment.
=============================
Backup VM number：VM1～VM5
▼Backup jobs integrated with storage snapshots
Set and retrieve VM1-VM5 as VirtulMachine in one job.
▼Backup jobs that use hotadd
Set up a hotadd job for each VM
Job a: vm1
Job b: vm2...
=============================
For example, what would be the possible impact if a Hotadd job is executed when a backup job with storage snapshot coordination is running ahead of it?
In the case of VMware snapshot-only job without storage snapshot coordination, while the VMware snapshot exists in the preceding job, the message that the machine to be backed up is locked is displayed in the following job, and it becomes Pending.
In the case of a job that is linked to a storage snapshot, the VMware snapshot will be created, the static point will be acquired, and the VMware snapshot will be deleted immediately after the storage snapshot is created.
In the case of a job that is linked with a storage snapshot, the data will be acquired from the storage snapshot.
Will there be any problems in this situation?
My guess is that after the VMware snapshot is deleted by the backup job on the storage snapshot collaboration side, the subsequent Hotadd job will resume from the Pending state, and both will be able to retrieve data without any problems.
Kind Regards,
Asahi,
Climb Inc.
