Create FSDR Groups

Before continuing make sure you went through the prerequisite section to Create FSDR Group

Create Ashburn DR group (primary)

Once we have the standby database up and running we need to create Full Stack Disaster Recovery Groups and associate the Control Center as a member of these groups.

Open DR Group menu by pressing “Migration & Disaster Recovery” → “DR Protection Groups” button.

Click on the button ”Create DR protection group”

Fill in following:

Name of the primary group (ashburn_grp)
Choose a compartment, where to create the group
Choose a storage bucket for DR group objects created in previous section
The role leave “Not configured” for now
Press Create

We can leave the members empty for now, we will add them once the standby DR group will exist.

Create another DR Group meant for processing members in the standby region.

Switch to a DR region if you are going to create DR region instead of Availability domain setup. In our example we use AD setup.

Fill in following:

Name of the primary group (phoenix_grp)
Choose a compartment, where to create the group
Choose a storage bucket for DR group objects
The role leave “Not configured” for now
Press Create

Define 2 IP addresses for primary and standby side for moving instance

Before adding a moving instance to the DR group, we need to prepare a free IP address, that will be specified to the new machine created after a failover of the machine.

Find the subnet of the VCN created in section Create Virtual Cloud Network(s)

Open the Virtual Cloud Networks menu and get the subnet:

In our example the subnet is 10.0.0.0, and for the migration purposes, we choose, that Central Console machine will have following IP addresses:

10.0.0.157, when active on ashburn region
10.0.0.158, when active on phoenix region

Define DR Group Role

Let’s first associate primary role to this group. Press the Associate button.

From the DR Group overview, click on the primary DR group:

Choose a Primary Role
Select Peer Region, where the standby DR group exists.
Choose the DR protection group
Press Associate button

Add a member to the primary DR Group

Now we need to add the Central Console compute instance to the primary DR group as a moving instance.

Moving instance means, that the machine gets destroyed on primary side and new machine gets created on the standby region/AD. There is a boot volume synchronization job running between the two sites, so the Control Center machine always start with product data.

From the DR Group overview, click on the Primary DR group and on the left sided menu choose option members. Then press Add member button.

In the Context menu fill in following things:

Confirm, that adding the member to DR group drops all DR plans
Choose a type of the resource you want to add to Compute
Choose the Control Center machine
Set, that the machine is added as a Moving instance
Press the Add VNIC mapping

In Add VNIC mapping menu, we need to tell Oracle, what IP address will the newly created machine have. The address cannot be the same as the one on the primary side, because you cannot have 2 machines with the same IP address in the VCN.

Control Center should be predefined in this field
Choose the correct subnet, that has the 10.0.0. range of addresses. If unsure, go to VCN menu and double check
Specify an IP adress, that will be assigned to Control Center after migration to standby region/AD
Press Add button

Confirm the addition of the member to DR group by pressing Add button:

Volume group of the Control Center’s boot volume is automatically added as the member.

If the Volume Group is not added automatically, please add it manually. Press Add member button again.

Confirm, that you understand, that the member addition will remove all existing plans
Choose a “Volume group” Resource type
Choose a Volume group of the Control Center machine

Press Add to add the Volume group the DR group.