vrealize Suite 7.0 Backup and Restore by Using EMC Avamar vrealize Suite 7.0

Transcription

1 vrelize Suite 7.0 Bckup nd Restore y Using EMC Avmr vrelize Suite 7.0

2 You cn find the most up-to-dte technicl documenttion on the VMwre wesite t: If you hve comments out this documenttion, sumit your feedck to VMwre, Inc Hillview Ave. Plo Alto, CA Copyright 2017 VMwre, Inc. All rights reserved. Copyright nd trdemrk informtion. VMwre, Inc. 2

3 Contents vrelize Suite 7.0 Bckup nd Restore y Using EMC Avmr 4 1 Bckup nd Restore Introduction 5 2 Prepring to Bck Up vrelize Components 6 vrelize Components Bckup Order 6 vrelize Business Preprtions for Bcking Up 7 vrelize Log Insight Preprtions for Bcking Up 8 vrelize Opertions Mnger Preprtions for Bcking Up 10 vrelize Orchestrtor Preprtions for Bcking Up 13 vrelize Automtion Preprtions for Bcking Up 13 3 Bcking Up vrelize Suite y Using EMC Avmr 19 Perform n On-Demnd Bckup of Client 19 Perform nd On-Demnd Group Bckup 21 Schedule Bckups 21 4 Restoring, Powering On, nd Vlidting vrelize Suite 23 vrelize Suite Strtup Order 23 vrelize Automtion System Recovery 24 vrelize Orchestrtor Restore Process 33 vrelize Opertions Mnger Restore Process 34 vrelize Log Insight Restore Process 39 vrelize Business Restore Process 45 5 Restore vrelize Suite y Using EMC Avmr 46 6 Restrt the Cluster Anlytic Service 49 7 Mnul Bckup Procedure Appers to Stll 50 VMwre, Inc. 3

4 vrelize Suite 7.0 Bckup nd Restore y Using EMC Avmr vrelize Suite 7.0 Bckup nd Restore y Using EMC Avmr provides informtion out how to perform full, differentil, incrementl, nd synthetic full ckups leverging VMwre Chnged Block Trcking to ck up nd restore VMwre vrelize Suite y using EMC Avmr. Intended Audience This informtion is intended for nyone who wnts to ck up nd restore vrelize Suite 7.0 components y using Avmr. The informtion is written for experienced Windows or Linux system dministrtors who re fmilir with virtul mchine technology nd dt center opertions. VMwre Technicl Pulictions Glossry VMwre Technicl Pulictions provides glossry of terms tht might e unfmilir to you. For definitions of terms s they re used in VMwre technicl documenttion, go to VMwre, Inc. 4

5 Bckup nd Restore 1 Introduction You cn ck up nd restore the vrelize Suite 7.0 components. You cn ck up nd restore the following versions of vrelize Suite 7.0 components with EMC Avmr 7.4. vrelize Automtion 7.3.0, 7.2.0, 7.1.0, nd vrelize Orchestrtor 7.3.0, 7.2.0, 7.1.0, nd vrelize Opertions Mnger 6.6.0, 6.5.0, 6.4.0, 6.3.0, nd vrelize Log Insight 4.5.0, 4.3.0, 4.0.0, 3.6.0, 3.3.x vrelize Business 7.3.0, 7.2.0, 7.1.0, When to Bck Up Components You should ck up vrelize Suite components for the following resons: To prepre for mjor mintennce of ny of the system components To implement scheduled mintennce ckup To prepre for updting certifictes To protect certifictes fter updting them VMwre, Inc. 5

6 Prepring to Bck Up vrelize 2 Components You cn successfully prepre the vrelize Suite components for ckup y plnning nd oserving some sic guidelines. This section includes the following topics: vrelize Components Bckup Order vrelize Business Preprtions for Bcking Up vrelize Log Insight Preprtions for Bcking Up vrelize Opertions Mnger Preprtions for Bcking Up vrelize Orchestrtor Preprtions for Bcking Up vrelize Automtion Preprtions for Bcking Up vrelize Components Bckup Order You should ck up the VMs for vrelize Suite components in specific order. Overll Bckup Order vrelize Business vrelize Log Insight vrelize Opertions Mnger vrelize Orchestrtor vrelize Automtion VMwre, Inc. 6

7 Depending on the vrelize Suite components tht you hve configured nd your requirements, schedule ckups for your vrelize Suite components in the following order. If you do not hve prticulr component, you cn move to the next component in the specified order. The order of the VMs cn e lso defined in the ckup tools. 1 vrelize Business. Bck up the VM for vrelize Business. 2 vrelize Log Insight. If the resources re not n issue, it is recommended to enle concurrent cluster node ckups to speed up the ckup process. Bck up ll the nodes t the sme time. 3 vrelize Opertions Mnger. All nodes re cked up t the sme time. 4 vrelize Orchestrtor. You cn tke ckups of the vrelize Orchestrtor VMs, individully nd in cluster mode, in no prticulr order. If vrelize Orchestrtor is stndlone component, ck it up efore vrelize Automtion components in no prticulr order. If vrelize Orchestrtor is emedded with in the vrelize Automtion deployment, ck it up s prt of the vrelize Applince. 5 vrelize Automtion. Bck up the vrelize Automtion components in the following order: c d e f g h Proxy Agents DEM Workers DEM Orchestrtor Mnger Services We sites vrelize Automtion Applinces PostgreSQL, if pplicle MS SQL If you hve multiple components on VM, select the order considering the ltter component on the VM from the list. vrelize Business Preprtions for Bcking Up To minimize system downtime nd dt loss when filures occur, dministrtors ck up the vrelize Business Stndrd instlltion on regulr sis. If your system fils, you cn recover it y restoring the lst known working ckup. You ck up vrelize Business y exporting or cloning the virtul pplince nd use ckups to restore the virtul pplince. vrelize Business Bckup Order vrelize Business Applince (Only one Node) VMwre, Inc. 7

