Instant space?

Similar Questions

• Instant space question - images

  Hi people,

  This is my first post here, because we are quite new to this and I want that what may be an obvious question.

  I tried searching but as you'll see in the issue specifics mean no search results does not give the information I'm looking for.

  Basically - I am deleting snapshots and the snapshot copy in the parent image before deleting the snapshot itself.

  So the amount of used space increases actually before that this tax is reduced.

  So you need to more than enough space to delete snapshots.

  My question is:

  Based on the attached picture, space must be in the "storage used" Vs "storage provisioned" in the summary view.

  Or is it the 'ability' Vs 'Space used' in the views of storage?

  I saw my storage used to achieve the same capacity as the storage provisioned last time I deleted a snapshot and I panicked that I was running out of space!

  I would be grateful to anyone who can me explain this in simple terms please.

  Thank you!!

  

  RSW

  Instant virtual computer just use any free space to store data.   This free space is the difference between the capacity column and space used.

  Implemented storage is the amount that could use the virtual machine, and this double amount whenever you take a snapshot in order to allow a rate of 100% full of change in this snapshot.

  Above all, you won't have to hit major problems (as VM stop) unless your space used = data store capacity.

• Instant space requirements

  Hello

  I have a few questions on space for a virtual machine snapshots including an 80G hard for hard Windows OS and 500G for data. We use the VSphere 4.1 and VSphere 5.

  1. how much space is required for the instant 80 G or 580 G?

  2. If the .vmdks are on different LUNS will be snapshots stored with the virtual machine configuration file?

  Thanks for helping clear this up.

  Robert

  As mentioned previously, a snapshot can grow up to the size of certain overhead costs as well as the basic disk. Regarding overhead, take a look at table "Load calculation required by the snapshot files" at http://kb.vmware.com/kb/1012384

  André

• Use of instant space for disc RDM

  Dear all,

  ESX Server can support data store VMDK, physical RDM & RDM compatibility.

  Is the comparability of disk speed, physical RDM > RDM compatibility > VMDK Data Store?

  RDM compatibility seems can take advantage of instant virtualization.

  How the use of snap RDM compatibility spaces?

  Thanks for any input.

  Dennis Dai

  Take a look on: http://www.vmware.com/files/pdf/vmfs_rdm_perf.pdf

  Physical RDM are a little faster, but you can not the snapshot on this subject.

  Virtual RDM can create snap by creating a delta file in the folder of the virtual machine, if you need space in this point to have the instant copy growing up.

  André

• Instant space utilization

  Hello: is any similarly limit the use of a snapshot of the VM space?

  Thank you

  David

  Unless there is a new feature in fantasy somewhere there is no "cap" the snapshot space. In vCenter, you can set limits to alarms to warn you of storage space. It's a big problem out of space to store data with snapshots.

  Take a look at the Snapshots of understanding

• Backups DPM Hyper-V fail until I have allot of space of the snapshot in PS6100XV

  I have a PS6100XV connected to my virtual host nine of 4 processor 64 Core.  Was super happy to live my VMs migration to this new server until I tried to save them.  I've lost hours trying to understand why the 2012 DPM could not make a backup.  I finally realized if I gave the volume of instant space in the end Equallogic backups work.  My question is this:

  What is the advantage of using the the Equallogic VSS?

  Can I disable VSS and have just DPM uses the one built into the operating system?

  What would you recommend for the most reliable solution?

  You can unsubscribe from the VSS EQL recorder.   Volume Shadow Service is asked to calm a disc, it uses the writer to determine who is the owner of this record.   find the EQL writer he will ask the Board to take a snap of HW.    You can unsubscribe from the writer to the CLI.   In my view, the command is located in the Administrator's guide.  If you are not decided by using snapshots, which would be the best option.

