Site Protection and Recovery. VMware Validated Design 4.0 VMware Validated Design for Software-Defined Data Center PDF Free Download

Site Protection nd Recovery VMwre Vlidted Design 4.0 VMwre Vlidted Design for Softwre-Defined Dt Center 4.0

You cn find the most up-to-dte technicl documenttion on the VMwre wesite t: https://docs.vmwre.com/ If you hve comments out this documenttion, sumit your feedck to docfeedck@vmwre.com VMwre, Inc. 3401 Hillview Ave. Plo Alto, CA 94304 www.vmwre.com Copyright 2016 2017 VMwre, Inc. All rights reserved. Copyright nd trdemrk informtion. VMwre, Inc. 2

Contents Aout VMwre Vlidted Design 5 1 Filover nd Filck Checklist for the SDDC Mngement Applictions 6 2 Prerequisites for SDDC Filover or Filck 8 3 Filover of the SDDC Mngement Applictions 9 Configure Filover of Mngement Applictions 10 Configure Filover of vrelize Opertions Mnger 10 Configure Filover of the Cloud Mngement Pltform 27 Test the Filover of Mngement Applictions 46 Test the Filover of vrelize Opertions Mnger 46 Test the Filover of the Cloud Mngement Pltform 49 Perform Plnned Migrtion of Mngement Applictions 52 Initite Plnned Migrtion of vrelize Opertions Mnger 52 Initite Plnned Migrtion of the Cloud Mngement Pltform 54 Perform Disster Recovery of Mngement Applictions 56 Reconfigure the NSX Instnce for the Mngement Cluster in Region B 56 Recover the Control VM of the Universl Distriuted Logicl Router in Region B 59 Reconfigure the Universl Distriuted Logicl Router nd NSX Edges for Dynmic Routing in Region B 60 Verify Estlishment of BGP for the Universl Distriuted Logicl Router in Region B 63 Enle Network Connectivity for the NSX Lod Blncer in Region B 63 Initite Disster Recovery of vrelize Opertions Mnger in Region B 64 Initite Disster Recovery of the Cloud Mngement Pltform in Region B 65 Post-Filover Configurtion of Mngement Applictions 66 Configure the NSX Controllers nd the UDLR Control VM to Forwrd Events to vrelize Log Insight in Region B 67 Updte the vrelize Log Insight Logging Address fter Filover 71 Reconfigure the NSX Instnce for the Mngement Cluster in Region A fter Filover 72 4 Filck of the SDDC Mngement Applictions 76 Test the Filck of Mngement Applictions 76 Test the Filck of vrelize Opertions Mnger 77 Test the Filck of the Cloud Mngement Pltform 80 Perform Filck s Plnned Migrtion of Mngement Applictions 83 Initite Filck s Plnned Migrtion of vrelize Opertions Mnger 83 Initite Filck s Plnned Migrtion of the Cloud Mngement Pltform 86 VMwre, Inc. 3

Perform Filck s Disster Recovery of Mngement Applictions 88 Reconfigure the NSX Instnce for the Mngement Cluster in Region A 89 Recover the Control VM of the Universl Distriuted Logicl Router in Region A 91 Reconfigure the Universl Distriuted Logicl Router nd NSX Edges for Dynmic Routing in Region A 92 Verify the Estlishment of BGP for the Universl Distriuted Logicl Router in Region A 95 Enle Network Connectivity for the NSX Lod Blncer in Region A 98 Initite Disster Recovery of vrelize Opertions Mnger in Region A 98 Initite Disster Recovery of the Cloud Mngement Pltform in Region A 99 Post-Filck Configurtion of Mngement Applictions 101 Configure the NSX Controllers nd the UDLR Control VM to Forwrd Events to vrelize Log Insight in Region A 101 Updte the vrelize Log Insight Logging Address fter Filck 106 Reconfigure the NSX Instnce for the Mngement Cluster in Region B fter Filck 107 5 Reprotect of the SDDC Mngement Applictions 111 Prerequisites for Performing Reprotect 111 Reprotect vrelize Opertions Mnger 112 Reprotect the Cloud Mngement Pltform 113 VMwre, Inc. 4

Aout VMwre Vlidted Design Site Protection nd Recovery VMwre Vlidted Design provides step-y-step instructions out performing disster recovery of VMwre mngement components in the softwre-defined dt center (SDDC). You use VMwre Site Recovery Mnger nd VMwre vsphere Repliction to perform site protection nd recovery of the Cloud Mngement Pltform tht consists of vrelize Automtion, vrelize Orchestrtor nd vrelize Business, nd of the vrelize Opertions Mnger nlytics cluster. Intended Audience The VMwre Vlidted Design documenttion is intended for cloud rchitects, infrstructure dministrtors, cloud dministrtors nd cloud opertors who re fmilir with nd wnt to use VMwre softwre to deploy in short time nd mnge n SDDC tht meets the requirements for cpcity, sclility, ckup nd restore, nd disster recovery. Required VMwre Softwre VMwre Vlidted Design is complint nd vlidted with certin product versions. See VMwre Vlidted Design Relese Notes for more informtion out supported product versions. VMwre, Inc. 5

Filover nd Filck Checklist for the SDDC Mngement Applictions 1 Use checklist to verify tht you hve stisfied ll the requirements to initite disster recovery nd plnned migrtion of the SDDC mngement pplictions. Tle 1 1. Checklist for Filover nd Filck Checklist Activtion nd Assessment Approvl Tsks Verify tht the disster filover or filck is relly required. For exmple, n ppliction filure might not e cuse to perform filover or filck, while n extended region outge is vlid cuse. Also, consider usiness continuity events such s plnned uilding mintennce or the possiility of hurricne. Sumit required documenttion for pprovl to the following roles: IT mngement Business users CTO Activtion Logistics Ensure tht ll required fcilities nd personnel re ville to strt nd complete the disster recovery process. Verify tht Site Recovery Mnger is ville in the recovery region. Verify the repliction sttus of the pplictions. Verify the stte of the NSX Edge in the recovery region. Are the NSX Edges ville? Are the IP ddresses for VXLAN cked networks correct? Is lod lncer on the NSX Edge configured ccording to the design? Is the firewll on the NSX Edge correctly configured ccording to the design? VMwre, Inc. 6

Tle 1 1. Checklist for Filover nd Filck (Continued) Checklist Communiction, Initition nd Filover/Filck Vlidtion Tsks In the cse of plnned migrtion, Notify the users of the outge. At the scheduled time initite the filover or filck process. In the cse of disster recovery filover/filck, notify ll stkeholders nd initite the filover or filck process Test the ppliction vilility fter the completion of filover or filck. Notify ll stkeholders of completed filover or filck. Post Filover/Filck Configurtion In the cse of disster recovery filover/filck, perform the following configurtion: Updte the ckup jos to include the pplictions tht re now running in Region B. Configure the NSX Controllers nd the UDLR Control VM to forwrd events to vrelize Log Insight in the recovery region. Redirect the log dt from the filed over or filed ck pplictions to vrelize Log Insight in the recovery region. Complete post-recovery ssessment. For exmple, note which items worked nd which did not work, nd identify plces for improvement tht you cn incorporte ck in the recovery pln. VMwre, Inc. 7

Prerequisites for SDDC Filover 2 or Filck For fultless filover or filck to the recovery region, verify tht your environment stisfies the requirements for filover or filck cple SDDC configurtion. Tle 2 1. Filover or Filck Prerequisites Prerequisite Compute The compute in the recovery region must mirror the compute in the protected region. Storge The storge configurtion nd cpcity in the recovery region must mirror the storge configurtion nd cpcity in the protected region. Shred dtstore spce on the mngement pod with enough cpcity must e ville for ll VMs of vrelize Automtion nd vrelize Opertions Mnger. Externl Services Provide the following services in the recovery region. See Externl Service Dependencies from the Plnning nd Preprtion documenttion. Active Directory DNS NTP SMTP Syslog Virtul Infrstructure ESXi, vcenter Server nd NSX for vsphere mirrored in the protected region Site Recovery Mnger nd vsphere Repliction deployed in oth regions nd pired NSX Edge devices for North-South Routing deployed nd configured in oth regions Universl distriuted logicl router deployed nd configured NSX Lod Blncer deployed nd configured in oth regions VMwre, Inc. 8

Filover of the SDDC 3 Mngement Applictions Configure nd perform filover of the mngement pplictions in the SDDC from the protected region, Region A, to the recovery region, Region B. You fil over the following mngement components: Anlytics cluster of vrelize Opertions Mnger Primry components of vrelize Automtion, vrelize Orchestrtor, nd vrelize Business The remote collector nodes of vrelize Opertions Mnger re not filed over. You deploy seprte pir of remote collectors in ech region in n ppliction isolted network. The vsphere Proxy Agents of vrelize Automtion nd the vrelize Business dt collector re not filed over. You deploy seprte pir of gents nd collector in ech region in n ppliction isolted network. 1 Configure Filover of Mngement Applictions Prepre the mngement pplictions in the SDDC for filover or plnned migrtion. Replicte ppliction-specific virtul mchines y using vsphere Repliction nd crete recovery plns for these virtul mchines y using Site Recovery Mnger. 2 Test the Filover of Mngement Applictions Test the recovery pln for the mngement pplictions in the SDDC to eliminte potentil prolems during future filover. 3 Perform Plnned Migrtion of Mngement Applictions After you hve successfully configured nd tested filover of the mngement pplictions, strt the migrtion process from Region A to Region B. 4 Perform Disster Recovery of Mngement Applictions Prepre networking in Region B nd perform filover of Relize Automtion, vrelize Orchestrtor, vrelize Business, nd vrelize Opertions Mnger to Region B if Region A ecomes unville in the event of disster or if you pln grceful migrtion. 5 Post-Filover Configurtion of Mngement Applictions After filover of the cloud mngement pltform nd vrelize Opertions Mnger, you must perform certin tsks to ensure tht pplictions perform s expected. VMwre, Inc. 9

Configure Filover of Mngement Applictions Prepre the mngement pplictions in the SDDC for filover or plnned migrtion. Replicte ppliction-specific virtul mchines y using vsphere Repliction nd crete recovery plns for these virtul mchines y using Site Recovery Mnger. Configure Filover of vrelize Opertions Mnger Prepre vrelize Opertions Mnger for filover y replicting the virtul mchines of the nlytics cluster nd creting recovery pln for them in Site Recovery Mnger. Configure Filover of the Cloud Mngement Pltform Prepre vrelize Automtion, vrelize Orchestrtor, nd vrelize Business for filover. Replicte the virtul mchines of the primry vrelize Automtion components, vrelize Orchestrtor, nd of vrelize Business Server. Crete recovery pln for them in Site Recovery Mnger. Configure Filover of vrelize Opertions Mnger Prepre vrelize Opertions Mnger for filover y replicting the virtul mchines of the nlytics cluster nd creting recovery pln for them in Site Recovery Mnger. Procedure 1 Replicte the VMs of vrelize Opertions Mnger Configure the repliction of the virtul mchines tht prticipte in the nlytics cluster of the vrelize Opertions Mnger to support filover of vrelize Opertions Mnger to Region B. 2 Crete Protection Group for vrelize Opertions Mnger After you configure repliction solution for the nlytics virtul mchines of vrelize Opertions Mnger, include the virtul mchines in protection group so tht Site Recovery Mnger protects them together. 3 Crete Recovery Pln for vrelize Opertions Mnger After you crete protection group for the virtul mchines of the vrelize Opertions Mnger nlytics cluster, crete recovery pln. You use this pln to run commnds on Site Recovery Mnger nd the nlytics virtul mchines, nd configure dependencies etween the virtul mchines. 4 Customize the Recovery Pln for vrelize Opertions Mnger After you crete the recovery pln for the vrelize Opertions Mnger filover, configure the strtup priority nd the strtup nd shutdown options for the virtul mchines of the nlytics cluster. 5 Duplicte the Anti-Affinity Rules for vrelize Opertions Mnger in Region B VM nti-ffinity rules re not retined during Site Recovery Mnger ssisted recovery. You must duplicte the nti-ffinity rules for the nlytics virtul mchines in Region B so tht the rules pply fter filover of vrelize Opertions Mnger. VMwre, Inc. 10

