Handling of Renamed Datastores in vSphere Backup Jobs

[d3k]

What happens if a vSphere backup job is configured with a VMFS datastore as the VM source (for instance, named "storage-old-convention") and later I rename this datastore (i.g. "new-storage-convention")? Will the backup job continue to work as expected?

Essentially, I want to understand if Veeam references datastores by their UUID (which remains unchanged despite a name change) or by their name. If it's the latter, renaming the datastore might cause the backup job to reference a nonexistent location and require manual intervention? If manual intervention is required, are the VMs seen as 'new' and require active fulls?

Side case: Is there any difference if the datastore is NFS or vSAN?

[Mildur]

Hello Jimmy

We track the UUID, not the name. The job will still protect the renamed datastore without any modification of the job source settings required.
The next backup session will continue the backup chain. Running active full is not required. That would only be necessary if the VM MoRef ID is changed. Which is not the case by renaming a datastore.

Best,
Fabian