Veeam Availability Orchestrator – v.3.0 – DR from Netapp – Storage Replica

The fifth article will show how to use VAO version 3.0 to automatize the Disaster Recovery using the Netapp snap-mirror technology as an engine.

 

Netapp – SnapMirror

The article (quite long) is composed of 6 parts:

  1. Setting up Netapp Snap-mirror Protection
  2. Setting up the Recovery Location
  3. Setting up the Scope
  4. Creation of Orchestration Plan
  5. Starting the Plan
  6. Checking the Orchestration Plan status

1 Setting up Netapp Snap-mirror Protection

In my personal lab, I added two NetApp simulators 9.6 setted-up in peer relationships.

Pictures 1 to 5,  show how I set-up  a protection rule for a single Volume (named Vol_iScsi_N01)

Picture 1

Picture 2

Picture 3

Picture 4

Picture 5

Picture 6 shows the VMware console view of DR site; the replicated volume is presented as read-only volume.

Picture 6

Tips: My personal suggestion is asking your storage expert the right procedure to set-up a snap-mirror relation between two Netapp storages.

2. Setting up the Recovery Location

The recovery location wizard is shown in pictures 7, 8 and 9.

Picture 7

Picture 8

Picture 9

3. Setting up the Scope

The Scope wizard is shown in picture 10.

Picture 10

4. Creation of Orchestration Plan

Let’s go back to the main steps.

The wizard drives the users to select the right voices as shown in pictures 11, 12, 13 and 14.

Picture 11

Picture 12

Picture 13

Picture 14

The test scenarios are available in this configuration too

The Readiness Test is a low-impact and fast method one to confirm that configuration of an orchestration plan matches the DR environment.

The Data-lab test verifies the DR plan starting VM in a separate network.

 As shown in pictures 15,16,17 and 18. the steps are:

– Assigning  Datalab to VM Group (it is available from the admin menu)

– Setting up the Lab Group

Picture 15

Tips: for testing the Netapp integration select the option Restore.

It means the Replica option is just available for VBR Replica jobs.

Picture 16

Picture 17

Picture 18

5. Starting the Plan

Next pictures show how to run the just created Orchestration plan.

Picture 19

Picture 20

Picture 21

Picture 22 shows the restore points available.

Tips:  the shown Restore points are the replicated snapshot  (created by snap-mirror).

Picture 22

Picture 23 shows my favorite option available on VAO 3.0 in the Storage replica scenario.

Let’s imagine you run the orchestration plan.
While failover is running, the primary site is back normal operativity.

Your IT manager asks to revert the failover. Is it possible? Well, it can be. If you selected “reprotect storage volumes after failover” during the steps you can easily do it!

Picture 23

Picture 24

Picture 25

6. Checking the Orchestration Plan status

Time to run the orchestration plan and watch the steps performed.

I would like you to give your attention to the following three pre-plan steps:

a. Breaking the snapshot relationship

b. Putting the destination volumes on-line

c. Mounting the volumes

(Clicking on the picture you can enlarge the images)

Picture 26

From picture 27 you can see  the main steps:

d. VM registration

e. Network founding and connection

f. Booting VM

Picture 27

Pictures 28 and 29 show the result of post plan steps:

g. heart-beating test

h. Unmounting source Datastore

Picture 28

Picture 29

Tips: how to check in 5 points if everything is correctly working

1. VM in the DR site is running (from DR vCenter console connect remotely to VM as shown in picture 30 and 31).

Picture 30

Picture 31

2. Source VM has been deleted (from Production vCenter console check if VM is disappeared) (Picture 32).

Picture 32

3. The Orchestration plan launch button is grey and the plan has to be reset (picture 33)

Picture 33

4. Destination volumes on Netapp console have been set as read/write (Picture 34)

Picture 34

5. The Netapp relationship between source and destination volumes is broken (Picture 35)

Picture 35

– Readiness check report example dowload

That’s all folks for now.

Veeam Availability Orchestrator – v.3.0 – DR from Backup

Fourth article about VAO 3.0 and the second use case.

How to use a Backup Job to implement a DR scenario with VAO. In this article, I don’t cover the mandatory step related to VMs tag.

If you need a guide please refer to my previous writes (Baseline  1  & 2)

The main steps are:

  1. Creating a Failover location where the VMs can be restarted
  2. Setting up scope
  3. Creating the orchestration plan

Let’s start!

1 . Creating the Failover location

Pictures 1 to 3 show how easier it is to set Name, computers, and storage resources.

Picture 1

Picture 2

Picture 3

Picture 4 shows the maximum storage % that can be used by Restore task and picture 5 shows if the Instant VM recovery has to be enabled.

