MSCS VMs and snapshots

Similar Questions

• Clarification on the protection of the VMS with snapshots. SRM 5.1

  In SRM 5.1 documentation one of the limitations listed is:

  When the protection of the VMS with snapshots of the memory state, the ESXi hosts on protection and restoration sites must have compatible processors as defined in the articles of the VMware knowledge base CPU VMotion for Intel processors compatibility requirements and CPU VMotion for AMD compatibility requirements. Guests must also have the same characteristics of active BIOS. If the BIOS of the server configurations do not match, they show a compatibility error message, even if otherwise, they are identical. The two most common to check features are the No-Execute memory Protection (NX / XD) and virtualization technology (VT / AMD - V).

  
  

  
  

  You can work around this limitation by using the mode of the VCA on groups the and protected?
  

  VCA mode will mitigate this risk, but you must make sure that the two Clusters to the protégé and recovery Sites are at the SAME level CVS before take snapshots of the memory.

  At the end of the day, only a "planned actual Migration" will verify this.

  Good luck!

• Storage VMotion on VMS with snapshots

  Currently intend to move to a new san and have read problems with storage vmotion on VMS with snapshots.  Storage vmotion can be run on the virtual machine with snapshots?

  No.:

  http://pubs.VMware.com/vsp40u1/Admin/c_storage_vmotion_requirements_and_limitations.html

  -MattG

  If you find this information useful, please give points to "correct" or "useful".

• List vCloud organization Org VCT, VMs and metadata of a VM field

  How can I use PowerCLI to quickly list the organizations vCloud, Org VCT, VMs and metadata of the computer called 'rent virtual field '?

  I want to do by using the views, but I can't find information on how to do it, especially the part of metadata.

  Any ideas?

  It is simple to find info from metadata.

  Make sure that you have imported the following module:

  Import-Module Vmware.VimAutomation.Cloud

  You must connect first to vcloud Director with the following command:

  User to be connect-CIServer - Server - - password - org

  Then, you need information of VM with the command Get-CIVM as:

  $vmv = get-CIVM | Sort-Object-property name

  Then, you need to get the VM metadata information with. ExtensionData.GetMetadata (as):

  Foreach ($vm $vmv) {$Metadata = $vm. ExtensionData.GetMetadata ()}

  If the metadata entry is not inserted until the property $Metadata.MetadataEntry.Count is 0.

  If not, you can take the metadata information Vlue of the field named location like this:

  $MetaValue = $Metadata.MetadataEntry [[array]: indexof ($Metadata.MetadataEntry.Key, "Location")]. TypedValue.Value

  Sctipt together to get the metadata should be something like this: (replace the values of vclouddirector, username and password with your)

  Import-Module Vmware.VimAutomation.Cloud

  Connect-CIServer-Server - of the username-password - org

  $vmv = get-CIVM | Sort-Object-property name

  {Foreach ($vm to $vmv)

  $Metadata = $vm. ExtensionData.GetMetadata)

  $MetaValue = $Metadata.MetadataEntry [[array]: indexof ($Metadata.MetadataEntry.Key, "Location")]. TypedValue.Value

  Write-Host $vm + $MetaValue

  }

  If ($global: DefaultCIServers.Count - gt 0) {Disconnect-CIServer-server * - force - confirm: $false} #For disconnect

