Storage vMotion for a virtual machine on vCD

Similar Questions

• Storage VMotion for a virtual machine with SAN LUNS attached to it. They are all going to?

  Hello

  Don't know which section of this post, so sorry if its wrong.

  We are eager to Storage VMotion of our SQL VM. These are our SAN 3040 of NetApp. In the virtual machine (windows 2003), they have also connected to the network SAN NetApp 3040 LUN.

  What I need to know is, if we tried to do the other (NetApp 3170) SAN Storage VMotion problems due to the fact that its storage not only fast vMotioning of VMs its self, but also the LUN or LUNS will remain on 3040, and the virtual machines moved to the 3170?

  Who is?

  If more info should help just shout!

  Cheers in advance...

  Rik

  RDM's Raw card device.

  As I posted earlier, you need to move data to the Raw LUN for LUN Raw new either through data copy inside the VM if you map the new LUNS brutes who him or copy.

• Disable vmotion for 1 virtual machine in an ESX host

  Hello

  We have an ESX environment that is configured with vMotion.

  As a result, I've seen VMs from one ESX to another very frequently.

  Among these virtual machines, I have a very critical virtual machine, I want to move to any other host ESX.

  Y at - it an option that I can use to disable VMotion only for this particular virtual machine of mine (in order to keep constant on the ESX on which it is right now) and allow the other virtual machines to continue.

  Appreciate your help.

  Thanks in advance

  I guess that your VMS migrate between ESX servers because configuration automated DRS ESX cluster level. You can replace it for a specific virtual machine. Cluster of right click Select-> "Settings"-> click on options of the Virtual Machine under VMware DRS,. On the right, make sure 'Enable the levels of automation individuak virtual machine' is checked. You can see VMs list below. Select the virtual machine that you want to replace and change the level of automation for people with reduced mobility

• Can join a Cluster of storage disk out of Maintenance DTS Mode to set up the profiles for a virtual machine storage policies?...

  Can join a Cluster of storage disk out of Maintenance DTS Mode to set up the profiles for a virtual machine storage policies?...

  
  IE can you define the rules of affinity DTS depending on how the rules of storage of profiles are configured for a virtual machine?

  In my mind it seems there is disconnect from the DTS and storage profiles.

  Thank you.

  = NOTE =.

  My lab at home, 2 organizes running ESXi 5.0

  Dv01 has

  Of startup vmfs 7200 RPM 160 G = dv01-BOOT

  Vmfs 1 TB 7200 RPM = VM02-VMFS

  VM02 has

  Of startup vmfs 7200 RPM 160 G = VM02-BOOT

  Vmfs 1 TB 7200 RPM = VM02-VMFS

  Vmfs 5900 RPM 2 TB = VM02-TV01

  I have (3) facility profiles of storage using 'User-defined storage Capablity' as shown below:

  (160 @ 7200 RPM SATA) boot > Boot

  Fast (160 7200 RPM SATA and 1 TB @ 7200 RPM SATA) > fast

  Slow (2 TB @ 5900 RPM SATA) > slow

  Then, I set up a storage Cluster with my local disks on dv01 (only to date)

  LocalVM disc dv01-BOOT and dv01-VMFS disk of the 'cluster of storage.

  I have a computer virtual called DC01 (HardDisk1) want to live on 'Boot' profile storage drive
  His "Non-compliant" poster according to the storage profile, it should run on drive 'boot' on dv01

  To get to this point, I put the StorageCluster in Mode of Maintenace 'DTS' and forced a sVmotion of all virtual machines off dv01-BOOT

  No disks are IO or claim of space.

  But once I take the 'DTS Maintenacne mode' STARTUP dv01 floppy is now get the DTS to return him to satisfy the storage profile (rule) I install... IE do the 'storage profile' VM complient (without doing a few externall API, the PS script or the 3rd party software calls)... ??

  Seems weird it is (or may be) such disconnection of a memory of the profiles and the StorageClusters and the DTS?

  Thank you...

  At this point, I think that storage DRS and storage profiles are two technologies to separate and work independently, but what you suggest is a great idea-

