Thin Provisioning not reduce size of backup

Similar Questions

• time machine, not the size hourly backups

  I've been running Time Machine on a large partition of a hard drive external backup since June 2012.

  I noticed a week ago about 13 December 2015, the TM backup used disk space faster. I found that TM was maintaining all hourly backups since November 1, 2015. It was delete no, he wasn't going to the daily or weekly. So I have every hour Nov. 1 to Dec. 20 (so far) of backup 2015. No idea why started from that date either.

  I then ran disk utility to repair the TM and initially found some mistakes (which I had not), but repaired OK.

  A few days later, I ran THE NEW and confirmed drive was OK.

  I deleted library/preferences/com.apple.TimeMachine.plist and then configure TM again via system preferences. He backed up in the right place but still retained all of the hourly backups.

  I created a small TM backup on another partition of the external hard drive for 36 hours. He kept one then deleted backups older than 24 hours. Just as it takes.

  I put back to elements of TM and original score, but even once he kept keep all backup schedules.

  I started in safe mode, run TM without change.

  I would like to than TM fix/delete all backups hours/then every day as it should be past or in the future.

  All solutions other than 1. manually remove the redundant backups via 'Star Wars' or 2. leave full to have to buy another external hard drive.

  I have a mini PPC running 10.5.8. The backup of my hard drive is about 58 GB, the partition on the HDD is 385 GB with 22 GB of spare right now.

  Follow these instructions for a complete reset Time machine

• Thin provisioned VMDK consume all available space

  Hello

  • Server: Win 2008 R2 with SP1 (file server)
  • Storage: VMDK on VMFS5 datastore (thin provisioned), which underlies the SAN fiber storage
  • vSphere: vCenter Server Standard 5, ESXi 5.0 Patch 2 (build 515841)

  ... So, I have a VM file server running Windows 2008 R2 with SP1.  The system (c) partition has been successfully thin (VMDK using 13 GB to 40 GB).

  However, for all subsequent hard disks virtual created on the server, the NTFS partition is very slow to get into shape - and the actual size of the VMDK creeps slowly up to the size of the VHD (you can see the gradual rise of the VMDK size in the browser to store data during the formatting process).

  The VMFS data store that we create new virtual hard disks is version 5.  All virtual machines with virtual hard disks on VMFS version 3 seem to be supplied thin OK.

  Nobody knows what could happen here?

  Hello

  Do you use quick format?

  Otherwise, your score will take up any space. Check here:VMware KB: using thin provisioned disks with virtual machines

  "If a guest operating system needs to use a virtual disk, the must invited first operating system partition and format the drive in a file system it can recognize." Depending on the format selected in the guest operating system, the format can cause the disc thin provisioned in full size.

  For example, if you have a drive end with a Microsoft Windows operating system implemented and format the drive, unless you explicitly choose to fast formatting, Microsoft Windows format tool written information to all sectors on the disk, which in turn inflates the disc thin provisioned in full size. "

  Kind regards

  Julien.

• ESXI 5.1 "the disc is not thin-provisioned" after copying to the new data store vmdk

  I wanted to create an external backup as a 2nd VM ready-to-run on the 2nd data store.

  I've removed all snapshots, stop the machine virtual and exported the OVF file to a computer, adjusted to the size of the original virtual machine starts in Gparted to update the partition and restart. All very well.

  I then tried to deploy the OVF in the data store alternative (235GB slim, thickness according to the deployment of 250 Wizard). I tried both thick and thin but the error message "cannot deploy the OVF. The operation was cancelled by the user.

  I then manually downloaded the VMDK & OVF file to the 2nd data store and tried to inflate but then received the message "a specified parameter was not correct. The disc isn't thin provisioned. ».

  It seems I have dealing with the same thing, as this is the document here (http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-vcenter-server-55u3-release-notes.html).  However, I have no idea what to do now... and I'm worried because it seems that my backup plan may not work if I can't restore an OVF/VMDK from a disk of visas.

  The solution to the first problem here: https://communities.vmware.com/message/2172950#2172950 that solved my problem 2nd too.

