Disaster Recovery Hybrid Cloud

1y ago
8 Views
1 Downloads
3.82 MB
76 Pages
Last View : 1d ago
Last Download : 2m ago
Upload by : Luis Wallis
Transcription

acronis.comDisaster Recovery HybridCloud22.02Administrator GuideREVISION: 3/21/2022

Table of contentsIntroduction5Infrastructure planning7Planning capacity for new deployment of Backup and DR infrastructurePlanning capacity for a backup storage77Option 1. Compute (with disks for hot storage) cluster and storage (with disks for cold storage)cluster7Option 2. Hyperconverged cluster9Planning capacity for DR infrastructure10General hardware recommendations10Compute (with hot disks) cluster10Network infrastructure requirements11Evaluation configuration for testing purposes11Deployment procedure13Deployment scenarios13Prerequisites14Deploying Acronis Cyber Infrastructure14Deploying Acronis Cyber Infrastructure on a hardware node15ACI infrastructure traffic type configuration23ACI compute networking configuration24Deploying the Disaster Recovery infrastructure36Step 1. Download the Disaster Recovery installation archive36Step 2. Prepare the configuration file37Step 3. Run the DR installer37Step 4. Register the DR infrastructure in Acronis Cyber Cloud38Step 5. Prepare templates for primary servers and upload them to Acronis CyberInfrastructureMaintenance40Creating templates for primary servers40Uploading templates for primary servers41Update procedure43Scaling procedure44Deletion procedure45Troubleshooting46How to collect logs for further investigationAppendix A. The default config.yml2394648 Acronis International GmbH, 2003-2022

Appendix B. Working with the dr-installer tool66Appendix C. Disaster Recovery architecture and components67Appendix D. Calculating hardware needs69Calculating hardware needs for a compute cluster69Predefined parameters for hardware needs calculationsCalculating hardware needs for a storage cluster70Predefined parameters for hardware needs calculationsExample of hardware needs calculation707171Appendix F. Direct routing to the Backup storage73Helpful links74Index753 Acronis International GmbH, 2003-2022

Copyright statement Acronis International GmbH, 2003-2022. All rights reserved.All trademarks and copyrights referred to are the property of their respective owners.Distribution of substantively modified versions of this document is prohibited without the explicitpermission of the copyright holder.Distribution of this work or derivative work in any standard (paper) book form for commercialpurposes is prohibited unless prior permission is obtained from the copyright holder.DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THEEXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.Third party code may be provided with the Software and/or Service. The license terms for suchthird-parties are detailed in the license.txt file located in the root installation directory. You canalways find the latest up-to-date list of the third party code and the associated license terms usedwith the Software and/or Service at https://kb.acronis.com/content/7696Acronis patented technologiesTechnologies, used in this product, are covered and protected by one or more U.S. Patent Numbers:7,047,380; 7,246,211; 7,275,139; 7,281,104; 7,318,135; 7,353,355; 7,366,859; 7,383,327; 7,475,282;7,603,533; 7,636,824; 7,650,473; 7,721,138; 7,779,221; 7,831,789; 7,836,053; 7,886,120; 7,895,403;7,934,064; 7,937,612; 7,941,510; 7,949,635; 7,953,948; 7,979,690; 8,005,797; 8,051,044; 8,069,320;8,073,815; 8,074,035; 8,074,276; 8,145,607; 8,180,984; 8,225,133; 8,261,035; 8,296,264; 8,312,259;8,347,137; 8,484,427; 8,645,748; 8,732,121; 8,850,060; 8,856,927; 8,996,830; 9,213,697; 9,400,886;9,424,678; 9,436,558; 9,471,441; 9,501,234; and patent pending applications.4 Acronis International GmbH, 2003-2022

IntroductionThis guide describes the Disaster Recovery (DR) hybrid deployment case when Acronis Cyber Cloudis deployed in the Acronis data center, while the backup storage and disaster recovery infrastructureare deployed on the partner's premises.The guide describes how to deploy and configure the Acronis Cyber Protect Cloud with AdvancedDisaster Recovery service on top of Acronis Cyber Infrastructure.The Disaster Recovery infrastructure is a set of software components that you must install onAcronis Cyber Infrastructure, and register in Acronis Cyber Cloud as an infrastructure entity withdisaster recovery capabilities.This document assumes that you are familiar with the following products:lLinuxlAcronis Cyber CloudlAcronis Cyber InfrastructureWith the DR hybrid deployment, partners can build their own Disaster Recovery infrastructure toachieve optimal configuration and control costs.5 Acronis International GmbH, 2003-2022