• Migration of virtual machines to vCD and again in a standard ESXi cluster itself?

  We currently have a relatively small cluster of ESXi (5.0.0 1489271) which uses a dedicated installation vCenter (5.0.0 1300600) and an instance of vCD (vCD 5.1.2.1068441).  Our goal is to move the virtual machines running in this configuration to our standard ESXi clusters (5.5.0 1892794) supported by installation of different vCenter (5.5.0 1891313).

  The instance of vCD seems to add additional parameters to the level of the virtual machine that prevents the VM of to be easily transferred out of the instance of vCD.  What we are looking for is a way to easily migrate these servers on and completely remove the vCD of the equation.  The only details around that we found cause downtime for exports out of vCD can be extended to reason the total amount of drive to the VM and VM level, which we really do not think it is an option to open a window of time to stop long enough to work through this process.

  Did someone went down this road before?  We have approximately 120 virtual machines in the cluster vCD using about 52 TB of disk.

  Maybe we're wrong understand something fundamental about the nature of migration of VMs on the vCD instance, but we have not been able to find many details on what options exist to make this move.  We have spoken several times with VMware support in this regard.  They mentioned a potential tool in the work within engineering migrate vCD to vCAC (which isn't really fall under our goal unless vCAC would then provide a clear path to return the virtual machines to a standard ESXi cluster).

  Any suggestions or ideas are appreciated.

  I am a colleague of GTC and wanted to just sent to our discussion of this topic with the help of VMware.  Basically, we should be able to Setup VMs in vCenter, outside of vCloud Director, pointing them to the same files VMDK and MAC then power off VM vCD and power on VM vCenter.

  : The NASA-EAST region

  Moment of validation: 2014-09-05 11:32 EDT

  Severity of the request for assistance: 4 - low

  Description of the request for assistance: we are looking for ways simple and less disruptive migrate VMS off vCloud Director and vCenter management.

  We have the advantage of a single principle in vCloud, managed by a vCenter and the network configuration is simple with no VXLAN.

  What are the problems with the realization of the following?

  vCD 5.1 is managed by vCenter 5.0, the final result will move VMs in vCenter even

  -Create a new virtual machine in vCenter that points to the same vmdk files as virtual machine in vCD you want to migrate, allocate same configurations of processor, memory, and network (we do not use the vCD with advanced networking)

  -Turning off the virtual computer in vCD

  -Once the vCD WHAT VM is off, power on VM in vCenter

  We must ensure that the VM vCD never gets turned on again and then when we are completely finished with all migrations of VMS in vCenter we abandon vCD.

  Of course there are details to help users migrate to how they use the vCD to vSphere vCenter client web interface or web interface.

  Entry date: 04/09/2014

  Since the opening of the case, I had interviews with several members of VMware support staff and these additional points were added.

  -Configure vCenter VM with the same vNIC driver MAC and like vCD VM vNIC

  -Rename VMDK files to make for easier management, or if not renamed then detach from the propelled out of vCD VM

• Storage DRS, move a virtual machine that is in the data store is not a member of DTS

  Dear all,

  If I've set up storage DRS that contains, for example, DS1 and DS2. I have another virtual machine that resides on DS that is not part of the cluster of DTS. Can I move this virtual machine to one of the (DS1, DS2) data store? OR will some disruptions?

  Thank you

  Jocelyn,

  Which is correct in both cases. You can leave DTS place it for you (which is my suggestion), but I thought you wanted it to go to a specific data store.  That being said you can reactivate the DTS for a virtual machine under the SDR change settings if you do not ever clear for a virtual machine

• How to get the moref vCenter for a virtual machine

  I use with the vCloud orchestrator plugin.  I would like to understand how I can access the moref for a virtual machine identifier (as see vcenter) that is contained in a vCloud VAPP.

  Thank you

  Here is something I wrote to do. It uses the query service.

  Note that to be able to do, you need your plugin vCD to be connected to the org of system and use the administrator credentials.

  var vcdHost = vm.getHost();
  var vApp = vm.parent;
  
  var vms = new Array();
  var queryService = vcdHost.getQueryService();
  
  expression = new VclExpression(VclQueryAdminVMField.CONTAINER, vApp.getReference().href, VclExpressionType.EQUALS);
  filter = new VclFilter(expression);
  params = new VclQueryParams();
  params.setFilter(filter);
  
  var resultSet = queryService.queryRecords(VclQueryRecordType.ADMINVM, params);
  while (resultSet != null) {
      var records = resultSet.getRecords(new VclQueryResultAdminVMRecord());
      System.log(records.length + " VM records found");
      for each (var record in records) {
          if (record.name == vm.name) {
              return record.moref;
              }
  
      }
      resultSet = resultSet.getNextPage();
  }
  return null;
  

  Christophe.

