Multiple snapshots

Similar Questions

• Take a multiple snapshot of different VM´s

  Hello

  Anyone got a script to take different VM´s. example multiple snapshots when you windows patch id like to snapshot slected vm´s before applying the patch.

  Concerning

  Christer S

  Hi Chrsun02,

  "is it a medium esay to ad a function report to the commnad.

  Please tell more that you want to report on

  "im"wishing to' an easy way to get rid of stereotypes when I know that servers is ok. "

  Right, so before patching, you created snapshots for some virtual machines, and gave you the name of the snapshot for this purpose.

  for example

  Get - vm testgk | New-cliché - memory: $false - suspend: $false-name "testsnapshot001" - Description "my snapshot test patch before.

  on my vm testgk, I created the new snapshot with the name "testsnapshot001" for this pupose

  now I want to remove it

  Get - vm testgk | Get-Snapshot? {$_. Name - eq "testsnapshot001"} | Remove-Snapshot

  So I have vm testgk query, ask this virtual machine snapshots that have name testsnapshot001, and then delete the snapshot.

  If you have created snpahosts for more virtual machines give their name separated by a ",".

  Get - vm "vm1', 'vm2', 'vm3 | Get-Snapshot? {$_. Name - eq "testsnapshot001"} | Remove-Snapshot

  If you're sure you didn't any what other snapshots you can omit this part?: {$_. Name - eq "testsnapshot001"}

  so in the end, you would write:

  Get - vm "vm1', 'vm2', 'vm3 | Get-Snapshot | Remove-Snapshot

  If you don't want to answer the question confirmation add - confirm: $true

  Get - vm "vm1', 'vm2', 'vm3 | Get-Snapshot | Remove-Snapshot - confirm: $true

  If you want to specify vms not with names but with location:

  Get-cluster "my_cluster01" | get - vm | Get-Snapshot | Remove-Snapshot - confirm: $true

  If you want to get a report for snapshots:

  Get - vm | Get-Snapshot? {$_.name - eq "testsnapshot001"} | Select the name of name,@{N='VM'; {E = {$_.vm}}, @{N = "CreatedOn"; E={$_. Created}}

  So it will go through all of the virtual machines, instant advertising with the name: testsnapshot001 and display its name, date, name of the virtual machine

  Get - vm | Get-Snapshot? {$_.name - eq "testsnapshot001"} | Select the name of name,@{N='VM'; {E = {$_.vm}}, @{N = "CreatedOn"; E={$_. Created}}

  VM name CreatedOn name
  ----                                         -------                                 ---------
  testsnapshot001 testgk 21/08/2012 14:09:47

  And even once on the line will interview all machines virtual registerd in vc. If you want to check only for some more specific:

  Get - vm "vm1', 'vm2', 'vm3 | Get-Snapshot? {$_.name - eq "testsnapshot001"} | Select the name of name,@{N='VM'; {E = {$_.vm}}, @{N = "CreatedOn"; E={$_. Created}}

  or

  Get - vm "vm1', 'vm2', 'vm3 | Get-Snapshot | Select the name of name,@{N='VM'; {E = {$_.vm}}, @{N = "CreatedOn"; E={$_. Created}}

  to query all snapshots there and not only those that have been made for the purposes of the application of patches

  OR!

  a dirty, quick control for VMS with snapshots in general:

  Notice-EEG - ViewType VirtualMachine-filter @{"snapshot" = ""} | Select name

  I would like to know if it works for you.

  Kind regards

  Greg

• Small Noob Question - multiple snapshots

  VMware Server 2 using the Web interface to manage my VMs, I see the following commands under the snapshot:

  Take a snapshot

  Go back to the snapshot

  Remove the snapshot

  I took several shots.  but when choosing to go back to the snapshot, it is only up to the last snapshot.  Also withdrawal snapshot deletes the last snapshot.  Is it not possible to have multiple snapshots in this version of VMWare? TIA!

  VMware Server 1 and 2 have only the ability to 1 snapshot.  (A limitation of design from the beginning.)  If you need multiple snapshots, you must change for ESX (i) or workstation (or merge if you have a Mac).

• Display of multiple snapshots?

  In develop mode, is it possible to see/compare multiple snapshots of an image?

  Side by side - not so make virtual copies

• Multiple snapshot monitors led Flash memory-based

  Hello

  I am facing a problem this instant monitor two program have produced snapshots based on memory in a planning MRP process.

  Void queries have been respectively resulted in each instant monitor.

  But the fact is that these two programs of the monitors was stuck between them for a very long time with the plan option Lock Tables snapshot is activated.

  I could see that the MTL_MATERIAL_TRANSACTIONS_TEMP Table snapshot is locked by one of them as well.

  Finally, I had to cancel this process of planning about 8 hours later and re-run the MRP again.

  Anyone seen this before?

  To the EBS Version 12.0.6

  Thank you.

  

  Hello

  Ask your DBA to recreate a link to executable files and test it on the issue.

  He could solve.

  Kind regards

  Mohan Balaji

• Trying to hot-clone VM with multiple snapshots

  I have a virtual machine with two snapshots.  I need to make a clone of this virtual machine, and I want to clone the current state-based, not off a previous snapshot or the basic disk.

  When I try to clone, compatility validation is to give the warning "returning to snapshot may generate error (warnings) on the destination host."

  I'm curious to know what, if anything, will break if I continue with the clone?  I would like once again, the VM cloned to be based on the latest state of the virtual machine, not on a snapshot or the basic disk?  I thought that was possible?

  Thank you!

  The reason for the error is that when you clone to another ESX host a snapshot (especially if it includes memory) may not work on the new host because it is based on the current hardware that is running the virtual machine (at the time the snapshot is taken) maybe not on that get back you to the snapshot on. Also all the files that make up the snapshot are not available on the destination virtual machine.

  The best way is to simply validate snapshots and then do it. If this is not possible just clone and it will be based on the virtual machine running and you will have no problem.

  Leonard...

  -

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

• Delete a snapshot in ESXi 5 when data store is almost full

  I'm very skiddish on use or deletion of snapshots after a disaster, I had with them last year. So, I thought I would get your recommendation before you continue.

  I have a virtual machine running on the host with about 700 GB of total space on the data store. The virtual machine uses about 500GB and there is only a snapshot of the virtual machine. The virtual machine uses a disc thin provisioned. I received a warning that there is insufficient data on the space store and there are only about 120 GB left. Is it safe to remove the snapshot? Should we double the size of the virtual machine to "consolidate? The last time I did it with multiple snapshots and a lot less space, it's disaster.

  Edit: Here's what's on the data store (for this virtual machine). There is an another VM on the same data store which shows it takes 40 GB of space.

  

  Here's what it says on the storage to Apollo (the virtual computer name) under summary in vSphere:

  

  The basic disk can only 'baloon' upward only by the amount of data in the snapshot, which is 214 GB function provided screenshot and to be on the safe side, you have to assume that he will do. If you need to at least 214 (I'd Go 220) free on the data store for a safe removal-snapshot operation.

  Worse: these 214 GBs are given new, added after the creation of the snap. You the kickoff of the removal process. Basic disk to grow per GB 214. Currently, it consumes 355 GB so it will grow up to 569GB. Only one time all the data of the snap is committed to basic disk, the snapshot will be deleted. This is why you need some 220 GB free and available on the data store to start the removal process.

  Instant deletion on an engine out of VM might help a little, but looks like not as much as you want.

  If you shut down the virtual, pagefile will be deleted which will free up to 4 GB.

  Also if you delete a wink on the virtual machine performance, actually another cliché will be created to store the changes that VM is done during the delete operation. According to the rate of change of data within your VM and the time required for the delete operation, it will take little extra space on the data store as well. This need for extra space can be avoided by removing the snap while the VM is turned off.

  However, in your case the virtual computer power on off won't help

  Bottomline - if you can, find a way to get 220 + GB of free space on your data store before you delete the snapshot. Otherwise, the next option is VM migration to a different data store with storage vMotion (without interruption) and deletion of snapshots there (once again, potentially without interruption). A last - cloning in another data store that involves downtime.

  And you cannot clone to USB.

• Cannot start or export VM after removal of all snapshots

  Hello

  I just delete all the snapshots via vClient on 3 machines 4 on an ESXi 4.

  Now I can't export via vConverter or boot... The only machine with snapshots works OK.

  Is this a bug? Because I thought that I did nothing wheird.

  Series of lines in the 'system log' export, logs, I found:

  5 cpu5:5152) DevFS: 2370: could not find the device: 5e3e2186-COLIS_CATALOGUE_NODE-000005 - delta.vmdk
  14 February 14:24:21 pass: [14-02-2013 14:24:21.369 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000005-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.369 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000008-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.369 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000006-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.369 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000007-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.369 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000004-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.370 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000003-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.370 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000002-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.370 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-000001-delta.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.370 info 'DiskLib' 7201CB90] DISKLIB-VMFS: ' / vmfs/volumes/4a311e04-d8eb9109-26be-002481a8a5e1/COLIS_CATALOGUE_NODE/COLIS_CATALOGUE_NODE-flat.vmdk ': closed.
  14 February 14:24:21 pass: [14-02-2013 14:24:21.371 7201CB90 info "Libs"] NfcServerLoop [NFC DEBUG]: ready to READ sock
  14 February 14:24:21 pass: [14-02-2013 14:24:21.371 7201CB90 info "Libs"] NfcServerLoop [NFC DEBUG]: received full session
  14 February 14:24:21 pass: [2013-02-14 14:24:21.374 71D57D90 verbose 'App'] CloseSession called for the session id = 52369170-f4c0-71a1-a29c-668f25f09c68
  14 February 14:24:21 pass: [14-02-2013 14:24:21.375 71D57D90 'ha-eventmgr' info] event 95: root user is disconnected
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) scsi_cmd_alloc returned NULL
  !
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x410005134f00) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:30 0 0 x 0 0 x 0.
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) WARNING: NMP: nmp_DeviceRetryCommand: device 'naa.600508b1001030343843434234300500': waiting for updated status of fast path for blocked with e/s failover. No prior reservation is on the device.
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005161180) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:30 0 0 x 0 0 x 0.
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005096900) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:30 0 0 x 0 0 x 0.
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x410005092c00) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:30 0 0 x 0 0 x 0.
  14 February 14:24:30 vmkernel: 2:04:02:31.338 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005116980) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:30 0 0 x 0 0 x 0.
  14 February 14:24:31 vmkernel: 2:04:02:32.338 cpu0:4343) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.600508b1001030343843434234300500" world - order 0x410005134f00
  14 February 14:24:31 vmkernel: 2:04:02:32.358 cpu5:4327) NMP: nmp_CompleteRetryForPath: retry world component 'naa.600508b1001030343843434234300500 '.
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) scsi_cmd_alloc returned NULL
  !
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x41000517f9c0) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:42 0 0 x 0 0 x 0.
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) WARNING: NMP: nmp_DeviceRetryCommand: device 'naa.600508b1001030343843434234300500': waiting for updated status of fast path for blocked with e/s failover. No prior reservation is on the device.
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005113880) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:42 0 0 x 0 0 x 0.
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005075900) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:42 0 0 x 0 0 x 0.
  14 February 14:24:42 vmkernel: 2:04:02:43.815 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x41000510ea80) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:42 0 0 x 0 0 x 0.
  14 February 14:24:43 vmkernel: 2:04:02:44.816 cpu2:4343) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.600508b1001030343843434234300500" world - order 0x41000517f9c0
  14 February 14:24:43 vmkernel: 2:04:02:44.826 cpu6:5151) NMP: nmp_CompleteRetryForPath: retry world component 'naa.600508b1001030343843434234300500 '.
  14 February 14:24:49 vmkernel: 2:04:02:50.524 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:49 vmkernel: 2:04:02:50.524 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:49 vmkernel: 2:04:02:50.524 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:49 vmkernel: 2:04:02:50.524 cpu0:5109) scsi_cmd_alloc returned NULL
  !
  14 February 14:24:49 vmkernel: 2:04:02:50.524 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x41000517dac0) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:49 0 0 x 0 0 x 0.
  14 February 14:24:49 vmkernel: 2:04:02:50.525 cpu0:5109) WARNING: NMP: nmp_DeviceRetryCommand: device 'naa.600508b1001030343843434234300500': waiting for updated status of fast path for blocked with e/s failover. No prior reservation is on the device.
  14 February 14:24:49 vmkernel: 2:04:02:50.525 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005139500) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:49 0 0 x 0 0 x 0.
  14 February 14:24:49 vmkernel: 2:04:02:50.525 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005097800) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:49 0 0 x 0 0 x 0.
  14 February 14:24:49 vmkernel: 2:04:02:50.525 cpu0:5109) NMP: nmp_CompleteCommandForPath: command 0x2a (0 x 410005114680) to the 'naa.600508b1001030343843434234300500' NMP device failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:49 0 0 x 0 0 x 0.
  14 February 14:24:50 vmkernel: 2:04:02:51.526 cpu2:4343) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.600508b1001030343843434234300500" world - order 0x41000517dac0
  14 February 14:24:50 vmkernel: 2:04:02:51.544 cpu3:4099) NMP: nmp_CompleteRetryForPath: retry world component 'naa.600508b1001030343843434234300500 '.
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) scsi_cmd_alloc returned NULL!
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) scsi_cmd_alloc returned NULL
  !
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x4100050f7fc0) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:50 0 0 x 0 0 x 0.
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) WARNING: NMP: nmp_DeviceRetryCommand: device 'naa.600508b1001030343843434234300500': waiting for updated status of fast path for blocked with e/s failover. No prior reservation is on the device.
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x41000507ef00) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:50 0 0 x 0 0 x 0.
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x4100051b32c0) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:50 0 0 x 0 0 x 0.
  14 February 14:24:50 vmkernel: 2:04:02:51.756 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x4100051797c0) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:50 0 0 x 0 0 x 0.
  14 February 14:24:51 vmkernel: 2:04:02:52.526 cpu2:4343) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.600508b1001030343843434234300500" world - order 0x4100050f7fc0
  14 February 14:24:51 vmkernel: 2:04:02:52.533 cpu3:602831) NMP: nmp_CompleteRetryForPath: retry world component 'naa.600508b1001030343843434234300500 '.
  14 February 14:24:55 pass: [14-02-2013 14:24:55.841 71FDBB90 verbose 'ResourcePool ha-root-pool'] root of the pool changed 14300 MHz/6124 MB to 14300 MHz/6128 MB
  14 February 14:24:55 vmkernel: 2:04:02:57.193 cpu0:5109) scsi_cmd_alloc returned NULL
  !
  14 February 14:24:55 vmkernel: 2:04:02:57.193 cpu0:5109) NMP: nmp_CompleteCommandForPath: 0x2a (0x41000507c200) to the device 'naa.600508b1001030343843434234300500' NMP command failed on the physical path 'vmhba1:C0:T0:L0' H:0 x 1 D:0 x 0 P:0 x 0 Possible sense data: 0 x
  14 February 14:24:55 0 0 x 0 0 x 0.
  14 February 14:24:55 vmkernel: 2:04:02:57.193 cpu0:5109) WARNING: NMP: nmp_DeviceRetryCommand: device 'naa.600508b1001030343843434234300500': waiting for updated status of fast path for blocked with e/s failover. No prior reservation is on the device.
  Feb 14 14:24:56 pass: [2013-02-14 14:24:56.498 7201CB90 verbose 'App'] rising object with the name = "haTask - vim.SearchIndex.findByUuid - 750 ' failed.
  Feb 14 14:24:56 pass: [2013-02-14 14:24:56.499 7201CB90 verbose 'App'] rising object with the name = "haTask - vim.SearchIndex.findByUuid - 751 ' failed.
  Feb 14 14:24:56 pass: [2013-02-14 14:24:56.499 7201CB90 verbose 'App'] rising object with the name = "haTask - vim.SearchIndex.findByUuid - 752 ' failed.
  14 February 14:24:56 vmkernel: 2:04:02:58.194 cpu2:4343) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.600508b1001030343843434234300500" world - order 0x41000507c200
  14 February 14:24:56 vmkernel: 2:04:02:58.203 cpu3:5107) NMP: nmp_CompleteRetryForPath: retry world component 'naa.600508b1001030343843434234300500 '.
  Feb 14 14:24:57 pass: [2013-02-14 14:24:57.500 71FDBB90 verbose 'App'] rising object with the name = "haTask - vim.NfcService.randomAccessOpenReadonly - 754" failed.
  14 February 14:25 pass: [14-02-2013 14:25:00.120 7201CB90 info "TaskManager"] task created: haTask-ha-host - vim.DiagnosticManager.generateLogBundles - 826

  It seems that the ESXi still needs these deleted snapshots.

  What should I do now? Restart the machine would help? Or directly edit the vmx files?

  BTW I would have attached the vmx files but I don't know how to export, the box does not have ssh...

  I'm sorry for the post of beginner, but I'm not very familiar with ESXi 4.

  Thanks for your suggestions,

  Karel

  Do you recommend a specific action before I 'Delete All '?

  The 'Delete All' process can take some time depending on the size of the snapshot and the progress bar can be used to estimate the time remaining. It will always show something superior to 90% until there finishes the job. All I can recommend is to be patient.

  With the ESX version you are using (4.0 before update 2) the "Delete All" will require a lot more time with multiple snapshots in place. There are also if make sure there is enough free disk space on the data store to avoid exit of space conditions. The behavior has changed with ESX 4.0 Update 2.

  André

