Examples of changing the backup sequence - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

The following examples illustrate problems with the current backup sequence and how to correct them.

Example 1 - Changing the backup sequence when primary node is ok

The following table shows a four-node environment where the current backup sequence does not reflect the desired behavior in the event of a switch. Also, the relative order of the configured backup sequence does not match the relative order of either the current sequence or the desired sequence.

Table 1. Example 1, showing discrepancies in backup sequences

Desired Order

Initial Values, Example 1

Work with Node Entries

Status View

                                            

Configured View

     

Each row in the following table shows a change to be made to the nodes on the configured view of the Work with Node Entries display. The rows are in the order that the changes need to occur to correct this example configuration to the desired order.

Table 2. Order in which to change nodes to achieve the desired configuration for example 1

Node to Change

Change To

Effect on Configured Order, Example 1

Notes

NODEB

Role = *BACKUP Position = *FIRST

Configured View

 

Intermediate step

NODED

Role = *BACKUP Position = *FIRST

Configured View

                                                     

Desired configuration but it is not effective until STRAG ROLE (*CONFIG) is performed.

Example 2 - Correcting the configured primary node and changing the backup sequence  

The following table shows a four-node environment where the current backup sequence does not reflect the desired behavior in the event of a switch. Also, the current and configured primary node do not match. The configured primary node must be corrected first, before attempting to correct any backup node sequence problems.

Table 3. Example 2, showing discrepancies in primary node and backup sequences

Desired Order

Initial Values, Example 2

Work with Node Entries

Status View

                                                

 Configured View

 

Each row in the following table shows a change to be made to the nodes on the configured view of the Work with Node Entries display. The rows are in the order that the changes need to occur to correct this example configuration to the desired order.

Table 4. Order in which to change nodes to achieve the desired configuration for example 2.

Node to Change

Change To

Effect on Configured Order, Example 2

Notes

NODEB

Role = *BACKUP Position = *FIRST

Configured View

                                           

Intermediate step

NODEA

Role = *PRIMARY

Configured View

Intermediate step, corrects configured *PRIMARY.

The sequence number for Backup 3 may appear as 4. The  relative order is equivalent.

NODED

Role = *BACKUP Position = *FIRST

Configured View

                                                

Desired configuration but it is not effective until STRAG ROLE (*CONFIG) is performed.