When a configuration has been changed, the Configuration Summary area lists the steps required to initialize the configuration and shows which steps have been completed or are in progress. When the initialization is successfully completed, the summary area displays the normal Configuration Summary content. Configuration initialization cannot be stopped once it is started.
When the configuration is saved and validated, you can view the progress of the configuration initialization in the Configuration Initialization Progress section in the Configuration Window. As each step is successfully completed, a checkmark appears next to the step. When you change an existing configuration, Assure MIMIX for AIX runs commands for each step.
The step and command sequence can change depending upon the configuration changes that you make. The table below describes steps and commands that are run when you change a configuration:
Order |
Step |
Command |
---|---|---|
1. |
Save configuration. |
This was done when you clicked Finish in the Change Replication Group wizard on the Summary panel. |
2. |
Copy configuration to S (S is production server, recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
3. |
Delete internal logical volumes. |
|
4. |
Delete replication container logical volumes on S (S is production server, recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
5. |
Delete log record file container and snapshot logical volumes on S (S is recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
6. |
Delete replication container and snapshot logical volumes on S (S is recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
7. |
Delete all containers and logical volumes on S (S is recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
8. |
Delete snapshot logical volumes on S (S is recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
9. |
Delete snapshot container logical volumes on S (S is recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
10. |
Delete replication container, snapshot, and log record file container logical volumes. |
|
11. |
Create containers and logical volumes on S (S is production server or recovery server). You will see a row for each server in the configuration. |
|
12. |
Set all logical volumes as replicated. |
|
13. |
Set new logical volume X as requiring replication (X is a device such as /dev/ rLV_p520-95_0001). |
|
14. |
Reset Send process (LCA) |
|
15. |
Reset Apply process (ABA) on S. (S is recovery server, recovery server 1, or recovery server 2) |
|
16. |
Load drivers on S (S is production server or recovery server). You will see a row for each server in the configuration. |
|
17. |
Delete logical volume device special files on S. (S is production server, recovery server, recovery server 1, or recovery server 2). You will see a row for each server in the configuration. |
|
18. |
Delete failover context on S. (S is production server, recovery server, recovery server 1, or recovery server 2) You will see a row for each server in the configuration. |
|
19. |
Delete failover context on S (S is production server or recovery server). You will see a row for each server in the configuration. |
|
20. |
Verify configuration on S. (S is production server, recovery server, recovery server 1, or recovery server 2) |
|
Related Topic: