8 Replies Latest reply on Oct 23, 2015 11:49 AM by Slubot

    Unable to Take Snapshot

    Slubot Lurker
    Visibility: Open to anyone

      Hello Everyone,

       

      I really appreciate you taking the time to read my post.  I am relatively new to vmware and I require some assistance.

       

      One of my virtual machines is no longer taking snapshots. I first noticed the problem when our backup appliance, unitrends, started reporting errors when attempting to backup the VM.
      Their support ended up pinpointing the problem to the inability to take a snapshot. I confirmed this by attempting to take a snapshot directly with Vsphere.

       

      The exact Error I am getting when attempting to take a snapshot is the following:

       

      *********************

       

      An error occurred while taking a snapshot: msg.fileio.generic.

      An error occurred while saving the snapshot: msg.fileio.generic.

      *********************

       

      I am currently running ESXi 5.5 and Vsphere Client 5.5.0.  I have already attempted numerous things...


      - Rebooted the VM

      - Uninstalled and Reinstalled vmtools.

      - Tried installing vmtools without VSS(volume shadow copy)

      - Tried different combinations of services being on and off.( VSS, Virtual Disk, VMware Snapshot Provider)

      - Followed the following three KB articles:

           1) VMware KB: Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off …
           2) http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1031298
           3) VMware KB: Creating quiesced snapshot fails with the error: An error occurred while saving the snapshot: msg.snapsho…

      - Also Tried freeing up some space inside the VM itself and that didnt work either.

       


      I am at wits end and unfortunately do no have support with VM...

       

      Please help!

       

      Summary:
      Snapshots dont work.

      Backup Appliance: Unitrends
      Virtual Machine- Windows Server 2008 R2

      Host - ESXi 5.5
      Vsphere - 5.5.0

      Error:

      An error occurred while taking a snapshot: msg.fileio.generic.

      An error occurred while saving the snapshot: msg.fileio.generic.

       

      Thank you once again for your help!

        • 1. Re: Unable to Take Snapshot
          a.p. Guru
          Community WarriorsvExpertUser Moderators

          Welcome to the Community,

           

          please attach the current vmware.log file from the VM's folder to a reply post. Maybe this file contains any hints on what's wrong.

           

          André

          • 2. Re: Unable to Take Snapshot
            Slubot Lurker

            Hello and thank you for the welcome.

             

            I have attached the log file below...

             

            I looked through it...perhaps I should have attempted to find this log earlier..I apologize for not doing that.

             

            This jumps out at me, but I dont know exactly how to solve it...as I said, I am a novice in vmware. It seems like the problem could be a space issue? How do I increase the space on the storage disk?
            Unitrends is our backup appliance.

             

            Thank you!

            ------------------------------

             

            2015-10-21T06:59:02.956Z| vmx| I120: SnapshotVMX_TakeSnapshot start: 'Unitrends_backup', deviceState=0, lazy=0, logging=0, quiesced=1, forceNative=0, tryNative=0, sibling=0 saveAllocMaps=0 cb=28487540, cbData=323517D0

            2015-10-21T06:59:04.412Z| vcpu-2| I120: ToolsBackup: changing quiesce state: IDLE -> STARTED

            2015-10-21T06:59:14.581Z| vcpu-0| I120: ToolsBackup: changing quiesce state: STARTED -> COMMITTED

            2015-10-21T06:59:14.581Z| vcpu-0| I120: Destroying virtual dev for scsi0:0 vscsi=9317

            2015-10-21T06:59:14.581Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

            2015-10-21T06:59:14.629Z| vcpu-0| I120: Destroying virtual dev for scsi0:1 vscsi=9318

            2015-10-21T06:59:14.629Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

            2015-10-21T06:59:14.630Z| vcpu-0| I120: Destroying virtual dev for scsi0:2 vscsi=9319

            2015-10-21T06:59:14.630Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

            2015-10-21T06:59:14.683Z| vcpu-0| I120: SnapshotVMXTakeSnapshotWork: Transition to mode 0.

            2015-10-21T06:59:14.683Z| vcpu-0| I120: Closing all the disks of the VM.

            2015-10-21T06:59:14.683Z| vcpu-0| I120: Closing disk scsi0:2

            2015-10-21T06:59:14.685Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 151418447.

            2015-10-21T06:59:14.685Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

            2015-10-21T06:59:14.731Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01_2-flat.vmdk" : closed.

            2015-10-21T06:59:14.731Z| vcpu-0| I120: Closing disk scsi0:1

            2015-10-21T06:59:14.734Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 141784652.

            2015-10-21T06:59:14.734Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

            2015-10-21T06:59:14.763Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01_1-flat.vmdk" : closed.

            2015-10-21T06:59:14.763Z| vcpu-0| I120: Closing disk scsi0:0

            2015-10-21T06:59:14.767Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 138311241.

            2015-10-21T06:59:14.767Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

            2015-10-21T06:59:14.954Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01-flat.vmdk" : closed.

            2015-10-21T06:59:14.974Z| vcpu-0| I120: SNAPSHOT: SnapshotConfigInfoReadEx: Creating new snapshot dictionary, '/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01.vmsd.usd'.

            2015-10-21T06:59:15.049Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01-flat.vmdk" : open successful (65557) size = 85899345920, hd = 0. Type 3

            2015-10-21T06:59:15.049Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01-flat.vmdk" : closed.

            2015-10-21T06:59:15.050Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01_1-flat.vmdk" : open successful (65557) size = 536870912000, hd = 0. Type 3

            2015-10-21T06:59:15.050Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01_1-flat.vmdk" : closed.

            2015-10-21T06:59:15.058Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01_2-flat.vmdk" : open successful (65557) size = 217969590272, hd = 0. Type 3

            2015-10-21T06:59:15.058Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01_2-flat.vmdk" : closed.

            2015-10-21T06:59:19.857Z| vcpu-0| W110: File_GetFreeSpace: Couldn't statfs /vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01

            2015-10-21T06:59:19.857Z| vcpu-0| I120: SNAPSHOT: SnapshotCheckSpaceAndSnapshotNum: Error getting the free space on the storage disk

            2015-10-21T06:59:19.857Z| vcpu-0| I120: Checkpoint_Unstun: vm stopped for 5276420 us

            2015-10-21T06:59:19.858Z| vcpu-0| I120: SCSI: switching scsi0 to push completion mode

            2015-10-21T06:59:19.862Z| vcpu-0| I120: DISK: OPEN scsi0:0 '/vmfs/volumes/5420ba57-19081720-69b0-001cc4485549/SV-AP-01/SV-AP-01.vmdk' pe

             

            -----------------------

            • 3. Re: Unable to Take Snapshot
              a.p. Guru
              User ModeratorsvExpertCommunity Warriors

              How much free disk space do you currently have on the datastore (please use the "Refresh" link to update the space usage)?

              What type of storage do you use? Local or shared storage? In case of shared storage it should be possible to increase the LUN size, and then grow the datastore (assuming there's free disk space on the storage).

               

              André

              • 4. Re: Unable to Take Snapshot
                Jimmy15 Enthusiast

                As per logs

                2015-10-21T06:59:19.857Z| vcpu-0| I120: SNAPSHOT: SnapshotCheckSpaceAndSnapshotNum: Error getting the free space on the storage disk

                is the only error, rest looks good.

                generally (most of the cases) after reinstalling VMtools without VSS, snapshot woks with Quiesce option.

                 

                It's tried and tested , I am using TSM-VE backup tool which use same APIs.

                 

                Regards

                 

                Pankaj Sharma

                • 5. Re: Unable to Take Snapshot
                  Jimmy15 Enthusiast

                  One more thing to add , check is there and Snapshot already or any staled delta file is there in place.

                   

                  Regards

                  Pankaj Sharma

                  • 6. Re: Unable to Take Snapshot
                    Slubot Lurker

                    Please see screenshot attached.

                     

                    Currently using local storage.  The Datastore in question is LSATA_2-H3. Which...currently has 120.54 GB of free space.

                     

                    Can I then just increase the space of the virtual disk in the VM under edit settings? Or do I need to increase space somewhere else?

                     

                    Thank you once again for all your help everyone.

                    • 7. Re: Unable to Take Snapshot
                      Slubot Lurker

                      Hello Pankaj,

                      Thank you for taking the time to help me. As I stated earlier...I am a novice. Where would I check to see that?

                      • 8. Re: Unable to Take Snapshot
                        Slubot Lurker

                        Hey everyone,

                         

                        Just thought I should update.  I ended up migrating the VM to another datastore because I could not delete old snapshots on the original datastore.

                        Then, I realized that the VM virtual disks had all be thick provisioned. So they were taking up space when there was no actual data on them.

                         

                        Ended up removing one of those vdisk and that solved the problem! Back ups are now working.

                         

                        Thank you all!