1. Guide for building DR / migration system using Veeam Backup & Replication’s replication function¶
1.1. Purpose of this document¶
Using Veeam Backup & Replication’s replication function to build a system to DR and migrate from VM on vSphere such as customer’s on-premises environment to VM on Dedicated Hyper-Visor (vSphere) provided at Enterprise Cloud 2.0 we will introduce reference information.
1.2. Precautions for Use¶
Before using this solution guide, please make sure on the followings:
・This solution guide provides an example of some configurations which Service Provider deployed.Please make sure that actual procedures and parameters required for your configuration may differ from this by depending on your environment.
・This solution guide mainly introduces operations specific to the construction of the configuration dealt with in this solution guide. Please refer to the Enterprise Cloud 2.0 Tutorial on how to operate general functions of Enterprise Cloud 2.0.
・Service Provider reserves that the right to alter or revise the descriptions in this document.
Note
The configuration introduced in this document is an example and it does not guarantee the performance itself. Please remind that it requires your own configuration which meets the requirements for capacity, availability and maintainability at your place.
Customers are requested to individually license licenses (OS, applications, etc.) other than Veeam Backup & Replication license.
For Veeam Backup & Replication, please contact Veeam Backup & Replication license distributor.
Please refer to the Enterprise Cloud 2.0 Tutorial on how to operate general functions of Enterprise Cloud 2.0.
1.3. About Veeam Backup & Replication and the composition outline (Introduction of configuration example)¶
By using this function, you can replicate the VM on vSphere in your customer’s on-premises environment (primary site) to the VM on vSphere(a Dedicated Hyper-Visor) in Enterprise Cloud 2.0(used as a DR destination or as a secondary site to be migrated). Here, we will introduce the procedure for constructing that mechanism.
・Required components and prerequisites
In order to construct the system introduced in this case, the following components and preconditions are required.
・vSphere (using ESXi 5.5 in this example) of the primary site (replication source)：
This is the host that has the VM as the replication source. Your on-premises environment and so on are assumed.
・vSphere (using ESXi 5.5 in this example) on the secondary site (replication destination)：
This is the host that has the VM as the replication destination. In this case, we will assume that you will use the Enterprise Cloud 2.0 Dedicated Hyper-Visor (vSphere) as a DR destination or migration destination.
・Replication software (in this case, Veeam Backup & Replication Standard Ver. 9.0 is used)：
It is software that provides the function to replicate. It consists of a Veeam Backup Server and a Backup Proxy to be described later.
・VM to be replicated (Windows Server 2012 R2 in this case)：
It is the replication target VM on vSphere of the primary site.
・Line for connecting the primary site and the secondary site：
Primary site (replication source) and secondary site (replication destination) need to be able to communicate via NW line.
（The communication requirements between the sites must satisfy the port requirements of Veeam.）
・Veeam Backup Server：
Physical server or virtual server running Veeam Backup & Replication.
This server is the management component of replication, and it plays the role of configuration and control.
Also install Veeam Backup & Replication setup file on this server.
In this case, we created a VM (Windows Server 2012 R2) on vSphere at the secondary site (Enterprise Cloud 2.0) as a Veeam backup server.
・Backup proxy：
It is responsible for obtaining VM data of ESXi’s DataSetre, transferring and receiving between sites.
In this case, we created one VM (Windows Server 2012 R2) on vSphere of the primary site and one VM (Windows Server 2012 R2) on vSphere, of the secondary site as backup proxy.
＊The Veeam Backup Server and Backup Proxy must be connected to VM Kernel.
＊For detailed functions and requirements of Veeam Backup & Replication please refer to Veeam’s website at the end of this page.
・Veeam Backup & Replication setup file and license file
Please obtain the setup file and license file of Veeam Backup & Replication by the method to tell when purchasing the license. Please also place it on the Veeam backup server.
・Configuration information such as IP address and host name spanning each component
・Administrator authority ID and password of ESXi on each of the primary site and the secondary site
（In Veeam Backup & Replication, it is necessary to register these information when communicating with each ESXi of the primary site and the secondary site.）
Image of configuration example
●Other components (optional) and points to keep in mind
・vCenter：
With Veeam Backup & Replication, replication can be performed by registering and communicating vSphere host information of the replication source and the replication destination, but replication can also be executed by registering vCenter information managing the vSphere host and communicating.
・Backup Repository：
It is the location used to store the backup file and the auxiliary file of the replica.
Veeam Backup Server also has this function.
The Backup Repository also has a function to store backup data, but in this case it will be an introduction in the case of replication, so its explanation will be omitted. For details, please refer to the manual etc provided on Veeam’s website.
＊In order to operate Veeam Backup & Replication, there is no need to be connected to the Internet, but when you place the setup file and license file of Veeam Backup & Replication on a server on Enterprise Cloud 2.0, need to connect with the external environment.
＊Please refer to the following for necessary to use Enterprise Cloud 2.0.
https://ecl.ntt.com/en/documents/tutorials/rsts/Introduction/preparation.html
・Work server (using a virtual instance of Enterprise Cloud 2.0 etc.)
Setting up a work server to use it for the following work increases convenience.
Connect to vSphere on the primary site and secondary site using VMWare vSphere Client etc., and manage and control.
Connect to Remote Desktop to Veeam Backup Server and manage Veeam Backup & Replication.
It is used as an Internet connection environment for downloading files.
Work log storage location
＊In this case, we use virtual instance (Windows Server 2012 R2) for the above purpose.
Since it is also used as the primary storage location of the file, we recommend that the disk capacity be large to some extent.
1.4. Flow of construction¶
Below is the flow of construction of each component which constitutes this construction example.
(1)．Preparation at the primary site (replication source)
・Preparation of vSphere as the replication target source: It is assumed that it already exists as an existing environment.
・Selection of the target VM
・Preparing the VM for the Backup Proxy ：
It is recommended to build it on the same host as the VM to be replicated. (We prepared Windows Server 2012 R2 in this case).
＊The backup proxy must be able to communicate with the vSphere VM kernel at the primary site.It is necessary to be able to communicate with the backup proxy of the secondary site.
(2)．Preparation at the secondary site (replication destination)
・Prepare vSphere for replication: Build a Dedicated Hyper-Visor (vSphere) for Enterprise Cloud 2.0.
Construction procedure please refer to Knowledge Center below.
How to create a new vSphere ESXi server
https://ecl.ntt.com/en/documents/tutorials/rsts/Dedicated-Hypervisor/vSphere/vSphereESXi/create.html
＊Please Design and build with resources meeting customer requirements.
＊Reference: The environment of this case
・Flavor: General Purpose 2
・ESXi:vSphere_ESXi5.5
Created by.
Datasotere uses built-in storage in the flavor.
＊When building Datastore as block storage, please refer to the following.
How to use block storage
https://ecl.ntt.com/en/documents/tutorials/rsts/Storage/block_storage/index.html
It is recommended that you prepare the work server for management and control of vSphere by using virtual instances etc.
Please confirm that vSphere can manage and control from the work server (install VMWare vSphere Client etc).
・Preparing the server for the Veeam Backup Server
It is not indispensable to build this server with VM. Physical servers, virtual instances, etc. can be used. However, it is necessary to be able to communicate with the VM Kernel network of vSphere of the primary site and the secondary site. You also need to be able to communicate with the backup Proxy of the primary site and the secondary site. (In this case, we prepared VM of Windows Server 2012 R2.)
・Preparing the VM for the Backup Proxy : Build a server (VM) that plays the role of the Backup Proxy. It is recommended to build it on the same host as the VM as the replication destination.(Windows Server 2012 R2 was prepared in this case).
＊In addition, this server needs to be able to communicate with the VM Kernel of vSphere of the secondary site. You need to be able to communicate with the Backup Proxy of the primary site.
(3)．Construction of NW connecting the primary site (replication source) and the secondary site (replication destination)
In this case, the primary site is set as the collocation rack of our data center, and it is connected with the secondary site, Enterprise Cloud 2.0, by CIC(NW service connecting colocation and Enterprise Cloud 2.0).
(4)．Construction of Veeam Backup & Replication
For installation and setting of Veeam Backup & Replication please refer to the evaluators guide provided by Veeam which we will inquire below.
https://www.veeam.com/veeam_backup_9_0_evaluators_guide_vsphere_pg.pdf
(4)-1. Installing Veeam Backup & Replication
Please refer to evaluators guide P12 to 15.
(4)-2. Register each Infrastructure of Veeam Backup & Replication (ESXi and Backup Proxy)
Please refer to evaluators guide P16 to 23.
(4)-3. Create a replication job and execute job
Please refer to evaluators guide P76 to 88.
(4)-4. Failover a VM Replica (to secondary site)
Please refer to evaluators guide P89 to 91.
＊Canceling failover and failback (processing when cancellation of Failover to the secondary site or Failing back to the primary site becomes necessary)
Please refer to evaluators guide P92 to 98.
1.5. About Veeam Backup & Replication¶
Please refer to Veeam’s website below for detailed explanation of the product and system requirements of Veeam Backup & Replication.
（Regarding the description of this site it will be outside our control.）
・Various introduction page about Veeam Backup & Replication
Veeam Backup & Replication 9.0
Veeam Backup & Replication 9.5
・Supported platforms
Veeam Backup & Replication 9.0
Veeam Backup & Replication 9.5
・System requirements
Veeam Backup & Replication 9.0
Veeam Backup & Replication 9.5
・Communication requirement
Veeam Backup & Replication 9.0
Veeam Backup & Replication 9.5
・License registration method
Veeam Backup & Replication 9.0
Veeam Backup & Replication 9.5
・Veeam Backup & Replication Best Practices
The evaluators guide for using Veeam Backup & Replication in constructing the configuration example described on this page is as follows.
Veeam Backup & Replication 9.0
Veeam Backup & Replication 9.5
that’s all.