• Disk space remaining time 0 days... but what VMs.

  Hi all.

  I installed the VAPP for VCOPS is about 2 weeks and continues through he's trying to learn it.

  I was looking at the warnings and try to get health upward.   Most of the things are clickable, but for that I can't figure out what/where to go.

  If I highlight something on the left (my vCenter for me), then go to the planning on the right, then the views.

  I find a lot of things RED.  For example, if I choose 'Ability to Virtual Machine', then down I see next to "Disk space" that I have the time that remains "0 days."

  Also that 27 of my virtual machines are more.   I can't figure out how to find just what VMs that is.

  I have attached a screenshot showing the screen page.

  5.7.1 vCops build 1166139

  Thank you very much.

  If you use the admin account from vCenter for the collector of vCOps, perms are probably not a problem here. vCenter creds are used only to collect data from vCenter, and to access user acts as a degree of transmission for advanced access to the USER interface. Whatever it is, I don't think it's an immediate question since you are using your administrator account.

  1. instant space on a virtual computer will count just use of disk space. After a certain age it is even considered as a waste (configurable, default 180 days).

  2. who would absolutely have an impact on the accuracy of what vCOps sees. vCOps needs to see all the virtual machines on a store of data and giving only even if partial access through vCenters can cause serious situations of angle with these #s of planning. I recommend that you add the 2nd vCenter to vCOps for monitoring to help to clean up, but you can find that data warehouses are the same signature, but with "possibly" differing vCOps resource name - see what it does in your case. When you migrate computers virtual to the new vCenter, he'll gen new unique identifiers for resources and you will lose your historical data for those VMs. The virtual machines in the new vCenter will be collected as long as new resources and collect measures under this new resourceid... the old resource and associated metrics will be left to age with the rest of your data.

  How long until the migration is complete? Until you get your warehouses of data cleaned and VMs on them fully visible to vCOps, I think that the #s will be a little off.

• Old clichés auto removal

  We have Veeam do backups of VMS, which generates snapshots of volume on our SAN. The question is, even if 'delete the oldest snapshot' is checked in the instant policy volume and "borrow space according to needs" is not checked, finally instant space fills up and the volume is offline.

  Does anyone know a solution to this? I think that "delete the oldest snapshot" would solve this problem, but it doesn't.

  Thank you

  Hello

  I remember well, it's that VEEAM operates not instant material EQL.  So you can disable the HIT. / ME driver for MS Volume Shadow Service.

  The command is "" eqlvss / unregister "now a snapshot will not be created on the SAN."

  I don't know why remove it the oldest is not honored.  To do this, I would suggest opening a case of pension, so they can take a look at the diagnosis.

  To reactivate the H/W snapshots, it's "eqlvss /register" you can add these commands to the VEEAM backup if you also use ASM to create snapshots.

  Kind regards

  Don