Replicte the VMs of vrelize Opertions Mnger Configure the repliction of the virtul mchines tht prticipte in the nlytics cluster of the vrelize Opertions Mnger to support filover of vrelize Opertions Mnger to Region B. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, select VMs nd Templtes. 3 Nvigte to the vrops01 VM folder. Oject vcenter Server Dt center Folder mgmt01vc01.sfo01.rinpole.locl SFO01 vrops01 4 On the vrops01 pge, click the VMs t, click Virtul Mchines nd select the virtul mchines of the nlytics cluster. Nme vrops-mstrn-01 vrops-repln-02 Role Mster node Mster replic node vrops-dtn-03 Dt node 1 5 Right-click the VM selection, nd select All vsphere Repliction Actions > Configure Repliction. VMwre, Inc. 11

6 Click Yes in the dilog ox out performing repliction for ll ojects. The Configure Repliction for 3 Virtul Mchines wizrd opens. 7 On the Vlidtion pge of the Configurtion Repliction dilog ox, wit until the vlidtion completes, click Next. 8 On the Repliction type pge, select Replicte to vcenter Server nd click Next. 9 On the Trget site pge, select the mgmt01vc51.lx01.rinpole.locl vcenter Server in Region B nd click Next. 10 On the Repliction server pge, select Auto-ssign vsphere Repliction server nd click Next. If the environment contins severl replictions servers, selecting this option mkes use of ny of these repliction servers. VMwre, Inc. 12

11 On the Trget loction pge, set the loction on the vsan dtstore in Region B to store replicted VM files. Click the Edit for ll link. In the Select Trget Loction dilog ox, select the LAX01A-VSAN01-MGMT01 dtstore from the dtstore list in the upper prt of the dilog ox. VMwre, Inc. 13

c In the Select trget loction pne, select the LAX01-VSAN01-MGMT01 root folder underneth, nd click OK. vsphere Repliction will crete folder in the root dtstore folder for the vrelize Opertions Mnger VMs. d Bck on the Trget Loction pge, click Next. VMwre, Inc. 14

12 On the Repliction options pge, select only the Enle network compression for VR dt check ox, nd click Next. Importnt Do not enle guest OS quiescing ecuse some of the vrelize Opertions Mnger dtses do not support quiescing. Quiescing might result in cluster filure ecuse virtul disks remin in frozen stte for too long. Compression requires extr resources. Do not enle it if the hosts re over-utilized. 13 On the Recovery settings pge, enter the following settings nd click Next. Set the Recovery Point Ojective (RPO) to 15 minutes. Select Enle under Point in time instnces nd keep 3 instnces per dy for the lst 1 dys. VMwre, Inc. 15

14 On the Redy to complete pge, review the configurtion nd click Finish. 15 (Optionl) Monitor the repliction progress. c In the vsphere We Client, click Home > vsphere Repliction nd click the Home t. Select the mgmt01vc01.sfo01.rinpole.locl nd click Monitor to open the pge for repliction configurtion pge for this vcenter Server instnce. On the Monitor t, click the vsphere Repliction t nd select Outgoing Replictions. VMwre, Inc. 16

Crete Protection Group for vrelize Opertions Mnger After you configure repliction solution for the nlytics virtul mchines of vrelize Opertions Mnger, include the virtul mchines in protection group so tht Site Recovery Mnger protects them together. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, select Site Recovery. 3 On the Site Recovery home pge, click Sites nd select the mgmt01vc01.sfo01.rinpole.locl protected site. 4 If the Log In Site dilog ox ppers, re-uthenticte y using the svc-srm@rinpole.locl user nme nd the svc-srm_pssword pssword. Re-uthentiction is required if the network connection etween Region A nd Region B hs een interrupted fter the lst successful uthentiction. 5 On the Relted Ojects t, click the Protection Groups t nd click Crete Protection Group. The Crete Protection Group wizrd ppers. 6 On the Nme nd loction pge, configure the following settings nd click Next. Nme Description Site pir vrops-pg vrops Cluster Protection Group mgmt01vc01.sfo01.rinpole.locl - mgmt01vc51.lx01.rinpole.locl VMwre, Inc. 17

7 On the Protection group type pge, configure the following settings nd click Next. Direction of protection Protection group type mgmt01vc01.sfo01.rinpole.locl -> mgmt01vc51.lx01.rinpole.locl Individul VMs 8 On the Virtul mchines pge, select the nlytics virtul mchines from the list of mchines replicted y using vsphere Repliction nd click Next. vrops-mstrn-01 vrops-repln-02 vrops-dtn-03 VMwre, Inc. 18

9 On the Redy to complete pge, review the protection group settings nd click Finish. The vrops-pg protection group ppers in the list of protection groups for Site Recovery Mnger. Crete Recovery Pln for vrelize Opertions Mnger After you crete protection group for the virtul mchines of the vrelize Opertions Mnger nlytics cluster, crete recovery pln. You use this pln to run commnds on Site Recovery Mnger nd the nlytics virtul mchines, nd configure dependencies etween the virtul mchines. VMwre, Inc. 19

7 On the Protection group pge, select the protection group for the recovery pln nd click Next. Protection Group Option Group type Protection group VM protection groups vrops-pg 8 On the Test networks pge, leve the defult vlues nd click Next. The defult option is to utomticlly crete n isolted network. VMwre, Inc. 21

9 On the Redy to complete pge, click Finish. The vrops-rp recovery pln ppers in the list of the recovery plns ville in Site Recovery Mnger. Customize the Recovery Pln for vrelize Opertions Mnger After you crete the recovery pln for the vrelize Opertions Mnger filover, configure the strtup priority nd the strtup nd shutdown options for the virtul mchines of the nlytics cluster. VMwre, Inc. 22

5 Chnge the strtup priority of the virtul mchine of the mster node. On the recovery pln pge, click the Monitor t nd click the Recovery Steps t. Under Power on priority 3 VMs, right-click vrops-mstrn-01 nd select All Priority Actions > 1 > (Highest). c In the Chnge Priority dilog ox. click Yes to confirm. VMwre, Inc. 24

6 Configure strtup nd shutdown options for the mster node. c Right-click vrops-mstrn-01 nd select Configure Recovery. In the VM Recovery Properties dilog ox, expnd Shutdown Actions nd increse Shutdown guest OS efore power off to 10 minutes. Expnd Strtup Actions, increse the timeout to 10 minutes, nd click OK. 7 Repet Step 5 nd Step 6 for the other virtul mchines of the nlytics cluster. Virtul Mchine Strtup Priority Order Updte Timeout s vrops-repln-02 2 No vrops-dtn-03 3 Yes VMwre, Inc. 25

Duplicte the Anti-Affinity Rules for vrelize Opertions Mnger in Region B VM nti-ffinity rules re not retined during Site Recovery Mnger ssisted recovery. You must duplicte the nti-ffinity rules for the nlytics virtul mchines in Region B so tht the rules pply fter filover of vrelize Opertions Mnger. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 In the Nvigtor, click Hosts nd Clusters nd nvigte to the mgmt01vc51.lx01.rinpole.locl vcenter Server oject. 3 Under the LAX01 dt center oject, select the LAX01-Mgmt01 cluster. 4 On the Configure t, nd under Configurtion, select VM/Host Rules. 5 In the VM/Host Rules list, click Add to crete virtul mchine nti-ffinity rule. VMwre, Inc. 26

6 In the Crete VM/Host Rule dilog ox, dd new nti-ffinity rule for the virtul mchines of the mster nd mster replic nodes, nd click OK. Nme Enle Rule Type nti-ffinity-rule-vropsm Selected Seprte Virtul Mchines Memers vrops-mstrn-01 vrops-repln-02 vrops-dtn-03 Configure Filover of the Cloud Mngement Pltform Prepre vrelize Automtion, vrelize Orchestrtor, nd vrelize Business for filover. Replicte the virtul mchines of the primry vrelize Automtion components, vrelize Orchestrtor, nd of vrelize Business Server. Crete recovery pln for them in Site Recovery Mnger. Procedure 1 Replicte the Required VMs of vrelize Automtion, vrelize Orchestrtor, nd vrelize Business Enle repliction of the virtul mchines tht uild up the primry functionlity of the cloud mngement pltform to support filover to Region B. 2 Crete Protection Group for the Cloud Mngement Pltform After you configure repliction for the Cloud Mngement Pltform VMs, configure dedicted protection group so tht Site Recovery Mnger protects them together. 3 Crete Recovery Pln for the Cloud Mngement Pltform After you crete protection group for the cloud mngement pltform VMs, crete recovery pln. You use this pln toconfigure dependencies etween the virtul mchines. 4 Customize the Recovery Pln for the Cloud Mngement Pltform After you crete the recovery pln for the Cloud Mngement Pltform VMs, configure strtup priority. 5 Duplicte the Anti-Affinity Rules for vrelize Automtion nd vrelize Orchestrtor from Region A in Region B VM nti-ffinity rules re not retined during Site Recovery Mnger ssisted recovery. You must duplicte the configured nti-ffinity rules from Region A in Region B so tht the rules pply fter filover. Replicte the Required VMs of vrelize Automtion, vrelize Orchestrtor, nd vrelize Business Enle repliction of the virtul mchines tht uild up the primry functionlity of the cloud mngement pltform to support filover to Region B. VMwre, Inc. 27

Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 On the vsphere We Client Home pge, click VMs nd Templtes. 3 Nvigte to the vra01 VM folder. Oject vcenter Server Dt center Folder mgmt01vc01.sfo01.rinpole.locl SFO01 vra01 4 On the vra01 pge, click the VMs t, click Virtul Mchines, nd select the virtul mchines of vrelize Automtion, vrelize Orchestrtor, nd the vrelize Business Server. vrelize Automtion Component IS Mnger Service nd DEM Orchestrtor IS Mnger Service nd DEM Orchestrtor IS We Server IS We Server Microsoft SQL Server vrelize Applince vrelize Applince vrelize Automtion DEM Worker vrelize Automtion DEM Worker vrelize Orchestrtor Applince vrelize Orchestrtor Applince vrelize Business Applince VM Nme vr01ims01.rinpole.locl vr01ims01.rinpole.locl vr01iws01.rinpole.locl vr01iws01.rinpole.locl vr01mssql01.rinpole.locl vr01svr01.rinpole.locl vr01svr01.rinpole.locl vr01dem01.rinpole.locl vr01dem02.rinpole.locl vr01vro01.rinpole.locl vr01vro01.rinpole.locl vr01us01.rinpole.locl VMwre, Inc. 28

