wiki/info/landscape/archive-server-upgrade.md
... ...
@@ -10,12 +10,25 @@
10 10
Use Plain archive-candidate.sapsailing.com 172.31.46.203 8888
11 11
```
12 12
with ``172.31.46.203`` being an example of the internal IP address your new archive candidate instance got assigned.
13
+ - Check the configuration by running ``httpd -t``. If you get an "OK" as the output, commit and distribute the configuration change to all reverse proxies like this:
14
+```
15
+ git checkout main
16
+ git commit -a
17
+ git push
18
+```
19
+This will disseminate the configuration to all reverse proxies through a Git hook, merge as required and check out the appropriate configuration for that environment again, then reload the configuration in ``httpd``.
13 20
- Compare server contents, either with ``compareServers`` script or through REST API, and fix any differences
14 21
```
15 22
java/target/compareServers -ael https://www.sapsailing.com https://archive-candidate.sapsailing.com
16 23
```
17 24
- Do some spot checks on the new instance
18
-- Switch reverse proxy, by adjusting the archive IP definitions at the top of ``root@sapsailing.com:/etc/httpd/conf.d/000-macros.conf``, followed by ``service httpd reload``
25
+- Switch reverse proxy, by adjusting the archive IP definitions at the top of ``root@sapsailing.com:/etc/httpd/conf.d/000-macros.conf``, followed again by
26
+```
27
+ httpd -t # ensure you get "OK" as the response
28
+ git checkout main
29
+ git commit -a
30
+ git push
31
+```
19 32
- Terminate old fail-over EC2 instance; you will have to disabel its termination protection first.
20 33
- Adjust Name tags for what is now the fail-over and what is now the primary archive server in EC2 console
21 34