8 Guidelines for Bcking Up Use the following guidelines to pln ckups: Verify tht vrelize Business is up nd running nd vrelize Automtion is registered with it. Verify tht you cn view the Business Mngement t in your vrelize Automtion deployment. Verify tht vrelize Business is clculting the correct cost of the VMs. Verify tht the VMs provisioned for vrelize Automtion nd vrelize Orchestrtor re visile in vrelize Business nd tht vrelize Business cn clculte the cost for the VMs. vrelize Log Insight Preprtions for Bcking Up You cn perform full, differentil, nd incrementl ckups nd restores of vrelize Log Insight VMs. If resources re not prolem ck up ll the nodes t the sme time, to speed up the ckup process. Verify tht you re incresing the numer of concurrent ckups from one, which is the defult. Liner ckup is lso supported ut it slows down the restore opertion. vrelize Log Insight Bckup Order Worker Node1 Worker Node2 Worker Noden Mster Node Guidelines for Plnning Bckups You cn use the following informtion for cking up vrelize Log Insight 3.3 clusters in new environment. Ensure tht you hve no configurtion prolems on source nd trget sites efore performing the ckup nd restore opertions. During the ckup opertion, the memory usge cn increse due to the vrelize Log Insight cluster usge. In some cses, the worker nodes might e disconnected for 1 to 3 minutes due to high memory usge. To reduce the memory throttling on vrelize Log Insight nodes, follow these guidelines: Allocte dditionl memory over the vrelize Log Insight recommended configurtion. Schedule the recurring ckups during off-pek hours. Disle quiesced snpshots, ecuse vrelize Log Insight does not support them. The vrelize Log Insight server supports Linux nd Windows gents. If the gent configurtion is creted on the server side, seprte ckup of the gent node is not required. VMwre, Inc. 8

9 If you use the gent nodes for more thn instlling the gent softwre nd if these nodes need full ckup, follow the sme ckup procedure s for ny VM. If the gent configurtion is done on the client side, on the gents, nd if the gent nodes re used only to instll vrelize Log Insight gent softwre, scheduling ckup of the gent configurtion file is sufficient. Bck up the ligent.ini file nd replce the file on the recovered gent or Linux or Windows mchine with the ckup file. If concurrent ckup is not possile, ensure tht the vrelize Log Insight mster node is cked up first efore the worker nodes. Worker nodes cn e cked up in ny order. Ensure tht the ckup frequency nd ckup types re selected sed on the ville resources nd customer-specific requirements. Use the following guidelines when scheduling recurring ckups. For resonle loded cluster setup, it might tke while for the first ckup to finish irrespective of the tool. The first ckup is usully full ckup. Successive ckups cn e incrementl or full ckups, Successive ckups finish reltively fst, compred to the first ckup opertion. Use sttic IP ddresses for ll nodes in vrelize Log Insight cluster. Using sttic IP ddresses elimintes the need to updte the IP ddresses of vrelize Log Insight cluster nodes ech time the IP ddress of vrelize Log Insight node chnges. vrelize Log Insight includes ll node IP ddresses in ech cluster node configurtion file t /storge/core/loginsight/config/loginsight-config.xml#<n> where <n> is the lrgest numer. Some products tht integrte with vrelize Log Insight to feed their logs, use fully qulified domin nme (FQDN) or IP ddress s the syslog trget. For exmple, vsphere ESXi, vsphere, nd vrelize Opertions Mnger use the nodes of the cluster mster's or the lod lncer's (if configured) FQDN or IP ddress s the syslog trget. Use n FQDN for ll nodes in the vrelize Log Insight cluster. For the mster node, when you use lod lncer, fully resolvle FQDN is required. Otherwise, the ESXi hosts fil to feed the syslog messges to vrelize Log Insight or to ny remote trget. Using n FQDN sves time on post-restore nd recovery configurtion chnges, ssuming tht the sme FQDN cn e resolved on the recovery site. For system lerts, vrelize Log Insight uses FQDN host nmes if ville insted of IP ddresses. Assuming tht only underlying IP ddresses chnge post-ckup nd recovery or disster recovery opertions, using FQDN elimintes the need to chnge the syslog trget ddress (mster node FQDN or internl lod lncer FQDN) on ll the externl devices feeding logs to the vrelize Log Insight cluster. VMwre, Inc. 9

10 With vrelize Log Insight 2.5, you must updte the configurtion file, locted t /storge/core/loginsight/config/loginsight-config.xml#<n> where <n> is the lrgest numer. This configurtion file replces the worker node IP ddress with the new IP ddress used for the restored nodes ecuse the FQDN is not used for worker node ddresses in the configurtion file. You need to mke this chnge only on the mster node to synchronize the chnges with ll the worker nodes. Join requests from vrelize Log Insight worker node should use the FQDN of the vrelize Log Insight mster node. Beginning in vrelize Log Insight 2.5, the mster node host vlue in the configurtion file on ech of the nodes, locted t /storge/core/loginsight/config/loginsight-config.xml#<n>, is sed on the vlue used y the first worker node sending join request. Using the FQDN of the mster node for the join request prevents mking ny mnul chnges to the mster node host vlue post-disster recovery. Otherwise, the worker nodes cnnot rejoin the mster node until the mster node host nme is updted in the configurtion files on ll restored cluster nodes. Provide sttic IP ddresses s well s optionl virtul IP ddresses for the lod lncer. When configuring n integrted lod lncer, provide the optionl FQDN for the virtul IP ddress. This optionl FQDN enles vrelize Log Insight to revert to the FQDN when n IP ddress is not rechle for ny reson. vrelize Opertions Mnger Preprtions for Bcking Up To minimize vrelize Opertions Mnger downtime nd dt loss if filure occurs, ck up on regulr sis. If your system fils, you cn recover it y restoring to the lst full or incrementl ckup. You cn ckup nd restore vrelize Opertions Mnger single-node or multi-node clusters y using ckup tools. You cn perform full or incrementl ckups nd restores of virtul mchines. vrelize Opertions Mnger Bckup Order Mster Node Replic Node Dt Node1 Dt Node2 Dt Noden Note All nodes re cked up nd restored t the sme time. You cnnot ck up nd restore individul nodes. VMwre, Inc. 10

