Protect you running virtual servers between Zettagrid Zones!
Table of Contents
Step 1:
...
Enable Interzone Replication
Log into MyAccount
Open up the VDC that has the VMs you wish to protect via SecondSite Interzone replication.
Select Replicate with SecondSite Interzone and continue .
...
Step 2: Order
Select the number of
...
VM's you
...
want to protect
...
and the
...
...
Zone you want to use as your recovery location (Endpoint)
Purchase
Follow through the payment gateway and confirm your selection.
...
Step 3: Secondsite Interzone
...
VDC Information
Go back to your MyAccount page and witness that a new VDC with the prefix SS is being provisioned and appears as below.
...
As you can see it is highlighting a few important items;
- The VDC it is protecting
- An alert that there are currently no VPGs created
- The number of VMs you have purchased protection for
Step 4: Virtual Machines Available to Protect
Click the Management tab and see that there are no networks created as yet.
These networks are what the VMs will be attached to in the VDC in the new availability zone. This might be the same or completely different to what they are in the current availability zone.
Step 5: Network Configuration
Head to the Network tab and begin the network configuration.
Select an uplink and then hit on the edit button on the right hand side as per below.
Enter in the relevant information that you would like the production network to be. Ensure that you select to make the network Connected.
Now you have configured the production network. SecondSite also allows you to perform test failovers which are typically unrouted or internal networks that do not have any outbound connectivity. You will need to repeat the above process and create a test network for your VMs.
...
Interzone - (Your Protected VDC Name)
Replication - (Number of VMs and VPGs Protected)
Licenses - (Licenses and Extra storage ordered)
Take note - No VM's will be visible under failover vms and your SS VDC till FAILOVER
Step 4: Firewall requirement
Default - If the default NSX-T firewall is sufficient (In most cases) - Go to Step 5
Excluded - If you require a BYO firewall, please following the following process
- Log a Ticket at Zettagrid Support - support@zettagrid.com
- Ticket information to Include: Example
Secondsite Number (SS_1175368)
Secondsite Zone (Brisbane)
Account number (214xxxxxx)
Public IPs (Default /31 - More on Request)
Internet Traffic (Data Block or Unlimited per Mbps - Used on failover and can be resized)
Data Block - (100GB - 500000GB)
Mbps - (100Mpbs - 10Gbps)
- Continue with Step 5 while waiting for support to create your Internet uplink and public IP assignment
Step 5: Configure your Secondsite Interzone Service
Configure Networks
Log into your SS_ VDC and add networks required
NSX-T Firewall
Live Failovers - Routed Network (Connected to Firewall)
Test Failovers - Isolated Network
BYO Firewall
Live Failovers - Isolated Network (Connected to Firewall)
Test Failovers - Isolated Network
Please note: Secondsite Firewalls
NSX-T or new BYO Firewall - If you have advanced firewall rules or NAT rules setup in your production VDC then you will need to also create these on the new SecondSite instance as it is entirely separate from your production VDC.
...
Step 6: Enabling Protection
Return back to the Management tab and select the relevant networks and IPs for both production failover network and test failover network.
Make sure you select to enable protection for all the VMs you wish to protect and then hit Request Protection.
The VMs will now begin replicating. The initial replication can take considerable time (can be hours or days) as it will be potentially transferring multiple terabytes across the country so please be patient.
Once complete you will be able to see the status of the replication from the Overview page of the service as per below. You will be able to see how many VMs are protected and the overall information on whether they are meeting a 5 minute RPO target SLA or not.
Proceed over to the Management tab again for specific information about each VM under protection.
...
Replicated BYO Firewall - Possible config and license changes would be required
Select your VM's to be protected
Go to Manage located on the right of your SS service portal and select Protect VM's
Select Yes to the VM or vApp you want to protect and complete the IP and Network section before protecting
Step 6: Confirm Protection
Log into your SecondSite services via MyAccount and confirm Protected VM's and SLA's
Request protection process can take several hours to complete. (Initial Replication and config)
Step 7: Failover Process
Test Failover
Start of Virtual Servers in another zone without affecting Production! - Failover via MyAccount Portal
Log into MyAccount https://account.zettagrid.com/
Open up the SecondSite Service under My Services
Select View VPGs
Click Start Test on the VPGs you want to failover
Verifying Failover is In Progress (This can take a few minutes)
Verify your VM's started
Can be seen in MyAccount and Cloud Director
MyAccount
Cloud Director (Access VM's)
Confirm NIC's are connected before testing connectivity
Stop Test Failover
Stop of Virtual Servers in another zone without affecting Production! - Stop via MyAccount Portal
Log into MyAccount https://account.zettagrid.com/
Open up the SecondSite Service under My Services
Select View VPGs
Click Stop Test on the VPGs you want to cancel failover
Verify you VM's were removed
MyAccount
Cloud Director
Live Failover
Start of Virtual Servers in another zone when Production is down! - Can't be performed via MyAccount Portal
Contact Zettagrid Support to perform LIVE failovers! https://www.zettagrid.com/wp-content/uploads/2022/02/ZGSupportCard-v5.4.pdf
Support Phone 1300 597 656 (+61 8 6314 6580)
Support Email support@zettagrid.com