• How to find the age of a child and snapshot number snapshot for a virtual machine.

  Hi all

  How to find the age of a snapshot for a virtual machine child count and snapshot.

  This code snippet should help... Assuming that you have the following entries:

  VM (VC:VirtualMachine)

  snapshot (VC:VirtualMachineSnapshot)

  System.log("====== Snapshot details for VM: "+snapshot.config.name+" ======");
  var snapshotTrees = vm.snapshot.rootSnapshotList;
  System.log("Snapshot Tree Count: "+snapshotTrees.length);
  for each (snapshotTree in snapshotTrees){
      showSnapshotInfo(snapshotTree, snapshot);
  }
  
  function showSnapshotInfo(snapshotTree, selectedSnapshot){
      if(selectedSnapshot == snapshotTree.snapshot){
          System.log("====================");
          System.log("Name: "+snapshotTree.name);
          System.log("Id: "+snapshotTree.id);
          System.log("Description: "+snapshotTree.description);
          System.log("createTime: "+snapshotTree.createTime);
          System.log("quiesced: "+snapshotTree.quiesced);
          System.log("replaySupported: "+snapshotTree.replaySupported);
          System.log("backupManifest: "+snapshotTree.backupManifest);
          System.log("snapshot id: "+snapshotTree.snapshot.id);
          System.log("state: "+snapshotTree.state.value);
          var childSnapshotList = snapshotTree.childSnapshotList;
          if(childSnapshotList != null){
              System.log("childSnapshotList length: "+snapshotTree.childSnapshotList.length);
          }
          System.log("");
      }
      if(snapshotTree.childSnapshotList != null){
          System.log("Children found: "+snapshotTree.childSnapshotList.length);
          for each (childSnapshotTree in snapshotTree.childSnapshotList){
              showSnapshotInfo(childSnapshotTree, selectedSnapshot);
          }
      }
  }
  

  During the passage of one of my virtual machines, here is an example of output I get:

  [2014-06-12 15:19:21.493] [I] Snapshot Tree Count: 1
  [2014-06-12 15:19:21.493] [I] ====================
  [2014-06-12 15:19:21.494] [I] Name: before upgrade to 5.0.1
  [2014-06-12 15:19:21.494] [I] Id: 31
  [2014-06-12 15:19:21.494] [I] Description:
  [2014-06-12 15:19:21.495] [I] createTime: Mon Mar 19 2012 13:48:57 GMT-0400 (EDT)
  [2014-06-12 15:19:21.495] [I] quiesced: false
  [2014-06-12 15:19:21.495] [I] replaySupported: null
  [2014-06-12 15:19:21.495] [I] backupManifest: null
  [2014-06-12 15:19:21.496] [I] snapshot id: snapshot-83
  [2014-06-12 15:19:21.496] [I] state: poweredOff
  [2014-06-12 15:19:21.496] [I] childSnapshotList length: 1
  [2014-06-12 15:19:21.496] [I]
  [2014-06-12 15:19:21.497] [I] ====================
  [2014-06-12 15:19:21.497] [I] Name: Before 5.1 upgrade
  [2014-06-12 15:19:21.497] [I] Id: 36
  [2014-06-12 15:19:21.497] [I] Description:
  [2014-06-12 15:19:21.498] [I] createTime: Fri Sep 21 2012 21:59:58 GMT-0400 (EDT)
  [2014-06-12 15:19:21.498] [I] quiesced: false
  [2014-06-12 15:19:21.498] [I] replaySupported: null
  [2014-06-12 15:19:21.498] [I] backupManifest: null
  [2014-06-12 15:19:21.499] [I] snapshot id: snapshot-84
  [2014-06-12 15:19:21.499] [I] state: poweredOff
  [2014-06-12 15:19:21.499] [I] childSnapshotList length: 1
  [2014-06-12 15:19:21.499] [I]
  [2014-06-12 15:19:21.500] [I] ====================
  [2014-06-12 15:19:21.500] [I] Name: Before Named Instance
  [2014-06-12 15:19:21.500] [I] Id: 37
  [2014-06-12 15:19:21.501] [I] Description:
  [2014-06-12 15:19:21.501] [I] createTime: Mon Nov 11 2013 13:40:46 GMT-0500 (EST)
  [2014-06-12 15:19:21.501] [I] quiesced: false
  [2014-06-12 15:19:21.501] [I] replaySupported: null
  [2014-06-12 15:19:21.502] [I] backupManifest: null
  [2014-06-12 15:19:21.502] [I] snapshot id: snapshot-236
  [2014-06-12 15:19:21.502] [I] state: poweredOff
  [2014-06-12 15:19:21.502] [I]
  

