How to Disaster Recovery from a Backup Copy
This documentation is to guide you how to disaster recovery from an offsite backup copy with Vinchin Backup & Recovery.
l Make sure you have two sites (let’s say site A and site B, site A as primary Site, site B as Disaster Recovery Site) production environment available.
l Install a Vinchin Backup Server on each Site, totally you will have two Vinchin Backup Servers with two web consoles available. Let’s say Site A Backup Server (server A) IP is 192.168.84.100, and Site B Backup Server (server B) IP is 192.168.84.190.
l Make sure each site backup server can access the IP of the other site backup server, and if there's any firewall between the two backup servers, port 30050 and 30051 needs to be opened on the server B side.
u Copy VM Backups from site A to site B
1. Add server B (192.168.84.190) as an “offsite storage” to server A from server A’s web console (192.168.84.100) “Resources-Storage”.
2. Create a backup job for the target VM ad execute this backup job on Server A. You will get backup data of this VM and you can see this restore point from the “Backup Data” list.
3. Create a backup copy job for target VM, choose off-site storage 1 as a copy destination, and execute this copy job on Server A. Once the job is finished, the copy of this backup data will be transferred to server B successfully.
You will see this copied restore point from the “Copy Data” list in server A (192.168.84.100) is stored in “offsite storage”. And see this restore point from the “Copy Data” list in server B (192.168.84.190) is stored in “onsite storage”.
That means your backup data has been replicated from site A to site B.
u Disaster Recovery
Now, if site A production data are all destroyed together with server A backup data, remember, you still have a copy of your backup data stored in site B server B. You only need to use the copy data in site B to recover the VM. The options are whether to recover the target VM directly on site B (DR site) or recover the VM to site A (primary site) if site A is rebuilt and available again. You can achieve both options by Vinchin Backup & Recovery.
l Recover the VM on-site B
First, let’s recover the VM directly on-site B using the copy data stored in server B. Log in to server B (192.168.84.190), go to “VM Backup -Restore” to create a restore job for the target VM, you will see the copy data is available in the first step.
Choose a target production host which is located in site B as restore destination for the VM.
Once this job is created, execute this restore job, the target VM will be restored to the target host in site B. That’s the way how to use copy data to restore target VM to site B (DR site).
l Recover the VM on site A
Suppose site A is rebuilt and available again, let’s see how to disaster recover the VM to site A from site B. There are actually two ways to achieve the disaster recovery.
1st way: Restore the copy data from site B to site A by executing a “Copy Restore” job, and restore the VM to site A production host by executing a “VM Restore” job.
2nd way: If the site A and site B are connected with each other by a dedicated network, you can add site A’s production hosts to server B from “Resources-Virtual Infrastructure”. And execute a VM restore job to restore target VM to site A production host.
To achieve 1st way, you need to firstly install a new Vinchin Backup Server (let’s say server A+, IP address 192.168.84.300) on site A new environment. Add server B as “offsite storage” on server A+ from “Resources-Storage”. The step is the same as Copy VM Backups from site A to site B step 1. Once done, server B and server A+ are connected with each other.
Now you can create a “Copy Restore” job on server A+, you will see the copy data stored in server B is visible and selectable.
Select this copy job and complete the copy restore job setting steps, then execute this job, the copy data will be transferred to server A+ from server B. You will see the restored copy data from “Copy Data” list in server A+. Now you can restore the VM directly from “VM Backup – Restore”.
To achieve 2nd way, you don’t need to install any Vinchin Backup Server on site A new environment, instead, you need to do some configurations on server B (site B) – add site A’s production hosts to server B from “Resources-Virtual Infrastructure”. The steps are just the same as the first time you added your production hosts to the backup server. And most important pre-requirement is that you have to make sure the site A and site B are connected with each other by a dedicated network.
Once added successfully, you can directly restore the target VM from server B “VM Backup –Restore”. Choose copy data as restore source.
And in the second step, you will see your site A’s production hosts are recognized and listed in the “Target Host” tree, and you can select a host as restore destination. Once done, execute this VM restore job, your target VM will be restored to target production host in site A.