5 Right-click the VM selection, nd select All vsphere Repliction Actions > Configure Repliction. 6 Click Yes in the dilog ox out performing repliction for ll ojects. The Configure Repliction for 12 Virtul Mchines wizrd opens. 7 On the Vlidtion pge, wit until the process completes successfully nd click Next. 8 On the Repliction type pge, select Replicte to vcenter Server nd click Next. 9 On the Trget site pge, select the mgmt01vc51.lx01.rinpole.locl vcenter Server in Region B nd click Next. VMwre, Inc. 29

10 On the Repliction server pge, select Auto-ssign vsphere Repliction server nd click Next. If the environment contins severl replictions servers, selecting this option mkes use of ny of these repliction servers. 11 On the Trget loction pge, set the loction on the vsan dtstore in Region B to store replicted VM files. Click the Edit for ll link. In the Select Trget Loction dilog ox, select LAX01A-VSAN01-MGMT01 s dtstore for replicted files. VMwre, Inc. 30

c In the Select trget loction pne, select LAX01A-VSAN01-MGMT01 to select the root folder of the dtstore nd click OK. d On the Trget Loction pge, click Next. VMwre, Inc. 31

12 On the Repliction options pge, select only the Enle network compression for VR dt check ox nd click Next. Importnt Do not enle guest OS quiescing ecuse some of the vrelize Automtion nd vrelize Orchestrtor dtses do not support quiescing. Quiescing might result in cluster filure ecuse virtul disks remin in frozen stte for too long. Compression requires extr resources. Do not enle it if the hosts re over-utilized. VMwre, Inc. 32

13 On the Recovery settings pge, enter the following settings nd click Next. Set the Recovery Point Ojective (RPO) to 15 minutes. Select Enle under Point in time instnces nd keep 3 instnces per dy for the lst 1 dys. 14 On the Redy to complete pge, review the configurtion nd click Finish. Repliction configurtion for the virtul mchines from the cloud mngement pltform strts. VMwre, Inc. 33

15 (Optionl) Monitor the repliction progress. c From the Home menu, select vsphere Repliction nd click the Home t. Select the mgmt01vc01.sfo01.rinpole.locl nd click Monitor to open the repliction configurtion pge for this vcenter Server instnce On the Monitor t, click the vsphere Repliction t, nd select Outgoing Replictions. Crete Protection Group for the Cloud Mngement Pltform After you configure repliction for the Cloud Mngement Pltform VMs, configure dedicted protection group so tht Site Recovery Mnger protects them together. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, select Site Recovery. 3 On the Site Recovery home pge, click Sites nd select the mgmt01vc01.sfo01.rinpole.locl protected site. VMwre, Inc. 34

4 If the Log In Site dilog ox ppers, re-uthenticte y using the svc-srm@rinpole.locl user nme nd the svc-srm_pssword pssword. Re-uthentiction is required if the network connection etween Region A nd Region B hs een interrupted fter the lst successful uthentiction. 5 On the Relted Ojects t, click the Protection Groups t nd click Crete Protection Group. The Crete Protection Group wizrd ppers. 6 On the Nme nd loction pge, configure the following settings nd click Next. Nme Description Site pir vra-vro-vrb-pg vra-vro-vrb Cluster Protection Group mgmt01vc01.sfo01.rinpole.locl - mgmt01vc51.lx01.rinpole.locl 7 On the Protection group type pge, configure the following settings nd click Next. Direction of protection Protection group type mgmt01vc01.sfo01.rinpole.locl -> mgmt01vc51.lx01.rinpole.locl Individul VMs (vsphere Repliction) VMwre, Inc. 35

8 On the Virtul mchines pge, select the virtul mchines of vrelize Automtion, vrelize Orchestrtor nd the vrelize Business Server VM, from the list of replicted mchines nd click Next. VM Nme vr01ims01.rinpole.locl vr01ims01.rinpole.locl vr01iws01.rinpole.locl vr01iws01.rinpole.locl vr01mssql01.rinpole.locl vr01svr01.rinpole.locl vr01svr01.rinpole.locl vr01dem01.rinpole.locl vr01dem02.rinpole.locl vr01vro01.rinpole.locl vr01vro01.rinpole.locl vr01us01.rinpole.locl VMwre, Inc. 36

9 On the Redy to complete pge, review the protection group settings nd click Finish. The vra-vro-vrb-pg protection group ppers in the list of protection groups for Site Recovery Mnger. Crete Recovery Pln for the Cloud Mngement Pltform After you crete protection group for the cloud mngement pltform VMs, crete recovery pln. You use this pln toconfigure dependencies etween the virtul mchines. VMwre, Inc. 37

7 On the Protection groups pge, select the protection group for the recovery pln nd click Next. Protection Group Group type Protection group VM protection groups vra-vro-vrb-pg 8 On the Test networks pge, leve the defult vlues nd click Next. VMwre, Inc. 39

9 On the Redy to complete pge, click Finish. The vra-vro-vrb-rp recovery pln ppers in the list of the recovery plns ville in Site Recovery Mnger. Customize the Recovery Pln for the Cloud Mngement Pltform After you crete the recovery pln for the Cloud Mngement Pltform VMs, configure strtup priority. VMwre, Inc. 40

6 Chnge the priority of the vr01mssql01.rinpole.locl VM. Under Virtul Mchine, right-click vr01mssql01.rinpole.locl nd select All Priority Actions > 1 (Highest). In the Chnge Priority dilog ox, click Yes to confirm. 7 Repet the previous step to reconfigure the priorities of the following VMs. VM Nme Priority vr01vro01.rinpole.locl 2 vr01vro01.rinpole.locl 2 vr01svr01.rinpole.locl 2 vr01svr01.rinpole.locl 2 vr01iws01.rinpole.locl 3 vr01iws01.rinpole.locl 3 vr01ims01.rinpole.locl 4 vr01ims01.rinpole.locl 4 vr01dem01.rinpole.locl 5 vr01dem02.rinpole.locl 5 vr01us01.rinpole.locl 5 VMwre, Inc. 42

8 Configure the VM dependencies. c Right-click vr01svr01.rinpole.locl in the recovery pln nd select Configure Recovery. In the VM Recovery Properties dilog ox, expnd the VM Dependencies section nd click Configure. Select vr01vro01.rinpole.locl, click OK, nd click OK. 9 Repet the previous step to configure dditionl VM dependencies for the following VMs. VM Nme Priority VM Dependencies vr01svr01.rinpole.locl 2 Depends on vr01vro01.rinpole.locl vr01iws01.rinpole.locl 3 Depends on vr01iws01.rinpole.locl vr01ims01.rinpole.locl 4 Depends on vr01ims01.rinpole.locl VMwre, Inc. 43

10 Configure dditionl strtup dely for the second IS We Server instnce nd the IS Mnger Service. Right-click vr01iws01.rinpole.locl nd select Configure Recovery. In the VM Recovery Properties dilog ox, expnd the Strtup Action section nd under Additionl Dely, set Dely to 5 minutes, nd click OK. c Repet the step to configure dditionl dely of 5 minutes for the vr01ims01.rinpole.locl VM. Duplicte the Anti-Affinity Rules for vrelize Automtion nd vrelize Orchestrtor from Region A in Region B VM nti-ffinity rules re not retined during Site Recovery Mnger ssisted recovery. You must duplicte the configured nti-ffinity rules from Region A in Region B so tht the rules pply fter filover. Tle 3 1. Anti-Affinity Rules for the Cloud Mngement Pltform Nme Type Memers vr-svr Seprte Virtul Mchines vr01svr01.rinpole.locl, vr01svr01.rinpole.locl vr-dem Seprte Virtul Mchines vr01dem01.rinpole.locl, vr01dem02.rinpole.locl vr-ims Seprte Virtul Mchines vr01ims01.rinpole.locl, vr01ims01.rinpole.locl vr-iws Seprte Virtul Mchines vr01iws01.rinpole.locl, vr01iws01.rinpole.locl vr-vro Seprte Virtul Mchines vr01vro01.rinpole.locl, vr01vro01.rinpole.locl VMwre, Inc. 44

Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 In the Nvigtor, click Hosts nd Clusters. 3 Under mgmt01vc51.lx01.rinpole.locl, expnd LAX01 nd click LAX01-Mgmt01. 4 Click the Configure t, nd under Configurtion, select VM/Host Rules. 5 Under VM/Host Rules, click Add to crete virtul mchine nti-ffinity rule. 6 In the Crete VM/Host Rule dilog ox, dd the first rule for the vrelize Automtion virtul pplinces, click OK, nd click OK. Nme Enle rule Type Memers vr-svr Selected Seprte Virtul Mchines vr01svr01.rinpole.locl, vr01svr01.rinpole.locl VMwre, Inc. 45

7 Repet the procedure to configure the remining nti-ffinity rules. Test the Filover of Mngement Applictions Test the recovery pln for the mngement pplictions in the SDDC to eliminte potentil prolems during future filover. Test the Filover of vrelize Opertions Mnger Test the recovery pln for vrelize Opertions Mnger to eliminte potentil prolems during future filover. Site Recovery Mnger runs the nlytics virtul mchines on the test network nd on temporry snpshot of replicted dt in Region B. VMwre, Inc. 46

9 On the Redy to complete pge, click Finish to strt the test recovery. Test filover strts. You cn follow the progress on the Recovery Steps pge. 10 After the test recovery is complete, click the Clenup Recovery Pln icon to clen up ll the creted test VMs. VMwre, Inc. 48

11 On the Confirmtion options pge of the Clenup wizrd, click Next. 12 On the Redy to complete pge, click Finish to strt the clen-up process. Test the Filover of the Cloud Mngement Pltform Test the recovery pln for vrelize Automtion, vrelize Orchestrtor, nd vrelize Business to vlidte the configurtion. Site Recovery Mnger runs the virtul mchines on the test network nd on temporry snpshot of replicted dt in Region B. VMwre, Inc. 49

8 On the Confirmtion options pge, leve the Replicte recent chnges to recovery site check ox selected nd click Next. 9 On the Redy to complete pge, click Finish to strt the test recovery. Test filover strts. You cn follow the progress on the Recovery Steps pge. 10 After the test recovery is complete, click the Clenup Recovery Pln icon to clen up ll the creted test VMs. Note Becuse recovered VMs re using the Test network, VMwre Tools in vr01svr01.rinpole.locl nd vr01svr01.rinpole.locl VMs might not ecome online within the defult timeout vlue. Increse the timeout vlue for the VMs to complete the test. VMwre, Inc. 51

