Shulou(Shulou.com)06/02 Report--

Data storage is a virtual representation of the combination of basic physical storage resources in a data center. Because of the storage cost of virtualization and the rapid expansion of virtual machines, it is very important to use storage space efficiently. VMotion is a unique technology developed by VMware, which uses the full virtualization of servers, storage, and network connections to instantly migrate entire running virtual machines from one server to another. (if you don't understand the blog post here, you can refer to the previous blog posts I wrote in Virtualization.)

How ESXI 5.5 works and how to install and deploy ESXI

Install and deploy vCenter Server

Create and manage ESXi network

Blog catalog 1, case analysis 2, case pre-knowledge points 3, case implementation 4, cloning, template, snapshot 1, case analysis 1, case overview

Storage is a very critical part of vSphere basic physical architecture. Without good storage, virtualization has no value, and it can determine its system performance and whether advanced functions such as vMotion can be realized. This case will focus on the storage and advanced features of vMotion in vSphere.

Case pre-knowledge point 1. What is ESXi storage?

ESXi provides host-level storage virtualization, divided into local storage and external shared storage. They are mainly used to store virtual machine files, such as common vmdk, vmx and nvram files, and the files in the virtual machine system are stored on the virtual disk vmdk.

1) Local Stora

Local storage is an internal or external disk that can communicate without a network, including storage systems such as SCSI, IDE, SATA, USB, and SAS, but cannot use IDE/ARA or USB drives to store virtual machines. Local storage between multiple ESXi hosts does not support sharing, and the above data storage can only be accessed by 1 ESXi host.

2) external shared storage

External shared storage is the external storage disk or array connected by ESXi hosts through the network, including SAN, iSCSI, NFS and other storage protocols. The data stored above can be accessed by multiple ESXi hosts, and advanced functions such as vMotion can also be realized.

2. What is Openfiler?

Openfiler is a free NAS/iSCSI SAN server system that is mainly used to provide stand-alone storage systems for LAN hosts.

Openfiler provides a variety of connection methods, including NFS, SMB, iSCSI, Target and so on, which are generally managed by HTTP. If you want to access the data on Openfiler, you can do so through iSCSI Initiator, shared folder, mount, and so on. It is the best tool for the Provisiong phase for small and medium-sized enterprises that want to build virtualization.

3. What is vMotion?

VMotion is the basis of all vSphere advanced features and enables hot migration, that is, virtual machines can be migrated from one ESXi host to another ESXi host in real time without power off, making it easier to maintain, reduce failures, and so on.

1) the migration process of vMotion (if the virtual machine is traveling during the migration, the virtual machine will restore its original state and location) (1) when migrating vMotion, vCenter Server verifies that the virtual machine and the ESXi host state are stable. (2) at this point, the source ESXi host clones the virtual machine memory to the new ESXi host. (3) the source ESXi host records the memory information changed during cloning on the memory map (Memory Bitmap). (4) when the virtual machine memory data is migrated to the new ESXi host, the source ESXi host will put the virtual machine in a quiescent state when the virtual machine cannot provide services, and then clone the Memory Bitmap to the new ESXi host. The time required for a static state is extremely short. (5) after the new ESXi recovers the memory data according to the Memory Bitmap, the memory of the two ESXi hosts is exactly the same for this virtual machine. (6) finally, run the virtual machine on the new ESXi host and delete the memory data in the source ESXi host. 2) compatibility requirements for running vMotion (1) it is not allowed to connect devices that can only be recognized by a single ESXi host, such as optical drive, floppy drive, etc. (2) connection to a virtual switch without a physical network is not allowed. (3) the migrated virtual machines must be stored in external shared storage and accessible to all ESXi hosts. (4) the ESXi host has at least 1 gigabit network card for vMotion. (5) if you use a standard switch, you must ensure that the port group network labels of all ESXi hosts are consistent. (6) CPU vendors used by all ESXi hosts must be consistent (Intel or AMD). III. Case implementation

1. Enable the ESXi01 server:

Add three network cards to the ESXi01 server, VM1 management network / 192.168.100.0xxmv2 migration network (vMotion) / 192.168.100.0xxmv3 shared storage / 192.168.200.0Universe 24

2. Start the ESXi02 server:

Add three network cards to the ESXi02 server, VM1 management network / 192.168.100.0xxmv2 migration network (vMotion) / 192.168.100.0xxmv3 shared storage / 192.168.200.0Universe 24

3. Enable domain controller, SQL and vcenter:

4. Open the client vclient:

5. Deploy the storage server:

Create a new virtual machine, typical installation, click next

Select to install the operating system later, and click next

Select a different operating system, select another version, and click next.

Edit the virtual machine name, browse the storage location, and click next

To set the disk size, click next

Creation completed

Edit the virtual machine hardware device, set the memory to 1GB, mount the openfiler CD, and adjust the network card to VM3

Turn on the virtual machine and enter.

Click Next.

To choose English, click next

Default next step

Manually configure the IP address and turn off IPv6

Edit the name and click next

Select time zone

To set the password, click next

By default, the next step is to wait for the installation to complete

Installation completed and restart

Enter the user name and password, shut down and add the hard drive

Add hard disk

Select to create a new virtual hard disk, and click next

Set the disk size to 1TB, and click next