• Question about Equallogic snapshots.

  Hello forum

  I could not confirm this, but instant never need to commit anything to the basic volume?

  Lets say I have 10 snapshots and delete the oldest? There will be a load of e/s to validate these instant changes?

  Also, if someone could point me to any type of indepth explanation of this technique of snapshot, I would be interested to read all that.

  Thank you!

  N ° current data are already on the base volume.  There is nothing to commit.   Only if you are completely restoring a volume from a snapshot will be there in writing for the base volume.

  On the site of Equallogic Support KB:

  Solution title TABLE: how the snapshot reserve space is allocated and used

  Solution details Snapshot Reserve Allocation and use

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

  In a series group PS, snapshots can protect against errors, of a volume

  virus or the database. A cliché represents the content of a volume

  at the time you created the snapshot. Creating a snapshot does not disturb

  access to the volume, and the snapshot is instantly available allowed

  iSCSI initiators.

  Before you can create snapshots for a volume, you must allocate space (called

  snapshot pool) for snapshots. You set the value of the snapshot reserve

  When you create or modify a volume. Snapshot reserve benefits from the same

  as the volume of the pool data.

  When snapshot data consume entire supply snapshot, the Group remove is

  the oldest snapshots to free up space for new images or sets the volume and

  snapshots offline, according to the policy you selected for instant recovery

  space.

  The functionality for creating snapshots is called hybrid allocate when writing.

  Operation of sharing and snapshot of the page

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

  A PS Series Group organizes the physical storage into logical segments called pages.

  Each page is composed of several logical blocks. This is similar to the way file

  systems combine areas of physical disk in 'clusters' or 'chunks '. Each page has

  a reference count which records the number of volumes and snapshots that share

  the page.

  When you create a volume, the group creates an internal table, called the volume

  table, which contains pointers to pages that use the volume. When you create

  a snapshot of a volume, the group creates a snapshot table by making a copy of

  the volume table, which is usually an operation in memory that the Group

  run in a transactional manner. For each page of volume in use, the support group increases the

  reference count to indicate that the volume and the snapshot share page.

  Because the group does not move or copy the data or allocates a new pages, photos

  are fast and efficient.

  Reserve of the snapshot stores the differences between the data on the volume and snapshot data

  (in addition to differences between the data of multiple snapshots). When you

  first create a snapshot, the page for the volume and the snapshot tables are

  In brief identical copies and the snapshot consumes no snapshot

  reserve. A reading of the same logical block of the volume application or the

  snapshot returns the same data because the application is reading from the same page.

  However, if you write a page that has a volume and a snapshot of share, snapshot

  reserve is consumed.

  Here's a simplified example of a snapshot operation. In general, no.

  additional I/o operations are needed to manage the data volume or snapshot.

  However, other internal operations can occur due to virtualization and

  data balancing on berries of the PS Series.

  If an application performs a write to 8 KB for a volume containing a snapshot, the

  Group:

  1. determine what page is modified by the write operation.

  2 - If the page is not shared, writes the data to the page.

  3. If the page is shared:

  . (a) allocates a new page of disk space and reduces the instant to reserve

  . the volume of a single page.

  . (b) update the page of volume table to point to the newly allocated page.

  . (c) mark the newly allocated page as having new data on the volume and the references of the

  . original page for unchanged data.

  . (d) writes the data to the new page.

  When writing is complete, if you read the data on the volume, you have access to the

  new page and new data. However, if you read the same logical block of the

  Instant, you get the original data, because the snapshot will always point towards the

  original page. Similarly, if you set a snapshot online, write to the snapshot.

  feature hybrid write protects the original data volume by allocating

  a new page for the new snapshot data.

  Only the first page of writing to a volume shared (or snapshot) consumes additional

  snapshot reserve. Each subsequent entry is considered identical to a writing on a

  non-shared the page because the original data are already protected.

  Functionality similar to hybrid allocate when writing is used in cloning operations.

  However, unlike when you create a snapshot, cloning a volume immediately

  consumes space additional group. If a clone is moved to another pool, data

  is copied during the operation of moving pool.

  Restoring a Volume from a snapshot

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

  Because of the layout table, restore a volume from a snapshot is very

  quick. First of all, the group automatically creates a snapshot of the volume by copying

  the volume table to a new table of snapshot. Then the Group transposes the page tables

  the volume and the snapshot you selected for the restore operation. NO.

  additional space is required, and no data is moved.

  Deletion of Volumes and Snapshots

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

  Because volumes and snapshots to share pages, if you delete a volume, you

  automatically remove all the clichés associated with the volume.

  You can manually delete snapshots (for example, if you need more of)

  snapshot data). In addition, the group can delete snapshots automatically in the

  following situations:

  1 - failure instant free reserve. If the snapshot data consume the snapshot

  . reserve, the group either deletes the oldest snapshots to free up space for new

  . snapshots or sets the volume and snapshots in offline mode, according to the policy

  . you have chosen for the snapshot space recovery.

  2 - maximum number of snapshots, created from an agreed timetable. If you set up a

  . timetable for the creation of snapshots, you can specify the maximum number of

  . photos you want to keep. Once the program creates the maximum number

  . clichés, the group will delete the oldest snapshot for planning

  . to create a new snapshot.

  Snapshot are deleted in the background queue. The group travels

  the snapshot page table and decremented the reference count on every shared page.

  Any page that has a zero reference count is released into free space. Pages

  with a zero reference count are not released because they are shared with

  the volume or other snapshots.

  Because stereotypes can be automatically deleted, if you want to keep the

  given to a snapshot, you can clone the snapshot.

  Reserve snapshots use agreement

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

  The snapshot reserve is consumed only if you write a shared volume or snapshot

  page. However, it is difficult to establish a correlation between the amount of data written in one

  volume (or snapshot) with the amount of instant reserve consumed as a result.

  especially if you have multiple snapshots.

  Because the pages consist of several logical blocks, size e/s and distribution

  volume merge affect overall performance of e/s in addition to the snapshot

  reserve its use.

  For example, do much written about a narrow range of logical blocks in a volume

  consumes a relatively low amount of reserve of the snapshot. This is because as Scripture

  the same logic block more than once, does not require not additional snapshot

  reserve.

  However, doing random number wrote a range of logical blocks in a

  volume can consume a large amount of reserve of the snapshot, because many other

  pages are affected.

  In general, use instant reserve depends on the following:

  1. number of entries that occur in the volume (or snapshot) and at least one

  . snapshot exists. In general, more Scriptures tend to use more snapshot reserve.

  . Although multiple writes to the same logical block do not require additional

  . space.

  2 - the range of logical blocks, on which occur the Scriptures. Written in a wide range of

  . logical blocks tend to use more instant reserve written in a narrow

  . rank, because more of the written word are to different pages.

  3. number of snapshots of the volume and timing of the write operations. Most

  . snapshots that you create more snapshot reserve is necessary, unless there is

  . few entries on the volume or snapshots.

  4 - age of snapshot. Snapshots older tend to consume more snapshot reserve only

  . the clichés of recent because the group must retain the original data for a

  . longer time.

  Design Snapshot reserve

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

  You cannot create snapshots until you book instant space. Snapshot reserve

  is set as a percentage of the reserve volume (space) for the

  volume.

  When you create a volume, by default, the volume uses instant group-wide

  reserve adjustment. (The reserve in the scale default setting is 100%. You

  can change this default value.) You can change the reserve snapshot setting when you

  create a volume or later, even if the volume is in use.

  Although the snapshot reserve is not used until the volume or writing snapshot occur, it

  is consumed immediately free pool space. For example, if you create a

  fully allocated (not thin provisioned) 200 GB volume and specify a snapshot of 50%

  pool of reserve, free space is immediately reduced to 300 GB (200 GB for the volume

  reserve and 100 GB for Snap reserve), even if there are no pages in use.

  Therefore, before you create a volume, you should consider how many snapshot

  reserves, if any, to assign to the volume. The reserve of the snapshot set to zero (0)

  If you do not want to create snapshots.

  The optimal size of the snapshot reserve depends on the amount and type of

  changes in the volume and the number of shots you want to keep.

  By example, if you set the snapshot reserve 100%, and then create a snapshot.

  You can write to each byte of the volume without missing snapshot

  reserve. However, if you create another snapshot and then write in each byte of

  the volume, the first snapshot is deleted in disk space available for the new snapshot. If

  you set the instant reserve at 200%, there would be a sufficient reserve of snapshot

  for the two snapshots.

  A very conservative strategy in terms of instant reserve sizing is to put the snapshot

  book value at 100 times the number of shots you want to keep. This

  guarantees that keep you at least the number of snapshots, regardless of the

  the number of entries on the volume. However, this strategy is generally allocates

  book an excessive amount of snapshot, because that rarely crush you all the

  the data in a volume during the lifetime of a snapshot.

  The best way to instant size reserves is to assign an initial value to the reserve

  and watch how instant you can keep over a period of time specified under a

  normal workload. If you use tables to create snapshots, allow the

  calendar of work for several days.

  To get an initial value for a snapshot reserve volume, you must estimate

  the quantity and the type of entries in volume and the number of snapshots, you want

  keep. For example:

  -If you wait a few Scriptures or writings which are concentrated in a narrow range

  . logical blocks and you want to keep only a few shots, start with a value

  . 30%.

  -If you wait several entries or entries that are random in a wide range of

  . logical blocks and you want to keep more than a few shots, start with a value

  . 100%.

  If the snapshots are deleted until you reach the desired number of snapshots,

  increase the percentage of snapshot reserve. If you reach the desired number

  shots without consuming much of the instant free reserve, decrease the

  percentage of reserve snapshot. Continue to follow instant reserve and

  adjustments as needed.

  How Thin Provisioning button Snapshot Reserve

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

  The snapshot reserve is based on a percentage of volume reserve (allocated space

  a volume). For a volume fully provisioned, the reserve volume is equal to the

  stated volume size. However, a thin volume put into service, the volume of reserve

  is initially very inferior to the reported size (default is subject to minimum volume

  10% of the reported size) and increases as the written volume occur.

  If you change a thin volume supplied in a volume fully provisioned, the

  amount of reserved snapshot increases automatically, because the volume of reserve

  increase in the size of the stated volume.

  If you change a volume of fully provisioned to thin-provisioned, the amount of

  snapshot of reserve decreases automatically, because the volume of reserve declines.

  However, if the snapshot resulting reserves will be too small to store all the

  existing snapshots, the group will automatically increase the instant reserve

  percentage of value that preserves all existing snapshots.

  Reducing the use of instant reserve

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

  Over time, you can reduce the use of instant reserve by periodically (for example,

  Once a month) defragmentation of databases and file systems. Defrag operations

  try to consolidate segments of files in a volume and, consequently, to reduce the scope

  logical blocks addresses used in the pages of the volume.

  Defragment the data read operations from one place and then write data to a new

  location. So increased use of instant reserve during and immediately

  after defragmentation, because existing snapshots will use more of the usual

  amount of the snapshot reserve. However, snapshots created after defragmentation

  operation must use less instant reserve, because the data on the volume are more contiguous.

  When a volume is highly fragmented, potential reduction of the snapshot reserve

  use can be dramatic, especially after removing the large before you defragment

  snapshots. Defrag operations can also reduce the I/O load on the group,

  because the contiguous data makes more efficient i/o operations, in order to improve the

  e/s overall performance.

  Latest defragmenters are good to reduce the fragmentation that is not seeking to be

  too thorough. Some defragmenters also try to combine the inactive data

  further restricting the likelihood of changes to shared pages. However, are not

  Defragment too frequently.

  Sector alignment may also affect the use of snapshot of the space, especially in

  larger volumes. File systems must be correctly aligned with the sector. It comes

  described in technical reports for VMware and Windows environments.

