50. Offsite (Azure) disaster recovery for local VMware Environment virtual machines (on)

Tag: Cloud Platform for Cloud computing

The first step is to complete the preparation ahead of time. Offsite (Azure) Disaster recovery-readiness

To implement an offsite azure disaster recovery for a virtual machine on a VMware virtualization platform, check the following prerequisites:

• The VMware platform is at least vcenter server 6.5, 6.0, 5.5 or VSphere 6.5, 6.0, 5.5, the recommended use of vcenter servers;

Virtual machines in VMware support the following types:

• Windows operating systems: 64-bit Windows Server 2016 (Server Core, server with Desktop Experience), Windows Server R2, Windows Server 2012, Windows Ser with SP1 (or later) Ver. R2. Windows Nano Server is not supported.
• Linux operating system: centos:5.2 to 5.11, 6.1 to 6.9, 7.0 to 7.4;ubuntu 14.04 LTS Server (supported kernel version), Ubuntu 16.04 LTS Server (supported kernel version); Debian 7/debia n 8;suse Linux Enterprise Server SP3, SUSE Linux Enterprise Server one-SP4 (does not support upgrading replication computers from SP3 to SP4. To upgrade, disable replication and re-enable it after the upgrade. ）

More detailed support list such as storage, network, etc. can be see:

Domestic version: Https://docs.azure.cn/zh-cn/site-recovery/vmware-physical-azure-support-matrix#on-premises-virtualization-servers

International Version: https://docs.microsoft.com/zh-cn/azure/site-recovery/vmware-physical-azure-support-matrix# On-premises-virtualization-servers

I've prepared an esxi stand-alone environment, and a vcenter,vcenter manages this ESXi host

Vcenter is also a Linux version

These VMs are running on ESXi hosts.

Vcenter manages this ESXi host

Where Centosweb simulated business systems provide Web services

Whether you are a single esxi or vcenter-capable environment, you need to prepare a virtualized platform account on the vcenter server or vsphere ESXi host to automate the discovery of ESXi or vcenter-managed virtual machines. This account requires the ability to discover VMS, schedule replication, failover, and failback, as well as create and delete disks, and open operations such as shutting down VMs. Here I take vcenter for example, first I need to open my vcenter ssh access, press F2 enter the root password to enter

Open SSH

Connect to vcenter via SSH

Create a Azureconnect account

Localaccounts.user.add--role operator--username Azureconnect--password

Set Azureconnect account password

You can then go back to the vcenter console to turn off SSH and then log in to the admin console of vcenter to assign roles to the Azureconnect account you just created, where I simply choose the administrator directly.

If you need strict control of permissions, you can refer to

The next step is to prepare the account in the virtual machine to install the mobile service, which requires the ability to install the software in the virtual machine. You can either be a domain account or a local account, but if it is a virtual machine for Windows and is not a domain account, first disable remote user access control for that Windows virtual machine:

Under Hkey_local_machine\software\microsoft\windows\currentversion\policies\system of the registry, add a DWORD entry Localaccounttokenfilterpolicy and set the value to 1

If it is a Linux virtual machine, you can use the root account;

Next you need to check:

Whether the Windows virtual machine RDP is turned on, and whether Windows Firewall allows all network types to run RDP access

If the virtual machine for Linux needs to check if secure Shell service is automatically started with the system, then firewall rules allow SSH connection

Since the business system here is Linux, then to successfully perform a configuration server push to install the mobile service to this Linux virtual machine requires a pre-requisite preparation:

• Make sure the network connection is established between the Linux computer and the configuration server
• Create an account that can be used by the configuration server to access the computer. The account should be the root user on the source Linux server. You can use this account only for push installations and updates
• Ensure that the/etc/hosts file on the source Linux server contains the hostname mapping to all native IPs

Vim/etc/hosts

• Install the latest openssh, Openssh-server, and OpenSSL packages on the computer you want to replicate

OpenSSH

Openssh-server

Openssl

• Make sure that SSH is enabled and running on Port 22.
• Enable the SFTP subsystem and password authentication in the Sshd_config file. Perform the following steps:

A. Log in as root.

B. In the/etc/ssh/sshd_config file, locate the line that begins with "Passwordauthentication"

C. Uncomment the line and change the value to Yes

D. Locate the line that begins with "Subsystem" and uncomment the line.

E. Restarting the SSHD service

The next step is to set up a disaster recovery environment:

Or use a Offsitedr instance of a previous recovery vault to set the protection target to a virtualized environment with VMware vsphere hypervisor

Choose Yes

Next you need to add a configuration server, this configuration server is to download a Microsoft Good VOF virtual machine template imported into the local vcenter into a virtual machine (if your company has restrictions, not allowed to deploy the OVF template, You can download the UnifiedSetup.exe installation configuration server yourself, the template virtual machine contains three roles: The component includes the configuration server, the process server, and the master target server.

• Configure the server: Orchestrate communications between on-premises and Azure and manage data replication.
• Process Server: acts as a replication gateway. It receives replicated data, optimizes it for caching, compression, and encryption, and then sends it to Azure storage. The process server also installs the mobile service on the VMS to be replicated and performs automatic discovery for local VMware VMs.
• Master target server: Handles replication data generated during failback from Azure.

Click Download, download the OVF virtual machine template file, about 18.13G, use the downloaded OVF template to go to vcenter to deploy the virtual machine. Then download the installation package for VMware VSphere POWERCLI 6.0 to install it on a deployed virtual machine.

To configure the server's virtual machine template OVA:

• International Version: http://download.microsoft.com/download/D/5/2/D52EC1B6-320E-4AC2-BD83-8F7766BB1E07/ Microsoftazuresiterecoveryconfigurationserver.ova
• Domestic version: http://download.microsoft.com/download/D/6/8/D68C528F-872D-4E20-BE2D-3C99999B461D/ Microsoftazuresiterecoveryconfigurationserver_cn.ova

Download down is a Microsoftazuresiterecoveryconfigurationserver.tar file that needs to be decompressed

Vmware POWERCLI 6.0:

Https://my.vmware.com/web/vmware/details?productId=491&downloadGroup=PCLI600R1

After the download is ready, you can deploy the OVF template virtual machine to the Vcenter console.

Browse to select the location of the OVF template file

Next

Specify the name of the virtual machine

Select Place Host

Choose which storage disk to place

Select disk Provisioning format

Click Finish

Wait for deployment to complete

After the deployment is complete, you can modify the configuration of the virtual machine yourself according to your environment (by default, the configuration server template is deployed using a single NIC.) You can add additional NICs after deployment to add additional NICs to the configuration server, which you add before registering the server with the vault. Adding additional adapters is not supported after registration)

50. Offsite (Azure) disaster recovery for local VMware Environment virtual machines (on)