September 15, 2022

DR Plan and Inventory Mapping in VCDR- Part2

 

Disaster Recovery Plan and Inventory Mapping.

Before we will DR Plan First create Protection Group:

Protection Group: 

Protection Group is grouping of virtual machines which will recovered together.

In VMware Cloud Disaster Recovery supports protecting VM’s which is running on any kind of datastore like NFS,vSAN , VMFS or VVols …

Creating Protection group and grouping Virtual machine is helpful when you want to put the VM’s which is dependent on another server. For example, VM1 application is dependent on VM2 database or talking to VM2. If you want to recover both virtual machine as part of one plan and without any delay, then you can put together VM1 and VM2 in one protection group so during recovery they will power on as part of one Plan under one protection group.

Similar Fashion you can prep the application bundling of all VM’s and basis of that you can create Protection group and put in Specific protection group.

Create Protection Group:

1.        1. Go to VMware Disaster Recovery console Dashboard.

  2. In Navigation Plan you will Protection Group, Click on Protection group.


3.      3.  Right Side Corner you will get option to create Protection group, Navigate to Create                                Protection Group and Click.

4. Provide the Name of Protection as per Company standard or Planned name.Next, you must choose          the Protection Site from where you want to Protect VM’s.

 5. Under Group Member ship you can select the VM on basis of VM pattern, Tag, and folder.

E.g.

5.1.If you have List of VMs which name is starting from WIN01, WIN02, WIN03 then you can put WIN in search bar and it will reflect all VM’s Name starting from WIN.

5.2 If List of VM’s is tag with any security or any special tag example oracle then you can search with Oracle, and it will give you list of ALL VM’s which is tag with Oracle.

5.3 If List of VM’s is part of one specific folder like RHEL or RAC or Windows you can search with name of folder, and it will list down the all VM’s under that folder and you can choose VM’s which you want to protect.

 6.  Next You have schedule Snapshot schedule. Means on which frequency snapshot of Protected                will start.

6.1 Standard-frequency snapshots allow you to set snapshots schedules every hour, 4, 6, 8, or            12 hours, daily, weekly, or monthly.

 
6. 2 For High Frequency snapshot will schedule for every 30 minute.


Note : For High Frequency Snapshot you have to check the compatibility matrix like.If vCenter and Host are not compatible then you can not perform high frequency snapshot for protected VM’s.



7.To Use quiesced snapshot, you must uncheck the high frequency snapshot.
8. Click Preview VMs and FINISH.


Configure Inventory Mapping for DR Plan:

1. Network Mapping

2. vCenter and Folder Mapping

3. Compute Resource Mapping

Purpose of this Mapping is that when you will Perform DR activity VM’s or workload will attach with Pre-defined Mapping and using that it will attach with same resource, network folder in destination End.

vCenter Mapping: We have to Map all source vCenter which contains VMs need to be protected by VCDR.

DR Plan has vCenter mapping for the following components:

vCenter Folder

Compute Resource

Virtual Network

 

1.       Go to VMware Cloud Disaster Recovery Console page.

2.       Navigate DR Plan on Left side Bar and Click on DR Plan.

3.       Once You will click on DR Plan on Top Right Side it will highlight Create DR PLAN option.



4.       Click on Create DR Plan and Name DR as per your industry standard.



5.       In Recovery Site Section you have to choose the existing recovery SDDC which is deployed in Previous discussion.

                                                    

6.     Next section we have to select the Protected Site, we have to choose vCenter or site where VM’s are running which you want to protect. CLICK Next.

7.  Choose the protection group which you want to associate with DR plan.




8.  Now you have to choose the Protected vCenter and Revery vCenter Mapping.

                                    


9. Next is Folder Mapping, Click on Map Folder and choose Folder from Protected site and where 
    you want to recover virtual machine.
    Choose the Folder and Click on ADD .In my case Source Folder is HOL and Destination Folder is
    Workload .

            






10. Click on Map Compute resource and Map resource from Protected and recovery site .
                                            

11. Next We have Map the Virtual Network ,If you are going to use the streched network the it will
      Same subent on source and destination .In case you want to chnage the Network after recovery
      it will be diffrent .

      In My case ,you can see soource network is VM Network and Recovery side network is DR 
      DR Network after failover .

                                          


12. Next is IP address change ,VCDR will not change any ip address ,Recovered VMs Should                    use DHCP or Stretched netwrok .

13. We you want to run any script which you need to be run after failover you can intesrt script 
      using hilighted option using script for VM.

      Select list of VM's where you want to run the insert script .If you do not want
      to run any script the choose do not run any script and Click on Next.
                                          
               
14. If you want to Edit Recovry step the click on EDIT and change in recovery .Like ,Recover all VM's ,if you do not want to power on after recovery you can choose that option also .Its depend on you plan .
                                            

  15. Last you can set alert trigger for every complinace .Click on Configure email alert and
        enter genric mail id .Also from right side check the box for which you want to configure alert.               
                                               
              
 16. Review DR Plan and Click on Finish .


What Next ? :


1.Testing DR Plans and Monitor Failover Process .

2.Failback Plan and Compliance Health Checks .







No comments:

Post a Comment