11 Guidelines for Plnning Bckups Verify tht the following prerequisites re met efore you ck up vrelize Opertions Mnger systems y using ny tool. Do not quiesce the file system. Use resolvle host nme nd sttic IP ddress for ll nodes. All nodes must e powered on nd ccessile during ckup. Bck up the entire VM. You must ck up ll VMDK files tht re prt of the virtul pplince. Do not stop the cluster while performing the ckup. Verify tht the following prerequisites re met for the vcenter server where vrelize Opertions Mnger is deployed. The vsphere Dt Protection pplince is instlled on the vcenter Server instnce where the vrelize Opertions Mnger cluster is deployed. You hve sufficient disk spce ville for your vsphere Dt Protection instnce. This depends on the size of the multi-node cluster tht you wnt to ck up Use the vsphere We Client to log in s n dministrtor to the vcenter Server instnce tht mnges your environment. In the vsphere We Client verify tht the virtul mchines hve the ltest version of VMwre Tools instlled. Note Do not perform ckup while dynmic threshold (DT) clcultions re running ecuse this ckup might led to performnce prolems or loss of nodes. DT clcultions run t 2.m. y defult. The initil ckup might tke longer to complete depending on the cluster size nd numer of nodes, so you should turn off the DT. Schedule the differentil or incrementl ckups so tht they end efore the DT clcultions egin. If you re using ckup tools, such s NetBckup nd vsphere Dt Protection, nd hve mnully creted vsphere snpshots of ny of the VMs to e cked up, e wre tht the tools delete ll existing snpshots t the time of the ckup or restore. Common Bckup Scenrios The common ckup scenrios for vrelize Opertions Mnger systems include full ckup of single node virtul pplince system nd full ckup of multiple node virtul pplince cluster. Single-Node Virtul Applince This scenrio cks up single-node system on the sme host. 1 Assign sttic IP ddress. 2 Ensure tht the power is on for the entire ckup process. VMwre, Inc. 11

12 3 If the system is Linux or Windows instlltion, you need to prepre the system efore you strt the ckup. For more informtion, see Prepring for vrelize Opertions Mnger Instlltion in the VMwre vrelize Opertions Mnger Documenttion Center. Multiple-Node Virtul Applince Clusters This scenrio cks up multiple-node virtul pplince clusters. 1 Assign sttic IP ddress for ech node. 2 Ensure tht ll nodes tht re configured with high vilility re ccessile nd re enled for high vilility. 3 Ensure tht the power remins on during the entire ckup process. 4 If the system is Linux or Windows instlltion, you must prepre the system efore you strt the ckup. For more informtion, see Prepring for vrelize Opertions Mnger Instlltion in the VMwre vrelize Opertions Mnger Documenttion Center. Disle Quiescing Before you ckup your vrelize Opertions Mnger multi-node cluster y using vsphere Dt Protection, disle quiescing of the file system. Procedure 1 Log in to the ESXi host with n SSH session, nd power off ll nodes. 2 Nvigte to the /vmfs/volumes/virtul_mchine_dtstore/ virtul_mchine/ directory, nd open the virtul_mchine.vmx file for editing. 3 Set the disk.enleuuid prmeter to flse. You my hve to dd the disk.enleuuid prmeter to the virtul_mchine.vmx file. 4 Sve nd close the file. 5 Power on ll nodes. 6 Open console session to the virtul mchine, nd log in to ech node. 7 Nvigte to the /etc/vmwre-tools directory, nd open the tools.conf file for editing. If you cnnot locte the tools.conf file, run the vi tools.conf commnd to crete file. 8 Add these prmeters to the file. [vmckup] enlesyncdriver = flse This runs synchroniztion opertion efore the snpshot, nd does not run freeze on the file system. 9 Sve nd close the file. VMwre, Inc. 12

13 Wht to do next Bckup your vrelize Opertions Mnger multi-node cluster y using vsphere Dt Protection. vrelize Orchestrtor Preprtions for Bcking Up You cn ckup your vrelize Orchestrtor VMs in no prticulr order. You cn lso ck up the vrelize Orchestrtor elements tht you modified. If vrelize Orchestrtor is emedded within the vrelize Automtion pplince, perform its ckup long with Mnger Services for vrelize Automtion. If vrelize Orchestrtor is stndlone component, perform its ckup efore cking up vrelize Automtion components in no prticulr order. vrelize Orchestrtor Bckup Order Node1 Node2 Noden (Nodes in ny order) Ech vrelize Orchestrtor server instnce hs unique certifictes, nd ech vcenter Server plug-in instnce hs unique ID. The certifictes nd the unique ID identify the vrelize Orchestrtor server nd thevcenter Server plug-in. If you do not ck up the vrelize Orchestrtor elements or export the vrelize Orchestrtor configurtion for ckup purposes, mke sure tht you chnge these identifiers. All components of the vrelize Orchestrtor must e cked up together nd t the sme time including the dtse components. You must ck up the vrelize Orchestrtor dtse nd VMs (custom workflows nd pckges). vrelize Orchestrtor Dtse You cn tke full dtse ckups of the dtse in your environment efore full VM ckup. The min purpose is to ensure consistency of the dt when you hve to restore. Follow your in-house procedures to ck up the vrelize Orchestrtor dtse outside of the vrelize Suite frmework. vrelize Automtion Preprtions for Bcking Up A system dministrtor cks up the full vrelize Automtion instlltion on regulr sis. Pln the ckup round efficiencies nd periods of low ctivity. You cn use severl strtegies, singly or in comintion, to ck up vrelize Automtion system components. For virtul mchines (VMs), you cn use the Snpshot function to crete snpshot imges of criticl components or use tools like Verits NetBckup nd vsphere Dt Protection. If system filure occurs, you cn use these imges to restore components to their stte when the imges were creted. Alterntively, nd for non-virtul mchine components, you cn crete copies of criticl configurtion files for system components, which cn e used to restore these components to customer configured stte following reinstlltion. VMwre, Inc. 13

14 A complete ckup includes the following components: IS components Proxy Agents DEM Workers DEM Orchestrtor Mnger Services We sites vrelize Automtion pplince PostgreSQL dtse. Applicle only for legcy instlltions tht do not use n emedded pplince dtse Infrstructure MSSQL dtse (Optionl) Softwre lod lncers (Optionl) Lod lncers tht support your distriuted deployment. Consult the vendor documenttion for your lod lncer for informtion out ckup considertions Guidelines for Plnning Bckups Use the following guidelines to pln ckups: When you ck up complete system, ck up ll instnces of the vrelize Automtion pplince nd dtses s ner simultneously s possile, preferly within seconds. Minimize the numer of ctive trnsctions efore you egin ckup. Schedule your regulr ckup to when your system is lest ctive. Bck up ll dtses t the sme time. When you ck up the vrelize Automtion pplince nd the IS components, disle in-memory snpshots nd quiesced snpshots. Crete ckup of instnces of the vrelize Automtion pplince nd the IS components when you updte certifictes. vrelize Automtion Bckup Order You must ck up the VMs for vrelize Automtion components in specific order. When you use ckup tools to schedule ckups for your vrelize Automtion deployment, you must ck up the components in the following order: VMwre, Inc. 14

