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

For vSPhere administrators, VDP is a disk-based backup and recovery solution that is reliable and easy to deploy. VDP, an updated backup device, completely replaces the original backup architecture of VMware, and VDP is fully integrated with vCenter server to perform effective centralized management of backup jobs.

OVF template is an open, common, secure virtual machine compression format, usually using templates with .ova extension, but there is no difference between the two. OVF templates can be operated on multiple major virtualization platforms.

VDP, short for vSPhere Data Protection, is a new generation of disk-based backup and recovery solution launched by VMware and EMC through technical collaboration. It is reliable and easy to deploy, replacing the previous VDR and VCB;. It can be used to perform efficient centralized management of backup jobs while storing backups on deduplicated target storage.

There are two versions of VDP, VDP and VDP Advanced. The difference between them is that each appliance VDP Advanced supports up to 400 virtual machines and 8TB storage space, while ordinary VDP only supports up to 100 virtual machines and 2TB storage space, and VDP Advanced also supports application-level replication, can be restored to the level of granularity on Microsoft server and guest-level backup and restore for SQL server, exchange server and SharePoint server. In particular, it is important to note that VDP Advanced requires a license to use.

The difficulty of using VDP to backup is to install VDP. The steps are tedious and the waiting time is long, so it is a bit of a test of patience. When the backup and recovery operation is successful, it is very simple. In order to simplify the environment, use the following topology diagram to experiment.

VDP can be said to be a virtual machine installed on an ESXi host. Of course, no matter which ESXi host installs the VDP, as long as it is an ESXi host that vCenter server can control, it can be used for backup and recovery.

First, prepare before deployment:

1. To determine whether the time of all hosts is synchronized, if not, configure the time NTP server by doing the following: (if the time is synchronized, ignore these steps)

① type "regedit" on the DC server, open the registry, find: HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parameters and change the value of Type to "NTP"

② modifies HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Config to change the announceFlags value to 5:

③ modifies HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ TimeProviders\ NtpServer to change the Enabled value to 1

④ restarts the windows time service

⑤ turns off the firewall, or type "netsh firewall add portopening protocol = UDP port = 123 name = NTPSERVER" at the CMD command prompt to release traffic on this port.

⑥ configures ESXi as a NTP client:

192.168.1.1 is the IP address of the NTP server

⑦ starts the command line of the exsi host:

⑧ uses Alt+F1 to switch to character terminal

⑨ uses vi / etc/ntp.conf to modify the file and add a line to it

"tos maxdist 30"

⑩ executes the following command to modify the permissions of the file: Chmod + w / etc/likewise/lsassd.conf

⑪ modifies the file vi / etc/likewise/lsassd.conf, finds the line sync-system-time=no, and removes "#".

⑫ executes the following commands in turn:

/ sbin/auto-backup.sh / etc/init.d/lsassd restart/etc/init.d/ntpd restart

On the vcenter service, log in to web client again to see if the time is synchronized with the ntp server.

2. At this point, the problem of time synchronization is solved, and then the parsing information of the DC server is manually added to the "forward lookup zone" and "reverse lookup zone" in DNS on the VDP server.

1) as follows:

2) find the following on the vCenter web side, and click it to add:

3) add specific users (be careful here, do not ignore the add permissions, if you do not add the corresponding permissions, then the management page will not see any hosts. Solution: when you deploy the vCenter server at that time, add a new user to the group specified in the interface of the "4) figure, then log in to the vCenter web side with the newly added user, and then grant the appropriate permissions):

4) when vCenter server is deployed, add the users in that group here when the group specified in the following interface belongs to the computer:

Add as follows:

Pay attention to whether the selected computer name is the name of the computer in which the group belongs, and click add after you confirm it.

To set permissions, click OK:

At this point, you are ready for deployment, and now you are ready to deploy VDP's OVF template:

2. Deploy the OVF template for VDP:

1. Right-click the ESXi host and select "deploy OVF template" from the pop-up shortcut menu:

2. Click "Allow" as shown below:

3. As follows (I have prepared a VDP template here, the link address of the network disk: link: https://pan.baidu.com/s/1rfSvcb0cx4lSllq029q2Fg

Extraction code: e3dq):

