1 2 Previous Next 25 Replies Latest reply on Feb 17, 2014 12:22 PM by Q3Q Go to original post
      • 15. Re: Please Help Backup Problem
        lamw Guru
        VMware EmployeesCommunity Warriors

        It's a best practice to not run on a snapshot for long durations and that is one of the reasons I did not want to support this use case initially as you can get yourself in loads of trouble if you forget and then realize you have a redo log of 1TB. Depending on the size of the snapshot and the rate of growth, it can take sometime for it to consolidate. ghettoVCB does use snapshot as a way to get the base disk into read-only mode so we can back it up and so snapshot is only used during the duration of the backup. Once the backup is complete, we remove it. Glad to hear you were able to get your backups going and I suspect this should also resolve other folks having a similar problem.

        • 16. Re: Please Help Backup Problem
          chungl83 Lurker

          It work. Thanks

          • 17. Re: Please Help Backup Problem
            Q3Q Novice

            Works. Thanks.

            • 18. Re: Please Help Backup Problem
              OresteCanello Lurker

              Hi, for me not working: ESXi 5.5.0.1331820. I tried both version ( 26 november main version and version you linked on github https://github.com/lamw/ghettoVCB/blob/32487120adcf8a01b7e1ab73baa711fcc9a93bc0/ghettoVCB.sh, adding a fi at line 1197 )

              dryrun with both on them i obtain the same result:

               

              2013-12-19 17:26:50 -- dryrun: ###############################################

              2013-12-19 17:26:50 -- dryrun: Virtual Machine: vmname

              2013-12-19 17:26:50 -- dryrun: VM_ID: 8

              2013-12-19 17:26:50 -- dryrun: VMX_PATH: /vmfs/volumes/md3200_r05/

              2013-12-19 17:26:50 -- dryrun: VMX_DIR: /vmfs/volumes

              2013-12-19 17:26:50 -- dryrun: VMX_CONF:

              2013-12-19 17:26:50 -- dryrun: VMFS_VOLUME: md3200_r05

              2013-12-19 17:26:50 -- dryrun: VMDK(s):

              2013-12-19 17:26:50 -- dryrun: INDEPENDENT VMDK(s):

              2013-12-19 17:26:50 -- dryrun: TOTAL_VM_SIZE_TO_BACKUP: 0 GB

              2013-12-19 17:26:51 -- dryrun: THIS VIRTUAL MACHINE WILL NOT BE BACKED UP DUE TO EMPTY VMDK LIST!

              2013-12-19 17:26:51 -- dryrun: ###############################################

               

              same result with different VMs. All VMs are in folders with the same VM name (no space, no strange char etc.)

               

              Many thanks for your help

              • 19. Re: Please Help Backup Problem
                ChupaMe69 Lurker

                Hi OresteCanello

                 

                I had the same problem on my ESXi 5.5 host.

                Did you copy and paste the script from the repository? I did and the script worked but gave me the "THIS VIRTUAL MACHINE WILL NOT BE BACKED UP DUE TO EMPTY VMDK LIST!" error.

                Try to download the shell-script and copy it to your server via scp.

                It worked for me.

                 

                Kind regards

                • 20. Re: Please Help Backup Problem
                  Phatsta Enthusiast

                  Ledig!

                  /Daniel Jokinen

                  Linford Communication AB

                  • 21. Re: Please Help Backup Problem
                    ChupaMe69 Lurker

                    I'm sorry?

                    • 22. Re: Please Help Backup Problem
                      wila Guru
                      vExpertCommunity WarriorsUser Moderators

                      My guess is that it's an out of office message with "holidays!" in Swedish.

                      Especially as there's a signature with his name/company which is not in his other messages.

                      --

                      Wil

                      | Author of Vimalin. The virtual machine Backup app for VMware Desktop Products
                      | Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
                      | More info at https://www.vimalin.com
                      | Twitter @wilva
                      | VMware Wiki at http://www.vi-toolkit.com
                      • 23. Re: Please Help Backup Problem
                        Q3Q Novice

                        Still seeing the same problem.

                         

                        Using: ghettoVCB.sh

                        LAST_MODIFIED_DATE=2013_26_11

                        VERSION=2

                         

                        The VM contains two disks. One of them is independant.

                         

                        While the backup seems to do OK, the output of the final result is wrong.

                         

                        The config file contains this parameter:

                        VMDK_FILES_TO_BACKUP="server.vmdk"

                         

                        The log contains these lines:

                         

                        2014-02-14 01:23:34 -- info: WARN: server has some Independent VMDKs that can not be backed up!

                         

                        2014-02-14 01:23:38 -- info: ###### Final status: ERROR: No VMs backed up! ######


                        The backup directory contains a copy of the server.vdmk.

                        And it contains a 'STATUS.WARN' containing 'WARN: server has some Independent VMDKs that can not be backed up'.


                        That is all correct.


                        But the final conclusion

                        ###### Final status: ERROR: No VMs backed up! ######


                        is WRONG!!!


                        Dryrun returns this:

                        2014-02-17 09:08:10 -- dryrun: Snapshots can not be taken for indepdenent disks!

                        2014-02-17 09:08:10 -- dryrun: THIS VIRTUAL MACHINE WILL NOT HAVE ALL ITS VMDKS BACKED UP!

                        2014-02-17 09:08:10 -- dryrun: ###############################################

                         

                        2014-02-17 09:08:10 -- info: ###### Final status: OK, only a dryrun. ######

                        • 24. Re: Please Help Backup Problem
                          JoergD Novice

                          In my ghettoVCB.sh I find following section. Starting with DO NOT MODIFY PAST THIS LINE

                          Are you sure that changing the option VMDK_FILES_TO_BACKUP is correct?

                          I used the value "all" and have no problems.

                           

                          ########################## DO NOT MODIFY PAST THIS LINE ##########################                   
                          # RSYNC LINK 1=yes, 0 = no                                                                       
                          RSYNC_LINK=0                                                                        
                          LOG_LEVEL="info"                                                                                   
                          VMDK_FILES_TO_BACKUP="all"                                                                         
                          # default 15min timeout                                                                          

                           

                          SNAPSHOT_TIMEOUT=15

                           

                          LAST_MODIFIED_DATE=2011_06_28                                                                        

                          VERSION=1

                          • 25. Re: Please Help Backup Problem
                            Q3Q Novice

                            VMDK_FILES_TO_BACKUP="all" is certainly wrong.

                             

                            That way the script will try to back up the independant vmdk, which it cannot.

                            This returns an error because not all disk scan be backed up.

                            That's even worse than I am doing now.

                             

                            As described, the script works OK, but the concluding message is wrong.

                            1 2 Previous Next