This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VM Explorer target directory could not be created

Hi all,

I am running a free trial version VM Explorer V7.0,001,0 on Windows Server 2016

I have remote storage mapped as my Z drive and I am trying to backup a VM to this drive.

Via the Windows file explorer I can create folders on this drive, so I have what I believe are the appropriate access permissions.

I have created Z:\VMExplorer. My backup task is set to backup to Z:\VMExplorer\{VM}\{DATETIME}

When the task runs I get the error "The target  directory Z:\VMExplorer\my-vm-name\date-time could not be created (Could not find a part of the path Z:\VMExplorer\my-vm-name\date-time)

I also tried creating the folder Z:\VMExplorer\my-vm-name. Running the task after this creation leads to the same error.

Any ideas of what to look for, or what to change, would be appreciated.

 

TIA,

Dave

  • 0

    I don't know how to edit the original post, so I'll add some more info in a reply.

    When I created the backup task, I wasn't able to select the Z drive via the 'Browse' functionality, so I enter the path manually.

    I just tried browsing to Z using 'File Explorer and it isn't available.'

    Any ideas why this mapped drive wouldn't be visible?

  • 0 in reply to 

    Here's a little more info, from VMExplorer-Service-7_0_1.log,

    I see lots of the following message:

    'The Network Drive Z:\ is added. This drive is not usable until user intervention.'

    What user intervention is needed? What do I need to do?

    I also found the following curious line in VMExplorer-7_0_1.log,

    'INFO  CombineCurrentAndNewDrive procedure for drive Z:'

    What does this mean? Is it safe to ignore?

     

  • Verified Answer

    0   in reply to 

    Hi, have you mapped the Z drive in VM Explorer ? To do this go to Settings.Network Drives and then add your network drive via prompts. Once this is done, you should then see the drive showing when you try to back up under the local device option.

  • 0 in reply to   

    Alasdair, thanks for the solution.

    I guess 'Read The Fine Manual' applies in this case.

    It defies logic that this software would want to mount the drive, when the better solution is to have the drive already, or permanently, mounted.

  • 0   in reply to 

    Glad that's it sorted for you, if there's anything else just ask :-)   It can be a little strange at first, but the GUI is pretty straightforwards and generally driven by logic :-) 

    At the end of the user guide, there are also some tips on best practise and setup at the end of the user guide