15 vrelize Automtion Bckup Order Proxy Agents DEM Workers DEM Orchestrtor Pssive Mnger Service Active Mnger Service We Node1 We Node2 We Noden Secondry vrelize Automtion Applinces1 Secondry vrelize Automtion Applinces2 Secondry vrelize Automtion Applincesn Primry vrelize Automtion Applinces Postgres Dtse VA MS SQL Dtse If you hve multiple components on VM, select the order considering the ltter component on the VM from the list. If vrelize Orchestrtor is stndlone component, then it should e cked up in no prticulr order efore vrelize Automtion components. Bcking Up vrelize Automtion Certifictes A system dministrtor cks up certifictes nd certificte chins t instlltion time or when certificte is replced. Bck up the following certifictes: vrelize Automtion pplince certifictes nd the entire corresponding certificte chin. IS certifictes nd the entire corresponding certificte chin. VMwre, Inc. 15

16 Bcking Up vrelize Automtion Dtses The dtse dministrtor cks up the Infrstructure MSSQL Server nd Applince Dtse. As est prctice, ck up the Infrstructure MSSQL nd Applince Dtse or legcy PostgreSQL dtses s nerly simultneously s possile to prevent or minimize dt loss. Also, when pplicle, ck up dtses with Point-in-Time enled. By using Point-in-Time recovery, you ensure tht the two dtses re consistent with ech other. Note If only one dtse fils, you must restore the running dtse to the most recent ckup so tht the dtses re consistent. Infrstructure MSSQL Dtse Bck up the Infrstructure MSSQL nd Applince Dtse or legcy PostgreSQL dtses s nerly simultneously s possile to prevent or minimize dt loss. Also, when pplicle, ck up dtses with Point-in-Time enled. By using point-in-time recovery, you ensure tht the two dtses re consistent with ech other. If only one dtse fils, you must restore the running dtse to the most recent ckup so tht the dtses re consistent. Follow your in-house procedures to ck up the Infrstructure MSSQL dtse outside of the vrelize Suite frmework. Use the following guidelines when creting ckup: If possile, check tht ll IS workflows re complete nd tht ll IS services re stopped or tht ctivity is minimized. Bck up with Point-in-Time enled. Bck up the MSSQL dtse t the sme time tht you ck up the other components. Bck up the pssphrse for your dtse. Note Your dtse is protected y pssphrse. Hve the pssphrse ville when you restore the dtse. Typiclly, you record the pssphrse in sfe nd ccessile loction t instll time. Applince Dtse or Legcy PostgreSQL Dtse If you re using n Applince Dtse or legcy PostgreSQL dtse emedded in vrelize Automtion pplince, you cn ck up the dtse y cking up the entire pplince. If you re using stndlone legcy PostgreSQL pplince, you must ck up the pplince. If you re using legcy PostgreSQL dtse, you cn lso ckup the dtse seprtely. For more informtion, see the VMwre Knowledge Bse rticle Migrting from externl vpostgres pplince to vpostgres instnce locted in the vcac pplince ( ) t for more informtion. VMwre, Inc. 16

17 Bcking Up Lod Blncers Lod lncers distriute work mong servers in high-vilility deployments. The system dministrtor cks up the lod lncers on regulr sis t the sme time s other components. Follow your site policy for cking up lod lncers, keeping in mind the preservtion of network topology nd vrelize Automtion ckup plnning. Bcking Up IS Components The system dministrtor cks up the IS components in specific order. When you ck up IS components, disle in-memory snpshots nd quiesced snpshots. You cn ck up IS components y tking snpshot of the VMs in the following order: Proxy Agents nd DEMs Mnger Service We sites Bcking Up vrelize Automtion Applince You must ck up secondry vrelize Automtion pplince nodes, followed y the mster node. When you ck up the vrelize Automtion pplince, disle in-memory snpshots nd quiesced snpshots. The primry vrelize Automtion pplince instnce contins the writele Applince Dtse, if pplicle, nd is the lst pplince tht you shut down in n ordered shutdown procedure. (Optionl) Shut Down vrelize Automtion Shutting down vrelize Automtion is optionl. If you decide to shut down your vrelize Automtion system, use the specified order. If you re using vcenter Server to mnge your virtul mchines, use the guest shutdown commnd to shut down vrelize Automtion. Procedure 1 Shut down the DEM Orchestrtor nd Workers nd ll vrelize Automtion gents in ny order nd wit for ll components to finish shutting down. 2 Shut down the VMs tht re running the Mnger Service nd wit for the shutdown to finish. 3 (Optionl) For distriuted deployments, shut down ll secondry We nodes nd wit for the shutdown to finish. 4 Shut down the primry We node, nd wit for the shutdown to finish. 5 (Optionl) For distriuted deployments, shut down ll secondry vrelize Automtion pplince instnces nd wit for the shutdown to finish. VMwre, Inc. 17

18 6 Shut down the primry vrelize Automtion pplince nd wit for the shutdown to finish. If pplicle, the primry vrelize Automtion pplince is the one tht contins the mster, or writele, Applince Dtse. Mke note of the nme of the primry vrelize Automtion pplince. You use this informtion when you restrt vrelize Automtion. 7 If you re using legcy stndlone PostgreSQL dtse, lso shut down tht mchine. You hve shut down your vrelize Automtion deployment. VMwre, Inc. 18

