Snapshot question

Similar Questions

• Image not available snapshot - Question on usability in view Manager

  I was invited to establish a pool of linked clone VMs will be used for vWebservers on our network.  I just wanted to get some advice first and an answer to a question.

  First of all - I have just built a Windows 2003 r2 Enterprise image, installed the agent of the view out of the IP and it turned off to take a picture.  Once I took the snapshot - I jump in the view manager, start to build my pool, but it is not a list for the VM parent I am looking or the snapshot of what I created.  Could someone help me on this if you have any advice?

  Next - the pool is I'm creating is going to be several web servers associated with a model.  Is it possible to configure each of the child elements of the pool to have static IP addresses that hold their NIC configurations, even after I do an update of model parent?  I realize that the view is more user/desktop based, but demand has come to me looking for what it is.

  Thanks in advance!

  Theandyorr,

  View does not support creating pools of office with server operating systems.  You are limited to Windows XP and Vista VMs - see page 17 of the Guide of Directors 3.1 views: http://www.vmware.com/pdf/view31_manual.pdf

  ~ Aaron Patten

• Snapshot question: replaced VMDK in comments

  Hello

  I have a guest from Vmware, customers running Windows 2003.  The client is configured with a single hard drive SCSI, but I ran into a situation where there was not enough space on disk/partition C: from the prompt (the original VMDK was 16 GB, with two partitions, C: and D :).)  I also have a bunch of shots of this comments so far, and the VMX pointed to the last snapshot, VMDK, something like "xxx - 0012.vmdk".

  I did not see a way to increase the size of the VMDK in place, so what I did was:

  -Use vmware-vdiskmanager and created a new prealloues 20 GB VMDK, "big.vmdk."

  -Use Vmware to change the configuration of comments and added a new drive to the guest, pointing to "big.vmdk".

  -J' then started the guest in bare metal of imaging product I use, BootItNG and BootItNG to clone the C: partition from the original drive to the new drive.  I then used BootItNG to resize the C: partition.

  -J' I then re-configured the invited and removed the drive corresponding to the 'xxx - 0012.vmdk", for now: the guest had only 1 drive, pointing to"big.vmdk ".

  I was then able to start the client for Windows, with the largest disk.

  Everything worked, but now I'm a little puzzled by the situation with snapshots.  In particular, what happens if I try to take a snapshot of the guest at this stage?

  I think that the snapshot is supposed to create a differential VMDK containing changes compared to the previous backup, which is the 'xxx - 0012.vmdk", right?

  So if I now take a snapshot of the prompt, what happens?  I end with potentially a snapshot of 20 GB VMDK?

  Thank you

  Jim

  If I do what you suggest, and before I take the 1 snapshot, this comments will have no snapshots at all at that time here?

  I think that the answer is Yes?

  Fix. That's why you should delete the file .vmsd.

  That would be ok, but I think that before I do, I'll back up the directory to another drive (which has space).

  It is a good idea.

  ... and I think I should be able to do this by adding a new guest from that saved directory, right?

  Right. You can create a new virtual machine and add the initial ramdisk. However, you will need to change the new virtual machine configuration (.vmx) file and set the disk for the instant vmdk virtual you manually, since this can be done in the GUI.

  André

• Snapshot questions

  So one of my virtual machines had a glimpse into its VM folder in the data store, however the snapshot does not appear in snapshot manager. So I deleted the snapshot file and its secondary .vmdks in the folder of the virtual machine. However now I have leftovers of the snapshot which give me error messages when I try to 2 delta.vmdks felete it say it cannot be deleted.

  He also says, when I try to take a new shapshot of the virtual configuration snapshot invalid machine.

  Im guessing that I saw something somewhere.

  Hello

  you were rt abt the last part, u saw things a little here. I'm sure that you will not be able to take snapshots on the virtual machine. If you want to use the virtual machine with ease of snapshot, then I suggest to

  1 unregister the virtual machine from the ESX

  2. create a new virtual machine and run the virtual machine to use the vmdk < directly to the source vmdk >

  3. turn on the virtual machine with ease of snapshot. However, you will lose previously created on the virtual machine snapshots.

  THX,

  Selva

• Potentially simple Snapshot question

  Hello. I think it would be a simple thing to look upward, but for some reason that I can't find the answer to the it.

  I am running Vi3 with ESX 3.5i hosts 4. I need to know exactly where a VM snapshot records in. I have a 250 GB drive on an FTP server that I have I envy snapshot in the future. I just formatted a table iSCSI with 440GB LUN. So if a snapshot of my 250 GB drive MUST reside on the same LUN as the original machine, obviously I would not have enough space. Can I choose where to store my snapshots?

  Thanks for the help,

  Tim

  With the VM snapshot, they are stored in the same directory as the virtual machine.  That said, when you create a snapshot it saves only the changes and therefore the space requirements depend on how long the snapshot has been kept active. Committing, it's quite abit more complicated, but as long as you do not have an active snapshot or multiple snapshots on the virtual machine, you need also not 250 GB in order to commit (which would be just inefficient).  Unfortunately I do not know a calculation that will allow you to say that, because it is based on the number of changes and levels of snapshots on the virtual machine.

  I think that it is possible to change the directory stored in the snapshot, from the command-line editing the VMX file, however I do not recommend to change.  I don't remember the exact setting off my head to do it.

  See you soon,.

  / Jonathan