• Signs missing in the history and snapshot, not found in the drop down window

  My history and snapshot of the missing panels (LR5) suddenly, and only appears in the window > panels menu.

  This * may * have occurred when I was trying to show my collection of target (control B).  I must have accidentally hit the key or some other, because all of a sudden I was taken to the last folder I was in.

  I'm afraid to close LR and reopen it, in the case which exacerbates the problem.  I really want these back panels!

  You go back and forth between library and develop?

  Because there is no other situation where you should be able to "recover files, but snapshots and history have disappeared", files will never be with the snapshots and history

• Memory and snapshot management

  Where can I find detailed information on memory and snapshot management in VMware workstation?

  Memory:

  • How memory is allocated in the host PC?
    
  • If I sart a guest VM with 2 GB of RAM with 500 MB of RAM on a host PC with 3 GB of RAM, the amount of memory is allocated on the host?
    
  • What should happen if I start more guest VM and the amount of memory is the memory available on the host PC?
    

  In summary:

  • How are managed snapshot all the view host to PC file system?
    
  • What is the role and the content of the files being created whenever I take a snapshot?
    
  • What is - that supposed to happen if I delete a file containing a snapshot (file, not the snapshot)?
    

  Concerning

  Marius

  • 1. how memory is allocated in the host PC?
  • 2. If I sart a guest VM with 2 GB of RAM with 500 MB of RAM on a host PC with 3 GB of RAM, the amount of memory is allocated on the host?
  • 3. what should happen if I start more guest VM and the amount of memory is the memory available on the host PC?

  • 4. How are all managed snapshot view host to PC file system?
  • 5. What is the role and content of the files being created whenever I take a snapshot?
  • 6. What is - that supposed to happen if I delete a file containing a snapshot (file, not the snapshot)?

  1. that costs on the settings in your config.ini file
  2. the host can use somethiong between 2200 MB and a few MBs - depends on config.ini
  3 the host said 'not possible' either the virtual machine starts - with extreme settings, you can allocate 5 x physical RAM available to your virtual machine

  4 and 5.

  vmsd-file = list used by the customer snapshots
  VMSN-file = settings and configuring the host when the snapshot was created
  00000*.vmdk = file does the actual data of the snapshot

  6. cannot be predicted: anything can happen: System can be will start more or healthy - so NEVER do this

  > Should I expect to use as much RAM on the host computer as the sum of memory configured all virtual machines of comments?

  again it depends on your config.ini file settings - if twist you config.ini for better performance, then the answer is YES

  a few good things to read http://faq.sanbarrow.com/index.php?action=artikel&cat=78&id=76&artlang=en