19 Bcking Up vrelize Suite y Using EMC Avmr 3 You cn ck up vrelize Suite components y using EMC Avmr to perform on-demnd ckups nd schedule ckups. You cn tke on-demnd ckups nd schedule Avmr to perform scheduled ckups. Scheduled ckups run utomticlly to ensure tht ckups occur on n ongoing sis. You cn schedule ckups to run dily, weekly, or monthly. For informtion on scheduling ckups in Avmr, see the EMC Avmr for VMwre User Guide. This section includes the following topics: Perform n On-Demnd Bckup of Client Perform nd On-Demnd Group Bckup Schedule Bckups Perform n On-Demnd Bckup of Client You cn perform n on-demnd ckup of n individul client. If you configure scheduled ckups for group of clients, then you cn lso perform n on-demnd ckup of group or n on-demnd ck of single client y using group policy settings. Prerequisites Deploy nd configure the Avmr pplince. See the EMC Avmr for VMwre User Guide. Verify tht ll nodes re powered on nd re ccessile during ckup. Add ll vrelize Suite components to ckup s clients. See the EMC Avmr for VMwre User Guide. Disle quiesced snpshots. Procedure 1 In Avmr Administrtor, click Bckup & Restore. 2 Click the Bckup t. The top left pne contins list of domins. 3 Select domin in the upper tree, nd select virtul mchine client, VMwre folder, resource pool, or vapp in the lower tree. VMwre, Inc. 19

20 4 In the Browse for File, Folders, or Directories pne, select the dt to ck up. Option Bck up the entire imge Bck up specific virtul disks Description Right-click the top (root) folder, nd select Select All. Select one or more disks to ck up only the selected virtul disks. 5 In the Actions menu, select Bckup Now. The On Demnd Bckup Options dilog ox ppers. 6 Select the ckup retention setting. Option Retention period End dte No end dte Description Automticlly delete this ckup from the Avmr server fter specific mount of time. Specify the numer of dys, weeks, months, or yers for the retention period. Automticlly delete this ckup from the Avmr server on specific clendr dte. Browse to the dte to delete this ckup on the clendr. Keep this ckup while this client remins ctive in the Avmr server. 7 From the Avmr encryption method list, select the encryption method to use for dt trnsfer etween the client nd the Avmr server during the ckup. 8 (Optionl) Select proxy to perform ckup. The defult setting is utomtic, which enles the Avmr server to select the est proxy for this opertion. 9 Click More Options. The Bckup Commnd Line Options dilog ox ppers. Select the plug-in type. In most cses, the system defult settings re the optimum settings for on-demnd imge ckups. c d (Optionl) To increse performnce, select Use Chnged Block Trcking (CBT). To disle the quiesced snpshots, click More. Enter the ttriute nd ttriute vlue, nd click + to dd the flg. Option Attriute Attriute Vlue Vlue [vvcimge]quiesce_fs flse 10 Click OK. The On Demnd Bckup Options dilog ox closes nd the following sttus messge ppers: Bckup initited. 11 Click OK. VMwre, Inc. 20

21 Wht to do next For informtion on monitoring nd cncelling ckup procedures, see the EMC Avmr for VMwre User Guide. Perform nd On-Demnd Group Bckup You cn use EMC Avmr to ck up n entire group of clients. Prerequisites Deploy nd configure the Avmr pplince. See the EMC Avmr for VMwre User Guide. Verify tht ll nodes re powered on nd re ccessile during ckup. Add ll vrelize Suite components to ckup s clients. See the EMC Avmr for VMwre User Guide. Disle quiesced snpshots. Procedure 1 In Avmr Administrtor, click Policy. The Policy window ppers. 2 Click the Policy Mngement t. 3 Select the group to ck up y clicking the Groups t nd selecting the group from the list. 4 Click Bck Up nd click OK. Wht to do next For informtion on monitoring nd cncelling ckup procedures, see the EMC Avmr for VMwre User Guide. Schedule Bckups Scheduled ckups run utomticlly to ensure tht ckups occur on n ongoing sis. A scheduled ckup cn include multiple clients or single server. Prerequisites Deploy nd configure the Avmr pplince. See the EMC Avmr for VMwre User Guide. Verify tht ll nodes re powered on nd re ccessile during ckup. Add ll vrelize Suite components to ckup s clients. See the EMC Avmr for VMwre User Guide. Procedure 1 Crete dtset to define the dt tht is included in the ckups. VMwre, Inc. 21

22 2 Disle quiesced snpshots. c Select the plug-in type. For ech selected plug-in type, click More. Enter the ttriute [vvcimge]quiesce_fs nd ttriute vlue flse, nd click + to dd the flg. 3 Crete schedule for when the ckups should occur. 4 Crete retention policy to define how long to keep the ckups in the system. 5 Crete group for the ckups. c d e Assign the new dtset to the new group. Assign schedule to the new group. Assign retention policy to the new group. Add one or more clients to the new group. Assign the proxies to the new group. 6 Enle scheduling for the group. Wht to do next For informtion on monitoring nd cncelling ckup procedures, see the EMC Avmr for VMwre User Guide. VMwre, Inc. 22

23 Restoring, Powering On, nd 4 Vlidting vrelize Suite You cn restore, power on, nd vlidte tht the vrelize Suite components re restored correctly y using the following informtion. This section includes the following topics: vrelize Suite Strtup Order vrelize Automtion System Recovery vrelize Orchestrtor Restore Process vrelize Opertions Mnger Restore Process vrelize Log Insight Restore Process vrelize Business Restore Process vrelize Suite Strtup Order You should strt up the VMs for vrelize Suite components in specific order. Overll Strtup Order vrelize Automtion vrelize Orchestrtor vrelize Opertions Mnger vrelize Log Insight vrelize Business VMwre, Inc. 23

24 Depending on the vrelize Suite components tht you hve cked up, restore your vrelize Suite components in the specified order. If you hve tken ny snpshots, you must remove the snpshots efore you restore. 1 vrelize Automtion. Strt up the vrelize Automtion components in the following order: c d e f g h MS SQL PostgreSQL, if pplicle vrelize Automtion Applinces Wesites Mnger Services DEM vrelize Orchestrtor DEM Workers Proxy Agents 2 vrelize Orchestrtor. You cn tke strt up the vrelize Orchestrtor VMs in no prticulr order. 3 vrelize Opertions Mnger. All nodes cn strt t the sme time. 4 vrelize Log Insight. Strt up the mster node, followed y VMs with the worker nodes in ny order. 5 vrelize Business. Strt up the VM for vrelize Business. vrelize Automtion System Recovery A system dministrtor uses ckups to restore vrelize Automtion to functionl stte fter system filure. If IS components such s Mnger Service mchines fil, you must reinstll them. If you restore from ckup, mchines tht were provisioned fter the ckup still exist, ut re not mnged y vrelize Automtion. For exmple, they do not pper in the items list for the owner. Use the Infrstructure Orgnizer to import virtul mchines nd ring them ck under mngement. You must strt up your vrelize Automtion components in specified order. VMwre, Inc. 24