• Overview in vSphere Web Client?

  Hi community

  In vSphere Client c# , I had the chance to see an overview of all virtual machines and their snapshot spaces: home - inventory - warehouses and store data from cluster - storage tab views.

  By selecting my data center on the left, I had a glimpse of all the VMs on a data center and size of snapshot (on all data warehouses). See my attached screenshot.

  I just upgraded my vCenter to 6.0U2, so I did not tab views storage more.

  Does anyone know how to proceed with the Web Client vSphere? I don't want to check every vm or each data store but would like to have a similar overview of instant spaces of all the virtual machines on all data warehouses.

  Best regards

  Roland

  Version 6 does not offer this view more, see this KB article: VMware KB: The Storage Monitoring Service plug-in installs in VMware vCenter Server 6.0

  In VMware vCenter Server 6.0:

  • The selection of storage reports tab monitor an object is no longer available in the Web Client vSphere 6.0.
  • Tab views storage is no longer available in the vSphere Client 6.0.

  As I said before, you have the possibility to use RVTools or something like PowerCLI and vRealize Operations Manager, see this thread another talking about the same thing: the storage vsphere6 reports

  We were using display of storage reports to audit for forgotten shots. So far, there are some alternatives to see the snapshot size

  Use of Ops 1 Manager) and a heatmap personalized, note the Foundation (for some free version) does not have the feature. As we use Foundation, it is not an option.

  (2) RVTools - GUI based (easier for some) but pretty basic

  (3) PowerCLI - yup, get used to it. (get - vm | get-snapshot |) FT VM, SizeGB, created, name, Description)

