Skip to main content

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

  • December 6, 2022
  • 5 comments
  • 48 views

Forum|alt.badge.img

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
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • December 6, 2022

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

 


Forum|alt.badge.img
  • Author
  • Not a newbie anymore
  • December 6, 2022

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


Madi.Cristil
Forum|alt.badge.img+8
  • Community Manager
  • December 6, 2022

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 


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • December 6, 2022

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


Madi.Cristil
Forum|alt.badge.img+8
  • Community Manager
  • December 6, 2022

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 ! 😊