For more details about the Disaster Recovery architecture and main components, refer to"Appendix C".6 Acronis International GmbH, 2003-2022

Infrastructure planningThis section describes different options of deployment of the backup storage and DR infrastructure.Planning capacity for new deployment of Backup and DRinfrastructureIf you don't have backup storage deployed, then follow the instructions in this section. It describestwo options for deploying the backup storage and DR infrastructure.Planning capacity for a backup storageThe backup storage requires deployment of a storage cluster.The Acronis Cyber Infrastructure storage cluster is a group of physical nodes connected to eachother by network. Each of the nodes has one or several roles and runs the corresponding servicesaccording to its role.The Acronis Cyber Infrastructure storage cluster consists of a single management node and anumber of storage nodes.To organize a backup storage, do the following:1. Plan the infrastructure for the backup storage cluster. Consider the hardware requirements forthe storage node depending on a usage scenario, the minimum configuration for a storagecluster, the recommended configuration for a storage cluster, and the network hardwarerecommendations.For more information, see Acronis Cyber Infrastructure Installation Guide.2. Install and configure Acronis Cyber Infrastructure. For more details about the installationprocedure, see Installing Acronis Cyber Infrastructure.3. Configure the networks in Acronis Cyber Infrastructure. For more details, see Configuringnetworks.4. Create the storage cluster. For more details, see Creating the storage cluster.Option 1. Compute (with disks for hot storage) cluster and storage(with disks for cold storage) clusterIf you want a separate compute cluster with only compute resources (without disks) and a separatecluster with hot and cold storage, then you may use this deployment case.Minimum configurationThe infrastructure parameters listed below provide the following protected environment profile:100 tenants, 500 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of HDD, 500 GB of7 Acronis International GmbH, 2003-2022

SSD. About 10% of the protected virtual machines (50 VMs) can run simultaneously on the specifiedbelow infrastructure.The minimum required number of nodes for the DR infrastructure deployment:lThree compute nodeslThree storage nodesCompute resourcesServer nameCompute nodeCPU32 coresRAM256 GBDisaster Recovery storage (hot) and Backup storage (cold)Server nameStorage nodeCPU8 coresRAM32 GBDisk9 x 1,86 TB SSD, 4 x 6 TB HDDProduction configurationThe infrastructure parameters listed below provide the following protected environment profile:100 tenants, 1000 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of HDD, 500 GB ofSSD. About 10% of the protected virtual machines (100 VMs) can be run simultaneously on thespecified below infrastructure.The minimum required number of nodes for the DR infrastructure deployment:lFive compute nodeslSix storage nodesCompute resourcesServer nameCompute nodeCPU24 coresRAM256 GBDisaster Recovery storage (hot) and Backup storage (cold)Server name8Storage node Acronis International GmbH, 2003-2022

CPU8 coresRAM32 GBDisk9 x 1,86 TB SSD, 4 x 6 TB HDDOption 2. Hyperconverged clusterA hyperconverged cluster implies that each cluster node has compute resources, hot and cold disks.Below you will find the minimum and production configurations.Minimum configurationThe infrastructure parameters listed below provide the following protected environment profile:100 tenants, 500 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of HDD, 500 GB ofSSD. About 10% of the protected virtual machines (50 VMs) can be run simultaneously on thespecified below infrastructure.To deploy the DR infrastructure, you need a minimum of three compute nodes.Compute resources, hot and cold storageServer nameCompute node with disks for storageCPU32 coresRAM512 GBDisks6 x 8 TB SSD (hot)4 x 16 TB HDD (cold)Production configurationThe infrastructure parameters listed below provide the following protected environment profile:100 tenants, 1000 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of HDD, 500 GB ofSSD. About 10% of the protected virtual machines (100 VMs) can be run simultaneously on thespecified below infrastructure.To deploy the DR infrastructure, you need a minimum of five cluster nodes.Compute resources, hot and cold storageServer nameCompute node with disks for storageCPU32 coresRAM512 GBDisks2 x 8 TB SSD (hot)9 Acronis International GmbH, 2003-2022