• Storage and snapshot space views

  Hi all

  Among the new features of vSphere is the tab "storage views."  Click on an object in vCenter (for example, a cluster) and then click on the tab "storage views."

  This tab includes useful information on the topic, including the amount of snapshot space which currently consumes each VM.  This is a great way to eyeball a cluster quickly and see what virtual machines are currently a snapshot.

  My question is not a big problem - more a curiosity.  When I look at the tab "Storage views" I can see all virtual machines running on this group.  None of my virtual machines currently have a snapshot.  However, the amount of snapshot displayed for each virtual computer space varies.  Even say 1.08 KB, others say 633 B etc.  About three quarters of my virtual machines have a very low value like this (1 KB or less) with the remaining quarter actually list 0 B.

  I would have thought that any virtual computer without a snapshot must be 0 b.

  As I said, this isn't a big problem - just a curiosity.  It is still pretty easy to tell who the virtual machines have a real snapshot that you can ignore all those containing 1 KB or less space snapshot.  I expect always all VM without a snapshot to show 0 B well and I consider it a (minor) bug.

  Does anyone else get these strange numbers?

  See you soon,.

  David

  Did a little research on our environment and I think I know what you saw, we have a few shots in our environment but also show some VMs who have no snapshot with the display of 1.08 KB on the view of storage under use of snapshots, then I guess that its getting this information based on files located in the directory of the virtual machine. What I found to a specific VM has been there is a filed with an extension called .vmsd that contains the metadata about snapshots, also defined on VMwares Web site: http://www.vmware.com/support/ws5/doc/ws_learning_files_in_a_vm.html

  The size of the meta file:

  [root@himalaya Quentin]# ls -lha | grep .vmsd
  -rw------- 1 root root 1.1K Jul 12 08:18 Quentin.vmsd
  

  This metafile looks like the following (which I remember creation but via the CLI):

  [root@himalaya Quentin]# cat Quentin.vmsd
  .encoding = "UTF-8"
  snapshot.lastUID = "127"
  snapshot.numSnapshots = "0"
  snapshot.current = "0"
  snapshot0.uid = "127"
  snapshot0.filename = "Quentin-Snapshot127.vmsn"
  snapshot0.displayName = "BackupShot"
  snapshot0.description = "Snapshot for Backups"
  snapshot0.createTimeHigh = "290435"
  snapshot0.createTimeLow = "-1325916361"
  snapshot0.numDisks = "1"
  snapshot0.disk0.fileName = "Quentin.vmdk"
  snapshot0.disk0.node = "scsi0:0"
  
  snapshot.needConsolidate = "FALSE"
  
  snapshot1.uid = "101"
  snapshot1.filename = "Quentin-Snapshot101.vmsn"
  snapshot1.parent = "100"
  snapshot1.displayName = "Snapshot-2-8:45"
  snapshot1.description = "8:45am snapshot"
  snapshot1.createTimeHigh = "287640"
  snapshot1.createTimeLow = "-1172553953"
  snapshot1.numDisks = "2"
  snapshot1.disk0.fileName = "Quentin-000001.vmdk"
  snapshot1.disk0.node = "scsi0:0"
  
  snapshot0.type = "0"
  
  snapshot1.type = "1"
  
  snapshot0.disk1.fileName = "/vmfs/volumes/48e91a93-a0a8d3bf-f831-003048670887/Quentin/Quentin.vmdk"
  snapshot0.disk1.node = "scsi0:1"
  
  snapshot1.disk1.fileName = "Quentin-000002.vmdk"
  snapshot1.disk1.node = "scsi0:1"
  

  I also look at other virtual machines that are not instant and the size is more properly associated with it real snapshot deltas, although virtual machines without the clichés that the size of the .vmsd seems to fit with what is shown in the view of storage that you noted, these virtual machines have no snapshots. I think that if a virtual machine has snapshots at any given time and was afflicted with consolidation or remove, the .vmsd could not have been cleaned and then used as a benchmark as "thinking that it snapshots and uses the file size of the .vmsd.

  This hypothesis was fairly easy to test, what I did to remove Quentin.vmsd (the virtual machine has been turned off, may want to be careful when his online) and what you need to do, is not to update the display of storage, but go to the virtual abstract machine and do a refresh on the use of the storage. This will refresh the specific data store on which this VMs lived on and if you return to the storage view and put a refresh/update, you will notice that the size of the snapshot goes to 0bytes now, which is pending.

  So I think that explains which continues, perhaps a quirk or expected behavior. Yet once again, I agree that suits you just look for the use of delta< 1gb="" for="" real="" snapshots="" or="" you="" can="" always="" go="" in="" and="" clean="" up="" the="" .vmsd="" files="">

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  repository scripts vGhetto

  VMware Code Central - Scripts/code samples for developers and administrators

  http://Twitter.com/lamw

  If you find this information useful, please give points to "correct" or "useful".