• VStorage different Motion - copy of the file on a data store vmdk

  Hi all

  Hoping that someone will be able to help with a problem I have right now.

  Configuration:

  NetApp SAN - vmfs data warehouses.

  Data for the migration store is synchronous to a recovery site.

  I planned a day to the next task to migrate a VMDK virtual machines to a non synchronous Datastore to synchronous data store.  When I arrived yesterday morning - the virtual machine has been turned on - but I couldn't access the console and migration was still sitting 89% full.

  Checked the Netapp Filer and found the copy of the snapshot is greater than the instant space on the volume.

  SnapMirror suspend and break.  Delete the copy of Netapp snapshot on the volume.  Once I had done this on the Netapp file server - virtual machine has begun to respond to ping and I was able to access the console.

  I restarted the VM Windows - to make sure everything was fine - as the date / time on the server was out of sync with the date and time - so again, I am happy that my virtual machine is now in place and running.

  Problem. : I migrated virtual disks - one both of the old data store to the new - no problems - until I'm gone make the last record and felt that there is not enough space on the data store - now it would have taken and further investigation found that the virtual disk I wanted to migrate — was already sitting on the new data store.

  Check the settings on the virtual machine shows that the file in question vmdk is still sitting on the old data store - but - I also have a copy of the vmdk - same size etc. - file sitting on the new data store.

  RVtools displays the disk on the new data as a Zombie VMDK store.

  Question: What vmdk file is the one I need to remove?  I think about the new data store - in addition, shown as a zombie in RVTools vmdk - also, shows only not the settings of the virtual machine.

  All find what vmdk file, the system uses permanently.

  Thank you very much

  Open the .vmx file and check the path to your vmdk here.

  If you can, backupo the VMDK at both ends before going any further.

  as the VC (and I hope that the .vmx), as well as RVtools indicate that the destination is a zombie. . I would lean towards this being the one to delete.

  In theory, if you use the browser to store data to try to remove a new and it's in use, you will get an error message, so if it removes OK, you should be good to continue from where you were before.

  Good luck.

