Shutdown
When shutting down a redundant storage architecture, the inactive machine is shutdown first. Therefore, before a shutdown procedure can begin, the active machine must be known. The table at Large V3 assumes that acd-store2 is currently the active storage and displays the shutdown procedure according to that. Only start the next step if the previous shutdown was completed successfully:
First shutdown acd-tel and acd-jbN in no particular order. You do not have to wait until acd-tel and acd-jbN are down before shutting acd-dbs1/dbr1 and acd-dbs2/dbr2 down simultaneously, but in correct order. Wait until acd-dbs1/dbr1 and acd-dbs2/dbr2 are down until shutting acd-dbm1 down. Wait until acd-dbm1 is down before shutting down acd-dbm2. Wait until acd-dbm2 is down before shutting down acd-lb1. Wait until acd-lb1 is down before shutting down acd-lb2. Wait until acd-lb2 is down before shutting down acd-store1. Wait until acd-store1 is down until shutting acd-store2 down.
Startup
When starting up a redundant storage architecture, the pcs cluster and drbd replication status must be checked on all pcs cluster members. Additional information can be found here: System Health Check
First start acd-store2 and wait until it is up. Start acd-store1 and wait until it is up. Start acd-lb2 and wait until it is up. Start acd-lb1 and wait until it is up. Start acd-dbm2 and wait until it is up. Start acd-dbm1 and wait until it is up. start acd-dbs2/dbr2 and wait until it is up. Start acd-dbs1/dbr1 and wait until it is up. Start acd-jbN and acd-tel afterwards in no particular order.
Table
| Steps 1 to N | Shutdown | Startup |
|---|---|---|
| 1 | acd-telN | acd-store2 |
| 2 | acd-jbN | acd-store1 |
| 3 | acd-dbs1/dbr1 | acd-lb2 |
| 4 | acd-dbs2/dbr2 | acd-lb1 |
| 5 | acd-dbm1 | acd-dbm2 |
| 6 | acd-dbm2 | acd-dbm1 |
| 7 | acd-lb1 | acd-dbs2/dbr2 |
| 8 | acd-lb2 | acd-dbs1/dbr1 |
| 9 | acd-store1 | acd-jbN |
| 10 | acd-store2 | acd-telN |
Ensure system functionality
Information can be found here: System Health Check