25 Restoring vrelize Automtion Dtses A system dministrtor restores the IS MSSQL dtse nd the PostgreSQL dtse. Recover dtse in the following situtions: If oth dtses fil, restore them from the lst known time when oth dtses were cked up. If one dtse fils, restore it nd revert the functionl dtse to the version tht ws in use when the ckup used to restore the filed dtse ws creted. The ckup time for ech dtse cn differ. The greter the gp etween the lst working time of the dtses, the greter the potentil for dt loss. VMwre, Inc. 25

26 You should ck up full VMs of dtses, insted of cking up PostgreSQL dtse directly. For informtion out how to restore PostgreSQL dtse, see the VMwre Knowledge Bse rticle Migrting from externl vpostgres pplince to vpostgres instnce locted in the vcac pplince ( ). Dtse Pssphrses IS MSSQL dtse security requires security pssphrse to generte n encryption key tht protects the dt. You specify this pssphrse when you instll vrelize Automtion. If you lose the pssphrse, or wnt to chnge the pssphrse, consult VMwre technicl support for more informtion. Restoring the vrelize Automtion Applince nd Lod Blncer If filure occurs, system dministrtor restores the vrelize Automtion pplince. If lod lncer is used, the dministrtor restores the lod lncer nd the virtul pplinces tht it mnges. For vrelize Automtion 7.0, you cnnot chnge the host nmes during restortion. You might need to restore filed virtul pplince in the following circumstnces: You re running miniml deployment nd your only vrelize Automtion pplince fils or ecomes corrupted. You re running distriuted deployment nd some, ut not ll, virtul pplinces fil. You re running distriuted deployment nd ll virtul pplinces fil. How you restore vrelize Automtion pplince or virtul pplince lod lncer depends on your deployment type nd on which pplinces filed. If you re using single virtul pplince whose nme is unchnged, restore the virtul pplince, or redeploy it nd restore set of cked up files. No further steps re required. If you re running distriuted deployment tht uses lod lncer, nd you chnge the nme of the virtul pplince or the virtul IP ddress of the lod lncer, you must redeploy the pplince nd restore its cked up VMs or files. Also, you must regenerte nd copy certifictes for your deployment. If you re redeploying, reconfiguring, or dding virtul pplinces to cluster, see Instlltion nd Configurtion documenttion for vrelize Automtion pplince in the vrelize Automtion product documenttion for more informtion. Restoring the IS Wesite, Mnger Services, nd Their Lod Blncers A system dministrtor restores the IS Wesite nd Mnger Service nd their ssocited lod lncers. VMwre, Inc. 26

27 Restoring the DEM Orchestrtor nd the DEM Workers If filure occurs, system dministrtor restores ll DEMs from the ville ckups. Restoring the IS Agents The system dministrtor restores ll the IS gents from the ville ckups. If you reinstll vsphere gents, use the sme endpoint nme used t ckup. Restore vrelize Automtion in n Isolted Environment A system dministrtor cn use ckups to restore vrelize Automtion in n environment tht is isolted from other networks. Prerequisites Verify tht the environment hs DNS server with identicl zones nd records to the production server nd tht the vrelize Automtion virtul pplince nd Windows nd IS servers re configured to work with it. Procedure 1 Configure the vrelize Automtion virtul pplince. c d e f g h Check the vrelize Automtion virtul pplince PostgreSQL sttus, nd reset secondry node if needed. If the primry node is unle to strt, reset RitMQ on the primry node. Shut down the secondry node. Restrt the primry node. Wit 30 seconds, nd restrt the secondry node. Verify tht the primry server hs ll services except IS s Registered. If needed, perform join cluster opertion on the secondry node. Verify tht oth servers hve ll services except IS s Registered. If the environment uses Active Directory, you cn skip ll following steps. VMwre, Inc. 27

28 2 Configure IS mchine uthentiction. Option Using locl dministrtive ccount Using the locl system ccount Description This option is the most secure nd simultes production environment with n Active Directory nd Integrted Authentiction to the SQL server, so tests cn e closer to relity. Crete user with dministrtive privileges nd with the sme user nme nd pssword on ll servers, including the SQL server. Grnt this user sysdmin rights on the SQL Server nd owner rights on the IS dtse. You cn lso modify the connection string to reflect this new user or configure it to use SQL uthentiction. This option is less secure nd might cuse prolems with the mnger service uthenticting to the We repository. Strt ll services with the locl system ccount nd grnt the locl system ccounts on ll servers sysdmin rights on the SQL Server nd owner rights on the IS dtse. 3 Configure the We IS mchine. Check connection string in the we.config file of the Model Mnger We instlltion folder nd modify it ccording to the ccount you used for IS mchine uthentiction. If you re using SQL uthentiction, it should look similr to the following: Mx Pool Size=200;MultipleActiveResultSets=True;Connect Timeout=200;User Id=s;Pssword=pssword;" /> c Chnge the IIS IS ppliction pools to use the ccount you used for IS mchine uthentiction. Restrt the IIS services y running iisreset in commnd prompt on the IS We severs. 4 Configure the Mnger Service IS mchine. If the mchine running the SQL server is prt of filover cluster, disle the cluster service nd reoot the mchine. If the SQL server is prt of filover cluster, disle the cluster service nd reoot the SQL server. If the mchine running the SQL server is prt of filover cluster, the cluster service does not work ecuse there is no Active Directory. In filover cluster, the MSDTC service is controlled y the cluster service. When the Active Directory domin is missing, the cluster service is not le to ring up its resources nd keeps the DTC in locked stte. When you disle the cluster service nd reoot the mchine running the SQL server, this unlocks the locl DTC, nd the Mnger Service cn successfully initilize. c Enle NoAuthentictionRequired on the DTCs of oth the SQL server nd the mnger server from their respective component services console. 5 On the DEM Orchestrtor IS mchine, chnge the service ccount to the ccount you used for IS mchine uthentiction. VMwre, Inc. 28

