From 4f1ca5ee925ae545e82191cdc9f9fd18b7936c86 Mon Sep 17 00:00:00 2001 From: Lance Edgar Date: Sat, 15 Feb 2025 21:36:33 -0600 Subject: [PATCH] Add Deployment-ReplaceServer --- Deployment-ReplaceServer.-.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Deployment-ReplaceServer.-.md diff --git a/Deployment-ReplaceServer.-.md b/Deployment-ReplaceServer.-.md new file mode 100644 index 0000000..d4c9b91 --- /dev/null +++ b/Deployment-ReplaceServer.-.md @@ -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.