Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Step 1:

...

Enable Interzone Replication

  • Log into MyAccount
  • Open up the VDC that has the VMs you wish to protect via SecondSite Interzone replication.As seen below choose the number of VMs you wish to protect, the zone you would like them replicated to and hit Protect Now
  • 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)

...

Follow through the payment gateway and confirm your selection.


Step 4: 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;

  • 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 vm and in vms and  your SS VDC till FAILOVER


Step 5: Firewall requirement

Default - If the default NSX-T firewall is sufficient (In most cases) - Go to Step 6

Excluded - If you require a BYO firewall, please following the following process 

...

  • Continue with Step 6 while waiting for support to create your Internet uplink and public IP details


Step 6: Configure your Secondsite Interzone Service 

Configure Networks

Log into your SS_ VDC and add networks rquired  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

Image Removed

Select Yes to the VM or vApp you want protect and complete the IP and Network section before protecting

Image Removed

and what networks it needs to use on failover (Networks created above)

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.

Image Removed

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.

Image Removed

Enter in the relevant information that you would like the production network to be. Ensure that you select to make the network Connected.

Image Removed

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.

...

  • 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  


Image Added


Image Added


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.

Image Removed

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.

Image Removed

Proceed over to the Management tab again for specific information about each VM under protection.

Image Removed

...

 

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

Image Added


Select Yes to the VM or vApp you want protect and complete the IP and Network section before protecting

Image Added

Request replication process can take up to a day or two to complete.


Step 7: Confirm Protection   


Log into your SecondSite services via MyAcount and confirm Protected VM's and SLA's

Image Added