After the creation is completed, turn on the virtual machine

6. Vclient initializes the ESXi network:

Log in to the ESXi01 server

Add network, select VMkernel type, and click next

Default next step

Edit the network label, check use Port Group for vMotion, and click next

To configure the IP address and subnet mask, click next

Add completed, click do not configure gateway

Add a second

Default next step

Edit the network label and click next

To configure the IP address, click next

Add completed

Log in to the ESXi02 server

Add network, select VMkernel type, and click next

Default next step

Edit the network label, check to use this port group for vMotion, and click next

To configure the IP address and subnet mask, click next

Creation is completed, no gateway is required

Add a second

Default next step

Edit the network label and click next

Configure IP address and subnet mask

Add completed, no gateway is required

7. The client manages the storage server

Switch the network card VM3

Change the IP address to 200network segment

The Ping command tests whether interworking with the first, second host and storage server can be achieved.

Log in to the storage server to start management, user name openfiler password password

Create Volum

Select 1TB's hard disk to create a physical volume

Create

Create a volume group

Add a physical volume to a volume group

Add completed

Add an access control list

Add access point

Allow acc

Allow two hosts to access

Switch the network card to log in to the ESXi server

Modify IP address

Log in to the ESXi01 server

Add shared storage

Right-click the properties to add a network

Dynamic Discovery add Storage Server IP address

Rescan

Add shared storage to memory

Select disk

The file system version remains the default. Click next.

Edit data store name

Default next step

Add completed

Connected to the storage server

Log in to the ESXi02 server to connect to the storage

Add Stora

Add Network

Dynamic Discovery add Storage Server IP address

Memory automatically add shared memory

8. Migrate virtual machines

Cold migration of virtual machines to shared storage

To migrate the data store, click next

Choose to migrate to shared storage and click next

Default next step

Migration completed

Clone a virtual machine

Edit the name of the cloned virtual machine and click next

Select Clone to the ESXi01 server and click next

Choose to put it in shared storage, and click next.

Default next step

Cloning completed

Enable two virtual machines to configure IP addresses of the same network segment

Open the management console and configure the IP address for two virtual machines

Ping command to test the interworking between two virtual machines

Start heat transfer

Cancel the virtual machine CD before migration

Migrate two virtual machines

Migrate to an ESXi02 server

Default next step

Migration completed

Reposition

Logging in to ESXi02 using vclient will find that there are two more virtual machines, but there are no virtual machines on ESXi01

Clone, template, Snapshot 1, what is a cloned virtual machine?

As the name implies, a clone virtual machine is to create a replica virtual machine based on the original virtual machine. By cloning the virtual machine, the virtual machine can be deployed more quickly, and a certain backup effect can be achieved. The replica virtual machine has the same virtual hardware, installed software, and other properties as the original virtual machine. The original virtual machine can be cloned either in the boot state or in the shutdown state.

VCenter supports two types of cloning: full clone and linked clone full clone is a completely independent backup of the original virtual machine, it does not share any resources with the original virtual machine, and can be used independently from the original virtual machine. Link cloning needs to share the same virtual disk file with the original virtual machine and cannot run independently from the original virtual machine. However, the use of shared disk files can greatly shorten the time to create cloned virtual machines and save valuable physical disk space. By linking clones, you can easily create a separate virtual machine for different tasks. 2. What is a virtual machine template

Cloning virtual machines is a powerful tool for rapid deployment of virtual machines, but all virtual machines can be cloned, and the cloned virtual machines can also be cloned again. In the long run, the system will collapse, which brings a lot of trouble to administrators. Template is the best way to solve this problem, that is, a virtual machine that often initiates cloning is used as a virtual machine template, and every time a similar virtual machine needs to be cloned, it is initiated through a template.

3. What is a virtual machine snapshot

A snapshot is a "backup" of VMDK files for virtual machines at some point in time. As shown in the following figure, when the snapshot task starts, the virtual machine source VMDK file is frozen so that it is read-only everywhere, and a snapshot file is created, which will be written to all modified data in the future. Once the snapshot restore operation is triggered, the system will discard the contents of the snapshot file and return to the status of g\ un to the source VMDK file to achieve snapshot recovery. Strictly speaking, a snapshot is not a backup because the source VMDK file has not been backed up. Once the source VMDK file is corrupted, it cannot be recovered normally, and the performance of the snapshot file is not as good as that of the source VMDK file.

4. Case implementation

Clone a virtual machine

Edit the virtual machine name and click next

Clone to the first server

Store in shared storage

Default next step

Complete

Cloning

Cloning completed

Generate a snapshot

Edit the snapshot name and click next

Generating snapshot

View snapshot files

Manage Snapshot

Delete snapshot

Clone a virtual machine as a template

Edit the template name and click next

Clone the template to another ESXi server (ESXi01)

Choose to store it on shared storage, and click next

Complete

Template deployment of new virtual machines

Edit the name and click next

Select computing resources

Select shared memory and click next

Customize it according to your own needs. I default to the next step.

Complete

In process of deployment

Deployment complete

Start the li virtual machine and initialize the SID number

Send deploy.cab to the desktop quickly, copy all the contents to the new folder and open it.

Run sysprep

Select the shutdown mode and click repackage

Just make sure.

-this is the end of this article. Thank you for reading-

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.