I'm trying to figure out if a disaster recovery operation can be done from a system running networker 8.2.2 with a data domain to a system running networker 8.2.2 without a data domain. Specifically, I have a VMware environment with the 0.5 TB OVA managing the backups on my primary system. The backups are done to a data domain daily. From there I clone the VM backups to tape (last full backup) and copy the bootstrap information to tape. I then take the tape to my DR site, which is physically disconnected from my primary site, does not have a data domain but has other storage attached to it, has a freshly installed copy of networker, and is running the same VMware version (6.0) as my primary site. Does anyone know the steps to recover the VMs on the tape into my DR environment?
In case of a Total Disaster where you want the NetWorker Server to be also recovered? or only the VMs to recover?
In case you want the VM's to be recovered from Tape, you need the below things ready from High Level..
1. NetWorker Server with Calatalogs
2. VBA appliance - with DR done
3. Restoration of the VM's from Clone copy
At the DR site you will need to redeploy the VBA with the same name and recover the CheckPoint to get all catalogs back. In order for you to restore the VM's at the DR site from Tapes you will need another DataDomain and only then you will be able to recover the Data.
As per your explanation, primary backups are to data-domain and then they are cloned to a tape. The clone tapes are now mounted onto the DR site.
I am assuming that on the DR site, the NetWorker backup server is same as the original name ( If you have already not done this, then you will need to have this performed i.e. the DR of NetWorker server and networker server has to come up on DR site with same name and bootstrap imported into it.) Once done, you have to do the following:
1) Deploy a new VBA with a new network, name, IP as you may wish. On 8.2.2 the original VBA is not needed.
2) Register this new VBA onto the same NetWorker server ( this will be your current DR NW server).
3) Launch the vSphere web client GUI and connect to the new VBA that was deployed through the EBR plug-in.
4) Go to the 'Restore' tab.
5) There you will find a new option 'Choose restore points from' . Here click on the dropdown list and you will see that your old VBA name is listed. Click on it and it will generate the backups list.
6) Choose the VM that you want to restore, expand and select the secondary copy availaible and proceed with 'restore' .
Note: You may have to mark the primary SSID copy as 'suspect' in case it doesnt go through.
Let me know,
On 8.2.x , the DR of VBA is not required. You can simply deploy a new VBA and register it with same NetWorker server.
DR of VBA was required for 8.1.x versions.
I have deployed the VBA @ DR Site but I registered it to DR Site Networker and tested some backups which runs fine.(yes I also installed Hotfix Charlie on it before test )
Now I wanted to test the Restore of VM’s which I back in Prod VBA and Clone to DR Site DD. But I think for that I need to register the DR VBA to Prod Networker.
Also I think 1 VBA can be registered to only 1 Networker server at a time, is that correct?
Also since there is a FW between Prod and DR, so in order to register the DR VBA to Prod Site Networker I need to open some ports.
Can you give me the list of Ports required to be open with source / destination.
your vba @DR site that you registered with DR site networker will work like expected setup, it then becomes as good as a primary server.
And 1 VBA can only be registered on 1 networker server.
Is this DR site NetWorker server having the same info as the primary NetWorker server? i.e. NetWorker1 == NetWorkerDR by all means?
The requirement is that You should have the primary and DR VBA both registered to the same NetWorker server. If your primary NW server has gone down then you have to build it up ( disaster recovery of NW server) again with same name in the DR site.
Now here on the DR site, when you launch the NMC, you will see both the primary VBA and secondary VBA listed under Configuration tab. IF the secondary VBA is not there then you can simply follow my steps from earlier comments and get it running.
Once this is done, login to the secondary VBA web client GUI, you will be able to see the primary copies of the backups taken on primary VBA on the restore tab.
Thx for your answers. Since the DR site has its own Vcenter server and DR VBA is deployed in DR Vcentre.
Do we also need to open ports for communication for DR VBA @ Prod Vcentre?
Like for eg, below are the ports i have requested to open for this to work, is it ok :
|PROD vCenter||DR Site VBA||8543|
|DR Site VBA||VMware SSO||7444|
|Prod Site NetWorker server||DR Site VBA||8543|
|Prod Site NetWorker server||DR Site VBA||7937-9936|
|DR Site VBA||Prod Site NetWorker server||7937-9936|
|DR Site VBA||Prod Site NetWorker server||8080|
You have to open ports between DR VBA and the Production NetWorker backup server. there is no need for separate vCenter connection but if your environment is behind firewall then you will have ensure that the connection completes from DR vCenter and reaches to the datazone where primary backup server resides.
Additionally the DR VBA will be needed to registered with the primary backup server, once you have the ports open then it will communicate successfully.