Add Deployment-ReplaceServer
parent
4351ea2d6e
commit
4f1ca5ee92
15
Deployment-ReplaceServer.-.md
Normal file
15
Deployment-ReplaceServer.-.md
Normal file
|
@ -0,0 +1,15 @@
|
||||||
|
# Replacing a Live Server
|
||||||
|
|
||||||
|
This page tries to outline the basic steps for replacing a live server, using the Rattail [deployment framework](Deployment.-).
|
||||||
|
|
||||||
|
**NOTE:** *This is mostly a placeholder page for now.*
|
||||||
|
|
||||||
|
1. [Prepare a new server](Deployment-ServerMachinePrep.-) which will become the replacement.
|
||||||
|
1. [Prepare the server bundle](Deployment-ServerBundlePrep.-) within your control environment.
|
||||||
|
1. [Bootstrap](Deployment-BootstrapServer.-) the new server.
|
||||||
|
1. Synchronize all (relevant) databases and files from the (current/old) live server to the new server.
|
||||||
|
1. Optionally, perform additional backup(s) for the live server.
|
||||||
|
1. Stop all relevant services (Apache, Samba, Rattail daemons) on live server.
|
||||||
|
1. Synchronize all relevant data once more. (Idea being, the first sync and backup might have taken quite a while.)
|
||||||
|
1. Change hostname of current/old live server, if necessary, then power off and/or remove from network.
|
||||||
|
1. Ensure new server has correct hostname and IP address, reconfiguring/rebooting as necessary.
|
Loading…
Reference in a new issue