11 On the Confirmtion options pge of the Clenup wizrd, click Next. 12 On the Redy to complete pge, click Finish to strt the clen-up process. Perform Plnned Migrtion of Mngement Applictions After you hve successfully configured nd tested filover of the mngement pplictions, strt the migrtion process from Region A to Region B. Initite Plnned Migrtion of vrelize Opertions Mnger You cn run recovery pln under plnned circumstnces to migrte the virtul mchines of the nlytics cluster of vrelize Opertions Mnger from Region A to Region B. You cn lso run recovery pln under unplnned circumstnces if Region A suffers n unforeseen event tht might result in dt loss. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. VMwre, Inc. 52

3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc01.sfo01.rinpole.locl vcenter Server oject to open its site configurtion. 4 Click Recovery Plns nd click the vrops-rp recovery pln. 5 On the vrops-rp pge, click the Monitor t nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filover of the nlytics cluster. The Recovery wizrd ppers. 7 On the Confirmtion options pge, configure the following settings nd click Next. Confirmtion Option I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Plnned migrtion VMwre, Inc. 53

8 On the Redy to complete pge, click Finish to initite vrelize Opertions Mnger filover. Wht to do next Perform the steps required to verify the opertion of nd reprotect the system. Verify tht vrelize Opertions Mnger is up nd functions flwlessly fter filover. See Vlidte vrelize Opertions Mnger in the Opertionl Verifiction documenttion. Prepre vrelize Opertions Mnger for filck y reprotecting the virtul mchines of the nlytics cluster in Site Recovery Mnger. See Reprotect vrelize Opertions Mnger. Initite Plnned Migrtion of the Cloud Mngement Pltform You cn run recovery pln under plnned circumstnces to migrte the virtul mchines of vrelize Automtion, vrelize Orchestrtor nd vrelize Business from Region A to Region B. You cn lso run recovery pln under unplnned circumstnces if Region A suffers n unforeseen event tht might result in dt loss. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the vsphere We Home menu, select Site Recovery. VMwre, Inc. 54

3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc01.sfo01.rinpole.locl vcenter Server oject to open its site configurtion. 4 Click Recovery Plns nd click the vra-vro-vrb-rp recovery pln. 5 On the vra-vro-vrb-rp pge, click the Monitor t nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filover of the cloud mngement pltform. The Recovery wizrd ppers. 7 On the Confirmtion options pge, configure the following settings nd click Next. Confirmtion Option I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Plnned migrtion VMwre, Inc. 55

8 On the Redy to complete pge, click Finish to initite filover of the cloud mngement pltform. Wht to do next Perform the steps required to verify the opertion of nd reprotect the system. Verify tht vrelize Automtion, vrelize Orchestrtor nd vrelize Business VMs re up nd function flwlessly fter filover. See Vlidte the Cloud Mngement Pltform in the Opertionl Verifiction documenttion. Prepre vrelize Automtion, vrelize Orchestrtor nd vrelize Business Server for filck y reprotecting the virtul mchines of the vrelize Automtion components in Site Recovery Mnger. See Reprotect the Cloud Mngement Pltform. Perform Disster Recovery of Mngement Applictions Prepre networking in Region B nd perform filover of Relize Automtion, vrelize Orchestrtor, vrelize Business, nd vrelize Opertions Mnger to Region B if Region A ecomes unville in the event of disster or if you pln grceful migrtion. Reconfigure the NSX Instnce for the Mngement Cluster in Region B In the event of site filure, when Region A ecomes unville, prepre the network lyer in Region B for filover of mngement pplictions. Chnge the role of the NSX Mnger to primry, deploy universl controller cluster, nd synchronize the universl controller cluster configurtion. VMwre, Inc. 56

Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 Promote the NSX Mnger for the mngement cluster in Region B to the primry role. You must first disconnect the NSX Mnger for the mngement cluster in Region B from the Primry NSX Mnger in Region A. c d e From the Home menu, select Networking & Security. In the Nvigtor, click Instlltion. On the Mngement t, select the 172.17.11.65 instnce. Click the Actions menu nd click Disconnect from Primry NSX Mnger. In the Disconnect from Primry NSX Mnger confirmtion dilog ox, click Yes. The NSX Mnger gets the Trnsit role. f g h On the Mngement t, select the 172.17.11.65 instnce gin. From the Actions menu, select Assign Primry Role. In the Assign Primry Role confirmtion dilog ox, click Yes. 3 Configure n IP pool for the new universl controller cluster. c d In the Nvigtor, click NSX Mngers. Under NSX Mngers, click the 172.17.11.65 instnce. On the Mnge t, click Grouping Ojects, click IP Pools, nd click the Add New IP Pool icon. In the Add Sttic IP Pool dilog ox, enter the following settings, nd click OK. Nme Mgmt01-NSXC51 Gtewy 172.17.11.253 Prefix Length 24 Primry DNS 172.17.11.5 DNS Suffix lx01.rinpole.locl Sttic IP Pool 172.17.11.118-172.17.11.120 VMwre, Inc. 57

4 Deploy the universl controller cluster in Region B. c In the Nvigtor, click Networking & Security nd click Instlltion. Under NSX Controller nodes, click the Add icon to deploy three NSX Controller nodes with the sme configurtion. In the Add Controller dilog ox, enter the following settings nd click OK. You configure pssword only during the deployment of the first controller. The other controllers use the sme pssword. Nme nsx-controller-mgmt-51 NSX Mnger 172.17.11.65 Dtcenter Cluster/Resource Pool Dtstore Connected To IP Pool Pssword Confirm Pssword LAX01 LAX01-Mgmt01 LAX01A-VSAN01-MGMT01 vds-mgmt-mngement Mgmt01-NSXC51 mgmtnsx_controllers_pssword mgmtnsx_controllers_pssword d After the Sttus of the controller node chnges to Connected, deploy the remining two NSX Controller nodes. Wit until the current deployment is finished efore you strt the next one. 5 Configure DRS ffinity rules for the deployed NSX Controller nodes. c d From the Home menu of the vsphere We Client, select Hosts nd Clusters, nd expnd the mgmt01vc51.lx01.rinpole.locl tree. Select the LAX01-Mgmt01 cluster nd click the Configure t. Under Configurtion, click VM/Host Rules nd click Add under the VM/Host Rules section. In the LAX01-Mgmt01 - Crete VM/Host Rule dilog ox, enter the following settings nd click Add. Nme Enle rule Type Mgmt_NSX_Controllers Selected Seprte Virtul Mchines e In the Add Rule Memer dilog ox, select ll three NSX Controller virtul mchines, click OK, nd click OK. VMwre, Inc. 58

6 Use the updte controller stte mechnism on the NSX Mnger to synchronize the stte of the newly deployed controllers. c d e From the Home menu of the vsphere We Client, select Networking & Security. In the Nvigtor, click Instlltion. On the Mngement t, select the 172.17.11.65 instnce. From the Actions menu, select Updte Controller Stte. In the Updte Controller Stte confirmtion dilog ox, click Yes. Recover the Control VM of the Universl Distriuted Logicl Router in Region B Becuse of the filure of Region A, dynmic routing in Region B is not ville. Deploy Control VM for the universl dynmic logicl router UDLR01 in Region B to recover dynmic routing in the environment. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, click Networking & Security. 3 In the Nvigtor, click NSX Edges. 4 Select 172.17.11.65 from the NSX Mnger drop-down menu. 5 Doule-click UDLR01. 6 Re-deploy the universl distriuted logicl router control VM nd enle high vilility. c Click the Mnge t nd click s. Select Configurtion, nd under Logicl Router Applinces click the Add icon. In the Add NSX Edge Applince dilog ox, enter the following settings nd click OK. Dtcenter Cluster/Resource Pool Dtstore LAX01 LAX01-Mgmt01 LAX01A-VSAN01-MGMT01 d Click the Add icon to deploy nother NSX Edge device with the sme configurtion. VMwre, Inc. 59

7 Configure high vilility for the control VM. On the Configurtion pge for SFOMGMT-UDLR01, click Chnge under HA Configurtion, configure the following settings nd click OK. HA Sttus Connected To Enle Logging Enle vds-mgmt-mngement Selected In the Chnge HA configurtion confirmtion dilog ox, click Yes. 8 Configure the CLI credentils for the control VM. c d In the Nvigtor, click NSX Edges. Select 172.17.11.65 from the NSX Mnger drop-down menu. Right-click SFOMGMT-UDLR01 nd select Chnge CLI Credentils. In the Chnge CLI Credentils dilog ox, configure the following settings nd click OK. User Nme Pssword Enle SSH ccess dmin udlr_dmin_pssword Selected Reconfigure the Universl Distriuted Logicl Router nd NSX Edges for Dynmic Routing in Region B Configure the universl distriuted logicl router UDLR01 nd NSX Edges LAXMGMT-ESG01 nd LAXMGMT-ESG02 to use dynmic routing in Region B. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, select Networking & Security nd click NSX Edges in the Nvigtor. 3 Select 172.17.11.65 from the NSX Mnger drop-down menu. VMwre, Inc. 60

4 Verify the routing configurtion for the universl distriuted logicl router. c d Doule-click UDLR01. Click the Mnge t nd click Routing. Verify tht ECMP is Enled. Verify tht 192.168.10.3 (Uplink) is configured s the Router ID under Dynmic Routing Configurtion. 5 On the left side, select BGP to verify BGP configurtion. On the BGP pge, verify the following settings. Sttus Enled Locl AS 65003 Grceful Restrt Enled c Select 192.168.10.50 (LAXMGMT-ESG01) neighor nd click Edit icon. In the Edit Neighour dilog ox, updte the Weight vlue to 60, enter the BGP pssword tht ws configured during the initil setup of the UDLR nd click OK. LAXMGMT-ESG01 IP Address 192.168.10.50 Forwrding Address 192.168.10.3 Protocol Address 192.168.10.4 Remote AS 65003 Weight 60 Keep Alive Time 1 Hold Down Time 3 Pssword BGP_pssword VMwre, Inc. 61

d On the BGP pge, select 192.168.10.51 (LAXMGMT-ESG02) neighor, click Edit to chnge the following settings for the second ECMP NSX Edge, nd click OK. LAXMGMT-ESG02 IP Address 192.168.10.51 Forwrding Address 192.168.10.3 Protocol Address 192.168.10.4 Remote AS 65003 Weight 60 Keep Alive Time 1 Hold Down Time 3 Pssword BGP_pssword e Click Pulish Chnges. 6 On the left side, select Route Redistriution to verify redistriution sttus. Verify the following settings under Route Redistriution Sttus. OSPF BGP Deselected Selected Verify the following settings under Route Redistriution tle. Lerner From Perfix Action BGP Connected Any Permit 7 Reconfigure the routing nd weight vlue of LAXMGMT-ESG01 nd LAXMGMT-ESG02 edges. c d e f g h In the Nvigtor, click NSX Edges. Select 172.17.11.65 from the NSX Mnger drop-down menu. Doule-click LAXMGMT-ESG01. Click the Mnge t nd click Routing. On the left side, select BGP, select the 192.168.10.4 neighor under Neighors, nd click the Edit icon. In the Edit Neighour dilog ox, chnge Weight vlue to 60 nd click OK. Click Pulish Chnges. Repet the step for the LAXMGMT-ESG02 edge. VMwre, Inc. 62