• Backup errors with backup of thin provisioned disks on ESXi 5.1

  Hello

  I try to set up a backup solution for two servers in ESXi 5.1. (free version).

  I have installed and configured the ghettoVCB successfully and everything seems to be ok.

  However, when I start to create a backup, the process would end with an error :-(

  It didn't matter if the server is enabled or disabled, I get the same result.

  All data warehouses are local, 2 x free WD500GB with plenty of space.

  There is no snapshot, anything that could (in my eyes) prevent a good backup.

  The server works perfectly, when turned on.

  I'd appreciate any useful comment. Thanks in advance! The log is attached.

  / vmfs/volumes/519fceb8-3d39150e-2D0F-001999eeb339/ghettoVCB-Master #./ghettoVCB.sh f vms_to_backup
  Recording output to ' / tmp/ghettoVCB-2013-05-25_20-56-28-324192.log '...
  2013-05-25 20:56:29 - info: = ghettoVCB NEWSPAPER BEGIN =.

  2013-05-25 20:56:29 - info: CONFIG - VERSION = 2013_01_11_0
  2013-05-25 20:56:29 - info: CONFIG - GHETTOVCB_PID = 324192
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_VOLUME/vmfs/volumes/backup/ghettoBackups =
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 3
  2013-05-25 20:56:29 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2013-05-25_20-56-28
  2013-05-25 20:56:29 - info: CONFIG - DISK_BACKUP_FORMAT = thin
  2013-05-25 20:56:29 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
  2013-05-25 20:56:29 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0
  2013-05-25 20:56:29 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3
  2013-05-25 20:56:29 - info: CONFIG - POWER_DOWN_TIMEOUT = 5
  2013-05-25 20:56:29 - info: CONFIG - SNAPSHOT_TIMEOUT = 15
  2013-05-25 20:56:29 - info: CONFIG - LOG_LEVEL = info
  2013-05-25 20:56:29 - info: CONFIG - BACKUP_LOG_OUTPUT = /tmp/ghettoVCB-2013-05-25_20-56-28-324192.log
  2013-05-25 20:56:29 - info: CONFIG - ENABLE_COMPRESSION = 0
  2013-05-25 20:56:29 - info: CONFIG - VM_SNAPSHOT_MEMORY = 0
  2013-05-25 20:56:29 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 0
  2013-05-25 20:56:29 - info: CONFIG - ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP = 0
  2013-05-25 20:56:29 - info: CONFIG - VMDK_FILES_TO_BACKUP = all
  2013-05-25 20:56:29 - info: CONFIG - VM_SHUTDOWN_ORDER =
  2013-05-25 20:56:29 - info: CONFIG - VM_STARTUP_ORDER =
  2013-05-25 20:56:29 - info: CONFIG - EMAIL_LOG = 0
  2013-05-25 20:56:29 - info:
  2013-05-25 20:56:35 - info: start the backup for server W2003
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/519fceb8-3d39150e-2d0f-001999eeb339/w2003-server (2) 2/w2003 Server _1.vmdk'...
  Clone: 36% of fact.
  2013-05-25 20:59:34 - info: ERROR: error in the backup of "/ vmfs/volumes/519fceb8-3d39150e-2d0f-001999eeb339/w2003-server (2) 2/w2003 Server _1.vmdk ' to W2003 Server
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/WD500GB-1/W2003-Doma¤ne/w2003-server (2) hard '...
  Clone: 66% of fact.
  2013-05-25 21:08:59 - info: ERROR: error in the backup of "/ vmfs/volumes/WD500GB-1/W2003-Doma¤ne/w2003-server (2) hard" to W2003 Server
  2013-05-25 21:08:59 - Info: backup time: 12,40 Minutes
  2013-05-25 21:08:59 - info: ERROR: impossible to W2003 server from backup because of the error in VMDK backup!

  2013-05-25 21:09 - info: # final status: ERROR: No. VMs saved! ######

  2013-05-25 21:09 - info: = ghettoVCB JOURNAL END =.

  / vmfs/volumes/519fceb8-3d39150e-2D0F-001999eeb339/ghettoVCB-Master #.

  > However, when I start to create a backup, the process would end with an error :-(

  This is not correct.  Depending on your position, you've got to 66%, until he ended with an error.

  I have the same problem. In my case, I make a virtual disk full and mount it with Server 2003 for project a NFS volume.  I use GhettoVCB, as you do.  It uses the standard vkmfstools in the script to make the clone/backup.  I have proven that the problem also occurs when you use the command line vkmfstools.  GhettoVCB has the bad habit of you cache the error code.  The error code is he ran out of disk space, which we both did not happen.  Once the problem occurs, the only way I could fix is to delete the virtual disk and start over, however, the problem will come back.  The problem didn't surface until what I moved to ESXi 4.0 5.1 on the servers.  Through this process, the hardware off the VMS version did not change, nor dare, because I may need to take 5.1 and back to 4.x.

• Thin provisioning / "right-size" database disk

  OK, so I have the setting permissions and ready to deploy to the device.  I don't want to have a 200 + GB DB hard.  I know they say there is a special way, using the OVFTool application if you are using vSphere 4.0.  We run vCenter 4.1 and 4.1 ESXi hosts.  To specify the hard size I want, will it still thinly provision the device with the OVFTool?  I'm looking for clarity in this before deploying the machine, because I will be setting LUN space based on drive of 75 GB database (with room for future growth in LUN).  I apologize if this has already been covered, but I didn't see any other posts related to my question.

  virtualhudak,

  Technically, you should be prevented to deploy the virtual appliance CapacityIQ on a LUN with only 125 GB of free space on the disk.

  You need a data store with at least 258 GB free space on the drive in order to deploy the appliance CapacityIQ. That you complete the deployment wizard, two of the questions asked are if you want the first disk to be configured as a disk, thin or thick. and the same question for the second disk (/ data).

  Once you have deployed the virtual appliance successfully, you can follow the steps to reduce the size of the second (/ data) disk.

  James Ang | VMware engineering
  VMware vCenter operations
  VMware vCenter CapacityIQ
  VMware Capacity Planner
  VMware vCenter Guided Consolidation

• Thin Provisioning does not not as expected

  In my esxi 4.0 test environment, I created a machine thin-provision xp-32 bit.

  Provisioning was assigned to 50 GB and is a minimal install of XP (just the operating system, patches, vmware tools) leaving 44.7 GB free.

  The flat file hower, looks like she is supplied thickness.

  I searched every thread here and see no similar problem.

  Am I missing something? I thought that the vmdk file should be around 5 GB to do, 50...

  I do not use vcenter, just download free esxi 4.0.

  

  / vmfs/volumes/4afd5954-40f87539-4DE3-001aa0a6e9a3/XP pro SP3-Virgin # ls - al

  drwxr-xr-x 1 root root 1400 19 Nov 12:40.

  drwxr-xr-t 1 root root 2240 19 Nov 12:14...

  -rw - 1 root root 53687091200 Nov 12:40 19 XP Pro SP3-Virgin - flat hard

  -rw - 1 root root 8684 19 Nov 12:40 XP Pro SP3 - Pristine.nvram

  -rw - 1 root root 506 18 Nov 17:55 XP Pro SP3 - Pristine.vmdk

  -rw - 1 root root 0 18 Nov 14:00 XP Pro SP3 - Pristine.vmsd

  -rwxr-xr-x 1 root root 2731 19 Nov 12:40 XP Pro SP3 - Pristine.vmx

  -rw - 1 root root 1866 18 Nov 17:55 XP Pro SP3 - Pristine.vmxf

  -rw - rr 1 root root 230154 19 Nov 12:13 1.log - vmware

  -rw - rr 1 root root 63177 19 Nov 12:40 vmware.log

  Hello hamm3r,.

  It is normal that you feel. A directory of the regular list will show 50 GB. You need to do a query (use of the drive/directory) with the following:

  -ah *.

  Which should show the actual size of the vmdk file. You can also watch free space of your data store in the VI client to check that it lines up with your expectations. I hope this helps.

  Don't forget to mark this "correct" answer or 'useful', if you found it useful (you'll also points).

  Kind regards

  Harley stagnate

• Exhibitor do not reduce the size of police accordingly

  I have InDesign CS6 (PC) and I am working on a document created by our parent company in Germany. When I add the trademark and make exposing, it moves, but it does not reduce the size of the font of the actual registered mark. When I create one in a new file, it will work correctly. I tried to copy and paste into the existing document and it is up to the rear. I don't know there is a setting somewhere that needs to be changed. I hope someone out there has had experience with this and can help.

  It comes to the existing document. The first is earlier makes exposing. The 2nd is after that that she has made exposing. It moves upwards, it does not reduce the size of the font of the trademark accordingly symbol.

  

  

  It comes to the new document.

  

  Go to the InDesign / Edit menu and click on Preferences followed by advanced Type and percent correct.

• FLA, the size of the file is too big and will not reduce even after the removal of assets

  I loaded a png sequence in a FLA file. This makes the huge file, so I decided to remove them. However, this has not reduced the size of the DFL. I checked the library and deleted the PNGs with no luck. I even deleted all forms of asset library and deleted all the content of the scene and the timeline, but the FLA is still almost 1 GB. How can I fix it!

  I think that there is another bug in Flash.

  I don't know who marked this as "right answer", but he did not work for me!

  I took a whole new folder full of JPGs and then tried the above suggestion. Then for good measure, deleted ALL the content of the FLA file and emptied the library. I tried and then clear the Cache of publish and save as. The FLA file (empty) is always greater than 50 MB!

• Thin Provisioning does not work or unable to find space?

  Hello

  I have about 30 virtual machines using thin provisioning format. I found 1 especially with a 20 GB drive, TYPE THIN and 19.9 GB used. I entered in the console, check use of space inside the linux and it has 90% free. It uses only 2 GB.

  My question is why not taking advantage of the thin provisiong as other virtual machines. Any ideas?

  Post edited by: vmroyale to remove the PLUGS all THE of the subject line

  Fill the empty space with zero and do svmotion with thin disk as target, it should reclaim the unused space.

  It's how recover you for example 10 gigabytes of Linux root fs

  DD if = / dev/zero/foo bs = 10240 count = 1 M

  RM foo

  then svmotion

  Tomi

  http://v-reality.info

• Could not save file under Reduced Size!

  I can't save a ~ 2 MB as size using Acrobat Pro X 10.1.3. I spared smaller files in a reduced size. Why is this? I called Technical Support and left a message for a reminder to hopefully solve this problem quickly. I was reminded in two minutes about, I held for a while, and then I was disconnected without talking to anyone!

  Thank you.

  I thought I should finally mention that Acrobat X Pro just didn't shrink after selecting the size reduced. I still called Technical Support and found that I had to do an OCR of the document and which corrects the problem. Apparently some graphics or pictures caused a problem, I understand.

  Thank you.

• How to recover free space on Thin provisioned VM

  Hello

  We are trying to recover the thin provisioned VMDK using below UNMAP commands on esxi5.5 update1 host but get error backup volume not supported for UNMAP and we can see that delete also not taken in charge and all status by checking the ATAS list his indicates that the plugin is not loaded we use IBM SVC (VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  Let know us how to load the VMW_SATP_SVC plugin to the ESXi 5.5 update1 host and also suggest how to recover free space on thin provisioned VMs

  Here's the output of command, we checked and we suggest to conduct thorough on this

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

  ~ # esxcli storage vmfs unmap-l NONPROD-DS01

  Backup volume 5390312 a-1f3a16fd-b578-5ef3fc1eb0bb devices do not support undo the MAPPING

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

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

  ~ # esxcli central storage peripheral vaai situation get naa.60050768018105ced80000000 d

  CF 00010

  1. NAA.60050768018105ced8000000000010fc

  VAAI Plugin name:

  ATS status: supported

  Clone status: supported

  Zero status: supported

  Delete status: unsupported

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

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

  ~ # esxcli storage nmp ATAS list

  Description of default name PSP

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

  Tables VMW_SATP_ALUA VMW_PSP_MRU nonspecific media that use the Protocol AL AU

  VMW_SATP_MSA VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_DEFAULT_AP VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_SVC VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EQL VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_INV VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_EVA VMW_PSP_FIXED placeholder (not loaded plugin)

  VMW_SATP_ALUA_CX VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_SYMM VMW_PSP_RR placeholder (not loaded plugin)

  VMW_SATP_CX VMW_PSP_MRU placeholder (not loaded plugin)

  VMW_SATP_LSI VMW_PSP_MRU placeholder (not loaded plugin)

  Non-specific bays of VMW_SATP_DEFAULT_AA VMW_PSP_FIXED Supports active/active

  VMW_SATP_LOCAL VMW_PSP_FIXED direct support of connected devices

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

  Hi friend

  I checked with the storage provider and they confirmed that the storage system (currently no products support midsize or SVC SCSI unmap commands used by space VAAI claim.)

• Ability to store data when thin provisioned

  Hi all

  VSphere 4.1 running in a cluster of two hosts, this cluster uses a Dell Equalogic PS4000 SAN for storage.

  Confusion I have is with thin configured data stores and my Exchange Server (2010) - running on MS Server 2008 R2 Ent.

  Exchange server uses three data warehouses on the San, one for the OS, one for data and one for newspapers.

  The data of databases store is the one that gives me problems, it has been defined as thin provisioned 750 GB, when I look on the SAN & via VCenter he said 90% full until she went to 100% after the SAN sent several alerts - the virtual machine then crashed with out-of-space error.

  To cut a long story short, I have twol questions

  (1) in this case why the SAN & VMWare say the data store is full, BUT when I connect to the virtual Windows computer it was about 50% in use?

  (2) when the data store that contains the databases filled I don't understand Exchange has fallen more but why why the crash of the VM?  The OS data store still had plenty of free space.

  I got this error by increasing the space of 100 GB to 850 GB data store while the virtual machine is very well (even if Windows was complaining to a stop suddenly unexpected).

  Thanks in advance for your help.

  K

  And without perspective, as it was put in service end and touch 750 GB, 300 GB, then was removed, it would not 750Go because it may not decrease in size - is that correct?

  (This would answer why the SAN says he uses 750Go of 750 GB, but Windows thinks there ish 300 GB free).

  Yes, that's correct... the recovery of unused/dead/removed space don't is not automatically made.

• Thin Provisioning LUNS and virtual disks

  Hi all

  I recently came across a problem with our VMware View environment, where in vCenter about 20 of our virtual office message that there is no more space left. When I looked at the data warehouses that store with my clones related, they have both said more than 200 GB of free space.

  In an attempt to clarify the environment, but do not go off-topic, some of our pools view are configured to give each virtual desktop a disposable disc service end of 4 GB (Temp and swap files). I noticed that in vCenter, the question asked to VMware for more memory space pointed to these disposable disks.

  I was with the support of a few hours... on the side of EMC Clarion, LUN (which are thin provisioned) also showed full... but VMware support was able to create a 1 GB file on the data store that was full according to the Clarion.

  We sent EMC our papers and they were back and just said the table is fine, the LUN was out of space... but this does not explain to me why vSphere showed the LUN as having 200 GB free. EMC said they did not know and I need to talk with VMware. I'm confused, if the LUN was not always full, how we were able to create the 1 GB file on the data store?

  Curiously, all the desktop computers that do not have the disk of 4 GB disposable were very well... they had no problem. I'm almost thinking, perhaps disposable disc was full of temp and file exchange and that where this problem started, but I can't seem to be able to confirm that the 4 GB.

  Another thing is, began to be blocked on this data store, even if these virtual desktops, have been removed from the files. I'm unable to delete records in the data store. I know that I can restart the hosts to unlock, but let's just delete this store of data/lun individual completely.

  I was wondering if anyone has had similar problems or has any advice?

  Mike

  Teas because there are 2 parts of the area of thin provisioning.

  When you create a thin LUN on the side of the table, regardless of the size, it only * affects * about 1 GB (for Clariion).  Like many parts of this LUN if written, it allocates more.

  Now when you create an om VMFS file, unless you use eagerzeroedthick (which you're not), there still, not all these data in a 1 GB (10GB or other) is actually hit or written to the creation time.  Thus, the table side only sees (for example) hit 16 MB.  Now to delete some files on the side of VMFS.  The table does not know that those "affected" blocks are now free (because VMware doesn't have the ability to communicate that back to the table), so it independently as always in use.  As a result, you end up with a shift of how is used according to the table, and the file system.

  So now consider a 500 GB LUN, who think that the painting is "full", but said VMFS has 200 GB of free.  That 200 GB was probably written at a time in its history, then deleted.  Thus, full to the table, but not the file system.  When you create small files, VMFS is overwhelming the space previously used, which the Board considers acceptable, but as soon as you try to use the space that is not be 'recycled', it barfs, because its out of space on the backend.

• Reduce the Rman backup time

  Dear expert;
  
  RMAN for level 0 backup takes about 05:26 hours, size of backup is now 312 GB I activated the block check the track and it reduces the time for the additional workforce 1 of 2 hours to nearly 3 minutes.
  
  database displays the largest storage space is "users".
  
  I want some useful suggestions to reduce his time or is it possible to break the level 0 backup. I can assign channels, but ultimately it will take time when you take 'users' tablepace backup
  For now, I take the backup on USB & his version is 2.0
  
  
  Concerning

  As you take backup on a USB there is not much that can be done to improve the speed. If you are worried about the backup to slow down... then you might think that taking the backup to local drive (which would be faster and more efficient) and then move the backups from disk on USB.
  This can be done in one script backup as part 2 operation.
  1) take backup on the disk.
  (2) copy the backup to USB key and delete the backups from disk.

  There are many additional features that you can add to improve it commentator.

  Kind regards
  V