A good disaster plan needs careful preparation. But after your careful planning, how do you validate your DR strategy without disrupting your daily business operation? Veeam Availability Orchestrator just might be your solution.
As this blog post focuses on one aspect of the VBR and VAO configuration and to learn more about Veeam Availability Orchestrator, and to find out more about Veeam Replication and Veeam Virtual Labs, continue reading.
Veeam Availability Orchestrator is a very powerful tool to help you implement and document your DR strategy. However, this product relies on Veeam Backup & Replication Tool to:
- perform Replication, and
- Virtual Lab.
Therefore, to successfully configure the Veeam Availability Orchestrator, you must master Replication and the Virtual Lab. Don’t worry, I will take you through the important steps to successfully configure your Veeam Availability Orchestrator, and to implement your DR Plan.
The best way to get started is to share with you a real-life DR scenario I experienced last week during my VAO POC.
A customer wanted to implement Veeam Availability Orchestrator with the following objectives:
- Replication between the production and DR datacentre across the county,
- Re-Mapping the Network attached to each VM at the DR site,
- Re-IP the VM IP address of each VM at the DR site,
- Scheduling the DR testing to perform every Saturday morning,
- Document the DR Plan.
As you might already be aware, all those objectives can be achieved using Veeam VBR & VAO.
So let’s get started.
The Environment and the Design
To understand the design and the configuration lets first introduce the customer network subnets at PRODUCTION and the DR site.
- At the PRODUCTION site, the customer used the 192.168.33.x/24 subnet,
- Virtual Distribution Switch and Group: SaSYD-Prod.
- Production network at the DR site uses the 192.168.48.x/24 subnet
- Prod vDS: SP-DSWProd
- DR Re-IP subnet & Network name: vxw-dvs-662-virtualwire-4-sid-5000-SP_Prod_Switch
To accomplish the configuration and requirements at those sites, the configuration must consider the following steps:
- Replication between the PRODUCTION and the DR Sites
- Re-Mapping the VM Network from ProdNet to vxw-dvs-662-virtualwire-4-sid-5000-SP_Prod_Switch
- vLab with that configuration listed above.
Replication Job Configuration
To prepare for a disaster and to implement failover, we must create a replication job that will replicate the intended VMs from the PRODUCTION site to the DR site. In this scenario, to achieve the requirements above, we must use Veeam replication with Network Mapping and Re-IP options when configuring the Replication Job. To do this, we have to tick the checkbox for the Separate virtual networks (enable network mapping), and Different IP addressing scheme (enable re-IP):
At the Network stage, we will specify the source and destination networks:
Virtual Lab Configuration
Veeam Availability Orchestrator is a very powerful tool to help companies streamline and simplify their DR planning. The initial configuration of the VAO DR planning is not complex; but it is a little involved. You must navigate between the two products, Veeam Backup and Replication, and the Veeam Availability Orchestrator.
After you have grasped the DR concept, your next steps to DR planning will be smooth and simple. Also, you may have noted that to configure your DR planning using Veeam Availability Orchestrator, you must be familiar with Veeam vLabs and networking in general. I highly recommend that you read more on Veeam Virtual Labs before starting your DR Plan configuration.
I hope this blog post helps you to get started with vLab and VAO configuration. Stay tuned for my next blog or recording about the complete configuration of the DR Plane. Until then, I hope you find this blog post informative; please post your comments in the chatter below if you have questions or suggestions.
The post Prepare you vLab for your VAO DR planning appeared first on CloudOasis.