Verify Estlishment of BGP for the Universl Distriuted Logicl Router in Region B Verify tht the UDLR for the mngement pplictions is successfully peering, nd tht BGP routing hs een estlished in Region B. Procedure 1 Log in to the UDLR virtul pplince yusing Secure Shell (SSH) client. Open n SSH connection to UDLR01. Log in using the following credentils. User nme Pssword dmin udlr_dmin_pssword 2 Verify tht the UDLR cn peer with the ECMP-enled NSX Edge services gtewys. Run the show ip gp neighors commnd to disply informtion out the BGP nd TCP connections to the UDLR neighors. In the commnd output, verify tht the BGP stte is Estlished, up for 192.168.10.50 (LAXMGMT-ESG01) nd 192.168.10.51 (LAXMGMT-ESG02). 3 Verify tht the UDLR receives routes y using BGP nd tht multiple routes re estlished to BGPlerned networks. Run the show ip route commnd In the commnd output, verify tht the routes to the networks re mrked with the letter B nd severl routes to ech djcent network exist. The letter B in front of ech route indictes tht the route is estlished over BGP. Enle Network Connectivity for the NSX Lod Blncer in Region B Enle the network connectivity of LAXMGMT-LB01 lod lncer. VMwre, Inc. 63

Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, select Networking & Security. 3 In the Nvigtor, click NSX Edges. 4 Select 172.17.11.65 from the NSX Mnger drop-down menu. 5 Doule-click the LAXMGMT-LB01 device. 6 Click the Mnge t nd click the s t. 7 Click Interfces, select the OneArmLB vnic, nd click Edit. 8 In the Edit NSX Edge Interfce dilog ox, set Connectivity Sttus to Connected nd click OK. Initite Disster Recovery of vrelize Opertions Mnger in Region B If disster event occurs in Region A, initite the Disster Recovery of vrelize Opertions Mnger to fil over it to Region B. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. 3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc51.lx01.rinpole.locl vcenter Server oject to open its site configurtion. 4 Click Recovery Plns nd click the vrops-rp recovery pln. 5 On the vrops-rp pge, click the Monitor t nd click Recovery Steps. VMwre, Inc. 64

6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filover of the nlytics cluster. The Recovery wizrd ppers. 7 On the Confirmtion options pge of the Recovery wizrd, configure the following settings nd click Next. I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Disster recovery 8 On the Redy to complete pge, click Finish to initite vrelize Opertions Mnger filover. Site Recovery Mnger runs the recovery pln. After disster recovery, the Pln sttus of the recovery pln chnges to Disster recovery complete. Wht to do next Verify the opertion of nd reprotect the system. 1 Verify tht vrelize Opertions Mnger is up nd functions flwlessly fter filover. See Vlidte vrelize Opertions Mnger in the Opertionl Verifiction documenttion. 2 Prepre vrelize Opertions Mnger for filck y reprotecting the virtul mchines of the nlytics cluster in Site Recovery Mnger.See Reprotect vrelize Opertions Mnger. Initite Disster Recovery of the Cloud Mngement Pltform in Region B In the event of disster in Region A, initite the Disster Recovery of vrelize Automtion, vrelize Orchestrtor nd vrelize Business components to fil over them to Region B. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. 3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc51.lx01.rinpole.locl vcenter Server oject to open its site configurtion. VMwre, Inc. 65

4 Click Recovery Plns nd click the vra-vro-vrb-rp recovery pln. 5 On the vra-vro-vrb-rp pge, click the Monitor t, nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filover of the cloud mngement pltform. 7 On the Confirmtion options pge of the Recovery wizrd, configure the following settings nd click Next. Confirmtion Option I understnd tht this process will permnently lter the virtul mchinesnd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Disster recovery 8 On the Redy to complete pge, click Finish to initite the filover of the cloud mngement pltform. Site Recovery Mnger runs the recovery pln. After disster recovery, the Pln sttus of the recovery pln chnges to Disster recovery complete. Wht to do next Perform the steps required to verify the opertion of nd reprotect the system. 1 Verify tht vrelize Automtion, vrelize Orchestrtor nd vrelize Business VMs re up nd function flwlessly fter filover. See Vlidte the Cloud Mngement Pltform in the Opertionl Verifiction documenttion. 2 Prepre vrelize Automtion, vrelize Orchestrtor nd vrelize Business for filck y reprotecting the virtul mchines of the cloud mngement pltform in Site Recovery Mnger. See Reprotect the Cloud Mngement Pltform. Post-Filover Configurtion of Mngement Applictions After filover of the cloud mngement pltform nd vrelize Opertions Mnger, you must perform certin tsks to ensure tht pplictions perform s expected. Procedure 1 Configure the NSX Controllers nd the UDLR Control VM to Forwrd Events to vrelize Log Insight in Region B Configure the NSX Controllers nd UDLR Control VM instnces for the mngement cluster to forwrd log informtion to vrelize Log Insight in Region B. Use the NSX REST API to configure the NSX Controllers. You cn use REST client, such s the RESTClient dd-on for Firefox, to enle log forwrding. 2 Updte the vrelize Log Insight Logging Address fter Filover After you fil over the mngement pplictions in the SDDC to Region B, updte the ddress configured on the mngement pplictions for vrelize Log Insight. All mngement pplictions re still configured to send logs to the vrelize Log Insight instnce in Region A. VMwre, Inc. 66

3 Reconfigure the NSX Instnce for the Mngement Cluster in Region A fter Filover After Region A comes ck online, you must perform dditionl configurtion of the networking lyer to void conflicts. Configure the NSX Controllers nd the UDLR Control VM to Forwrd Events to vrelize Log Insight in Region B Configure the NSX Controllers nd UDLR Control VM instnces for the mngement cluster to forwrd log informtion to vrelize Log Insight in Region B. Use the NSX REST API to configure the NSX Controllers. You cn use REST client, such s the RESTClient dd-on for Firefox, to enle log forwrding. Prerequisites On Windows host tht hs ccess to your dt center, instll REST client, such s the RESTClient dd-on for Firefox. Procedure 1 Log in to the Windows host tht hs ccess to your dt center. 2 In Firefox rowser, go to chrome://restclient/content/restclient.html. 3 Specify the request heders for requests to the NSX Mnger. From the Authentiction drop-down menu, select Bsic Authentiction. In the Bsic Authoriztion dilog ox, enter the following credentils, select Rememer me nd click Oky. Authentiction Attriute Usernme Pssword dmin mngnsx_dmin_pssword The Authoriztion:Bsic XXX heder ppers in the Heders pne. c d From the Heders drop-down menu, select Custom Heder. In the Request Heder dilog ox, enter the following heder detils nd click Oky. Request Heder Attriute Nme Content-Type ppliction/xml The Content-Type:ppliction/xml heder ppers in the Heders pne. VMwre, Inc. 67

4 Contct the NSX Mnger to retrieve the IDs of the ssocited NSX Controllers. In the Request pne, from the Method drop-down menu, select GET. In the URL text ox, enter https://mgmt01nsxm51.lx01.rinpole.locl/pi/2.0/vdn/controller nd click Send. The RESTClient sends query to the NSX Mnger out the instlled NSX controllers. c After the NSX Mnger sends response ck, click the Response Body (Preview) t under Response. The response ody contins root <controllers> XML element, which groups the detils out the three controllers tht form the controller cluster. d Within the <controllers> element, locte the <controller> element for ech controller nd write down the content of the <id> element. Controller IDs hve the controller-id formt where id represents the sequence numer of the controller in the cluster, for exmple, controller-2. VMwre, Inc. 68

6 Verify the syslog configurtion on ech NSX Controller. In the Request pne, from the Method drop-down menu, select GET, nd in the URL text ox, enter the controller-specific syslog URL from Step 5, nd click the SEND utton. After the NSX Mnger returns response, click the Response Body (Preview) t under Response. The response ody contins root <controllersyslogserver> element, which represents the settings for the remote syslog server on the NSX Controller. c d Verify tht the vlue of the <syslogserver> element is vrlicluster-51.lx01.rinpole.locl. Repet the steps for the next NSX Controller. 7 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword VMwre, Inc. 70

8 Configure the newly deployed UDLR control VM to forwrd events to vrelize Log Insight in Region B. c d e f g h From the Home menu of the vsphere We Client, click Networking & Security. In the Nvigtor, click NSX Edges. Select 172.17.11.65 from the NSX Mnger drop-down menu. Doule-click UDLR01. On the NSX Edge device pge, click the Mnge t, click s, nd click Configurtion. In the Detils pne, click Chnge next to Syslog servers. In the Edit Syslog Servers Configurtion dilog ox, in the Syslog Server 1 text ox, enter 192.168.32.10 nd from the Protocol drop-down menu, select udp. Click OK. Updte the vrelize Log Insight Logging Address fter Filover After you fil over the mngement pplictions in the SDDC to Region B, updte the ddress configured on the mngement pplictions for vrelize Log Insight. All mngement pplictions re still configured to send logs to the vrelize Log Insight instnce in Region A. You updte the DNS entry for dc51rpl.rinpole.locl to point to the IP ddress 192.168.32.10 of vrlicluster-51.lx01.rinpole.locl in Region B. Procedure 1 Log in to the DNS server dc51rpl.rinpole.locl tht resides iin Region B. 2 Open the Windows Strt menu, enter dns in the Serch text ox nd press Enter. The DNS Mnger dilog ox ppers. 3 In the DNS Mnger dilog ox, under Forwrd Lookup Zones, select the sfo01.rinpole.locl domin y expnding the tree nd locte the vrli-cluster-01 record on the right side. 4 Doule-click the vrli-cluster-01 record, chnge the IP ddress of the record from 192.168.31.10 to 192.168.32.10 nd click OK. Fully qulified domin nme (FQDN) vrli-cluster-01.sfo01.rinpole.locl IP Address 192.168.32.10 Updte ssocited pointer (PTR) record Selected VMwre, Inc. 71

Reconfigure the NSX Instnce for the Mngement Cluster in Region A fter Filover After Region A comes ck online, you must perform dditionl configurtion of the networking lyer to void conflicts. You demote the NSX Mnger to the secondry role, delete the universl controller cluster, disle the lod lncer, nd perform dditionl configurtion on the NSX Edges. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, select Networking & Security. 3 In the Nvigtor, click Instlltion nd click the Mngement t. You see tht oth NSX Mngers 172.16.11.65 nd 172.17.11.65 re ssigned the primry role. 4 Force the removl of the registered secondry NSX Mnger efore removing the primry role. Select the 172.16.11.65 instnce, nd select Actions > Remove Secondry NSX Mnger. Select the Perform opertion even if the NSX mnge is inccessile check ox nd click OK. VMwre, Inc. 72