4. After confirming that the template information of OVF is correct, click "next":

5. Click the accept button, and then click next:

6. Customize the name of the virtual machine, then specify the location of the deployment, and click "next":

7. Specify the location where the virtual machine files are stored. If there is an ISCSI storage server, the first choice is to have an ISCSI storage server. I do not have an ISCSI storage server here, so I select the storage of the ESXi host, then change the disk format to "Thin Provision", and click "next":

8. Set the network of the virtual machine. I keep the default here, and click "next":

9. Configure a specific IP address for the virtual machine:

10. After confirming the correctness, click "finish":

11. Wait for the progress bar to deploy the VDP virtual machine to complete (this process is long, need some patience, about 20 minutes, smoke a cigarette):

12. Deployment completed:

13. Power on the VDP virtual machine (you can also open the console like an ordinary virtual machine, but you generally do not need to open the console):

If you are interested, you can also open the console to see the startup process of the VDP system:

After the startup is complete, you will see its management address in the initial interface, as shown below:

3. VDP configuration utility:

1. After turning on the power, you need to wait for the system to start (the startup process is slow). You can determine whether the boot is successful by dying the IP address of ping. The target CVM cannot be accessed at first, because the system has not been started yet. When the system can be ping connected, you can log in to its management address and configure:

2. Enter the administrator password of the VDP configuration utility. The user name cannot be changed. The default password is changeme. Click "Log in":

3. Click "next" as follows:

4. Configure the network, hostname and domain by default, and click "next" (these are all set before deploying VDP, and generally do not need to be changed, and it is best not to change them any more, otherwise, unexpected errors will inevitably occur):

5. Choose the time zone, and I choose "Shanghai" here:

6. Set the administrator password (must meet the complexity requirements):

7. Enter the administrator username, password and fully qualified domain name (hostname + domain name) of vCenter, as follows:

The fully qualified domain name of the vCenter server is shown here on the vCenter server:

Click next after showing that the connection is successful:

8. Set the storage size created according to the actual situation:

9. Set the type and location of storage disks allocated for VDP. Select the "thin" option here, and click "next", as shown below:

10. Keep the default and click "next":

11. After confirming the correctness, click "Yes":

12. Wait for VDP to be configured automatically:

13. Click "restart now" (since some VDP versions are different, you may need to open the console of the VDP virtual machine, log in with the account root, password: changeme, and execute the command reboot to restart):

14. After clicking restart, you will automatically return to the login page of the VDP configuration tool and cannot log in (the VDP system is restarting):

15. On the vCenter management page, wait for about a minute, click Refresh, and the progress bar for the restart process will appear (very slow again, wait! ):

16. After waiting for the progress bar to complete, close the web page and reopen the browser connection to log in to vCenter server.

17. After logging in again, you will see an additional component on the home page, as shown below:

Create a backup task:

1. VCenter connection VDP:

2. Create a backup task as shown in the following figure:

3. Select "full Image":

4. According to the actual situation, select one or more virtual machines to back up:

5. The following operations are defined according to the actual needs, in the following order: backup schedule, backup retention time, backup job name, until "completed":

6. Click OK when prompted as follows:

7. The backup task has been created. If you do not reach the specified backup time, you can also back up manually. For example, select the backup job you created and click "backup now", as shown below:

5. Back up the virtual machine:

1. Click "backup now" and two options will appear. "backup all sources" represents backing up all virtual machines in this task; "backing up obsolete sources only" means backing up only virtual machines that were not backed up successfully the last time the backup task was run. (for example, ten virtual machines were selected in the backup job, but only eight were backed up last time due to special reasons. Select "backup only obsolete sources" to back up the two machines that were not backed up last time):

2. At this point, a progress bar will also appear on the right, and after the backup is completed, you can see the recovery point in the "restore" tab:

6. Restore the virtual machine:

1. As follows:

2. You can select the location where the virtual machine is restored in the "Advanced options" option group. If you select the "restore to original location" check box to overwrite the original virtual machine, I will keep the default here:

3. Click finish to start recovery:

At this point, the virtual machine is successfully backed up and restored.

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.