need to migrate data to a new virtual machine

Similar Questions

• Suggestion on Vcenter DB migration on the new virtual machine and enhancement vcenter server

  Hello

  I'm looking for any suggestion/plan with Vcenter DB migration steps towards the new virtual machine, and then upgrade the server vcenter

  4.1 for Update1/2

  My plan will be

  (1) creating new virtual machine.

  (2) fresh install 64-bit OS

  (3) migration Vcenter DB of the physical server to the new virtual machine.

  (4) upgrade to Vcenter Server 4.1 update 41 4.1 Update1/2

  Anything else missing then please let me know.

  Thank you

  vmguy

  Hi vmguy

  I agree with this approach

  (3) migration Vcenter DB of the physical server to the new virtual machine.

  As long as you leave the old DB in tact and simply detach and copy the DB to the new Victoria Cross.

  Before you run the upgrade on the new VC and DB.

  This way, you have a restoration plan in case something goes wrong with the upgrade.

  Just to add:

  You must migrate the ADAM database so to maintain the specified permissions vCenter

  See: Migrateing vCenter new host

  Please allow points if you find this useful/correct

• USB HDD as a data store and storage of VMS and new virtual machines

  I have a server Esxi 4.1 with 1 TB RAID 5 storage and 3 virtual machines. The storage is full and no space for another HARD disk, so my question is: would it be possible to use a USB HDD as a data store and could be included as a storage for new virtual machines or the VM? If so, could someone let me know how to do it because I'm not able to detect the HARD disk on the host itself.

  No, it is not possible to use a USB drive as a data store.

  Linjo

• How to specify the file of virtual hard disk when you create a new virtual machine using virtual hard disk on the data store?

  I'm new to PowerCLI and find quite simple, but in the documentation I read, I don't see how to use a virtual hard drive, existing on a data store when you create a new virtual machine.

  Is this simple registration on the virtual hard disk, or did I miss something?

  My current create VM is the following statement:

  New-VM

  -Name $TargetHostName -host $TargetVMCenterHost -data store $TargetVMCenterDatastore DiskMB - 20000 -MemoryMB $TargetHostMemoryMB -NumCPU $TargetHostCPUs -ID $TargetHostOS -CD -Description $TargetHostName

  Didn't notice this before, but I think that vSphere will use a backslash instead of a slash in the paths.

• Could not start the new virtual machine or VM remove a data store

  Hi guys,.

  I'm not new with ESXi, but my knowledge with vCenter and Clustering must be improved, so here's my problem.

  We have a Cluster of 2 ESXi 4.1 hosts on a San with 2 VMFS.

  My first problem is when I created a new virtual machine and try to start it, I got an error message similar to the one included with this post.

  My Second problem is more picky. Since I am unable to start my new virtual machine, I had removed from drive and I had created a new. But when I took a peek in the data store where was deleted VM, the directory with all the files are still there. When I try to delete it, I got an error message telling me that it is impossible to proceed.

  Q please?

  Best regards

  Stéphane

  82% of failure can be other issues.  The article below

  http://KB.VMware.com/kb/1006052

  Also, I saw, where bad records DB for your ESXi hosts can cause weird problems as well.  The host with the problematic guest, can you do a right click on it and "disconnect"?  Try to get out of the bunch at the data center level.  If you get an error vCenter, that means return folder DB.  From there, while the host is in a disconnected state, remove the host to vCenter, then "add host". This will update the DB record.  Maybe worth it?

• Create new virtual machine of the model that have two hard drives in the different data store

  We do VM deploy automation with PowerCLI.

  There is already a model created with at least two hard drives to one side and each hard drive belong to difference datastore,

  In the model's operating system is Windows server 2008 R2 already installed VMware Tools and other software in the second (other than C: driver) driver

  We can successfully deploy a new virtual machine with this manually with vSphere client model.

  But when we try to make the deployment with PowerCLI, can not find examples of similar scripts in the document of reference,

  and we also google this question, still no similar question was found.

  Is this possible with PowerCLI? If it's possible could you give me some advice or an example of script, thank you!

  Best regards.

  I already found the solution.

  With the vSphere SDK .NET API, we can create the new virtual machine to the model

  Mainly used API listed below, sorry because I can not give the source code here.

  • VMware.Vim.VirtualMachineCloneSpec
  • VMware.Vim.VirtualMachineRelocateSpec
  • VMware.Vim.ManagedObjectReference
  • VMware.Vim.VirtualMachineRelocateSpecDiskLocator
  • VMware.Vim.ManagedObjectReference
  • CloneVM_Task

  For reference, you can take a look at this post and this post

  LucD , thanks for your help!