5 Demote the originl primry site NSX Mnger to the trnsit role. Select the 172.16.11.65 instnce, click Actions > Remove Primry Role. Click Yes in the confirmtion dilog ox. 6 Delete the NSX controllers in the primry site. c d Select the nsx-controller-mgmt-01 node nd click Delete. In the Delete Controller confirmtion dilog ox, click Yes. Repet the step to delete the remining two NSX Controller nodes. Select Forcefully remove the controller when you delete the lst controller. 7 Delete the UDLR01 edge in the protected site. c d In the Nvigtor, click NSX Edges. Select 172.16.11.65 from the NSX Mnger drop-down menu. Select the UDLR01 nd click Delete. In the Delete NSX Edge confirmtion dilog ox, click Yes. 8 Assign the Region A mngement cluster NSX Mnger the secondry role to the lredy promoted primry NSX Mnger in Region B. c d In the Nvigtor, click Instlltion. On the Mngement t select the primry 172.17.11.65 instnce. Select Actions > Add Secondry NSX Mnger. In the Add secondry NSX Mnger dilog ox, enter the following settings nd click OK. NSX Mnger 172.16.11.65 User Nme Pssword Confirm Pssword dmin mgmtnsx_dmin_pssword mgmtnsx_dmin_pssword e In the Trust Certificte confirmtion dilog ox, click Yes. 9 Disle network connectivity for the NSX lod lncer in Region A. c d In the Nvigtor, click NSX Edges. Select 172.16.11.65 from the NSX Mnger drop-down menu. Doule-click the SFOMGMT-LB01 device. Click the Mnge t nd click the s t. VMwre, Inc. 73

e f Click Interfces, select the OneArmLB vnic, nd click Edit. In the Edit NSX Edge Interfce dilog ox, select Disconnected s Connectivity Sttus nd click OK. 10 Configure the routing on the universl distriuted logicl router in Region B. c d e f In the Nvigtor, click NSX Edges. Select 172.17.11.65 from the NSX Mnger drop-down menu. Doule-click UDLR01. Click the Mnge t nd click Routing. On the left, select BGP. Select the following NSX Edge devices, click Edit, configure the following settings, nd click OK. SFOMGMT-ESG01 SFOMGMT-ESG02 IP Address 192.168.10.1 192.168.10.2 Forwrding Address 192.168.10.3 192.168.10.3 Protocol Address 192.168.10.4 192.168.10.4 Remote AS 65003 65003 Weight 10 10 Keep Alive Time 1 1 Hold Down Time 3 3 Pssword BGP_pssword BGP_pssword g h i j Click Pulish Chnges. On the left, select Sttic Routes. On the Sttic Routes pge, click the existing sttic route (Network: 172.17.11.0/24) nd click Edit utton. In the Edit Sttic Route dilog ox, updte the following vlues nd click OK. Network 172.16.11.0/24 Next Hop 192.168.10.1,192.168.10.2 MTU 9000 Admin Distnce 1 k Click Pulish Chnges. 11 Reconfigure the weight vlue of SFOMGMT-ESG01 nd SFOMGMT-ESG02 edges. In the Nvigtor, click NSX Edges. Select 172.16.11.65 from the NSX Mnger drop-down menu. VMwre, Inc. 74

c d e f g h Doule-click SFOMGMT-ESG01. Click the Mnge t nd click Routing. On the left, select BGP, select the 192.168.10.4 neighour nd click Edit. In the Edit Neighour dilog ox, chnge the Weight vlue to 10 nd click OK. Click Pulish Chnges. Repet the step for the SFOMGMT-ESG02 edge. 12 Verify tht the NSX Edge devices re successfully peering, nd tht BGP routing hs een estlished. Log in to the SFOMGMT-ESG01 NSX Edge device using Secure Shell (SSH) client with the following credentils. User nme Pssword dmin edge_dmin_pssword Run the show ip gp neighors commnd to disply informtion out the BGP connections to neighors. The BGP Stte will disply Estlished UP if you hve successfully peered with UDLR01. c d Run the show ip route commnd to verify tht you re receiving routes using BGP. Repet the step for the SFOMGMT-ESG02 NSX Edge device. VMwre, Inc. 75

Filck of the SDDC 4 Mngement Applictions Configure nd perform filck of the mngement pplictions in the SDDC from the protected region, Region B, to the recovery region, Region A. You filck the following mngement components: Anlytics cluster of vrelize Opertions Mnger Primry components of vrelize Automtion, vrelize Orchestrtor, nd vrelize Business The remote collector nodes of vrelize Opertions Mnger re not filed ck. You deploy seprte pir of remote collectors in ech region in n ppliction isolted network. The vsphere Proxy Agents of vrelize Automtion nd the vrelize Business dt collector re not filed ck. You deploy seprte pir of gents nd collector in ech region in n ppliction isolted network. Procedure 1 Test the Filck of Mngement Applictions Test the recovery pln for the mngement pplictions in the SDDC to eliminte potentil prolems during future filck. 2 Perform Filck s Plnned Migrtion of Mngement Applictions After you hve successfully tested filck of the mngement pplictions, strt the migrtion process from Region B ck to Region A. 3 Perform Filck s Disster Recovery of Mngement Applictions Prepre networking in Region A nd perform filck of vrelize Automtion, vrelize Orchestrtor, vrelize Business, nd vrelize Opertions Mnger to Region A if Region B ecomes unville in the event of disster or if you pln grceful migrtion. 4 Post-Filck Configurtion of Mngement Applictions After filck of the cloud mngement pltform nd vrelize Opertions Mnger, you must perform certin tsks to ensure tht pplictions perform s expected. Test the Filck of Mngement Applictions Test the recovery pln for the mngement pplictions in the SDDC to eliminte potentil prolems during future filck. VMwre, Inc. 76

Test the Filck of vrelize Opertions Mnger Test the recovery pln for vrelize Opertions Mnger to prevent potentil prolems during future filck. Site Recovery Mnger runs the nlytics virtul mchines on the test network nd on temporry snpshot of replicted dt in Region A. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. 3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc51.lx01.rinpole.locl protected site. 4 If the Log In Site dilog ox ppers, re-uthenticte y using the dministrtor@vsphere.locl user nme nd the vsphere_dmin_pssword pssword. Re-uthentiction is required if the network connection etween Region A nd Region B hs een interrupted fter the lst successful uthentiction. 5 Click Recovery Plns nd click the vrops-rp recovery pln. 6 On the vrops-rp pge, click the Monitor t nd click Recovery Steps. 7 Click the Test Recovery Pln icon to run test recovery. VMwre, Inc. 77

The Test wizrd ppers. 8 On the Confirmtion options pge, leve the Replicte recent chnges to recover site check ox selected nd click Next. 9 On the Redy to complete pge, click Finish to strt the test recovery. VMwre, Inc. 78

Test filck strts. You cn follow the progress on the Recovery Steps pge. 10 After the test recovery is complete, click the Clenup Recovery Pln icon to clen up ll the creted test VMs. 11 On the Confirmtion options pge of the Clenup wizrd, click Next. 12 On the Redy to complete pge, click Finish to strt the clen-up process. VMwre, Inc. 79

Test the Filck of the Cloud Mngement Pltform Test the recovery pln for vrelize Automtion, vrelize Orchestrtor nd vrelize Business to vlidte the configurtion. Site Recovery Mnger runs the virtul mchines on the test network nd on temporry snpshot of replicted dt in Region A. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery 3 On the Site Recovery Home pge, click Sites nd select the mgmt01vc51.lx01.rinpole.locl protected site. 4 If the Log In Site dilog ox ppers, re-uthenticte y using the dministrtor@vsphere.locl user nme nd the vsphere_dmin_pssword pssword. Re-uthentiction is required if the network connection etween Region A nd Region B hs een interrupted fter the lst successful uthentiction. VMwre, Inc. 80

5 Click Recovery Plns nd click the vra-vro-vrb-rp recovery pln. 6 On the vra-vro-vrb-rp pge, click the Monitor t nd click Recovery Steps. 7 Click the Test Recovery Pln icon to run test recovery. The Test wizrd ppers. 8 In the Confirmtion options pge of the Test wizrd, leve the Replicte recent chnges to recover site check ox selected nd click Next. 9 On the Redy to complete pge, click Finish to strt the test recovery. VMwre, Inc. 81

Test filck strts. You cn follow the progress on the Recovery Steps pge. 10 After the test recovery is complete, click the Clenup Recovery Pln icon to clen up ll the creted test VMs. Note Becuse the recovered VMs re using the Test network, VMwre Tools in vr01svr01.rinpole.locl nd vr01svr01.rinpole.locl VMs might not ecome online within the defult timeout vlue. Increse the timeout vlue for the VMs to complete the test. VMwre, Inc. 82

11 On the Confirmtion options pge of the Clenup wizrd, click Next. 12 On the Redy to complete pge, click Finish to strt the clen-up process. Perform Filck s Plnned Migrtion of Mngement Applictions After you hve successfully tested filck of the mngement pplictions, strt the migrtion process from Region B ck to Region A. Initite Filck s Plnned Migrtion of vrelize Opertions Mnger You cn run recovery pln under plnned circumstnces to migrte the virtul mchines of the nlytics cluster of vrelize Opertions Mnger from Region B to Region A. You cn lso run recovery pln under unplnned circumstnces if Region B suffers n unforeseen event tht might result in dt loss. VMwre, Inc. 83

Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. 3 On the Site Recovery Home pge, click Sites nd click the mgmt01vc01.sfo01.rinpole.locl vcenter Server oject to open its configurtion in Site Recovery Mnger. 4 Click Recovery Plns nd click the vrops-rp recovery pln. 5 On the vrops-rp pge, click the Monitor t nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filck of the nlytics cluster. The Recovery wizrd ppers. 7 On the Confirmtion options pge, configure the following settings nd click Next. Confirmtion Option I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Plnned Migrtion VMwre, Inc. 84

8 On the Redy to complete pge, click Finish to initite vrelize Opertions Mnger filck. 9 Perform the steps required to verify the opertion of nd reprotect the system. Verify tht vrelize Opertions Mnger is up nd functions flwlessly fter filck. See Vlidte vrelize Opertions Mnger in the Opertionl Verifiction documenttion. Prepre vrelize Opertions Mnger for filover y reprotecting the virtul mchines of the nlytics cluster in Site Recovery Mnger. See Reprotect vrelize Opertions Mnger in the Reprotect of the SDDC Mngement Applictions documenttion. VMwre, Inc. 85

Initite Filck s Plnned Migrtion of the Cloud Mngement Pltform You cn run recovery pln under plnned circumstnces to migrte the virtul mchines of vrelize Automtion, vrelize Orchestrtor nd vrelize Business from Region B to Region A. You cn lso run recovery pln under unplnned circumstnces if Region B suffers n unforeseen event tht might result in dt loss. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc51.lx01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the vsphere We Client Home menu, click Site Recovery. 3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc51.lx01.rinpole.locl vcenter Server oject to open its site configurtion. 4 Click Recovery Plns nd click the vra-vro-vrb-rp recovery pln. 5 On the vra-vro-vrb-rp pge, click the Monitor t nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filck of the cloud mngement pltform. VMwre, Inc. 86

The Recovery wizrd ppers. 7 On the Confirmtion options pge, configure the following settings nd click Next. Confirmtion Option I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Plnned Migrtion 8 On the Redy to complete pge, click Finish to initite filck of the cloud mngement pltform. VMwre, Inc. 87