3 x 16 TB HDD (cold)Planning capacity for DR infrastructureIf you already have a backup storage deployed, you may deploy only the DRinfrastructure. Itrequires deployment of a compute cluster with disks for hot storage.General hardware recommendationsAcronis Cyber Infrastructure works on the same hardware that is recommended for Red HatlEnterprise Linux 7 (servers, and hardware components).General considerations:loOne of the strongest features of Acronis Cyber Infrastructure is scalability. The bigger thecluster, the better Acronis Cyber Infrastructure performs.oIt is not recommended for production to run Acronis Cyber Infrastructure on top of SAN/NAShardware that has its own redundancy mechanisms.oTo achieve best performance, keep at least 20% of cluster capacity free.oIt is recommended to have the same CPU models on each node to avoid virtual machine livemigration issues.Compute (with hot disks) clusterIf you already have a backup storage (cold) and you want to add the DR infrastructure, then you mayuse this deployment case. Below you will find the minimum and production configurations.Minimum configurationThe infrastructure parameters listed below provide the following protected environment profile:100 tenants, 500 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of HDD, 500 GB ofSSD. About 10% of the protected virtual machines (50 VMs) can be run simultaneously on thespecified below infrastructure.To deploy the DR infrastructure, you need a minimum of three compute nodes.Compute resources and Disaster Recovery storage (hot)Server nameCompute nodeCPU32 coresRAM512 GBDisk8 x 2 TB SSD10 Acronis International GmbH, 2003-2022

Production configurationThe infrastructure parameters listed below provide the following protected environment profile:100 tenants, 1000 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of HDD, 500 GB ofSSD. About 10% of the protected virtual machines (100 VMs) can be run simultaneously on thespecified below infrastructure.To deploy the DR infrastructure, you need a minimum of three compute nodes.Compute resources and Disaster Recovery storage (hot)Server nameCompute nodeCPU32 coresRAM512 GBDisk8 x 2 TB SSDNetwork infrastructure requirementsLogical component requirementsPublic IP: 1 per Hybrid DR cluster (HA Proxy deployed) for the dmzvpn network. n IP addresses for customer environments (optional). These IP addresses are for customers whowant a public IP address for their DR workloads.Required minimum network infrastructureEnterprise-level network adapters, 2x 10 Gbit in the XOR or LACP bonding modeRecommended network infrastructureEnterprise-level network adapters, 6x 10 Gbit in the XOR or LACP bonding modeRecommended network configurationsFor more information about the networks that you must configure before deploying the DRinfrastructure, see "ACI infrastructure traffic type configuration" (p. 23).NoteDisaster Recovery Hybrid Cloud supports only the local Acronis Cyber Infrastructure cluster storagespace for backups.Evaluation configuration for testing purposesFor testing and evaluation purposes, you may use this deployment option.The infrastructure parameters listed below provide the following protected environment profile: 1tenant, 50 protected virtual machines with 2 vCPU, 8 GB of RAM, 250 GB of SSD, 500 GB of HDD.11 Acronis International GmbH, 2003-2022

About 10% of the protected virtual machines (5 VMs) can be run simultaneously on the specifiedbelow infrastructure.For the evaluation purpose of the DR infrastructure, you may use one node with compute andstorage services.Compute resources, hot and cold storagesServer nameCompute node with storageCPU16 coresRAM128 GBDisks3 x 1.86 TB SSD (hot)5 x 6 TB HDD (cold)12 Acronis International GmbH, 2003-2022