• Using PCD to migrate from VM to a virtual machine already deployed

  Hello

  I need to expand a cluster of 2,000 users to a cluster of 7,500 users. I tried to do that by deploying the DRS, but I wasn't able to do because the DRS estates the security password is different from the backup. I have an open case of TAC to investigate it, maybe the problem is the password @character.

  So I wonder if I can use PCD to transfer data from the small bunch for the big one to overcome the Drs I run a lab to do that however PCD me does not use a virtual machine already deployed as the destination of migration. Is there a way to get around this? The big problem is I have no permission to deploy a new virtual machine in VMware infrastructure, but I can ask the priming of a simple installation of CUCM to allow me to migrate data from the old cluster to the new VMWare.

  Kind regards

  Alberto

  Hello Alberto,.

  First of all you must always mention both cucm and other important info while posting something on the community, given that the procedures for various things change with different versions. Yes, with DRS backup and restore only the security password must be known, if not, that it will fail. If the cluster is still in place and launched, you can easily change the security password using the procedure mentioned in the following link and then take a backup of the DRS and use it on a freshly built with a similar version cluster

  http://www.Cisco.com/c/en/us/TD/docs/voice_ip_comm/CUCM/Cucos/8_6_1/Cuco...

  With PCD you must follow the steps mentioned in the PCD administration guide, basically you will build a virtual machine and then allow PCD migrate existing data to the new cluster. However, check the compatibility of the versions and other factors listed in the guide of PCD

  http://www.Cisco.com/c/en/us/TD/docs/voice_ip_comm/CUCM/pcdadmin/10_5_1/...

  Manish

• Cannot turn on new virtual machines

  Hello world

  I am running ESXi 5.1.0 (1483097) on a server Dell PowerEdge T300 with 24 GB of RAM and a couple of terabytes of HARD disk space. I have a 64 GB SSD as my default swap file location. I'm unable to turn any VMs created on this server (has only one handful of other virtual machines running on it currently, not more than 4-8GB RAM each). When I try to turn on a new virtual machine, I get the following error:

  An error was received from the ESX host turning on VM <vmname>.

  Has no power on the virtual machine.

  Could not power on VM: insufficient resources.

  Cannot extend the pagefile to 32768 k k 93504.

  Cannot extend the pagefile to 32768 KB 94208 KB.

  There are lots of free RAM available, and I don't have in my pool only resource that all virtual machines live subject. I tried to set the location of the swap file VM to store data of the VM, but that has no effect. Any ideas?

  Hello

  you are indeed running out of space on your destination of swap - you have only 56 MB of free space on your SSD. You're also out of space for swap on datastore1 and 4. I suggest check it and delete all unnecessary data. Please note that by default without reservation, the VM creates a swap file that is equal to the size of RAM allocated to it. If the startup fails with swap on the hard drive, try quick vMotioning or cold - migrate the virtual computer to another storage. Also you could do a lot better with the free space by consolidating all your storage to a single VMFS volume.

• VMware workstation, crashes when I try to create a new virtual machine

  Hello

  I never had this problem before, but I didn't create a new virtual machine in a very long time. Last time I created one was making Workstation 9 I think. Some time after the upgrade to Workstation 10 or 8.1 of Windows Update 1 it has started.

  In 10 Workstation running on Windows 8.1, I select the file > new Virtual Machine dialog coming upwards and in a few seconds crashes of VMware workstation and closes.

  So I checked the Windows event logs and find

  Warning "VMware Workstation to function properly, must be reinstalled after the upgrade to Windows."

  So, I upgraded from 10.0.2 to 10.0.3 and it uninstalled and reinstalled but I still get this warning.

  Followed by an error

  ***

  Journal name:	Application
  Source:	Application error
  Date:	15/08/2014 23:33:53
  Event ID:	1000

  Task category: (100)

  Level:	Error
  Keywords:	Classic
  User:	N/A
  Computer:	P7Win8MC

  Description:

  Name of the failing application: vmware.exe, version: 10.0.3.48389, time stamp: 0x539a4fb0

  Name of the failed module: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5

  Exception code: 0xc0000005

  Offset: 0x0003bece

  ID of the process failed: 0 x 1788

  Start time of application vulnerabilities: 0x01cfb902de541c11

  The failing application path: C:\Program Files (x 86) \VMware\VMware Workstation\vmware.exe

  Path of the failing module: C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll

  Report ID: 24d5effb-24f6-11e4-bedd-20cf30780548

  ***

  So I need help to track down what I am not sure what VMware paper to look to maybe see what is happening.

  Thank you

  Rainey

  Well, I found the problem.

  I looked in the UNK file and found a few ISO files wrongs tracks.

  I had mounted some ISO in the past and they have made the entry in this file of preferences such as "isoLocationMRUx".

  I'd change the leter this ISO file player so they could not be found as input, once I corrected the paths I can now create a new virtual machine.

  He is responsible for ion BONE the new virtual machine now.

