VMware Cloud Community
Smeagol
Enthusiast
Enthusiast
‎09-17-2009 07:08 AM

File Level Restore "unmounting disk" issue

Hi, Win2008 (NOT R2) server running the flr client 1.02 I get this error

C:\>vdrFileRestore.exe -a 192.168.100.40

0: Restore point

Date: "Thu Sep 17 12:35:55 2009"

1: Restore point

Date: "Thu Sep 17 14:51:33 2009"

2: Restore point

Date: "Thu Sep 17 14:53:11 2009"

Please input restore point to mount from list above

2

Opening disk "Test Server.vmdk"...

Unmounting disk "E"...

Basically it seems to mount and unmount immediately.

Any clues why!?

0 Kudos
5 Replies
admin
Immortal
Immortal
‎09-17-2009 11:23 AM

Does it do the same thing for restore points 0 and 1?

0 Kudos
Smeagol
Enthusiast
Enthusiast
‎09-24-2009 04:49 AM

Yes same error for all restore points.

0 Kudos
Kiemo
Contributor
Contributor
‎10-02-2009 04:44 AM

Hi Smeagol,

Did you get any further with your problem? I have exactly the same issue. If you run FLR with the -v switch I get the following output.

My Win2k3 servers work just fine, just not my 64bit Win2k8 VMs.

Can anyone else see what the issue might be from the logs?

Thanks in advance

John

C:\File Level Restore>vdrfilerestore -a 192.168.0.210 -v

plugin path is... "disklibpluginvcdr"

Searching for valid restore points from: "/SCSI-0:1/"...

"Web.vmdk"(size: 11954MB)

"Goldmine.vmdk"(size: 52681MB)

"Goldmine.vmdk"(size: 52681MB)

"Web.vmdk"(size: 11954MB)

"File.vmdk"(size: 5120MB)

"Goldmine.vmdk"(size: 52681MB)

"Goldmine.vmdk"(size: 52681MB)

"Goldmine.vmdk"(size: 52681MB)

"Goldmine.vmdk"(size: 52681MB)

"Web.vmdk"(size: 11954MB)

0: Restore point

Volume name: "File-Print" (vmdk count: 1)

Restore point: ""

Date: "Fri Oct 02 02:00:01 2009"

Machine uuid: "4233b3ec-c972-a1d4-f679-28548c938a1e"

Volume path: "\vcenter.colefabrics.local\Global Ribbons Group\host\Cole Fabrics

Plc\Resources\File-Print"

"File +Jg- Print.vmdk"(size: 40960MB)

1: Restore point

Volume name: "File-Print" (vmdk count: 1)

Restore point: "/SCSI-0:1/"

Date: "Fri Oct 02 11:47:59 2009"

Machine uuid: "4233b3ec-c972-a1d4-f679-28548c938a1e"

Volume path: "\vcenter.colefabrics.local\Global Ribbons Group\host\Cole Fabrics

Plc\Resources\File-Print"

"File-Print.vmdk"(size: 40960MB)

Please input restore point to mount from list above

1

Initializing disklib...

VixDiskLib: config options: libdir 'disklibpluginvcdr', tmpDir 'C:\Users\ADMINI~

1.COL\AppData\Local\Temp\1\vmware-administrator'.

VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib. A

ccelerated transport modes available.

VixDiskLib: Cannot find transport switch implementation in library disklibplugin

vcdr\plugins\disklibplugin.dll.

VMware VixDiskLib (1.1) Release build-163495

Using system libcrypto, version 9070AF

Mntapi_Init Asked - 1.0 Served - 1.0 was successful,TempDirectory: C:\Users\ADMI

NI~1.COL\AppData\Local\Temp\1\vmware-administrator-500.

Opening disk "File-Print.vmdk"...

DISKLIB-LINK : Opened 'vcdr://./File-Print.vmdk' (0x1e): plugin, 83886080 secto

rs / 40 GB.

DISKLIB-LIB : Opened "vcdr://./File-Print.vmdk" (flags 0x1e).

DiskLibProvider_GetDisk: Open successful - index 0.FVmount library: Error 2 whil

e opening VSTOR2 driver's control device

ileLevelRestore::vixMount: Vix cound not mount volume, error: 24307

Unmounting disk "F"...

Cleaning up...

FileLevelRestore::vixDone: Failed to dismount volume, error: 24304

VixDiskLibReaderWriter::Close: Ignoring closeFileLevelRestore::Go: std::exception occurred, exiting:Unknown exception

0 Kudos
uma_kits
Contributor
Contributor
‎11-10-2009 09:20 AM

I found the root cause that the currently version of File Level Restore is experimental version and it's not support 64 bit version. I tested FLR on Windows 2008 64 bit and it show an error same as you all.

Reference:

[File Level Restore with VMware Data Recovery 1.0

revisited|outbind://339/blog/archives/1303-File-Level-Restore-with-VMware-Data-Recovery-1.0-revisited.html|outbind://339/blog/archives/1303-File-Level-Restore-with-VMware-Data-Recovery-1.0-revisited.html]

http://www.ntpro.nl/blog/archives/1303-File-Level-Restore-with-VMware-Data-Recovery-1.0-revisited.ht...

*VMware also responded with an

email from their Product Manager for VMware Data Recovery, Azmir

Mohamed.*

+First of all, thank you for trying out VMware Data

Recovery! In terms of the file level restore (FLR) functionality that you

tried but could not get working ( it is an experimentally supported feature) it

could be that you ran into an issue but here are some of the

recommendations/suggestions that I received from the development

team.+

  • What is the guest OS running on the Windows VM that you are
    running the FLR client? While we plan to support 32-bit and 64-bit instances of
    Windows XP, Vista, Server 2003 and 2008 (including R2), the experimental version was primarily for use with 32-bit
    versions of Windows XP, Vista, Server 2003 and 2008 (no support for R2 with
    experimental version).

  • The FLR client can be used by users with Administrator
    privileges in virtual machines running Windows XP or later. Do you remember if
    the VM that your ran FLR on whether you were logged in as Administrator or
    equivalent?

  • While today we only support connection with the IP address
    to the appliance, we will be able to resolve using DNS names in the
    future.

0 Kudos
admin
Immortal
Immortal
‎11-19-2009 09:07 PM

We just released VDR 1.1 - and it comes with the fully supported File Level Restore Client for Windows VMs. It will support 64-bit guest OS and addresses the limitations that we had in the experimental version. You can download it here

http://downloads.vmware.com/d/details/datarecovery11/ZHcqYmQlcHBiZGUlcA==

Check out my post in the forum for more information about the VDR 1.1 release.

0 Kudos