• Consolidating snapshots

  I'm for all to recover some disk space and get a handle on some of our VM sprawl.   I have several virtual machines with multiple snapshots that make their appearance like orphans of vmdk.  Many of the snapshots have 6 + months.  I know that I can get rid of them.   I've never done a consolidation once (on our mail server) and it apparently queced the system for 20 minutes at the end (kill e-mail for the era and an unexpected result, thank God, it was after 6 pm, but we are a boutique health care 24 x 7).

  We are on a mixture of 4 and 5, most of our guests are on 5, so I the consolidation option in VCenter as opposed to the permanent command line.   But what I can expect?  What is the best method for consolidating or removing unused snapshots to recover from space?

  I can perform this action at rush hour or off-peak hours?

  Sorry, I don't know why there was a break of 20 minutes, I never experienced anything like myself. VMware made some improvements on the dismantling of the snapshot, so should not be a failure like this with the latest version of ESXi more!

  What you could do - if all three snapshots appear in the Snapshot Manager - is to remove the old 2 snapshots one by one (starting with the most close to the basic disk). Because it does not require the virtual machine switch to an another hard for write access, this should pose no outagel. Removal of two snapshots would free at least until a lot of disk space and you can try to plan for the removal of the last/current snapshot in a maintenance window.

  André

• Linked Clones and snapshots - which can be removed and when?

  Hello

  Sorry if this is a stupid question. I'm new to the linked clones.

  I was able to create clones related win2k8r2 invited.  Everything seems to work ok.  However, once a linked clone is created, is it still necessary to keep the parent snapshot?  That is to say, snapshot of the parent is necessary after related cloning?

  My env:

  VMware ESXi 4.1.0 build-433742

  VMware vSphere PowerCLI 4.1 build 332441 U1

  Thank you

  T

  It must be remembered that a clone is based on the parent machine and a snapshot that you see in the server view.  Multiple snapshots can be consolidated or "rolled up", but depends on the clone.  The parent can put off when the do not need to save on resources in your environment, because that's what the replica is for.  I do not agree with Andre and suggest that you keep the snapshot that you clones are configured to use, with the exception on the consolidation of old clichés.