• PowerCLI script - new virtual machine of the model

  Hi all

  I am very new to power CLI scripting, and these days, that I read a lot of help to automate the creation of a new virtual machine based on the model of the virtual machine.  Script that is not that hard, even location new virtual machine on a particular data and in a particular resource pool store is not difficult.  For this I came up with this very basic script/command:

  "New-VM - ResourcePool < resource_pool > - < folder_name > location - Datastore < datastore_name > - name < VM_name > - < template_name >"model

  However, I came across some problems that I can't find information in help or in the forums.  Problem with the above command is VM will be created in the pool of appropriate resources and file as long as they are unique, but if there are multiple instances of resource pool or a folder with the same name as the script spits out a mannequin.

  So for example if I want to create a new virtual machine to the location following Data_Centre = > RootFolder1 = > SubFolder1 = > SubFolder2 and SubFolder2 name is unique that no problem, the virtual machine is created at this location.  However, if the SubFolder2 exists in Data_Centre = > RootFolder2 = > SubFolder1 as well as the virtual machine is created in the folder root of the location of the model.  For example, if the model is in "DC = > Folder1 = > Subfolder1 = > Subfolder2 ' the virtual machine will be created in the folder Folder1

  Any suggestions on how to ensure that the virtual machine is created in the desired folder/location as well as a list of resources?  In my view, there are really smart guys here and I suspect that this issue would not be a problem at all.  Any help would be appreciated.

  See you soon

  It is not a matter of following the right path.

  You can use the location setting to get the exact folder you want. For example

  $dc = get-data center-name DC1

  $folder = get-file-name Folder1-location $dc

  $subfolder = get-file-name Folder2-location $Folder1

  or

  $dc = get-data center-name DC1

  $subfolder = get-file-name Folder2-location $dc

  You will need to find a "place" in the path to your destination folder where it will be unique.

• How to set vm-description/notes and get the name of the data store, where the virtual machine

  Hello guys,.
  I have vCenter Orchestrator 4.1.1 build 733 installed and it works fine, but I need your help for the following two issues:
  (1) I want to put the description/notes of a virtual machine using a workflow. But I have not found any API useful to create this workflow (I don't want custom attributes, see attachment for details).

  (2) how can I get the name of the data store, where the virtual machine? I need this name for a workflow.
  I need your help.
  Thanks in advance!

  With regard to the notes of the VM, the following code (see enclosed package) can do this:

  var oldNotes = vm.summary.config.annotation;
  If (oldNotes == null) {oldNotes = ' ' ;}}
  System.log ("Notes of VM current:" + oldNotes);
  Now put the new notes:
  Start by creating a context
  Context of var = new VcVirtualMachineConfigSpec();
  Update the annotation with the new value property
  configSpec.annotation = notes;
  launch the task to reconfigure the virtual machine with the new context
  NOTE: This is sure to apply with a virtual machine under tension
  var task = vm.reconfigVM_Task (configSpec);

  And, in what concerns the VM information, take a look at the workflow of the library: \Library\vCenter\Virtual Machine management\Others\Extract virtual machine information

• Move the HARD drive to the new virtual machine

  I think it's a real simple question, so a simple answer is very well...

  I currently have a computer virtual running windows server 2003 x 86.  This whole system is on C: and the D: is strictly files/shared user.  I need to upgrade this server 2 k 8 R2 x 64.  My plan is to detach the D: to the x 86 box, create a new x 64 VM and reattach the D: from the old server and re-create the shares.

  My question is, when I do that, I would wait to see the security reset on the player?  As in the new operating system will reorganize the security on all of its default value...

  Other issues anyone do with it?  Simple enough?  It is about 300 GB of user data, so I'm just a little nervous about it.  (it is supported of course however).

  Thanks for any info!

  I think that when you remove the drive and re - join a new virtual machine, it will inherit the rights of the current operating system. It is the same concept as if you had a USB HDD shared, connected to a PC, removed and attached to another PC. You would lose your actions and all other settings.

  You should not have problems - make sure to note all the shared available on disk as well as any special permissions (as denies explicit for Active Directory).