• Affinity processor for a virtual machine

  I have a lot of CPU 8 on which I have installed ESX 3.5 U3. I also created a virtual machine Windows 2003 Server SP2 with 2 CPU is assigned to the.

  I'm trying to set the processor affinity for this virtual machine to use 2 of my physical processors. I see now on the tab Advanced CPU, I am able to select all available 8 physics of the processor. So now I'm a bit confused regarding if VMware allows scaling of my machine virtual to use all 8 CPU when my virtual machine is only 2 CPU?

  Now if the above is true, and I am to be allowed to set the affinity of the virtual machine to the all 8 CPU, then why is this maximum limit of the processor for a virtual machine is only 4? A stupid question probably but I'm really confused?  :|

  Hi confused,

  Yes, the user interface is a bit confusing. As RParker said, basically what you are doing when you assign the processor affinity are to identify the nuclei on which the vCPU is eligible to run on. At no time will be the VM scheduled to be run on carrots than what there vCPUs, so he will never have access to a capacity more than expected.

  The processor affinity is one of those features that's been around since 'the beginning' and its utility is really a bit blurred. I've heard of cases where users were running Citrix workloads configured with 2 vCPU and assigned the processor affinity for each virtual computer with the result of improving the performance. I wonder this because I never saw myself, and have a decent knowledge of how works the vmkernel Scheduler, it make much sense.

  I would encourage you (and anyone else reading this) essentially forget that the processor affinity is an option. Use it can cause significant performance degradation (if, for example, you pin a VM through two nodes NUMA, rather than keep vCPUs all in the same node) and break features (VMotion, DRS and who knows what else in the future).

  Ken Cline

  VMware vExpert 2009

  VMware communities user moderator

  Blogs about: http://KensVirtualReality.wordpress.com/

• SRM 5.5 - vSphere replication - error: impossible to reverse the replication for the Virtual Machine. A snapshot operation cannot be performed

  Hi all, we have just run a test DR failover of a couple of virtual machines in our protected our failover site and all site swung perfectly, two virtual machines came online and all applications work well. However when we cam to r-eprotect machines virtual, we get some errors.

  One of the virtual machines seems to have lived the reprotect end process, it is still running, but has not moved to 89% for some time. The virtual machine has a couple of grand (a little less than 2 TB) VMDK. slow progress is just a consequence of the large VMDK?

  More worrisome is the virtual machine which don't reprotect at all. It generates an error whenever I click on the "Restore" button (error: impossible to reverse the replication for the Virtual Machine.) A snapshot operation can not be performed).

  
  Does anyone have any ideas as to the cause?

  Thanks in advance for any help.

  Andy

  Finally got to the bottom of this. The issue was that reprotect SRM work was trying to dispel any snapshots that were taken on the computer object virtual destination in VMWare, but could not clean snapshots.

  The reason why snapshots would not consolidate was because it was snapshots of temporary VEEAM who in fact any snapshot file listed in the VSAN data store. So when we looked through the browser data store, no snapshot file existed in the virtual computers folder. Trying a manual removal also failed.

  To fix this, we created a snapshot of the virtual machine in the original data center (note is the engine to the bottom of the virtual machine), this effect was to get rid of the 'fade' snapshot that was visible in the Snapshot Manager that VEEAM backup had left behind. Once this had disappeared, the reprotect back to DCA worked perfectly.