9 Perform the steps required to verify the opertion of nd reprotect the system. Verify tht vrelize Automtion, vrelize Orchestrtor nd vrelize Business VMs re up nd function flwlessly fter filck. See Vlidte vrelize Automtion in the Opertionl Verifiction document. Prepre vrelize Automtion, vrelize Orchestrtor nd vrelize Business Server for filover y reprotecting the virtul mchines of the vrelize Automtion components in Site Recovery Mnger. See Reprotect the Cloud Mngement Pltform in the Reprotect of the SDDC Mngement Applictions documenttion. Perform Filck s Disster Recovery of Mngement Applictions Prepre networking in Region A nd perform filck of vrelize Automtion, vrelize Orchestrtor, vrelize Business, nd vrelize Opertions Mnger to Region A if Region B ecomes unville in the event of disster or if you pln grceful migrtion. Procedure 1 Reconfigure the NSX Instnce for the Mngement Cluster in Region A In the event of site filure, when Region B ecomes unville, prepre the network lyer in Region A for filck of mngement pplictions. 2 Recover the Control VM of the Universl Distriuted Logicl Router in Region A Becuse of the filure of Region B, dynmic routing in Region A is not ville. Deploy Control VM for the universl dynmic logicl router UDLR01 in Region A to recover dynmic routing in the environment. 3 Reconfigure the Universl Distriuted Logicl Router nd NSX Edges for Dynmic Routing in Region A Configure the universl distriuted logicl router UDLR01, nd NSX Edges SFOMGMT-ESG01 nd SFOMGMT-ESG02 to use dynmic routing in Region A. 4 Verify the Estlishment of BGP for the Universl Distriuted Logicl Router in Region A Verify tht the UDLR for the mngement pplictions is successfully peering, nd tht BGP routing hs een estlished in Region A. 5 Enle Network Connectivity for the NSX Lod Blncer in Region A Enle the network connectivity on SFOMGMT-LB01 lod lncer. 6 Initite Disster Recovery of vrelize Opertions Mnger in Region A If disster event occurs in Region B, initite the Disster Recovery of vrelize Opertions Mnger in Region A to fil ck vrelize Opertions Mnger to Region A. VMwre, Inc. 88

7 Initite Disster Recovery of the Cloud Mngement Pltform in Region A In the event of disster in Region B, initite the Disster Recovery of vrelize Automtion, vrelize Orchestrtor nd vrelize Business in Region A to fil ck the cloud mngement pltform to Region A. Reconfigure the NSX Instnce for the Mngement Cluster in Region A In the event of site filure, when Region B ecomes unville, prepre the network lyer in Region A for filck of mngement pplictions. Chnge the role of the NSX Mnger to primry, deploy universl controller cluster, nd synchronize the universl controller cluster configurtion. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 Promote the NSX Mnger for the mngement cluster in Region A to the primry role. You must first disconnect the NSX Mnger for the mngement cluster in Region A from the Primry NSX Mnger in Region B. c d e From the Home menu of the vsphere We Client, click Networking & Security. In the Nvigtor, click Instlltion. On the Mngement t, select the 172.16.11.65 instnce. Click the Actions menu nd click Disconnect from Primry NSX Mnger. In the Disconnect from Primry NSX Mnger confirmtion dilog ox, click Yes. The NSX Mnger gets the Trnsit role. f g h On the Mngement t, select the 172.16.11.65 instnce gin. Click Actions nd select Assign Primry Role. In the Assign Primry Role confirmtion dilog ox, click Yes. VMwre, Inc. 89

3 Deploy the universl controller cluster in Region A. c In the Nvigtor, click Networking & Security, nd click Instlltion. Under NSX Controller nodes, click the Add icon to deploy three NSX Controller nodes with the sme configurtion. In the Add Controller dilog ox, enter the following settings nd click OK. You configure pssword only during the deployment of the first controller. The other controllers use the sme pssword. Nme nsx-controller-mgmt-01 NSX Mnger 172.16.11.65 Dtcenter Cluster/Resource Pool Dtstore Connected To IP Pool Pssword Confirm Pssword SFO01 SFO01-Mgmt01 SFO01A-VSAN01-MGMT01 vds-mgmt-mngement Mgmt01-NSXC01 mgmtnsx_controllers_pssword mgmtnsx_controllers_pssword d After the sttus of the controller node chnges to Connected, deploy the remining two NSX Controller nodes. Wit until the current deployment is finished, efore you strt the next one. 4 Configure DRS ffinity rules for the deployed NSX Controller nodes. c d From the Home menu of the vsphere We Client, select Hosts nd Clusters nd expnd the mgmt01vc01.sfo01.rinpole.locl tree.. Select the SFO01-Mgmt01 cluster nd click the Configure t. Under Configurtion, click VM/Host Rules nd click Add under the VM/Host Rules section. In the SFO01-Mgmt01 - Crete VM/Host Rule dilog ox, enter the following settings nd click Add. Nme Enle rule Type Mgmt_NSX_Controllers Selected Seprte Virtul Mchines e In the Add Rule Memer dilog ox, select ll three NSX Controller virtul mchines, click OK, nd click OK. VMwre, Inc. 90

5 Use the updte controller stte mechnism on the NSX Mnger to synchronize the stte of the newly deployed controllers. c d e From the Home menu, select Networking & Security. In the Nvigtor, click Instlltion. On the Mngement t, select the 172.16.11.65 instnce. Click the Actions menu nd select Updte Controller Stte. In the Updte Controller Stte confirmtion dilog ox, click Yes. Recover the Control VM of the Universl Distriuted Logicl Router in Region A Becuse of the filure of Region B, dynmic routing in Region A is not ville. Deploy Control VM for the universl dynmic logicl router UDLR01 in Region A to recover dynmic routing in the environment. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, click Networking & Security. 3 In the Nvigtor, click NSX Edges. 4 Select 172.16.11.65 from the NSX Mnger drop-down menu. 5 Doule-click UDLR01. 6 Re-deploy the universl distriuted logicl router control VM nd enle HA. c Click the Mnge t nd click s. Select Configurtion nd under Logicl Router Applinces click the Add icon. In the Add NSX Edge Applince dilog ox, enter the following settings nd click OK. Dtcenter Cluster/Resource Pool Dtstore SFO01 SFO01-Mgmt01 SFO01A-VSAN01-MGMT01 d Click the Add icon to deploy nother NSX Edge device with the sme configurtion. VMwre, Inc. 91

7 Configure high vilility for the control VM. On the Configurtion pge for UDLR01, click Chnge under HA Configurtion, configure the following settings nd click OK. HA Sttus Connected To Enle Logging Enle vds-mgmt-mngement Selected In the Chnge HA confirmtion dilog ox, click Yes. 8 Configure the CLI Credentils for the control VM. c d In the Nvigtor, click NSX Edges. Select 172.16.11.65 from the NSX Mnger drop-down menu. Right-click UDLR01 nd select Chnge CLI Credentils. In the Chnge CLI Credentils dilog ox, configure the following settings nd click OK. User Nme Pssword Enle SSH ccess dmin udlr_dmin_pssword Selected Reconfigure the Universl Distriuted Logicl Router nd NSX Edges for Dynmic Routing in Region A Configure the universl distriuted logicl router UDLR01, nd NSX Edges SFOMGMT-ESG01 nd SFOMGMT-ESG02 to use dynmic routing in Region A. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 In the Nvigtor, click Networking & Security nd click NSX Edges. 3 Select 172.16.11.65 from the NSX Mnger drop-down menu. VMwre, Inc. 92

4 Verify the routing configurtion for the universl distriuted logicl router. c d Doule-click UDLR01. Click the Mnge t nd click Routing. Verify tht ECMP is Enled. Verify tht 192.168.10.3 (Uplink) is configured s the Router ID under Dynmic Routing Configurtion. 5 On the left side, select BGP to verify the BGP configurtion. On the BGP pge, verify the following settings. Sttus Enled Locl AS 65003 Grceful Restrt Enled c Select the 192.168.10.1 (SFOMGMT-ESG01) neighor nd click Edit icon. In the Edit Neighour dilog ox, updte the Weight vlue to 60, enter the BGP pssword tht ws configured during the initil setup of the UDLR, nd click OK. SFOMGMT-ESG01 IP Address 192.168.10.1 Forwrding Address 192.168.10.3 Protocol Address 192.168.10.4 Remote AS 65003 Weight 60 Keep Alive Time 1 Hold Down Time 3 Pssword BGP_pssword d Select the 192.168.10.2 (SFOMGMT-ESG02) neighor nd click Edit icon. VMwre, Inc. 93

e In the Edit Neighour dilog ox, updte the Weight vlue to 60, enter the BGP pssword tht ws configured during the initil setup of the UDLR, nd click OK. SFOMGMT-ESG02 IP Address 192.168.10.2 Forwrding Address 192.168.10.3 Protocol Address 192.168.10.4 Remote AS 65003 Weight 60 Keep Alive Time 1 Hold Down Time 3 Pssword BGP_pssword f Click Pulish Chnges. 6 On the left side, select Route Redistriution to verify redistriution sttus. Verify the following settings under Route Redistriution Sttus. OSPF BGP Deselected Selected Verify the following settings under Route Redistriution tle. Lerner From Perfix Action BGP Connected Any Permit 7 Reconfigure the routing nd weight vlue of SFOMGMT-ESG01 nd SFOMGMT-ESG02 edges. c d e f g h In the Nvigtor, click NSX Edges. Select 172.16.11.65 from the NSX Mnger drop-down menu. Doule-click SFOMGMT-ESG01. Click the Mnge t nd click Routing. On the left, select BGP, select the 192.168.10.4 neighor, nd click Edit. In the Edit Neighour dilog ox, chnge Weight vlue to 60 nd click OK. Click Pulish Chnges. Repet the step for the SFOMGMT-ESG02 edge. VMwre, Inc. 94

Verify the Estlishment of BGP for the Universl Distriuted Logicl Router in Region A Verify tht the UDLR for the mngement pplictions is successfully peering, nd tht BGP routing hs een estlished in Region A. Procedure 1 Log in to the UDLR virtul pplince y using Secure Shell (SSH) client. Open n SSH connection to UDLR01. Log in using the following credentils. User nme Pssword dmin udlr_dmin_pssword VMwre, Inc. 95

2 Verify tht the UDLR cn peer with the ECMP-enled NSX Edge services gtewys. Run the show ip gp neighors commnd to disply informtion out the BGP nd TCP connections to the UDLR neighors. In the commnd output, verify tht the BGP stte is Estlished, up for 192.168.10.1 (SFOMGMT-ESG01) nd 192.168.10.2 (SFOMGMT-ESG02). VMwre, Inc. 96

3 Verify tht the UDLR receives routes y using BGP nd tht multiple routes re estlished to BGPlerned networks. Run the show ip route commnd In the commnd output, verify tht the routes to the networks re mrked with the letter B nd severl routes to ech djcent network exist. The letter B in front of ech route indictes tht the route is estlished over BGP. VMwre, Inc. 97