• ATG BCC business test case?

  Hello

  I want to test a condition at the CCI for the product catalog, I category that contains several products of the child, what happens to the products of the child when the respective category is removed? In the BCC field, we have categories and products as part of the navigation of the catalog. Please let me know how we can create a new project in BCC and add category - under which add the respective products and remove the category can see what happens if it is throwing an error or not before deployment? How to do? If I create a CCI project in "Trade Merchandising" by selecting the 'active' trade, then I can only navigate through the catalog, but how do I create a new project, BCC and add categories and respective products under it and then delete the category and see what happens? Please specify any documents or links are really appreciated.

  Thank you

  Please tick the correct answer so it is easy for others to find.

  And you must force the snapshot by watching the latest snapshot of database. Follow link below:

  ATG BCC SnapShot question ~ NAT

  Peace

  Shaik

• 10 issues in vmware with markets resolvation

  Hello

  Can u send most common common 10 questions in vmware with markets resolvation.

  Wres

  DJ

  Where to start and where to end?

  Some I can think of:

  -No hardware support--> check http://www.vmware.com/resources/compatibility/search.php HCL

  ---> Http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf compatibility issues

  -Storage issues--> choose the correct storage for your needs: storage vs. local storage, size LUNS/disks, controllers, shared write cache

  -hosts too much or too little used--> make an assessment of what you want to virtualize (IOPS / s, CPU, RAM, disk space,...)

  ---> Overcomitment of central units (for example 4-8 vCPUs for a virtual machine) use fewer vCPUs

  -Snapshot questions--> http://kb.vmware.com/kb/1015180

  -Install network--> http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf

  -VMware Tools--> always install VMware tools in the virtual machines

  -There are no backup backup--> snapshots! Make sure you have a backup strategy.

  -Keep up to date--> for example VMware KBs to http://blogs.vmware.com/kbdigest/

  André

• Backup - Snapshot issue / question.

  Greetings,

  I have a fairly new 5.5 ESXi update 2 installation (Essentials). (September 2014).  Currently, I have only a VM on it. It is a stand-alone Server SBS 2011 standard conversion.  The virtual machine works fine without any problems.
  

  The only issue I'm having is with my Barracuda backup system.   It fails at the end of the backup while trying to create a snapshot. I know what you think.  "Why I write this here? '...
  

  I go back with the support of Barracuda.  Everything that they asked me to check, host-wise, wise system and guest-wise I could do and are come empty-handed.  See between the asterisks below for tit last correspondence I had with them (they did the highlighting).
  

  I'm not very well the workings of VMware, so I don't really know where to go from here. Because I came before empty, I'm not even sure that Barracuda is on the right track here.  But I need to get back to them before they will help me any further.  I just need to some advice and assistance to determine if it actually, the question, and if it is, how to remedy or continue troubleshooting.
  

  Thanks for any idea and assistance, you may be able to provide me with.

  
  

  PEI

  Start of Barracuda support *.
  

  "Look in the error, I see that it looks to be another process running at the same time the backup is running or something is not finished before start backups." "That's what I see in the newspaper of bbs:

  26 Dec 11:31: 27 2014 barracuda backupd [14271]: failed to create the snapshot (vim25_TaskInProgress): another task is already underway.
  26 Dec 11:31: 27 2014 barracuda backupd [14271]: fatal: could not create any backup host vmware snapshot: SFD-SRV1. Stratfire.local

  
  

  End of support for Barracuda *.

  
  

  
  

  Hi p...

  The list of files seems ok now?  It's much better from my point of view...

  If so, it looks like success all around. See the attached list after deleting all.  I'll remind the Barracuda.

  I can't thank you enough for all your help and patience.  You really are an asset to the VMware forum community.  Thank you for taking the time to work with me. I learned a bit about yourself.

  Thanks again

  P.