• Probability of success of 3 to capture instant removal if system itself takes about 3 TB and he left only about 70 GB of space on the VMFS5 partion (vSphere 5.1)

  Hello.

  I have a problem... Computer virtual located on the storage VMFS5 vSphere 5.1 partition has 3 files vmdk (1 for each partition of data under windows 2008 server, ~ 1 TB each). There were snapshot taken by this system, which currently used almost all of the space available on the storage partition. I need to remove this snapshot, it is no longer necessary, but he doubts if there is enough free space left on that partition to detele instant (~ 70 GB on the left). I would be able remove snapshot or I get this operation migrate VM to a different data store VMFS5 with more space to this topic?

  It depends on whether the virtual disks are provisioned thin or thick. With thin configured virtual disks you will probably not be able to delete snapshots, because basic disks may develop. However, with thick, configured virtual disks basic disks will be will develop not just yet, so delete the snapshots should work without problems with the virtual machine off! Remove the snapshot with a virtual machine under tension will create snapshots of assistance, which will develop according to the activity of the virtual machine and cause a problem of out-of-disk space.

  André

• Cannot convert Server 2008 R2 Machine get error: Instant The VSS cannot be stored, because there is not enough space on the source volumes or because the source computer does not all NTFS volumes. Error code: 2147754783 (0x8004231F).

  I have a couple of server 08 R2 machines where the P to V conversion fails.  I did some research and the problem seems to be related to the system reserved Partition that has 0% available 100 MB free space.  Conversion fails with the error below.

  VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source computer has not all NTFS volumes. Error code:
  2147754783 (0x8004231F).

  
  

  Someone had this problem and came to the top with a solution or to get around?
  

  
  

  Thanks in advance
  

  Guessed it.  My snapshots Appassure did not also exist with a similar error, so that's what I did to solve it.  My servers now converted without any problem.

  1. Open disk management.
  2. Look at the partition of the PRS and see if it is 100% full.
     • If Yes, proceed to step 3.
     • If this is not the case, check if there are readers who have no more of 300 MB free (minimum requirement to use VSS).
  3. Click a drive, select properties and then select the instant snapshots tab.
  4. Ensure that all shadow copies are disabled and no limit on all players.
  5. Go to the partition of the SRP and assign the B:drive letter.
  6. Open the B: drive via disk management, and then locate the folder System Volume Information. Note: if necessary, change the folder options so that you can view hidden files, folders and drives.
  7. Right-click the System Volume Information folder, and then select Properties.
  8. On the Security tab, click Edit, and then add the group with full control everyone in the folder.
  9. Open the System Volume Information folder (you should see log files are full), open a running as an administrator command prompt and then type the following commands to unload the filter driver.
     • B:
     • B:\>FLTMC UNLOAD AAFSFLT
  10. Navigate to the System Volume Information folder, and then type the following commands:
      • B:\>CD System Volume Information
      • B:\System Volume Information > AALOG_ DEL * (this will remove all of the log files, and then re-create a new)
      • B:\System Volume Information > CD\
      • B:\>FLTMC LOAD AAFSFLT
  11. Close the command prompt window.
  12. In Windows, right click on the reserve system folder and remove the Group everyone.
  13. In Disk Manager, remove the B: drive (and click Yes when prompted with a warning window).