29 6 Chnge the mngement gent service ccount on ll IS mchines to the ccount you used for IS mchine uthentiction. (Optionl) Chnge the IP Addresses of vrelize Automtion Applinces After Restore You should perform these steps, only if you hve chnged the IP ddresses of the vrelize Automtion pplinces fter the restore of vrelize Automtion hs strted. This is workround in order to get the vrelize Automtion up nd running fter the restore, if you hve chnged the IP ddresses during the restore process. If you hve chnged the IP ddresses of the vrelize Automtion pplinces during the restore process, you must perform the following steps in order to hve the vrelize Automtion opertionl fter the restore. Procedure 1 Chnge the DNS server so tht the FQDNs of ll the vrelize Automtion mchines points to the new IP ddresses. 2 Add the new IP ddresses in the lod lncer pools, such s virtul pplinces, we, nd mnger. 3 Updte the /etc/hosts file for ech of the vrelize Automtion VA nodes with the new IP ddresses. 4 Updte the /etc/sysconfig/elsticserch for ech of the vrelize Automtion VA nodes with the new IP ddresses. 5 Restrt ll the vrelize Automtion VA Nodes. You should now e le to strtup vrelize Automtion. Strt Up vrelize Automtion When you strt vrelize Automtion from the eginning, such s fter power outge, controlled shutdown or fter recovery, you must strt its components in specified order. Prerequisites Verify tht the lod lncers tht your deployment uses re running. Procedure 1 Strt the MS SQL dtse mchine. If you re using legcy PostgreSQL stndlone dtse, strt tht mchine s well. 2 (Optionl) If you re running deployment tht uses lod lncers with helth checks, disle the helth check efore you strt the vrelize Automtion pplince. Only ping helth check should e enled. VMwre, Inc. 29

30 3 Strt ll instnces of vrelize Automtion pplince t the sme time nd wit for pproximtely 15 minutes for the pplinces to strtup. Verify tht the vrelize Automtion pplince services re up nd running. If you hve more thn one node nd you strt only one node, you my hve to wit for extr 35 minutes. However, the extr wit time would e cnceled out s soon s you strt the second node. 4 Strt the primry We node nd wit for the strtup to finish. 5 (Optionl) If you re running distriuted deployment, strt ll secondry We nodes nd wit 5 minutes. 6 Strt the primry Mnger Service mchine nd wit for 2 to 5 minutes, depending on your site configurtion. 7 (Optionl) If you re running distriuted deployment, strt secondry Mnger Service mchines nd wit 2 to 5 minutes. On secondry mchines, do not strt or run the Windows service unless you re configured for utomtic Mnger Service filover. 8 Strt the Distriuted Execution Mnger Orchestrtor nd Workers nd ll vrelize Automtion proxy gents. You cn strt these components in ny order nd you do not need to wit for one strtup to finish efore you strt nother. 9 If you disled helth checks for your lod lncers, reenle them. 10 Verify tht the strtup succeeded. c Open We rowser to the vrelize Automtion pplince mngement interfce URL. Click the Services t. Click the Refresh t to monitor the progress of service strtup. When ll services re listed s registered, the system is redy to use. Vlidte vrelize Automtion After the recovery is complete, you must vlidte tht the environment nd ppliction functionlity is restored. Procedure 1 Verify tht the vrelize Automtion services re registered on oth virtul pplinces. Log in to the vrelize Automtion Console on of VM>:5480/ y using root credentils. Click the Services t to verify tht the vrelize Automtion services hve the sttus of Registered nd the IS service is running. VMwre, Inc. 30

31 2 Verify tht the PostreSQL repliction is connected. c Log in to the vrelize Automtion Console on of VM>:5480/ y using root credentils. Click the vra Settings t nd click Dtse. Verify tht the Connection Sttus is CONNECTED. 3 Verify tht RitMQ is registered correctly on ll virtul pplinces. c Click vrelize Automtion Settings > Messging t. Verify tht ll virtul pplinces hve Running sttus of Yes. Verify tht the Connection Sttus is CONNECTED. If RitMQ fils to register correctly, see KB to reset RitMQ. 4 Verify virtul pplince nd IS service lst connected sttus. c Click vrelize Automtion Settings nd click Cluster. Verify tht ech virtul pplince node hs Lst Connected time of 9 minutes or less. Verify tht ech IS node hs Lst Connected time of three minutes or less. Verify tht ll services re in sync. 5 On the node where you instlled We IS, verify tht there re no errors displyed in Event Viewer > Administrtive Events. 6 Verify tht the We IS service is initilized. In your rowser, nvigte to Verify tht the displyed file contins the string "serviceintitiliztionsttus":"registered". 7 Verify tht the Model Mnger We log repository contins no exceptions. c Nvigte to C:\Progrm Files (x86)\vmwre\vcac\server\model Mnger We\Logs\Repository. Verify tht the file contins no exceptions. Verify tht the file contins the following strings: Model TrckingModel service hs een initilized. Model MetModel service hs een initilized. Model CoreModel service hs een initilized. 8 On the node where you instlled the mnger service, verify tht the VMwre vcloud Automtion Center service is running. 9 Verify tht the mnger service log contins no errors. Nvigte to C:\Progrm Files (x86)\vmwre\vcac\server\logs\all.log. Verify tht there re no exception errors fter the string Mnger service strted for processed workflows. VMwre, Inc. 31