Deployment procedureTo deploy the DR infrastructure on Acronis Cyber Infrastructure, do the following:1. Check all of the prerequisites.2. Prepare nodes according to the hardware and software requirements and check the networkand firewall requirements.3. Check the "Deployment scenarios" (p. 13) to identify the deployment procedures that you mustcomplete depending on the state of your environment.4. Complete the deployment procedures.Deployment scenariosThe deployment and configuration of Disaster Recovery Hybrid Cloud consists of several proceduresthat you can perform sequentially.1."Deploying Acronis Cyber Infrastructure" (p. 14) on a hardware node. This procedure is valid forthe management node, and for the rest of the nodes in your environment.NoteThe recommended number of network adapters for the deployment of Disaster RecoveryHybrid Cloud is six, while the required minimum number of network adapters is two.If your node has less than six physical networks adapters, you must add the correspondingnumber of virtual network interfaces, so that the total number of network adapters and virtualnetwork adapters becomes six. To do that, follow the procedure: "Creating VLAN adapters" (p.24).If your node has six physical networks adapters, skip the procedure.a. "Creating VLAN adapters" (p. 24), if necessary. This procedure is valid for the managementnode, and for the rest of the nodes in your environment.b. "Creating infrastructure networks" (p. 25). This procedure is valid for the management nodeonly.c. "Assigning network adapters to networks" (p. 25). This procedure is valid for the managementnode, and for the rest of the nodes in your environment.d. "Assigning traffic types to the infrastructure networks" (p. 25). This procedure is valid for themanagement node only.2. "Creating a storage cluster" (p. 27)3. "Creating a compute cluster" (p. 28)a. Configuring the compute cluster.b. Configuring the networks of the compute cluster, as described in "Creating virtual networks"(p. 31)4. "Adding nodes to the compute cluster" (p. 35)5. "Deploying the Disaster Recovery infrastructure" (p. 36)13 Acronis International GmbH, 2003-2022

The procedure you start from depends on the current state of your Acronis Cyber Infrastructure.If your environment is new and does not have any of the components, complete all procedures inthe "Deployment procedure" (p. 13) section, starting from the beginning.If in your environment Acronis Cyber Infrastructure is installed on the hardware node, but nofurther configuration is done, start from "Creating VLAN adapters" (p. 24) and complete all theprocedures that follow.If in your environment Acronis Cyber Infrastructure is installed on the hardware node, and youalready have a storage cluster, check if the configurations are correct, and then complete all theprocedures starting from "Creating a compute cluster" (p. 28).If in your environment Acronis Cyber Infrastructure is installed on the hardware node, and youalready have a storage cluster and a compute cluster, check if the configurations are correct, andthen complete all the procedures starting from "Deploying the Disaster Recovery infrastructure" (p.36).PrerequisitesThe following prerequisites must be met prior to the DR infrastructure deployment:lOn the machine where the DR installer will be run, generate the RSA SSH key pair for the accessto Acronis Cyber Infrastructure or use the existing SSH key pair. Upload the public key to theAcronis Cyber Infrastructure node by doing the following:1. In the Acronis Cyber Infrastructure admin panel, go to Settings Security SSH tab.2. Click Add.3. Copy your public key, paste it in the Key field, and click Add key.For more information about SSH keys, see Adding SSH keys for virtual machines.lYou must have a partner administrator account in Acronis Cyber Cloud.lA stable connection must be available between the machine on which you will run the DR installerand the target data center where you will deploy the DR infrastructure.Deploying Acronis Cyber InfrastructureThe deployment procedure of Acronis Cyber Infrastructure consists of several stages. Depending onyour existing infrastructure, follow all the stages of the procedure, or follow specific stages that aresuitable for your existing infrastructure.NoteDisaster Recovery Hybrid Cloud supports:ll14Acronis Cyber Infrastructure version 4.7 Update 1 or laterVirtuozzo Hybrid Infrastructure version 4.7 Update 1 or later Acronis International GmbH, 2003-2022

Deploying Acronis Cyber Infrastructure on a hardware nodeYou must install Acronis Cyber Infrastructure on a hardware node.To install Acronis Cyber Infrastructure on a hardware node1. Download the iso image with Acronis Cyber Infrastructure software and prepare the installationdisk. For more information, see How to download ISO (63431).2. Mount the disk in the driver and run the installation. The wizard opens.3. Accept the license terms, and click Next.4. In the Host name field, type the name of the node.5. Define the date and time for your node, and click Next.6. At the Cluster configuration step, when you configure the first node, choose Yes, create anew cluster. If it is not the first node, choose No, add it to an existing cluster.15 Acronis International GmbH, 2003-2022

In Internal management network, select a network interface for internal management andconfiguration purposes. This network interface will be automatically assigned to the Privatenetwork.In Admin panel network, select a network interface that will provide access to the admin panel.This network interface will be automatically assigned to the Private network.For more information about the Private and Public networks, see Acronis Cyber InfrastructureInstallation Guide.Type the password for the admin panel.When ready, click Next.7. Choose the disk where the system will be installed, and click Next.16 Acronis International GmbH, 2003-2022

