Experience: Migrate Windows hosts to virtual machines using VMware Convert

A few days ago in a unit, 7 Windows Server 2003 R2 servers (running SQL Server, Web site) migrated to the virtual machine, using VMware Convert 3.02 can be easily migrated, the main steps:

Find a larger server, create a shared folder, the folder share permissions for full control, assuming that the computer name is ABC, share name is D

Install VMware Convert 3.02 on the host that you want to migrate, using the Import tool, the source host selects the local host, the target host chooses \\abc\d, and the target host name sets itself (for example, ibm3650-1, which means that this is the first IBM3650 server). 10G of space to migrate less than 1 hours (no statistics, gigabit Network)

While migrating, select the type of target virtual machine, I am migrating to VMware Server 1.x, choose VMware Workstation 5, VMware Server1 host.

After migration, modify the configuration of the virtual machine (memory of the migrated virtual machine is the original host memory), usually, set between 1G to 3G can (see), a single CPU (double CPU is not significant, but if a physical host running more than one virtual machine, set 2 CPU will occupy the host CPU resources) can, Cancel the floppy drive and use the Bridging network card

After migrating virtual machines, you can use VMware Server to load, start

After migration, many servers (because they are OEM Windows Server 2003) are activated at installation time, but after migration, they need to be activated within 3 days. But the OEM version, is not allowed to change the machine (migrate to the virtual machine is equivalent to change the machine), you can call to activate, but if the number of migration is too much, it ...

After consideration, the problem is resolved (after the migration, when prompted 3 days to activate, select "No", and then use the Windows Server 2003 R2 VL version, upgrade the installation is OK.

Migration PostScript:

1. Before migrating, use CHKDSK C:/F, chkdsk d:/f to detect the partitions of the migrated servers.

2, when migrating, you can not shut down, do not stop SQL Server, Web sites and other services. Can be migrated with antivirus software. However, it is a good idea to stop SQL Server and Web services, which can reduce the time to migrate.

3, it is best to remove the useless software backup system (some servers with SQL Server, Windows Server 2003 installation backup), migrate to the virtual machine, directly using the ISO mirror can be.

4. If you have more than one server installed SQL Server, it is best to find another host to install SQL Server, will migrate to the database in the virtual machine and then "migrate" to the host SQL Server, uninstall the SQL Server in the virtual machine, so that the resources can be used rationally: SQL Server sets, each virtual machine does not use SQL Server, virtual machine performance can achieve the best. So, you can correspond to the server, install each virtual machine, copy the Web site to each virtual machine, copy the SQL Server database to the host's SQL Server, modify the site's configuration file, append the database in SQL Server, so you do not have to use VMware Convert so that the host is the fastest and best performing.

5, in the migration, the best use of gigabit network. Now the server is mostly a gigabit NIC. Without a gigabit switch, you can make a RJ45 straight line that migrates between two servers. In use, migrate about 16GB of data (with operating system, SQL Server database, etc.), if you use Gigabit network migration, about 45-90 minutes to complete migration, if it is hundred gigabit Network, about 3 hours or more time.

6, when using VMware convert migration, you must be patient, usually from 1% to 2% quickly, but the system will stay in the state of 2% for a long time, do not worry, wait a while (may have to wait for 1 hours), from 3% to 100%, the speed would be more stable. If you suspect that the migration is out of order, you can go to the destination folder of the migration to see, press F5 to refresh, if the file continues to increase, indicating that the migration is in progress.

Article Source: http://wangchunhai.blog.51cto.com/225186/56401