• Tried to remove the capture instant, insufficient space, space, how I now remove it?

  Hello

  I had a good search of the forum and knowledge base but cannot find someone with the same problem. If anyone has any suggestions, I'll be very grateful...

  Performance of Fusion 2.0.5 on Macbook with Windows XP in a virtual machine.

  I was running short of disk space on my hard drive then thought delete my and only instant (plug for a long time with Fusion 1) would be without space.  However, I didn't know that you had need of enough space to work on stereotypes.

  Remove failed with the following message "there is not enough space on the file system for the selected operation.  The snapshot has not been deleted, but the icon for that so it is more in the Snapshot Manager.  So despite freeing the space required, I can't repeat.  Is it possible to do it manually through the console.

  The relevant section of ~/Library/Logs/VM Fusion/vmware - fusion.log:

  17:00:23.502 Aug 05: unknown | SNAPSHOT: Consolidation of the ' / users/mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro work - 000001.vmdk' to ' / users/mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro Work.vmdk'.

  05 August to 17:00:23.669: vmfusion | -[PLGuestAppMgrDelegate updateHandlers]: comments does not "Manager set" capacity, does not update managers of guest.

  05 August to 17:00:23.669: vmfusion | -[DUIGuestAppMgr refreshGuestAppsToPublishWithDelegate:doneSelector:contextInfo:]: comments not has not the ability of the unit, not re - publish proxy applications.

  17:00:23.809 Aug 05: unknown | DISKLIB-DSCPTR: open : "Windows XP Pro Work.vmdk" (0x18)

  17:00:23.809 Aug 05: unknown | DISKLIB-LINK: open ' / users/Mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro Work.vmdk' (0x18): monolithicSparse, 62914560 sectors / 30 GB.

  17:00:23.809 Aug 05: unknown | DISKLIB-LIB: open ' / users/Mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro Work.vmdk "(flags 0 x 18).

  17:00:24.022 Aug 05: unknown | DISKLIB-DSCPTR: open : 'Windows XP Pro work - 000001.vmdk' (0x18)

  17:00:24.022 Aug 05: unknown | DISKLIB-LINK: open ' / users/Mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro work - 000001.vmdk' (0 x 18): monolithicSparse, 62914560 sectors / 30 GB.

  17:00:24.022 Aug 05: unknown | DISKLIB-LIB: open ' / users/Mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro work - 000001.vmdk "(flags 0 x 18).

  17:00:24.052 Aug 05: unknown | DISKLIB-LIB: not enough space to combine. Have 4873404416 bytes, 20842414080 bytes, of need. 17:00:24.053 Aug 05: unknown | DISKLIB-LIB: Impossible to combine: there is not enough space on the file system for the selected operation (81415693). 17:00:24.053 Aug 05: unknown | In SUMMARY: SnapshotCombineDisks: impossible to combine: there is not enough space on the file system for the selected operation (81415693). 17:00:24.362 Aug 05: unknown | In SUMMARY: SnapshotConsolidate failed: there is not enough space on the file system for the 17:00:24.362 Aug 05 selected operation (5): unknown | SNAPSHOT: Consolidate failed: there is not enough space on the file system for the 17:00:24.690 Aug 05 selected operation (5): vmfusion | Status of power (reported) poweredOff Aug 05 17:00:24.695: vmfusion | Reloading of config State: users/Mark/Documents/Virtual Machines.localized / Windows XP Pro Work.vmwarevm / Windows XP Pro Work.vmx 17:00:24.761 Aug 05: vmfusion | VMHS: Transition vmx/execState/val of poweredOff 17:00:24.768 Aug 05: vmfusion | Cmd /vm/ #3a34b888e28f7421/cmd / # 74e8/op/poweredOffConsolidate/failed: unable to clean up deleted files: 17:00:24.768 Aug 05: vmfusion | There is not enough space on the file system for the selected operation, GB 19.4 free on the file system and try again. 05 August to 17:00:24.768: vmfusion | Cmd /vm/ #3a34b888e28f7421/cmd / # 74e5/op/snapshotConsolidate/failed: unable to clean up deleted files: 17:00:24.768 Aug 05: vmfusion | There is not enough space on the file system for the selected operation, GB 19.4 free on the file system and try again. 05 August to 17:00:24.824: vmfusion | SnapshotTree: Build failed: failed to clean up deleted files: 17:00:24.824 Aug 05: vmfusion | There is not enough space on the file system for the selected operation, without 19.4 en on the file system and try again.

  Any suggestions would be welcome!

  See you soon,.

  Mark

  With stop the Virtual Machine, not suspended, take a new snapshot, and then delete it immediately. This will force the orphaned snapshots should be deleted in the process, or you will always have a problem and if the later then the only option is to create a new Virtual Machine using Disk Imaging of one kind or another. Products such as Symantec Norton Ghost can be used or even dd from an Image of CD/DVD/ISO of OS Linux Live or you can use VMware vCenter Converter.

  BTW I suggest you make a backup copy of the virtual machine or the rental very a full user of the virtual machine data backup before trying anything.  Keep in mind that in all cases it must have enough free disk space to solve this problem, even if an external hard drive to be used temporarily to facilitate the process.

• Backup Exec and instant / add disk space

  I use Backup Exec to make full VM backups

  After the backup, I can see a snapshot to the virtual machine in the Snapshot Manager

  I deleted all the snapshots of the virtual machine and stop the virtual machine.

  At this point providing drive area is grayed out and e/s can not add disk space on the existing drive

  I don't see that there is a-000001, 000002 vmdk still kicking around in the virtual machine folder

  (a) is it safe to delete the 00001 and 0002?

  (b) any idea how to prevent the creation of the Snapshot Backup Exec files

  Thank you

  Steve

  It is a VM DC

  It turns out that Backup Exec was hung on the VM backup

  Once I canceled the backup, I was able to consolidate

  Thanks for your help

  Steve