• Powering down VMs and ESXi via SSH

  Hello

  I need;

  (1) stop all virtual machines running on the host ESXi

  (2) then stop this ESXi host

  How to achieve this via SSH?

  Thank you.

  I found it much easier to do via PowerCLI...

  $vc = vcenter1

  $dc = 'Center '.

  SE connect-VIServer $vc

  # Gets the list of all virtual machines in the data center (except the vCenter VM itself)

  $vms = get-data center-name $dc | Get - VM | where {$_. - don't $vc name - and $_.} PowerState - eq "Receptor"}

  # Stop the virtual machines in the data center located in a State power.

  {Foreach ($vm to $vms)

  if($VM.) {ExtensionData.Config.Tools.ToolsVersion - only '0')}

  stop #gracefully

  Stop-VMGuest - VM $vm - confirm: $false

  sleep - 60 seconds

  }

  #forcefully VM stop

  Stop-VM - $vm VM - confirm: $false

  }

  # Stop vCenter VM (comment if vCenter is not virtual)

  sleep - 120 seconds

  Stop-VMGuest - VM $vc - confirm: $false

• No more available space and snapshots not taken (VEEAM)

  Hi all

  I have a BIG problem here and I do not see how to solve.

  For your info, I know my SAN is complete and really isn't a good way to run VMware, but I'm about to order the new SAN and servers this week.

  Right now, I have 3 data store. the one with the question is just related to Exchange 2007 and have total 380 GB.

  VEEAM has taken a backup of it and he sews it has never deleted the snapshot.

  So this morning, I got an instant "suppression" message on my VMware, Exchange is frozen and so was VEEAM.

  I have restart VEEAM, but I can't do a thing with seams Exhcnage is 'instant withdrawal. " No option available at the time where so he tries to remove it.

  But I guess it will never end because no more space is available.

  And I don't have any space anought on any data store to hold my Exchange Server...

  Can I do it fast?

  If I browse the data store, there is

  Exchange_1 - 0000001.vmdk

  Exchange_1 - 0000002.vmdk

  Exchange - 000002.vmdk

  It seems that something is missing (Exchange - 000001.vmdk)

  Well, please help, I'm stuck here!

  Martin L.

  Depends on the amount of RAM allocated to each of your virtual machines.

  There is a file (*.vswp), which is equal in size to the RAM configured for each virtual computer (unless there is a reserve memory for this virtual machine). Sometimes, if you're not too committed on physical RAM, setting a reserve memory for each equal to the configured RAM virtual computer will allow just enough room to go back to the feature (power - on virtual machines).

  The VMFS file system can be extended dynamically on Lun - to remove the snapshot for Exchange successfully, you may need to extend the VMFS volume where it is located. There are many ways to do this that go from 'good' to a bit dodgy.

  1. Best option: get your new business SAN and to create a LUN on where you can extend your existing VMFS volume, allowing enough space to commit the snapshot
  2. Improvised #1: Use an old server or workstation decent and build something like Openfiler, where you can introduce iSCSI and extend your VMFS
  3. Improvised #2: Use a physical Windows Server or workstation and the Wind Star to present an iSCSI LUN and expand your volume
  4. Out and buy a computer from office-SAN as Synology, present an iSCSI LUN and extend your volume

  Important: once the snapshot is engaged, move the virtual machine complete a contiguous VMFS volume on a single logic unit number and delete the extended volume!

  Good luck. Full VMFS because of clichés is a bitch! I have treated several times in a support capacity.

• Unable to start the virtual machine and snapshots are missing from snapshot Manager.

  Hello

  I'm new here in the VMWARE communities and I don't know if I'm posting this survey in the right place. I am currently using VMWARE Workstation 9. The issue I'm having is that I can not start my VM. The error that says:

  

  This is an overview of my settings:

  

  When I try to get a snapshot I can go back, I get this snapshot Manager screen:

  

  I checked the files on the directory of the virtual machine. The snapshot files are still there.

  I tried to solve the problem by editing the configuration of virtual machine file to use another vmdk. I got an error saying something about the parent and the child are not synchronized. Sorry I don't have a screenshot of that. I also tried to make a copy of one of the other VMDK and rename it to match with the name of the missing file. That also made me anywhere I tried looking on the net but I get answers to other vmware ESXi and vSphere products. So I don't know if they apply to my current situation.

  At this point, I'm hoping to recover my machine or at least be able to use snapshots. Please notify.

  I think that the restoration was the best way to solve this problem. I actually checked the different files, but it looks like I missed something. In any case, create snapshots with the virtual machine in a state engine is my personal preference. It is not only to save disk space (since there is no need to preserve the current state of memory), but also provides a consistent state. As for the number of snapshots, you're always on the stop side, and if you are not having issue of performace with small changes you make you should be ok. In case there is a performance problem, you may consider to store the computer virtual on an SSD that will certainly help.

  Since the Center of Documentation of VMware Workstation 10

  To the premises of the virtual machines, you can take more than 100 snapshots for each linear process. For shared virtual computers and remote, you can take a maximum of 31 snapshots for each linear process.

  André

  Post edited by: a.p. corrected fault, "SSD" instead of "SD".