• Delete all snapshots

  Hello

  I started all avoid the VM snapshot almost 4 hours ago. It rose to 95% at the beginning and stopped so far. After 90 minutes of waiting, I realized that VM has been activated (oops) so I decided to turn it off while the abduction was still used. Virtual computer system turns off but the machine not. I could not have done yet because (I think) instant withdrawal is underway.

  Now, how can I check if the deletion process is still running or that 95% is smth like zomie-process? In fact, this virtual machine is not the one I need, but there are still other virtual machines work so I think that I can not turn all ESX host to break the abduction.

  Last lines of dump of virtual computer journal:

  16:05:39.149 23 Feb: mks | MKS: Polling of the Base period is 10000us
  16:05:39.551 23 Feb: mks | VNCENCODE 55, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  16:05:39.562 23 Feb: mks | VNCENCODE 55, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  16:05:53.470 23 Feb: vcpu-2 | Protocol TOOLS autoupgrade version 0
  16:05:53.501 23 Feb: vcpu-2 | ToolsCapabilityGuestTempDirectory received TOOLS 0
  16:05:53.502 23 Feb: vcpu-2 | ToolsCapabilityGuestConfDirectory received TOOLS 0
  16:05:53.560 23 Feb: vcpu-2 | GuestRpc: Reset of channel 0 (toolbox)
  16:05:53.674 23 Feb: vcpu-2 | GuestRpc: Channel 0 reset.
  16:05:54.448 23 Feb: vcpu-3 | Ball: Start: vmmemctl reset ball
  16:05:54.448 23 Feb: vcpu-3 | Ball: Reset (pages n 3 0)
  16:05:54.448 23 Feb: vcpu-3 | Ball: Reset: size nUnlocked 0 0
  16:05:58.775 23 Feb: mks | TAKEN 55 (72) recv error 104: connection reset by peer
  16:05:58.776 23 Feb: mks | TAKEN 55 (72) destroying backend VNC on socket error: 1
  16:05:58.810 23 Feb: mks | MKS: Polling of the Base period is 1000000us
  16:06:32.768 23 Feb: vcpu-0 | VIX: [126031 vmxCommands.c:7612]: VMAutomation_HandleCLIHLTEvent. Do nothing.
  16:06:32.769 23 Feb: vcpu-0 | Msg_Hint: msg.monitorevent.halt (sent)
  16:06:32.769 23 Feb: vcpu-0 | The CPU has been disabled by the guest operating system. You will need to turn off or reset the virtual machine at this point.
  16:06:32.769 23 Feb: vcpu-0 | ---------------------------------------
  16:08:37.288 23 Feb: mks | MKS: Polling of the Base period is 10000us
  16:08:37.748 23 Feb: mks | VNCENCODE 56, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  16:08:37.761 23 Feb: mks | VNCENCODE 56, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  16:08:49.367 23 Feb: mks | TAKEN 56 (127) recv error 104: connection reset by peer
  16:08:49.368 23 Feb: mks | TAKEN 56 (127) destroying backend VNC on socket error: 1
  16:08:49.397 23 Feb: mks | MKS: Polling of the Base period is 1000000us
  16:22:34.311 23 Feb: mks | MKS: Polling of the Base period is 10000us
  16:22:34.751 23 Feb: mks | VNCENCODE 57, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  16:22:34.775 23 Feb: mks | VNCENCODE 57, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  16:27:32.428 23 Feb: mks | TAKEN 57 (120) recv error 104: connection reset by peer
  16:27:32.429 23 Feb: mks | TAKEN 57 (120) destroying backend VNC on socket error: 1
  16:27:32.458 23 Feb: mks | MKS: Polling of the Base period is 1000000us
  17:50:51.442 23 Feb: mks | MKS: Polling of the Base period is 10000us
  17:50:51.893 23 Feb: mks | VNCENCODE 58, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  17:50:51.903 23 Feb: mks | VNCENCODE 58, changing encoding mode: (720x400x16depth, 16bpp, 1440bytes/line)
  17:50:58.793 23 Feb: mks | BUSH 58 (120) recv error 104: connection reset by peer
  17:50:58.794 23 Feb: mks | SLEEVE 58 (120) destroying backend VNC on socket error: 1
  17:50:58.823 23 Feb: mks | MKS: Polling of the Base period is 1000000us

  Quick help appreciated, thanks.

  It is important to remove the snapshot when the virtual machine is turned off or does not matter?

  It doesn't really matter. However, depending on the workload of the virtual machine and the amount of disk space available on the data store, you need to delete snapshots, while the virtual machine is turned off.

  When the virtual machine has a single disk, say 50GB with multiple snapshots, why the data in the file are cut on several files that altogether occupy more than 120 GB, even if snapshots are deleted?

  The virtual machine is divided into several files, files of configuration and data files. Each snapshot will start a new file (actually two).

  In another discussion you mentioned use you ESX 4.0. What version do you use? With Update 2 and newer you won't usually problems to withdraw several snapshots using the "Clear all" button, but with older versions you could easily run out of disk space if the space is already low.

  André

