Sv translation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Starting Up and Shutting DownAll systems are designed to boot up and start all services independently. However, there are certain dependencies between the services, so a clean startup and shutdown is best done when a certain order is considered. Start UpDependenciesAll services of the platform are dependent on two central entities:
To boot the solution, the storage should always be booted first. If this is external to the solution, continue with the next step. Otherwise, the computer (or in case of redundancy - both computers) is started on which the storage is located. This is usually the load balancer, but for larger systems a separate storage machine could have been implemented. Afterwards, the master database is booted. As soon as its is finished, the slave can be started up. Finally, the telephony servers and web servers can be started up in any order, even simultaneously. OrderA non-redundant solution is assumed in the following. The operation of a redundant solution requires extra schooling. This results in the following starting order:
Checks
ShutdownOrderShutting down is done in the reverse order:
It is not absolutely necessary to wait between the individual steps, just step 1 should be completed before continuing. Startup and Shutdown - Redundant componentsIf the entire system is shut down, some components may not be immediately available or manual intervention may be necessary. Storage (Redundant) - CentOS
Shut down (only one)Always shut down one after the other. With:
determine which node is active Primary. On the other node Secondary Node:
Then shut down the active node Primary Node.
Boot up (only one)After booting the secondary node Secondary Node, check the status. It should be Secondary and UpToDate
Check Sync status with :
After the sync is done, if necessary, and is ready:
Check status with: It should be Primary/Primary + UpToDate/UpToDate
Shut down (both)With:
determine which node is active (the node on which Samba and the virtual IP is running). This is the Primary Node. WithSet the secondary Node to secondary with:
On the Secondary Node first, then Primary:
Start up (both)Boot the Primary Node first Check DRBD sync Status and pcs cluster status Check with:
The Primary Node should be primary, and Secondary Node should be secondary. Disc should be UpToDate Then on Secondary Node
Check with:
Both nodes should be set to Primary/Primary + UpToDate/UpToDate Then check if everything works a final time:
|
...