• Sharing of disk and snapshot

  Hello

  I'm deploying a small cluster using Red Hat GFS, so I have two virtual machines with a system (not shared) disk and a big shared disk.

  On each virtual machine, I'm a (paravirtual) SCSI controller without bus sharing (for the system disk) and a (paravirtual) SCSI controller with physical bus share (for the shared disk). The shared disk is INDEPENDENT.

  What I want is to take a snapshot of the virtual machine with only the system disk, but the vCenter do not allow me to take it! Is there a limitation of snapshot and sharing of bus or something wrong with my config?

  Thank you

  Andrea

  Excluding the snapshots of virtual disks form works only with affecting the independent-persistent, but as soon as the sharing of bus comes into play, snapshots are not longer supported.

  André

• Exception 0xc0000005 (access violation) peripheral USB connection; My Computer works, shared VMs and ESXi VM does NOT work

  Hello

  Running VMware Workstation on Windows 7 64 bit 9.0.2.

  Created a machine virtual 64-bit of Windows 7 at the workstation to VMware Workstation, I am able to connect a USB device and it is accepted within the virtual machine.

  Clone of this virtual machine using Workstation Drag & Drop in the shared VMs that throws the Exception when I click on the USB device:

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

  VMware Workstation error

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

  Fatal error VMware Workstation: (vmui)

  Exception 0xc0000005 (access violation) occurred.

  A log file is available in «...» ».

  You can request support.

  To collect the data to submit to the VMware support, choose "Collect load data" in the Help menu.

  You can also run the script 'vm-support' in the folder my computer directly.

  We will respond on the basis of your entitlement to support.

  Same Exception I get when I start this VM on ESXi and use via VMware Workstation.

  Journal of the fasteners.

  MKS. Enable3D true or false doesn't make any difference

  Thanks for the help, Philipp

  Hi PhilippD!

  It seems that you have reached a vice that crept into the manipulation of workstation s 9.0.2' of remote USB devices.  We have fixed the problem in our internal versions of workstation, but until an updated version is made public, it seems that you need to roll back to the workstation 9.0.1 if you need to work around the problem.

  Sorry for the inconvenience!

  --

  Darius

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

• Clone and snapshot operation failed because the file already exists

  I read the article "http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1007193.

  If the delta is named < diskname > - 0000xx - delta.vmdk, create an empty file named < diskname > - 0000xx.vmdk.

  Does anyone can say why is

  Case of inoticed something vmdk name is server01.vmdk (DRIVE C), SERVER01_1.VMDK (drive D). Now what I saw in the vm data store

  SERVER01.VMDK (DRIVE C), SERVER01_1.VMDK became something else

  Why it happened,

  How can I know when this gap that happened by creating snapshots?

  Timestamps of files, problems with snapshots is past may, 25 and 26.

  As I mentioned before, move ' _APLSV-000002 - delta.vmdk "in the directory"backup"or create a dummy"_APLSV - 000002.vmdk"(content should not serious). This will allow you to create a new snapshot to activate the button 'clear all '. It should still work with the virtual machine, so there is no need for the time stop.

  If deletion and creation of the snapshot has been good, then, the snapshot of the first and the second disc should be _x-000005

  Yes, usually the numbers for different drives are the same. However, in reality no matter.

  André