Picture 4

Picture 5

Picture 6 shows one of my favorites VAO options.

Why? Because it allows VAO to be implemented where the primary backup job has been copied to a second location.

To be clearer: the VBR backup copy job allows to copy backup data to the secondary site. If there are VMware hosts, it’s possible to create a DR site just restoring data from backup copy job.

Picture 6

Picture 7 shows how to twin the production with DR networks (the previous step sets-up the re-IP addressing just for windows VMs)

Picture 7

Picture 8 shows the GDPR option

Picture 8

2. Setting up scope

Pictures 9 to 12 show the main points:

To set-up a scope,  check-up the VM Groups,  select the Recovery Location and which plan steps have to be added.  (all details are available at Baseline articles).

Picture 9

Picture 10

Picture 11

Picture 12

3. Creating the Orchestration Plan

From Picture 13 to 16 the main points to set up the Restore Plan

Picture 13

Picture 14

Picture 15

Picture 16

Please find here an example of Readiness check Reports

Readiness check report example dowload

Veeam Availability Orchestrator – v.3.0 – DR from Replicas

First step by step guide how to set-up a Disaster Recovery plan starting from a replica job.

Anyway I suggest having a look at the previous articles befere reading this one.

Veeam Availability Orchestrator – v.3.0 – VAO-Baseline-1

Veeam Availability Orchestrator – v.3.0 – VAO-Baseline-2

In today example, I imagined implementing a DR-Orchestration for a company selling tickets. The two VMs that deliver the services are the Domain controller and SQL DB with installed the application needed.

The main points are:

  1. Setting up replica job using  VBR present into VAO (VBR-VAO)
  2. Creating Tags
  3. Adding the plan components to the scope
  4. Creating a lab group
  5. Configuring the Orchestration Plan
  6. Testing

1.  Setting up Replica Job

From the Veeam console, it’s quite easy to set up the Replica Job (From Picture 1 to 5)

Picture 1

Picture 2

Picture 3

Picture 4

Picture 5

Picture 6

 

2.Creating Tags

Veeam-One Business View is reachable from the Veeam Monitor console. To create the tagging just select add Category (Picture 7) from the resource you want to tag (in the picture are Virtual machines).

Picture 7

After folding it up with a name (Picture 8) in pictures 9, 10, 11, and 12 is shown how easy it is customizing the tag.

Picture 8

Picture 9

Picture 10

Picture 11

https://lnx.gable.it/wp-content/uploads/2020/08/bw-5.jpgPicture 12

Picture 11 shows how to concatenate the conditions.

thIt means that it is possible to add different conditions selecting for every entry the logical operator “and – or”

3. Adding the plan components to the scope

From the Administrator panel, through plan components, it is possible to select which VM groups can be added to the scope.

In our example, we are going to create a DR-strategy for SQL-Production scope (picture 14) using the VM Groups named SQL – Produzione (Picture 15). How to do it? Just clicking on the include button.

Picture 13

Picture 14

Picture 15

Now it’s time to repeat the same procedure for Recovery location (Picture 16), Plan steps (Picture 17), Credential (Picture 18), and Template jobs (Picture 19).

Picture 16

Picture 17

Picture 18

Picture 19

Now that we have finally added all components to the baskets. we need to create an Orchestration Plan for this specific service.

4. Creating a Lab group

From the main menu select Datalabs entry.

Now clicking on the add button, it’s possible to assign the tasks that will be performed during tests to the Datalab as shown in Picture 20,21,22.

Remember that the Datalab assignment has been already performed from the VAO administrator page.

Picture 20

Picture 21

Picture 22

5. Configuring the Orchestration Plan

The configuration wizard has been already explained in my previous article (VAO 3.0 – Baseline2).

Please find hereafter a short summary.

If you set it up correctly you should see your VMs in the VMGroups (picture 27&28) as they belong to the scope set on step 2 (Picture 24)

Picture 23

Picture 24

Picture 25

Picture 26

Picture 27

Picture 28

Picture 29

6. Testing

There are two different tests performed by VAO 3.0

Readiness Check (Picture 30-31) is a low-impact method to confirm that the configuration of an orchestration plan matches the DR environment.

Datalab Test simulates the DR starting VMs, Applications and Services into a different network. The data labs have to be set-up from the VBR console (Picture 32-34).

Picture 30

Picture 31

Picture 32

Picture 33

Picture 34

All reports are available from Reports menu (Picture 35)

Picture 35

Please find here two examples

– Readiness check report example download

– Datalab Test example download

The next articles will talk about Backup and Replica Storage.