ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    VMWare 5.5 disk taking forever to backup

    IT Discussion
    vmware esxi 5.5 vmdk
    2
    3
    1.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by JaredBusch

      Ok, I have an Elastix VM running on one of my client's VMware servers.

      The server is running 5.5 and the Elastix instance is 2.4

      I had set the disk to 250gb thin provisioned. I then forgot about having all calls on one extension being recorded and promptly began to fill up the VMDK. I noticed a few weeks back and I turned off recording and purged the recordings folder.

      CentOS is reporting normal usage.

      img

      VMWare is reporting 136GB used. I am assuming that this is the size the VMDK was expanded to. But my Backups with Veeam are taking over an hour. I was under the impression that an inflated VMDK that was empty would backup much quicker.

      img

      1 Reply Last reply Reply Quote 1
      • scottalanmillerS
        scottalanmiller
        last edited by

        It may not be empty. Depends on the filesystem and what has happened. Just because the pointers to those files are gone doesn't mean that the bits have been erased. You could zero out the empty space.... but be careful or that will expand the VMDK to full size.

        JaredBuschJ 1 Reply Last reply Reply Quote 2
        • JaredBuschJ
          JaredBusch @scottalanmiller
          last edited by

          @scottalanmiller said:

          It may not be empty. Depends on the filesystem and what has happened. Just because the pointers to those files are gone doesn't mean that the bits have been erased. You could zero out the empty space.... but be careful or that will expand the VMDK to full size.

          That is what I did, but I knew there was enough space for the entire disk to expand out.

          img

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post