0 Replies Latest reply on Apr 11, 2011 8:13 AM by skayser

    gvcb2 logs success even though backup failed (unavailable target datastore)

    skayser Enthusiast

      Hi,

       

      when trying to poke gvcb2 to see how it behaves in error conditions, I noticed that it doesn't detect an unavailable NFS target datastore as an error condition, but simply logs a successful backup .... which produces a false sense of security. Target datastore name is "nfs-from-w2k8r2", NFS server is down. No backup went to disk.

       

      [root@esx1 ~]# ls -l /vmfs/volumes/
      total 1024
      ?--------- ? ?    ?       ?            ? 029846f1-5b95eaf5
      drwxr-xr-t 1 root root 1680 Apr  7 18:29 4d9c6940-e4ff4390-bbd3-00238bbdec6d
      lrwxr-xr-x 1 root root   35 Apr 11 17:03 esx1-local1 -> 4d9c6940-e4ff4390-bbd3-00238bbdec6d
      lrwxr-xr-x 1 root root   17 Apr 11 17:03 nfs-from-w2k8r2 -> 029846f1-5b95eaf5
      

       

      Excerpt from the gvcb2 log:

       

              04-11-2011 07:53:50 --  debug: CopyThread: Start backing up VMDK(s) ...
              04-11-2011 07:53:56 --  debug: copyTask: send copySuccess message ...
              04-11-2011 07:53:56 --  debug: copyTask: waiting for next job and sleep ...
              04-11-2011 07:54:50 --  debug: backupVMDK: Successfully completed backup for [esx1-local1] vcenter/vcenter.vmdk Elapsed time: 1 min
      

       

      Has anyone observed this too? gvcb2 v4.3. Full log here:  http://paste.pocoo.org/show/369674/

       

      Sebastian