• EN

workingDir parameter will be removed when VM restore, that specify the root directory of the datastore

Y
Badge

Even though the datastore exists and can be referenced at destination ESXi host, the workingDir parameter was removed during restore with the following message.
2022/12/02 11:48:46          Removing workingDir parameter because it points to a non-existent datastore /vmfs/volumes/63652fbd-aed4fef5-8da8-48210b3d7365

After checking with support(Case # 05738353), we were told that the Veeam specification is that if the root directory of the datastore is specified, it is removed even if it exists.

Please note that there may be few cases where the root directory is specified.

5 comments

Chris.Childerhose
Userlevel 7
Badge +20

If this is meant to be a request you should post it on the R&D forum.  https://forums.veeam.com

 

Chris Childerhose - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
Y
Badge

Thanks.
I have an end user who is having trouble and I will make a request on the forum.

Madi.Cristil
Userlevel 7
Badge +7

Even though the datastore exists and can be referenced at destination ESXi host, the workingDir parameter was removed during restore with the following message.
2022/12/02 11:48:46          Removing workingDir parameter because it points to a non-existent datastore /vmfs/volumes/63652fbd-aed4fef5-8da8-48210b3d7365

After checking with support(Case # 05738353), we were told that the Veeam specification is that if the root directory of the datastore is specified, it is removed even if it exists.

Please note that there may be few cases where the root directory is specified.

@Mildur 

Madi Cristil
regnor
Userlevel 7
Badge +14

Even though the datastore exists and can be referenced at destination ESXi host, the workingDir parameter was removed during restore with the following message.
2022/12/02 11:48:46          Removing workingDir parameter because it points to a non-existent datastore /vmfs/volumes/63652fbd-aed4fef5-8da8-48210b3d7365

After checking with support(Case # 05738353), we were told that the Veeam specification is that if the root directory of the datastore is specified, it is removed even if it exists.

Please note that there may be few cases where the root directory is specified.

@Mildur

@HannesK Is already on it 😉

https://forums.veeam.com/vmware-vsphere-f24/feature-request-workingdir-parameter-will-be-removed-when-vm-restore-that-specify-the-root-directory-of-the-datastore-t83976.html

Max M. | Systems Engineer @Veeam | VMCE/VMCA | former Legend & Vanguard
Madi.Cristil
Userlevel 7
Badge +7

Even though the datastore exists and can be referenced at destination ESXi host, the workingDir parameter was removed during restore with the following message.
2022/12/02 11:48:46          Removing workingDir parameter because it points to a non-existent datastore /vmfs/volumes/63652fbd-aed4fef5-8da8-48210b3d7365

After checking with support(Case # 05738353), we were told that the Veeam specification is that if the root directory of the datastore is specified, it is removed even if it exists.

Please note that there may be few cases where the root directory is specified.

@Mildur

@HannesKIs already on it 😉

https://forums.veeam.com/vmware-vsphere-f24/feature-request-workingdir-parameter-will-be-removed-when-vm-restore-that-specify-the-root-directory-of-the-datastore-t83976.html

Thank you , @regnor ! 😊

Madi Cristil

Comment


Terms & Conditions