32 10 In your rowser, nvigte to nd verify tht it contins n XML file similr to the following: - <wsdl:service nme="proxyagentservice"> - <wsdl:port nme="bsichttpbinding_vmpsproxyagent" inding="tns:bsichttpbinding_vmpsproxyagent"> <sop:ddress loction=" 11 On the node where you instlled DEM Orchestrtor, verify tht the DEM Orchestrtor services re running. 12 Nvigte to C:\Progrm Files (x86)\vmwre\vcac\distriuted Execution Mnger\DEMONme-hostnme DEO\Logs\hostnme DEO_All.log, nd verify ll processed nd scheduled workflows. 13 On the node where you instlled DEM Worker, verify tht the DEM Worker services re running. 14 Nvigte to C:\Progrm Files (x86)\vmwre\vcac\distriuted Execution Mnger\DEMNme\Logs\DEMNAME_All.log, nd verify ll executed workflows. 15 On the node where you instlled the Proxy Agent, verify tht the Proxy Agent services re running. 16 Nvigte to C:\Progrm Files (x86)\vmwre\vcac\agents\agentnme\logs\vsphereagent.log, nd verify tht the gent cn successfully connect to the mnger service nd tht it is ttempting to connect to the endpoint. 17 Verify tht you cn log in to ll tennts with externl directory credentils if ville or vsphere.locl credentils. 18 In the vrelize Automtion Console, verify tht the Infrstructure t lods successfully. 19 In the vrelize Automtion Console, click the Monitoring t nd verify tht the DEM services hve green sttus. 20 If you re vlidting vrelize Automtion version 7.2, click the Continers t in the vrelize Automtion Console, nd verify tht the t lod successfully nd displys ll connected servers. 21. Click Administrtion > Helth, nd configure nd run system nd tennt tests using vrelize Automtion helth service. IS dministrtors cn configure the helth service to run tests tht ssess the helth of selected vrelize Automtion virtul mchine. These tests tell you if the components re registered nd ll the necessry resources re ville. See Monitoring vrelize Automtion Helth. 22 Click Infrstructure > Mnged Mchines, nd verify tht ll the mnged virtul mchines re present. 23 Click Infrstructure > Compute Resources, select ech endpoint, nd click Dt Collection, Request now, nd Refresh to verify tht the endpoints re working. 24 Click Administrtion > Ctlog Mngement, nd verify the contents listed under Services, Ctlog Items, Actions, nd Entitlements. VMwre, Inc. 32

33 25 Click Design > Blueprints, nd verify the elements of ech lueprint. 26 Click Design > XS, nd verify the contents listed under Custom Resources, Resource Mppings, XS Blueprints, nd Resource Actions. 27 Verify the detils for the provisioned virtul mchines. c d e Click Items > Deployment. Select provisioned, powered-off virtul mchine, nd select Actions > Power On. Click Sumit, nd click OK. Verify tht the virtul mchine powers on correctly. Repet these steps for ll provisioned virtul mchines. 28 Request new ctlog item. c d e Click Ctlog nd request new ctlog item. On the Generl t, enter the request informtion. Click the mchine icon nd ccept the defult settings. Click Sumit, nd click OK. Verify tht the request completes successfully. 29 Recrete or updte the contents creted or updted fter ckup. Virtul mchines provisioned fter ckup still exist on vcenter, ut they lose their mngement. You cnnot use ulk import to ring these virtul mchines under mngement. They must e deleted mnully in vcenter. vrelize Orchestrtor Restore Process A system dministrtor uses ckups to restore vrelize Orchestrtor to functionl stte fter system filure. After you restore the imges from the ckup, you must power the nodes on in ny order. vrelize Orchestrtor Strtup Order Node1 Node2 Noden (Nodes in ny order) The vrelize Orchestrtor server sttus ppers s Service is strting. The first oot cn tke 5 to 10 minutes ecuse the server is instlling the vrelize Orchestrtor plug-in's content in the dtse tles. A messge sttes tht the service hs strted successfully. VMwre, Inc. 33

34 Vlidte vrelize Orchestrtor After the recovery is complete, you must vlidte tht the environment nd ppliction functionlity is restored. Procedure 1 Log in to the vrelize Orchestrtor node 1 pplince configurtion We interfce t 2 Restrt the vrelize Orchestrtor service from the Strtup options pge nd wit for the service to strt. 3 Log in to the vrelize Orchestrtor node 2 pplince configurtion We interfce t 4 Restrt vrelize Orchestrtor service from the Strtup options pge nd wit for the service to strt. 5 Ensure tht your MSSQL dtse host server is running. 6 Ensure tht the two vrelize Orchestrtor nodes re working in cluster mode. 7 Verify tht every t in the configurtion is green. 8 Log in to the vrelize Orchestrtor server nd verify tht ll the running tsks, policies, nd workflows pper nd continue running on the home pge. vrelize Opertions Mnger Restore Process A system dministrtor uses ckups to restore vrelize Opertions Mnger to functionl stte fter system filure. You must strt the vrelize Opertions Mnger components in specified order fter the restore is complete. Common Restore Scenrios The common restore scenrios for vrelize Opertions Mnger systems include full restore of single-node virtul pplince system nd restore of multiple-node virtul pplince clusters. Stisfy the following prerequisites for the vrelize Opertions Mnger cluster. Power off the virtul mchines in the multi-node cluster tht you wnt to restore. Before restoring to different host, power off virtul mchines t the originl loction, nd then ring up the environment on the new host to void hostnme or IP conflict. Verify tht the dtstore on the new host hs sufficient cpcity for the new cluster. Verify tht ll VMDK files hve een ssigned to the sme dtstore. Bck up the vrelize Opertions Mnger multi-node cluster. VMwre, Inc. 34

35 Single-Node Virtul Applince This scenrio restores single node system on the sme host. 1 After the restore is complete, power on the VM. 2 Verify tht you hve set up sttic IP ddress for the node nd tht the IP ddress is restored. 3 Log in to the node to verify tht ll your dt is preserved nd tht ll vmwre-vcops services re running. 4 If your root pssword ws reset, you must chnge it now. For incrementl ckups, user must crete cumultive differentil policy. Every ckup fter full ckup is n incrementl ckup. Note If you restore to nother host, you must power off the environment t the originl loction nd strt the environment on the new host. Multiple-Node Virtul Applince Clusters This scenrio restores multiple-node virtul pplince clusters. 1 After the restore is complete, you must power on the nodes in the following order: c d mster replic dt remote collector Ensure tht ech node is online efore ttempting to strt the next component. 2 Verify tht you hve set up sttic IP ddress for the node nd tht the IP ddress is restored. 3 Log in to the dministrtor interfce of the mster node nd verify tht ll the nodes re online nd running. Log in to ech node to verify tht ll your dt is preserved nd ll of the vmwre-vcops services re up nd running y using the vmwre-vcops sttus commnd. 4 Log in to the dministrtor interfce of the mster node. Verify tht high vilility is enled. If the Enle High Avilility utton ppers, high vilility ws disled during the ckup nd restore process. Enle high vilility. Verify tht ll nodes re collecting metrics. 5 If your root pssword ws reset, you must chnge it now. 6 (Optionl) If node in non-high vilility cluster does restrt, you must tke it offline with the dministrtor interfce. 7 (Optionl) If the replic node in high vilility cluster does not restrt, you must ssign new mster-replic node. VMwre, Inc. 35