• Several snapshot

  Hello

  Is it possible to create multiple snapshots multiple clients at the same time? I for example. a host with 40 comments and you want to create a snapshot of all.

  Hello

  I think the answer you are looking for will be in the next http://communities.vmware.com/message/1596564. You will need to create a file with the names of server and we this file with the script of the post.

  I hope this is helpful and if she leaves then please me some points

• Commit snapshots by sentence

  Is it possible to hire some clichés about s VM by what is in the description? So if the snapshot had a description like "potatoes", you know the script to commit only these VM snapshots?

  Should be possible.

  Try something like this

  foreach($vm in Get-VM){
    $snap = $vm | Get-Snapshot | where {$_.Description -like "*potatoes*"} | Select -First 1
    if($snap){
      Set-VM -VM $vm -Snapshot $snap
    }
  }
  

  Note that I used a Select-1 first to avoid problems in a virtual machine would have multiple snapshots with potatoes in the Description

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Snapshots and Windows updates

  I try to create a snapshot that contains several versions of some software I need support. The software can also run running on different versions of SQL as a back-end, so I have different snapshots for the version of SQL. (see below)

  OS only-

  ---

  > SQL 2003-> App v1

  > app v2

  > SQL 2008-> App v1

  |----

  ---

  > app v2

  The problem arises when I have a pack of update or a Windows service that I need to apply. It seems that I can only apply the update for snapshots "grandchildren", making it so I have to update several grandchildren. This means also that if I have a new version, (App v3) I have to update as well when I turn a snapshot of SQL.

  Is there a way to retro-actively apply an update or update the 'grandfather' and have passed along it to children?

  LouisD says:

  Is there a way to retro-actively apply an update or update the 'grandfather' and have passed along it to children?

  There is no direct way to do it right now.  Once a snapshot is taken, its content cannot be changed.  Since snapshots work by recording the differences in discs (without taking into account its files and system files of comments), modification of the contents of a snapshot of parent could cause snapshots of children end up with corrupted data.

  If you really want to apply the updates of operating system, invited to multiple snapshots for each snapshot, you can restore, apply updates, take a new snapshot, and then delete the old snapshot.  Note that doing so will change the structure of your snapshot tree, however.