Enle Network Connectivity for the NSX Lod Blncer in Region A Enle the network connectivity on SFOMGMT-LB01 lod lncer. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu of the vsphere We Client, click Networking & Security. 3 In the Nvigtor, click NSX Edges. 4 Select 172.16.11.65 from the NSX Mnger drop-down menu. 5 Doule-click the SFOMGMT-LB01 device. 6 Click the Mnge t nd click the s t. 7 Click Interfces, select the OneArmLB vnic, nd click Edit. 8 In the Edit NSX Edge Interfce dilog ox, set Connectivity Sttus to Connected nd click OK. Initite Disster Recovery of vrelize Opertions Mnger in Region A If disster event occurs in Region B, initite the Disster Recovery of vrelize Opertions Mnger in Region A to fil ck vrelize Opertions Mnger to Region A. Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. VMwre, Inc. 98

3 On the Site Recovery home pge, click Sites nd click the mgmt01vc01.sfo01.rinpole.locl vcenter Server oject to open its configurtion in Site Recovery Mnger. 4 Click Recovery Plns nd click the vrops-rp recovery pln. 5 On the vrops-rp pge, click the Monitor t nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filck of the nlytics cluster. The Recovery wizrd ppers. 7 On the Confirmtion options pge of the Recovery wizrd, configure the following settings nd click Next. I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Disster recovery 8 On the Redy to complete pge, click Finish to initite vrelize Opertions Mnger filck. After disster recovery, the sttus of the recovery pln is Disster Recovery Completed. Wht to do next Perform the steps required to verify the opertion of nd reprotect the system. 1 Verify tht vrelize Opertions Mnger is up nd functions flwlessly fter filck. See Vlidte vrelize Opertions Mnger in the Opertionl Verifiction documenttion. 2 Prepre vrelize Opertions Mnger for filover y reprotecting the virtul mchines of the nlytics cluster in Site Recovery Mnger. See Reprotect vrelize Opertions Mnger. Initite Disster Recovery of the Cloud Mngement Pltform in Region A In the event of disster in Region B, initite the Disster Recovery of vrelize Automtion, vrelize Orchestrtor nd vrelize Business in Region A to fil ck the cloud mngement pltform to Region A. VMwre, Inc. 99

Procedure 1 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu, select Site Recovery. 3 On the Site Recovery home pge, click Sites nd doule-click the mgmt01vc01.sfo01.rinpole.locl vcenter Server oject to open its site configurtion. 4 Click Recovery Plns nd click the vra-vro-vrb-rp recovery pln. 5 On the vra-vro-vrb-rp pge, click the Monitor t, nd click Recovery Steps. 6 Click the Run Recovery Pln icon to run the recovery pln nd initite the filover of the cloud mngement pltform. 7 On the Confirmtion options pge of the Recovery wizrd, configure the following settings nd click Next. Confirmtion Option I understnd tht this process will permnently lter the virtul mchines nd infrstructure of oth the protected nd recovery dtcenters Recovery type Selected Disster recovery 8 On the Redy to complete pge, click Finish to initite the filover of the cloud mngement pltform. Site Recovery Mnger runs the recovery pln. Wht to do next Perform the steps required to verify the opertion of nd reprotect the system. 1 Verify tht vrelize Automtion, vrelize Orchestrtor nd vrelize Business VMs re up nd function flwlessly fter filck. See Vlidte the Cloud Mngement Pltform in the Opertionl Verifiction document. 2 Prepre vrelize Automtion, vrelize Orchestrtor nd vrelize Business Server for filover y reprotecting the virtul mchines of the vrelize Automtion components in Site Recovery Mnger. See Reprotect the Cloud Mngement Pltform. VMwre, Inc. 100

Post-Filck Configurtion of Mngement Applictions After filck of the cloud mngement pltform nd vrelize Opertions Mnger, you must perform certin tsks to ensure tht pplictions perform s expected. Procedure 1 Configure the NSX Controllers nd the UDLR Control VM to Forwrd Events to vrelize Log Insight in Region A Configure the NSX Controllers nd UDLR Control VM instnces for the mngement cluster to forwrd log informtion to vrelize Log Insight in Region A. Use the NSX REST API to configure the NSX Controllers. You cn use REST client, such s the RESTClient dd-on for Firefox, to enle log forwrding. 2 Updte the vrelize Log Insight Logging Address fter Filck After you filck the mngement pplictions in the SDDC to Region A, updte the ddress configured on the mngement pplictions for vrelize Log Insight. All mngement pplictions re still configured to send logs to the vrelize Log Insight instnce in Region B. 3 Reconfigure the NSX Instnce for the Mngement Cluster in Region B fter Filck After Region B comes ck online, you must perform dditionl configurtion of the networking lyer to void conflicts. Configure the NSX Controllers nd the UDLR Control VM to Forwrd Events to vrelize Log Insight in Region A Configure the NSX Controllers nd UDLR Control VM instnces for the mngement cluster to forwrd log informtion to vrelize Log Insight in Region A. Use the NSX REST API to configure the NSX Controllers. You cn use REST client, such s the RESTClient dd-on for Firefox, to enle log forwrding. Prerequisites On Windows host tht hs ccess to your dt center, instll REST client, such s the RESTClient dd-on for Firefox. Procedure 1 Log in to the Windows host tht hs ccess to your dt center. 2 In Firefox rowser, go to chrome://restclient/content/restclient.html. VMwre, Inc. 101

3 Specify the request heders for requests to the NSX Mnger. From the Authentiction drop-down menu, select Bsic Authentiction. In the Bsic Authoriztion dilog ox, enter the following credentils, select Rememer me nd click Oky. Authentiction Attriute Usernme Pssword dmin mngnsx_dmin_pssword The Authoriztion:Bsic XXX heder ppers in the Heders pne. c d From the Heders drop-down menu, select Custom Heder. In the Request Heder dilog ox, enter the following heder detils nd click Oky. Request Heder Attriute Nme Content-Type ppliction/xml The Content-Type:ppliction/xml heder ppers in the Heders pne. 4 Contct the NSX Mnger to retrieve the IDs of the ssocited NSX Controllers. In the Request pne, from the Method drop-down menu, select GET. In the URL text ox, enter https://mgmt01nsxm01.sfo01.rinpole.locl/pi/2.0/vdn/controller nd click Send. The RESTClient sends query to the NSX Mnger out the instlled NSX controllers. VMwre, Inc. 102

c After the NSX Mnger sends response ck, click the Response Body (Preview) t under Response. The response ody contins root <controllers> XML element, which groups the detils out the three controllers tht form the controller cluster. d Within the <controllers> element, locte the <controller> element for ech controller nd write down the content of the <id> element. Controller IDs hve the controller-id formt where id represents the sequence numer of the controller in the cluster, for exmple, controller-2. VMwre, Inc. 103

5 For ech NSX Controller, send request to configure vrelize Log Insight s remote syslog server. In the Request pne, from the Method drop-down menu, select POST, nd in the URL text ox, enter the following URL. NSX Mnger NSX Mnger for the mngement cluster NSX Controller in the Controller Cluster NSX Controller 1 NSX Controller 2 NSX Controller 3 POST URL https://mgmt01nsxm01.sfo01.rinpole.locl/pi/2.0/vdn/controller/<controller1- id>/syslog https://mgmt01nsxm01.sfo01.rinpole.locl/pi/2.0/vdn/controller/<controller2- id>/syslog https://mgmt01nsxm01.sfo01.rinpole.locl/pi/2.0/vdn/controller/<controller3- id>/syslog In the Request pne, pste the following request ody in the Body text ox nd click Send. <controllersyslogserver> <syslogserver>vrli-cluster-01.sfo01.rinpole.locl</syslogserver> <port>514</port> <protocol>udp</protocol> <level>info</level> </controllersyslogserver> c Repet the steps for the next NSX Controller. 6 Verify the syslog configurtion on ech NSX Controller. In the Request pne, from the Method drop-down menu, select GET, nd in the URL text ox, enter the controller-specific syslog URL from the previous step nd click the SEND utton. After the NSX Mnger returns response, click the Response Body (Preview) t under Response. The response ody contins root <controllersyslogserver> element, which represents the settings for the remote syslog server on the NSX Controller. VMwre, Inc. 104

c d Verify tht the vlue of the <syslogserver> element is vrlicluster-01.sfo01.rinpole.locl. Repet the steps for the next NSX Controller. 7 Log in to the Mngement vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 8 Configure the newly deployed UDLR control VM to forwrd events to vrelize Log Insight in Region A. c d e f g h From the Home menu of the vsphere We Client, click Networking & Security. In the Nvigtor, click NSX Edges. Select 172.16.11.65 from the NSX Mnger drop-down menu. Doule-click UDLR01. On the NSX Edge device pge, click the Mnge t, click s, nd click Configurtion. In the Detils pne, click Chnge next to Syslog servers. In the Edit Syslog Servers Configurtion dilog ox, in the Syslog Server 1 text ox, enter 192.168.31.10 nd from the Protocol drop-down menu, select udp. Click OK. VMwre, Inc. 105

Updte the vrelize Log Insight Logging Address fter Filck After you filck the mngement pplictions in the SDDC to Region A, updte the ddress configured on the mngement pplictions for vrelize Log Insight. All mngement pplictions re still configured to send logs to the vrelize Log Insight instnce in Region B. You updte the DNS entry for vrli-cluster-51.lx01.rinpole.locl to point to the IP ddress 192.168.31.10 of vrli-cluster-01.sfo01.rinpole.locl in Region A. Procedure 1 Log in to the DNS server dc01sfo.sfo01.rinpole.locl tht resides in the sfo01.rinpole.locl domin. 2 Open the Windows Strt menu, enter dns in the Serch text ox nd press Enter. The DNS Mnger dilog ox ppers. 3 In the DNS Mnger dilog ox, under Forwrd Lookup Zones, select the lx01.rinpole.locl domin nd locte the vrli-cluster-51 record on the right. 4 Doule-click the vrli-cluster-51 record, chnge the IP ddress of the record from 192.168.32.10 to 192.168.31.10 nd click OK. Fully qulified domin nme (FQDN) vrli-cluster-51.lx01.rinpole.locl IP Address 192.168.31.10 Updte ssocited pointer (PTR) record Selected VMwre, Inc. 106

Reconfigure the NSX Instnce for the Mngement Cluster in Region B fter Filck After Region B comes ck online, you must perform dditionl configurtion of the networking lyer to void conflicts. You demote the NSX Mnger to the secondry role, delete the universl controller cluster, disle the lod lncer, nd perform dditionl configurtion on the NSX Edges. Procedure 1 Log in to vcenter Server y using the vsphere We Client. Open We rowser nd go to https://mgmt01vc01.sfo01.rinpole.locl/vsphere-client. Log in using the following credentils. User nme Pssword dministrtor@vsphere.locl vsphere_dmin_pssword 2 From the Home menu from the vsphere We Client, click Networking & Security. 3 In the Nvigtor, click Instlltion nd click the Mngement t. You see tht oth NSX Mngers 172.17.11.65 nd 172.16.11.65 re ssigned the primry role. VMwre, Inc. 107

Site Protection and Recovery. VMware Validated Design 4.0 VMware Validated Design for Software-Defined Data Center 4.0