• questions about snapshot

  (my first post here... Please let me know if this isn't in the right place)

  
  

  I have a few questions on the snapshot after reading a bunch of KB articles:

  
  

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1025279

  -Don't use any single snapshot for more than 24 to 72 hours.

  Most of my live pictures for a long time and I have not noticed any problems. I do not understand why such suggestion.

  
  

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1013163

  ' In this example, the process took about 64 seconds... ". »

  This sounds like the take a snapshot on a production server might be a risky company is - it true?

  
  

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003302

  -I see that consolidate you option on vSphere and it also indicates if a virtual machine needs it or not, but what are the criteria? I understand that if you take a snapshot, the content of the link delta gets grouped in the parent disk, but when should you do consolidate without deleting?

  When you create a snapshot, a delta VMDK is created for each VMDK. These delta VMDK can grow bigger as size put into service of the VMDK. The problems are to have a free space on data warehouses. The longer a snapshot around, he can take to commit the changes when you remove it. In addition, to commit the changes, you must have enough free space on the data store equal space in service of the virtual machine itself.

  I saw snapshots is damaged after staying close to a lot of time. In addition, the more instant stored with a virtual machine, more corruption risks.

  I manipulated the environments with lots of snapshots and it was rough. I had the VMs is damaged and must be restored from backups on a regular basis.

  I avoid them when I can.

  Backup software is a better choice. As Veeam!

• Get - vm | question of Get-snapshot...

  I have the following line in a script

  $VMSnapshotReport = get - VM | Get-Snapshot | Select-Object VM, name, Description, created, SizeMB | Out-string

  The output looks like ths:

  VM: ThinAppWindows7

  Name: After pre-scan

  Description: After pre-scan

  Created on: 06/03/2012 12:12:22

  SizeMB: 1881.3

  My question is simple: is it possible to add a 'Select-Object' that will display the data store of the virtual machine?  Because after this line is another line that displays the statistics of data store (Get - VM |) Get - Datastore).  The goal is, that big shots, we can examine the output file and make sure that the data store is fit to support keeping the snapshot autour, etc..

  THX

  Try it like this

  $VMSnapshotReport = Get-VM | Get-Snapshot |
  Select-Object VM, Name, Description, Created, SizeMB,
  @{N="Datastore";E={[string]::Join(',',(Get-View $_.VM.DatastoreIdList | %{$_.Name})}} | Out-String
  

• Questions of snapshot after lack of space on Virtual Mode RDM

  We have a windows file server that ran out of disk space for its virtual RDM mode.  The server has several outstanding shots (VCB-created).  The LUN has been expanded and serve hung and restarted.  Restarts, none of the snapshots are loaded--just the VMDK origin.  None of the snapshots are displayed in the Snapshot Manager.

  If the sanpshots can be removed (commit all) or is it likely to corruption in the last Flash disk?  Wouldn't be better to remove the last snapshot and delete everything.  All the world is this themselves before?

  Thanks in advance for any idea that you can share.

  Hello

  I was wondering if you mind answering some questions before tackle us this?

  When you say

  Server that ran out of disk space, because it is the virtual mode of RDM

  do you mean the data store that hosts the virtual RDM or the actual volume of RDM file?

  Can you also check your VI client and see what VMDK virtual machine thinks it is running off? i.e. servername.vmdk or servername - 000001.vmdk

  Thank you and best regards,

  Glen

• Question about snapshots and virtual machines

  Hi all

  I have a small question about snapshots. I use VMware for about 6 months and I read about snapshots and how they work but still have a question to make sure that I understand how it works and it will work the way I think it works.

  I have a Windows 2003 server, which is a virtual machine. I have an application that uses MSDE database. I want to upgrade the database to MS SQL 2005, but to do this I need to back up the MSDE database, uninstall MSDE, and then install SQL 2005 and move the SQL database. This happens on the same VM.

  What I was thinking if I well Snapshots correctly is to snap turned the virtual machine before doing anything. Then do my upgrade steps and see if everything works. If its all messed up so I should be able to return to my shot and everything should be the way he had. What is the good? One of the main reasons I moved the server VM was because of this upgrade.

  After reading the documentation for the snapshots, it's how I undestood it. Pretty much any change could be reversed with snapshots. I wish just they had put in a few examples in the PDF file. Also it would be the same for all type of grades of the OS? Could I snapshot a Windows 2000 Server, and then "in the upgrade of the square" to Windows 2003? I've cloned a VM to do this but was curious about whether snapshots would be just as easy.

  Thanks for your help.

  Hello.

  What I was thinking if I well Snapshots correctly is to snap turned the virtual machine before doing anything. Then do my upgrade steps and see if everything works. If its all messed up so I should be able to return to my shot and everything should be the way he had. What is the good?

  That is right.

  After reading the documentation for the snapshots, it's how I undestood it. Pretty much any change could be reversed with snapshots. I wish just they had put in a few examples in the PDF file. Also it would be the same for all type of grades of the OS? Could I snapshot a Windows 2000 Server, and then "in the upgrade of the square" to Windows 2003? I've cloned a VM to do this but was curious about whether snapshots would be just as easy.

  Exactly the same thing for the upgrades of the OS.

  Perhaps the most important thing with the snapshots is to keep an eye on them and don't let them sit too long or become too big.  You have described the use cases are very good uses for snapshots.  Just make sure you have a solid plan with a schedule set, so that you can come back or validate changes before the snapshot becomes too large.

  Good luck!

• 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.

• Question about task scheduled task to create snapshots of computer virtual

  Hello

  We run 5.1 ESXi hosts.

  There is a requirement of applications consultant to do instant schedule for a particular virtual machine.

  I have set up the scheduled task, BUT would like to know is possible to specify how long the snapshot schedule to run?  As: 3 days OR between 01/05/2015 and on 05/03/2015?

  Your opinion is requested.

  Thank you

  Post edited by: TonyJK

  You can write a shell Script that will take the system time and do the comparison if it's more than an hour, you can trigger 'vim - cmd vmsvc/snapshot.create vmid' with the name of snapshot of timestamp.

• GhettoVCB and the Question of the snapshot

  I ' n trying to back up a computer virtual with GhettoVCB and its failure by saying a snapshot is present.  There isn't one in the Snapshot Manager so I created a snapshot and then made a completely remove but it is always a failure.

  I had a quick glance in the data store, and I can see that there is a delta file.  I think its an old file snapshot that is not used, but wanted to check before I deleted the.  It is the directory listed since the data store;

  drwxr-xr-x 1 root root 3780 18 Oct 12:40.

  drwxr-xr-t 1 root root 1960 19 June at 09:03.

  -rw - r - r - 1 root root 7 Sep 2013 chw - vm - 02.cheeswrights.local 73 - 346bdcd4.hlog

  -rw - 1 root root 8589934592 Sep 11 2013 chw - vm - 02.cheeswrights.local - 346bdcd4.vswp

  -rw - r - r - 1 root root 13 18 Oct 12:40 chw - vm - 02.cheeswrights.local - to the .xml

  -rw - 1 root root 6554112 18 Oct 12:41 chw - vm - 02.cheeswrights.local - ctk.vmdk

  -rw - 1 root root 107374182400 Oct 12:52 chw - vm - 02.cheeswrights.local - flat hard 18

  -rw - 1 root root 8684 18 Oct 12:41 chw - vm - 02.cheeswrights.local.nvram

  -rw - 1 root root 620 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmdk

  -rw - r - r - 1 root root 46 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmsd

  -rwxr-xr-x 1 root root 4243 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmx

  -rw - 1 root root 0 Sep 7 2013 chw - vm - 02.cheeswrights.local.vmx.lck

  -rw - r - r - 1 root root 283 17 Oct 09:28 chw - vm - 02.cheeswrights.local.vmxf

  -rwxr-xr-x 1 root root 4250 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmx ~.

  -rw - 1 root root 252071936 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001 - delta.vmdk

  -rw - 1 root root 364 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001.vmdk

  -rw - 1 root root 4915712 18 Oct 12:41 chw - vm - 02.cheeswrights.local_1 - ctk.vmdk

  -rw - 1 root root 322122547200 Oct 12:52 chw - vm - 02.cheeswrights.local_1 - flat hard 18

  -rw - 1 root root 624 18 Oct 12:40 chw - vm - 02.cheeswrights.local_1.vmdk

  -rw - r - r - 1 root root 1366075 28 June 2011 vmware - 4.log

  -rw - r - r - 1 root root 1294553 July 5, 2011 vmware - 5.log

  -rw - r - r - 1 root root 1285971 Aug 23, 2011 vmware - 6.log

  -rw - r - r - 1 root root 1295743 26 April 2013 vmware - 7.log

  -rw - r - r - 1 root root 1318787 July 31, 2013 vmware - 8.log

  -rw - r - r - 1 root root 240174 Sep 7 2013 vmware - 9.log

  -rw - r - r - 1 root root 44435410 18 Oct 12:42 vmware.log

  And it's the .vmx for the virtual machine disks:-

  scsi0:0. FileName = "chw - vm - 02.cheeswrights.local.vmdk"

  scsi0:1.filename = "chw - vm - 02.cheeswrights.local_1.vmdk"

  scsi0:2.filename = ' / vmfs/volumes/522857d3-a99e32f2-6ca5-3c4a92f58408/chw-vm-02.cheeswrights.local/chw-vm-02.cheeswrights.local.vmdk '.

  Given the two files associated with the snapshot are dated in February, and the .vmx isn't SEO and I sure to delete following text: -.

  -rw - 1 root root 252071936 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001 - delta.vmdk

  -rw - 1 root root 364 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001.vmdk

  Thank you!

  I tend to say yes, it seems that, in this case, they are obsolete files. However, if you can afford a short downtime, I recommend you stop the virtual machine, create a subdirectory, move the files to capture two instant in the new subdirectory and then put on the VM again. If everything works as expected, you can then delete the files.

  André