Learn how to add a load balancer or a network load balancer to a Disaster Recovery (DR) Protection Group.
Before adding a load balancer or a network load balancer, ensure to perform the following prerequisites:
- Create a load balancer if you want to add a load balancer. Alternatively, Create a network load balancer if you want to add a network load balancer.
- Update the load balancer.
- Create a standby DR Protection Group.
- Create a primary DR Protection Group.
Perform the following steps:
- From the Resource Type menu, select Load balancer.
- Select a load balancer or network load balancer to add from the list of load balancers.
- Select the Destination load balancer in your compartment.
- Select the Source backend set.
- Select the Destination backend set .
- Check the Is backend set for non-moving instance box if you do not want the load balancer to send any ingress traffic to the backend servers (Compute instances) in this backend set. You must select this checkbox for the backend set if all of its backend servers are non-moving compute instances.
- For non-moving compute instances, if you check this box, Full Stack DR removes the primary backend set and updates the standby backend set from offline to online. Full Stack DR updates the primary backend set from online to offline. As a prerequisite, you must specify the IP address of the backend server you want to add to your standby backend set.
- For moving compute instances, Full Stack DR removes all the backend servers from the primary backend set and adds them to the mapped backend set on the standby load balancers, to route the traffic to the standby backend set during DR Drill execution. Do not check this box for moving compute instances. Ensure that your standby backend sets are empty and primary backend sets are not empty. As a prerequisite, ensure that the IP addresses in the primary backend set point to the moving compute instances.
Note
- You need to create separate backend sets for moving and non-moving compute instances and add them in different backend sets and ensure that they have separate backend sets.
- The checkbox indicates that the backend servers added in the backend set are for non-moving compute instances.
- For non-moving compute instances that are a part of a backend set, Full Stack DR updates and disables them to stop sending any ingress traffic and they stay in an offline mode. The backend servers are not removed from the set in this scenario.
- Click the option to add the + Another backend set mapping to add the mapping of the load balancer or a network load balancer.
- Accept the warning that all DR Plans will be deleted.
- Click Add to add the load balancer or a network load balancer to the DR Protection Group.
Note
Ensure to add only those OCI resources such as compute instances to load balancers or network load balancers that are part of the primary DR Protection Group.