• A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\VMware vCenter Server Appliance.

  Hello gentlemen,

  I can not only save this virtual machine with Backup Exec 2014 for a long time.

  They are there was no snapshot in snapshot Manager.

  Could you help me?

  A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\VMware vCenter Server Appliance.

  V-79-57344-38260 - failed to create a snapshot of the virtual machine. The virtual machine is no longer exist, or may be too busy to pause to take the snap.

  A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\FRPA111PRIM01.

  V-79-57344-38299-\vm\FRPA111PRIM01 ha-data center (DC) VMVCB::\\192.168.204.42\VCGuestVm\ (DC). To try to take a snapshot of a virtual machine failed because it could not be suspended in a file system.

  Hello

  I found the solution.

  I disabled the JOB BE general relativity.

  and the host where the virtual machine belong was not the right time. No Ntp server has been configured.

  I did and now there works.

  I think that the problem can come from this.

• Definition of levels of booking for a virtual machine

  The vcloud usage meter says:

  NET points = (vGB hours X points per 1 GB reserved RAM) / hours per month

  
  

  A month calendar of 30 days, a service provider uses the vCloud package provider services - first Edition to configure its virtual machine with 16 vGB for 15 days and 48 vGB 15 days remaining. The level of booking for the virtual machine is set to 75 percent for the whole month.

  15 days x 24 hours x 16 vGB x 0.75 = 4 320 hours of vGB

  15 days x 24 hours x 24 vGB (vGB 48 x 0.75 but capped at 24 GB) = 8 640 hours of vGB

  Total number of hours of vGB = 12 960 hours of vGB

  Total points = 12 960 vGB hours ÷ 720 hours / month x 7 points (for Prime Minister) = 126 points

  Where "the level of booking' for a virtual machine?  Is - this talk on VM bookings each parameter in vCenter Server, or do something to the extent of consumption vCloud himself?

  Hello. The reservation level is set for each virtual machine, using a vSphere Client or API.

• VCenter shows a network for a virtual machine that is not associated with any host

  I have a win2k3 VM who at one point had a network assigned to him called "MONITORING".  This network is configured is no longer in the ESXi (5.5) environment.  The virtual machine is connected to a network called "PRD-SURVEILLANCE" which is correct.  It's not really cause a problem, but I can't find a way to get rid of the object of MONITORING network.

  In VCenter MONITORING networks has a VM of 1 meter, the number of hosts of 0.  I also see it in the VM - dialog box, change the settings, but there is no option to remove it.  Profile Image to the virtual machine is version 10 so I can't use the old Client of VI to try to remove it.  I have checked each host and do not see this listed network object.

  I tried to restart the VM, it migration between hosts, changing its network of SURVEILLANCE of PRD to another network and vice versa and close - remove NIC and add a new card network.  MONITORING legacy network still appears in the config.

  For the virtual machine's .vmx file shows that the correct network: ethernet0.networkName = 'RDP-ANALYSIS '.

  Any suggestions on how I can remove the artifact of MONITORING network?

  The virtual machine has a preview that was created at the time where the MONITORING network was still affected?

  André

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

• change default location for new virtual machines programmatically

  I know that you can change the default location for new virtual machines through the preferences GUI, but I want to be able to change it for all those who use VMWare Workstation in my company, so that it is more advanced to the personal folder of the user.

  Where exactly is stored?  I don't see in the registry.

  Thank you!

  WS does not use the registry to store settings.

  Set the path in UNK for each user:
  prefvmx.defaultVMPath = "F:\. »

• Change tracking (CTK) block is supported for this virtual machine, but was refused. This will increase the CPU proxy and consumption of IOP.

  I have problems with a client of VMware image-level in an EMC Avamar backup.  So far, we have not been able to find information about this message in the backup log file.  It is originally the backup to take a very long period of time (on average 10-11 hours).

  2014-02-28 14:20:57 avvcbimage < 14681 > Info: change tracking (CTK) block is supported for this virtual machine, but was refused. This will increase the CPU proxy and consumption of IOP.

  We cannot determine why CBT is "denied".  Has anyone here run across this issue before or seen any other type of backup VMware image have denied CBT?

  Everything I checked watch that CBT is successfully activated since the file vmx for the customer to the Avamar config.

  ESXi host is Enterprise Plus 4.1.0 260247

  After spending some time on this issue, the ultimate resolution withdrew the Avamar vm and then add it again.  After that, CBT began to work properly.  It seems that there is a parameter that has been 'stuck' pertaining to this virtual machine that wasn't behaving properly.