8. Type the password for the root account.Click Start installation.As a result, Acronis Cyber Infrastructure will be installed on the node. Now go to Settings Licenses,and activate the Acronis Cyber Infrastructure license.Repeat the procedure for all hardware nodes on which you want to deploy the DR infrastructure.Note that in step 6, you must choose the No, add it to an existing cluster option.You can access the Acronis Cyber Infrastructure admin panel by using the following URL:https://first-node-ip:8888.17 Acronis International GmbH, 2003-2022

Configuring networks and clusters in Acronis Cyber InfrastructureNetwork and firewall requirementsBefore deploying the DR infrastructure, you must create and configure the following networks inAcronis Cyber Infrastructure:NameNetworkDescriptionTypeDMZ VPNPhysical(dmzvpn)ManagementThe public-facing VPN gateways and their proxies. It is used for publicaccess to the servers over the Internet.Physical(drmgmt)The network required for general communications between theRunVM components, for outbound access to the Acronis cloud, and forthe Acronis Cyber Infrastructure OpenStack API access.ContentPhysical(content)The network required for transferring backed-up data by using theNBD protocol between the RunVM components and the Acronis CyberInfrastructure nodes.Note that this network is unprotected and not encrypted users' backupdata are passed.StoragePhysical(drcoldstorage)PrivateThe network providing fast, direct access to the cold storage backupgateway that contains customer backups.VirtualThe network that is used for storage traffic.This network is created automatically when you deploy Acronis CyberInfrastructure. If you are using an existing Acronis Cyber Infrastructure,the network may have been renamed.PublicVirtualThe network that is used for overlay network traffic between virtualmachines.This network is created automatically when you deploy Acronis CyberInfrastructure. If you are using an existing Acronis Cyber Infrastructure,the network may have been renamed.In the diagram below, you can find these networks.18 Acronis International GmbH, 2003-2022

General requirements to networksAll networks must meet the following requirements:lThe address assignment in all networks must be managed by Acronis Cyber Infrastructure. Whencreating the network in the UI, you must enable DHCP.lThere are no external DHCP servers in any of the networks.Firewall requirements: protocols and portsYou must set the following firewall rules to ensure that Disaster Recovery works properly.VLANProtocolTCP 43Acronis CyberRunVM agent, RunVMInfrastructureController ABGWACI Acronis:44445, :443BackupGateway(ABGW)This VLAN is neededwhen the backupstorage is separatefrom the DR cluster.dmzvpnVRRPn/aACI ACIVRRP traffic amonghighly available proxynodes (to be deployedon different ACI nodes)19 Acronis International GmbH, 2003-2022

VLANProtocolTCP portsConnectionCommentsdirectionTCP443Internet ACIVPN traffic from thelocal clientenvironments to theVPN serversTCP/UDP any Internet ACIAny traffic directed toclient servers must beallowed (Furtherfiltering must beconfigured on eachVPN Server) any any ACI InternetRecovery/primaryservers can freelyconnect to the InternetresourcescontentTCP10809ACI ACIAuxiliary VM RunVMController (NBD49300-65535server) :10809ACI (internal NBDserver) Auxiliary OpenStackAPI ports(see defaultOpenStackports)9090ACI ACIACI (a serviceworkstation) RunVMAgent, RunVMController,PostgreSQL, CoreCollector :22 (sshaccess fortroubleshooting)RunVM Agent RunVM Controller:2650 (to manageController)RunVM Agent, RunVMController PostgreSQL :5432 (toacquire/releasedistributed locks)RunVM Agent, RunVMController CoreDump Collector :808020 Acronis International GmbH, 2003-2022

VLANProtocolTCP portsConnectionCommentsdirection(to post core files forfuture analysis)ACI Admin panel: 8888ACI RunVM Agent:9090-9653lnode exporterdefaultconfiguration (seePrometheus defaultport allocations)RunVM Agent ACI :(see default OpenStackports)RunVM Agent ACI:9090 (request fromthe agent to ACI'sPrometheus the useddisk space)UDP123Internet ACIThe NTP protocol forNTP clients running inRunVM Agent VMsdrcoldstorageTCP44445ACI ABGWController ABGW443Deployment/updateTCP22 (ssh)using Acronis DCOOpenStackjenkinsAPI ports(see defaultOpenStackports)RunVM Agent, RunVM:44445, :443Acronis CyberAccess can be limitedCloud ACC by jenkins container IPACI (DCOaddressjenkins jobplaced intoACC)Networks used by the ACI clusterNetworkIP networkDHCPDescriptionnamedmzvpn21vpn -NoneCustomer VPN traffic from customer premises100.64.0.0/10to their private cloud environment.dmz - dataThere are 2 IP networks configured over a single Acronis International GmbH, 2003-2022

center specificvlan.(public IP pools)The DR service assigns IP addresses to VPNThe defaultservers. The range is configured during the DRgateway is toinfrastructure deployment as a subset ofbe assigned100.64.0.0/10.The External networking network in terms ofACI, see Network requirements andrecommendations.contentx.x.x.x/16Not routableyes, managed byData traffic: read/write of virtual disk dataACIbetween RunVM Agent/Controller and ACIinternal processes (possible location onoutside of thedifferent ACI nodes). The communication isnetworkdone within the same VLAN.No defaultgatewaydrmgmty.y.y.y/241. Some IPaddresses inThe defaultdrmgmtgateway is tonetwork (forbe assignedACI hosts, etc)Connection from RunVM Agent/Controller toAcronis Cyber Cloud (ACC) component.Connection among RunVM Agent, RunVMController, and PostgreSQL VMs.are assignedConnection from RunVM components to thestatically.Internet.2. The rest of theManagement and API network in terms of ACI,range issee Network requirements andmanaged byrecommendations.ACI.drcoldstoragez.z.z.z/16No defaultyes, managed byACIgatewayData traffic:RunVM Agents/Controllers read archives locatedon Backup (cold) storage.RunVM Agents (backupers) write new backupsto Backup (cold) storage.Access to the Backup (cold) storage is doneusing public DNS names (public IPs of Backupstorage).Maximum throughput and minimum latencyover this RunVM Backup storagecommunication is critical for the main DRservice operation.Private22c.c.c.c/24NoneInter ACI cluster communication: storageNot routableStorage Internal network in terms of ACI,seeoutside of theNetwork requirements and recommendations. Acronis International GmbH, 2003-2022

networkNo defaultgatewayPublicd.d.d.d/24NoneStretching the internal (virtual) networks acrossthe ACI cluster (encapsulation of private vxlanNot routabletraffic)outside of thenetworkOverlay Networking network in terms of ACI, seeNetwork requirements and recommendations.No defaultgatewayACI cluster network configurationACI infrastructure traffic type managementOSTORyesprivateABGW privateVM privateyesyesCompute APIyesVM backupsRegularyesS3 PublicyesNFSyesAdmin panelyesSSHyestraffictypesVM publicSelf-serviceyesyesyesyesyesyespanel23 Acronis International GmbH, 2003-2022

theusdrmgmtyestraffictypesACI compute networking configurationNetworkIP addressTypeSubnet lic/16-EnabledadmindmzvpnEnabledPublic/10 (or a subnetyesEnabledadminof mtEnabledPublic/16yesEnabledadminTo learn more about configuring direct routing for a cold storage, refer to Appendix E. Advancednetwork configuration.Creating VLAN adaptersAs a minimum configuration requirement, after deploying Acronis Cyber Infrastructure, you alreadyhave two network adapters assigned to the Public and Private networks. You must now create theVLAN adapters for the drmgmt, content, drcoldstorage, and dmzvpn networks.1. In the Acronis Cyber Infrastructure admin panel, go to Infrastructure Nodes, and click thenode.2. Click Network interfaces.NoteYou need network adapters for six networks. If the number of physical network adapters on thenode is less than 6, add the missing number of VLANs by repeating the steps below.3. Click Create.4. In the Create network interface wizard, select the VLAN interface type.5. Click the network interface from which you want to create the VLAN, and click Next.6. Type the VLAN ID of the adapter.7. In Select a network to assign to the interface, select Not assigned.8. In Specify the network parameters, select Manually.9. In the IP address field, click Add, and type the IP address of the VLAN using the CIDR notation.10. Configure the Gateway and the MTU, or leave the fields empty.11. Click Create.For more details, see Acronis Cyber Infrastructure Installation Guide.24 Acronis International GmbH, 2003-2022

Creating infrastructure networks1. In the Acronis Cyber Infrastructure admin panel, go to Infrastructure Network.Note that the Public and Private networks are already present, as they were created during theinstallation of the compute cluster. You must create four more networks with the e2. For each of the listed networks, repeat the steps:a. Click Create network and type the network name.b. Click Create.3. Create a new traffic type: Prometheus with the 9090 port.a. Click Create traffic type.b. In the Name, type Prometheus.c. In the Port, type 9090.d. Click Create.Assigning network adapters to networksTo assign network adapters to a network1. Go to Infrastructure Nodes, and click the node.2. Click Network interfaces.3. For each physical adapter or VLAN that you created, repeat the steps below.a. Click the VLAN that you want to assign to a network (content, dmzvpn, drmgmt, ordrcoldstorage), and click Edit.b. In the Edit network interface wizard, select a network to assign to the network interface.c. Click Save.Assigning traffic types to the infrastructure networksAfter assigning network adapters to the networks, you must assign the traffic types, as shown in thetable.The following table shows the correct ACI Infrastructure traffic type s25 Acronis International GmbH, 2003-2022

ementOSTORyesprivateBackupyes(ABGW)privateVM privateyesCompute APIyesVM backupsRegularyesS3 PublicyesNFSyesAdmin panelyesSSHyestraffictypesVM metheusyestraffictypesTo assign an exclusive traffic type to a network1. Go to Infrastructure Network2. In the Exclusive traffic types section, in the Assign to network drop-down list, click the traffictype that you wan

2. Install and configure Acronis Cyber Infrastructure. For more details about the installation procedure, see Installing Acronis Cyber Infrastructure. 3. Configure the networks in Acronis Cyber Infrastructure. For more details, see Configuring networks. 4. Create the storage cluster. For more details, see Creating the storage cluster. Option 1.

Related Documents:

NetWorker Server disaster recovery roadmap This guide provides an aid to disaster recovery planning an detailed step-by-step disaster recovery instructions. The following figure shows the high-level steps to follow when performing a disaster recovery of the NetWorker Server. Figure 1 Disaster recovery roadmap Bootstrap and indexes

4.2 State Disaster Recovery policy 4.3 County and Municipal Recovery Relationships 4.4 Recovery Plan Description 4.5 Recovery Management Structure and Recovery Operations 4.6 Draft National Disaster recovery Framework (February 5, 2010) 4.6.1 Draft Purpose Statement of the National Disaster Recovery Framework

FlexPod Hybrid Cloud for Google Cloud Platform with NetApp Cloud Volumes ONTAP and Cisco Intersight TR-4939: FlexPod Hybrid Cloud for Google Cloud Platform with NetApp Cloud Volumes ONTAP and Cisco Intersight Ruchika Lahoti, NetApp Introduction Protecting data with disaster recovery (DR) is a critical goal for businesses continuity. DR allows .

1. Post-Disaster Recovery and Disaster Risk Reduction require support from community participation in improving the quality and objectives of Disaster Management; 2. Community-based Disaster Risk Reduction is a key factor in participatory disaster management, including in post-disaster recovery, as indicated by best practices in Yogyakarta and .

Disaster Recovery to VMware Cloud on AWS vSphere Private Cloud VMware Cloud AWS on AWS. Confidential 2021 VMware, Inc. 57 LAB Lab - 9: Disaster recovery-as-a-service with Site Recovery service 1. Enable Site Recovery service in the SDDC 2. Configure vSphere Replication & Site Recovery On-Premises 3.

Private Cloud Public Cloud VMware vCloud: Shared, Unified Cloud Management Orchestration Compute Network Storage VMware vCloud Air VMware EMC Channel Partners EMC, Vblock, VSPEX EMC Hybrid Cloud EMC Hybrid Cloud The Only Complete, Engineered, hybrid cloud solution Deliver a Hybrid Cloud that leverages your existing infrastructure

community disaster—recognize that preparing for long-term disaster recovery demands as much attention as preparing for short-term response. After a major disaster, the recovery process takes months and even years to bring a community back to a "new normal" and as strong as or better than before the disaster. Disaster Recovery: A Local

Disaster Recovery in Cloud entails storing critical data and applications in Cloud storage and failing over to a secondary site in case of any disaster. Cloud Computing services are provided on a pay-as-you-go basis and can be accessed from anywhere and at any point of time. Backup and Disaster Recovery in Cloud Computing can be automated .