• vRA 6.2 API - is possible to ask a new virtual machine based on a machine of model using the API

  Hello

  Is this possible in version 6.2 API at the request of a new virtual machine based on a model of Machine catalog?

  Thanks for the help in advance,

  Pieter

  Yes, you need to specify the new virtual machine in json format and publish it on/catalog-service/api/consumer/requests

• Not possible to export a list of virtual machines that are created in the past 7, 30, 120 and 180 days since an imported csv file containing the date of creation of virtual machine

  Not possible to export a list of virtual machines that are created in the past 7, 30, 120 and 180 days since an imported csv file containing the date of creation of virtual machine. My questions is the correct statement to the variable: $VmCreated7DaysAgo: $_CreatedOn "-lt" $CDate7.

  # #SCRIPT_START

  $file = "C:\Users\Admin\Documents\WindowsPowerShell\08-18-2014\VM-Repo.csv".

  $Import = import-csv $file

  $VMCreatedLast7RDayRepoFile = "C:\Users\Admin\Documents\WindowsPowerShell\08-18-2014\Last7Days.csv".

  $start7 = (get-Date). AddMonths(-1)

  $CDate7 = $start7. ToString('MM/dd/yyyy')

  $VmCreated7DaysAgo = $Import | Select-object - property name, Powerstate, vCenter, VMHost, Cluster, file, Application, CreatedBy, CreatedOn, NumCpu, MemoryGB | Where-Object {$_.} CreatedOn - lt $CDate7} | Sort-Object CreatedOn

  $TotalVmCreated7DaysAgo = $VmCreated7DaysAgo.count

  $VmCreated7DaysAgo | Export-Csv-path $VMCreatedLast7RDayRepoFile - NoTypeInformation - UseCulture

  Write-Host "$TotalVmCreated7DaysAgo VMs created in 7 days" - BackgroundColor Magenta

  Invoke-Item $VMCreatedLast7RDayRepoFile

  # #SCRIPT_END

  You can use the New-Timespan cmdlet in the Where clause, it returns the time difference between 2 DateTime objects.

  An example of this cmdley

  New-TimeSpan-start (Get-Date). AddDays(-7)-end (Get-Date). Select days - ExpandProperty

  In your case, you could do

  Where {(New Timespan-démarrer ([DateTime] $_.))} CreatedOn) - end $start7). {7 days - gt}

  But beware of negative numbers.

• URGENT! After installing 6 Fusion and creation of new virtual machine with Windows 7, I get a message "VMware Fusion cannot enter the unit". WHAT SHOULD DO?

  After purchase, installation and activation Fusion 6 with the license key, I had a library of VMS showing 2 Boot Camp partitions. It's strange that I only have 1.
  I tried to activate them but received a message that it is out of date in 2 cases. (see annex 1)

  I started a new virtual machine with a Windows 7 installation disc directly on my HD. I have provided a way to do this and followed the instructions of Fusion to the screen.

  Apparently, everything went well and after several restarts, the installation appears to be over (see annex 2) I tried to open and run the installed Windows 7. I had however a window with the following message:

  "Pending the unit.

  "VMware Fusion cannot enter the unit. Please wait until the unit starts automatically, or interact with the virtual machine below. ' (see annex 3)

  Here Windows 7 seems to start but after a while with the home screen and of the Øresund finishing this window closed and open a new window called library Virtual Machine on the left showing the partitions of Bootcamp and the Virtual Machine Windows 7 x 64 and in the middle gray a representation of what is supposed to be the Windows 7 desktop. (see Exhibit 4). When I opened the settings button a window with different setting options pops up. This mark means to me that Windows is installed but the final opening isn't the case

  When you quit Vmware Fusion indeed Windows seems to be close (see part 5)

  What is going on? What has gone wrong? What should I do? I don't know how to solve the problem.

  I should f.i. remove the virtual machine from Windows 7 and is free automatically made partition on my HD as the reboot with the Windows installation disc? or y at - it another way to enter the UNIT?

  Help, please!

  Thanks in advance

  Your virtual machine is running. It is in the unit - which each windows gets its own window of Mac - and you have no application Windows running, there is no visible windows. You can start a Windows application in the start of Fusion menu in the menu bar at the top right, or turn on the Windows task bar on the view menu and start applications from there. Or use the view menu to switch to the Single mode or full-screen, which puts all of your Windows desktop in a window separate from Mac.

  You do not have two partitions to Boot Camp on your Mac, you have two virtual machines named "Boot Camp partition".

  The message about it being unable to enter the unit arrives while the merger is pending for the tools begin to run, because the tool is necessary for the unit.