Backup & Recovery

 View Only
  • 1.  VDR FLR restore errors

    Posted Apr 19, 2010 01:55 PM

    I'm having problems with the FLR client. Whenever I try to mount a disk, I get "Error: The drive could not be mounted. Please view the log for more details." In the log I'm getting:

    04/19/2010 02:31:13 PM > Vix Warn: vcdrPluginEngineGetSessionFile: internal exception was caught: "RefBackupset::Connect: error -1020"

    04/19/2010 02:31:13 PM > Vix Info: DISKLIB-LINK : "vdr://./server1.vmdk" : failed to open (One of the parameters was invalid).

    04/19/2010 02:31:13 PM > Vix Info: DISKLIB-CHAIN : "vdr://./server1.vmdk" : failed to open (One of the parameters was invalid).

    04/19/2010 02:31:13 PM > Vix Info: DISKLIB-LIB : Failed to open 'vdr://./server1.vmdk' with flags 0x1e (One of the parameters was invalid).

    04/19/2010 02:31:13 PM > Vix Error: VdrVixMount: Cannot open disk

    04/19/2010 02:31:13 PM > Exception: "VixMount: VIX_E_INVALID_ARG"

    > at RestoreClient.Api.ThrowError(String location, VixError result)

    > at RestoreClient.Api.VixMount(SessionFileItem[] sesVmdk, Int32& mntHandle, String& mntPoint, String vcServerAddress, String vcUser, String vcPassword)

    > at RestoreClient.MainView.b__3()

    This happens in a W2003 server and in any other client I try it in (W2008, 32 & 64-bit versions, etc), and with any restore point I try to access with FLR.

    The backups are working fine as I can do a whole-machine recovery from the images, but not a file-level recovery.

    Any help would be appreciated.

    Cheers,

    Dan

    VDR v1.1.0.707

    FLR client v1.1.0.707

    vCenter Server v4.0.0 208111

    vCenter Client v4.0.0 208111



  • 2.  RE: VDR FLR restore errors

    Posted Apr 23, 2010 09:05 PM

    <For some reason I am not being flagged as a VMware employee so let me say now that I am>

    This log excerpt is the key.

    04/19/2010 02:31:13 PM > Vix Warn: vcdrPluginEngineGetSessionFile: internal exception was caught: "RefBackupset::Connect: error -1020"

    This would lead me to believe this is a locked dedupe store.

    Consult "Deduplication Store May Remain Locked..." section of this document for solution.

    http://www.vmware.com/support/vdr/doc/vdr_100_releasenotes.html

    Note path to the lock will be the following.

    - if backing up to virtual disk

    /SCSI-x:x/VMwareDataRecovery/BackupStore/store.lck

    - if backing up to cifs share

    /<server>/<share>/VMwareDataRecovery/BackupStore/store.lck



  • 3.  RE: VDR FLR restore errors

    Posted Apr 25, 2010 09:23 PM

    DBJ, open an internal ticket and they will get the VM icon set on your profile



  • 4.  RE: VDR FLR restore errors

    Posted Jul 14, 2010 12:21 PM

    I am haveing a simular problem:

    07/14/2010 07:10:56 AM > Vix Warn: vcdrPluginEngineGetSessionFile: internal exception was caught: "RefBackupset::Connect: error -1020"

    07/14/2010 07:10:56 AM > Vix Info: DISKLIB-LINK : "vdr://./Commserver-2010.05.06-17.30.13.vmdk" : failed to open (One of the parameters was invalid).

    07/14/2010 07:10:56 AM > Vix Info: DISKLIB-CHAIN : "vdr://./Commserver-2010.05.06-17.30.13.vmdk" : failed to open (One of the parameters was invalid).

    07/14/2010 07:10:56 AM > Vix Info: DISKLIB-LIB : Failed to open 'vdr://./Commserver-2010.05.06-17.30.13.vmdk' with flags 0x1e (One of the parameters was invalid).

    07/14/2010 07:10:56 AM > Vix Error: VdrVixMount: Cannot open disk

    07/14/2010 07:10:56 AM > Exception: "VixMount: VIX_E_INVALID_ARG"

    > at RestoreClient.Api.ThrowError(String location, VixError result)

    > at RestoreClient.Api.VixMount(SessionFileItem[] sesVmdk, Int32& mntHandle, String& mntPoint, String vcServerAddress, String vcUser, String vcPassword)

    > at RestoreClient.MainView.b__3()

    Any help would be appreciated...



  • 5.  RE: VDR FLR restore errors

    Posted Jul 14, 2010 02:54 PM

    I managed to resolve the issue by (a) moving to smaller backup destinations (my original was 2TB, now use multiple 500GB destinations) and (b) making sure an integrity check had run successfully. I believe (a) was the main fix of my problems here.