VRA Installation Requirements
To install a VRA you require the following on the Hyper-V host:
■ 15GB storage space
■ At least 1GB of reserved memory.
■ Port 8100 must be enabled on SCVMM.
■ Minimum PowerShell version: 4.0
■ The following PowerShell cmdlet has been run:
Install-WindowsFeature –Name Hyper-V -IncludeManagementTools -Restart
You must know the following information to install a VRA:
■ The storage the VRA will use, and the local network used by the host.
■ The network settings to access the peer site; either the default gateway or the IP address, subnet mask, and gateway.
■ If a static IP is used, instead of DHCP, which is the Zerto recommendation, you need to know the IP address, subnet mask, and default gateway to be used by the VRA.
Note: In a non-production environment it is often convenient to use DHCP to allocate an IP to the VRA. In a production environment this is not recommended. For example, if the DHCP server changes the IP allocation on a reboot, the VRA does not handle the change.
Before You Begin:
You must also know the following information to install a VRA:
■ The storage the VRA will use, and the local network used by the host.
■ The network settings to access the peer site; either the default gateway or the IP address, subnet mask, and gateway.
Note: When the gateway is not required, you can specify 0.0.0.0 as the gateway, for example when performing self replication.
■ If a static IP is used, which is the Zerto recommendation, instead of DHCP, the IP address, subnet mask and default gateway to be used by the VRA.
Note: In a non-production environment it is often convenient to use DHCP to allocate an IP to the VRA. In a production environment this is not recommended. For example, if the DHCP server changes the IP allocation on a reboot, the VRA does not handle the change.
■ If the peer site VRAs are not on the default gateway, you must set up routing to enable the VRAs on this site to communicate with the peer site VRAs before defining the VRAs.
■ Setting up routing after defining VRAs only applies to VRAs installed after the routing is set.
■ Any existing VRA is not affected and access to these VRAs continues via the default gateway.
■ If the default gateway stops being used, you must reinstall the VRAs that were installed before setting up paired site routing.