This guide walks you through deploying the HyperV version of the dr2cloud vDPA (virtual data protection appliance).
The deployment process will consist of three phases:
- Choosing storage locations and importing vDPA VM
- Configuring imported vDPA VM and booting it up
- Initial setup of the virtual data protection appliance
What you need:
To prepare for step #1, consider the following recommendations for a Hyper-V server that will host the vDPA VM:
- At least 2 CPU cores and 8GB of RAM available (not already used by other VMs or the host system)
- 180GB of storage with low latency (preferably an SSD attached locally to the host machine) for the catalog volume
- 2TB (or more) of high throughput storage to house the storage volume
Step #1 Choosing storage locations and importing the vDPA VM
Before going any further, let’s decide where you are going to store the VM and virtual disk (VHD) files.
For optimal performance, there are a number of factors to consider when deciding where to locate the VM and virtual disk files:
- At a minimum, the files should be stored separately from other VM files to avoid disk contention and other performancedegrading issues.
- If you have an SSD available on the server, this would be an ideal location for the catalog volume since it will see a very high level of traffic. The catalog volume holds, among other things, the database that is used by the system for bookkeeping, tracking, etc and performance benefits from having low latency to this volume.
Select a location for the VM files
Decide where you want to store the VM files and create a folder there named ‘dr2cloudvDPAVM’ (you can use a different name, but please take note of it if you do). The storage device for these files doesn’t need to be very large. But, as mentioned before, try to locate them apart from any other VMs on the server.
Select a location for the catalog virtual disk (VHD) file
Decide where you want to store the catalog virtual disk (VHD) file and create a folder there named ‘dr2cloudvDPACatalog’ (you can use a different name, but please take note of it if you do). Important: this disk should reside on the highestperforming storage hardware you have. If you have an SSD, put it there, otherwise choose a lowlatency RAID or similar storage device. If not using an SSD, try to use a separate physical storage device from your other virtual machine files.
Select a location for the boot and storage virtual disk (VHD) files
Decide where you want to store the boot and storage virtual disk (VHD) files and create a folder there named ‘dr2cloudvDPAData’ (you can use a different name, but please take note of it if you do). Remember, select a location that is (preferably) on a separate physical device from all your other VM disk files. Ideally this device would be a high throughput RAID, or similar. If you don’t have an SSD, try to put these disk files on a separate device from where you put the catalog disk files.
Getting and unpacking the ZIP archive Download the vDPA ZIP file, and unzip this file into the ‘dr2cloudvDPAData’directory we created above. Do not move the catalog volume yet, or import will fail. We will move the catalog volume after the import.
Importing the vDPA virtual machine
- Open the HyperV Manager and, from the ‘Action’ menu, choose ‘Import Virtual Machine’. Note: if you have a VM selected, this option will not appear in the menu. Make sure nothing is selected if you don’t see the import item in the menu.
- Click the ‘Next’ button twice, taking you to the ‘Choose Import Type’ page. Select the option to ‘Copy the virtual machine’ (this will ensure that the VM gets assigned a new UUID). Do not check the “Duplicate all files so the same virtual machine can be imported again” checkbox, or vmware will copy all the VHDs into its default directory for virtual disks.
- Click Import. You should now see the dr2cloudvDPA VM that has just been created. Now we need to modify this VM’s configuration. First open the Windows Explorer, and move the catalog.vhd file from the dr2cloudvDPAData\Virtual Hard Disksdirectory to the ‘dr2cloud vDPACatalog’ directory you created earlier.
- Now back in the HyperV Manager window, right-click on the dr2cloud vDPA VM and click on settings.
- Under the SCSI controller select the catalog.vhd hard drive on the left. Click the browse button, and browse to the new location of the catalog.vhd file in the ‘dr2cloudvDPACatalog’ directory you created earlier, and then click apply.
- Click on the Network Adapter. In the network drop down list, select the virtual network to connect your vDPA to. It is recommended that you set a static MAC address while you are here so that HyperV doesn’t give it a different MAC in the future. If the MAC address changes the network settings will be lost. Select static and assign a MAC address that you know does not conflict with any other system on your network.
- If you add additional NICs to your vDPA be sure they are also setup with unique static MAC addresses.
- Once the VM is configured, it is time to boot up for the first time. During this initial boot, the Virtual Appliance will try to get an IP address via DHCP, and once it has finished booting it will display this address on its console.
- Go to the web interface at that IP in your web browser, and log in. The username is “admin”, and the default password is “rvxd2d2d”.
- Enter the license key (delivered via email), or your dr2cloud Dashboard credentials to login and authorize the Appliance.
- At the “Configure Storage” screen, there are 3 lists of disks. On the left is a list of available drive that have not been assigned, and on the right is a list of storage disks, and catalog disks. To assign a disk to one of these categories, checked the box next to the disk, and then click the right arrow (>>) next to the list you want to assign that disk to. Disks assigned to storage are used to store backup data, and disks assigned to the catalog volume will be used for the databases to manage backup jobs and deduplicated data.
- A summary screen is shown. Review you selected storage layout and then click finish.
- After you click finish, the virtual appliance will reboot. During this boot the disks are formatted, and the deduplicated storage is created. This can take a long time, but please do not shutdown or reboot the appliance until this has finished. Once the appliance has finished booting, log in to the web interface again. You will be shown the end user license agreement. Read the agreement and click the “I Agree” button at the bottom.
- At the quick start wizard, you will setup initial system settings. Go through the steps in the wizard to set your timezone and time, set the password, set the appliance’s hostname and IP addresses, etc. At the end of this quickstart, we will do a final reboot of the appliance, and it will then be ready to use.