Difference between revisions of "IRCC-Hyperkitty/SOP"
(Created page with '{{Admon/important|Seneca-Specific SOP|This SOP is specific to the environment at Seneca CDOT since it refers to specific hosts, configurations, and tools. It is intended solely a…') |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
== Login to a running container == | == Login to a running container == | ||
1. Login to colo server and become root | 1. Login to colo server and become root | ||
| − | ssh colo | + | ssh colo |
sudo -i | sudo -i | ||
| − | 2a. Run hyperkitty-docker.sh under the root home folder. The script should automatically attach | + | 2a. Run hyperkitty-docker.sh under the root home folder. The script should automatically attach to the running container, or start a new container if there is no container is running. |
/root/hyperkitty-docker.sh | /root/hyperkitty-docker.sh | ||
| − | 2b. '''Manually''' attach to running container | + | 2b. '''OR Manually''' attach to running container |
# Checkout container name | # Checkout container name | ||
docker ps | docker ps | ||
| Line 25: | Line 25: | ||
ssh colo | ssh colo | ||
sudo -i | sudo -i | ||
| − | 2a. Run hyperkitty-docker.sh under the root home folder. The script should automatically attach | + | 2a. Run hyperkitty-docker.sh under the root home folder. The script should automatically attach to the running container, or start a new container if there is no container is running. |
/root/hyperkitty-docker.sh | /root/hyperkitty-docker.sh | ||
| − | 2b. '''Manually''' start a new container | + | 2b. '''OR Manually''' start a new container |
# Checkout the latest image name | # Checkout the latest image name | ||
docker images | docker images | ||
| Line 49: | Line 49: | ||
All the backups files are located under <code>/Volume3/backup/colo</code> on our SAN, mounted on <code>/mnt/backup</code> inside the container. | All the backups files are located under <code>/Volume3/backup/colo</code> on our SAN, mounted on <code>/mnt/backup</code> inside the container. | ||
| + | |||
| + | == Backup facts == | ||
| + | |||
| + | * Data is backed up every half an hour | ||
| + | * Backup copies is limited to 6000 copies(4 months of backups), the script will start deleting the oldest copy once the number of copies reach 6000 | ||
| + | * duplicated backups are hard-linked automatically | ||
| + | |||
There are several directories under <code>/Volume3/backup/colo</code>: | There are several directories under <code>/Volume3/backup/colo</code>: | ||
Latest revision as of 22:20, 3 February 2016
This SOP is specific to the environment at Seneca CDOT since it refers to specific hosts, configurations, and tools. It is intended solely as a reference for the OSTEP team at CDOT, but the content may be useful to readers in other contexts.
Contents
Introduction
This page covers all the Hyperkitty/Postorius/Mailman3 maintenance information for IRCC instance. All the services are running inside a docker container.
Docker
Login to a running container
1. Login to colo server and become root
ssh colo sudo -i
2a. Run hyperkitty-docker.sh under the root home folder. The script should automatically attach to the running container, or start a new container if there is no container is running.
/root/hyperkitty-docker.sh
2b. OR Manually attach to running container
# Checkout container name docker ps # Attach to the Hyperkitty docker container docker attach <container_name>
3. Now you should get the bash prompt inside the container
Start a new container
1. Login to colo server and become root
ssh colo sudo -i
2a. Run hyperkitty-docker.sh under the root home folder. The script should automatically attach to the running container, or start a new container if there is no container is running.
/root/hyperkitty-docker.sh
2b. OR Manually start a new container
# Checkout the latest image name
docker images
# Start a container
docker run -it -p <IP_ADDRESS>:80:80 \
-p <IP_ADDRESS>:443:443 \
-p <IP_ADDRESS>:25:25 \
--cap-add SYS_ADMIN \
--add-host rcc-icn.ca:127.0.0.1 \
--add-host forum.rcc-icn.ca:127.0.0.1 \
--add-host forum.admin.rcc-icn.ca:127.0.0.1 \
--add-host wiki.rcc-icn.ca:127.0.0.1 \
<IMAGE_NAME> bash
3. Run the following scripts inside the container
# Mount the SAN and start backup scripts in the background start-services # Start postfix, mailman ,and httpd hk start
Backup
All the backups files are located under /Volume3/backup/colo on our SAN, mounted on /mnt/backup inside the container.
Backup facts
- Data is backed up every half an hour
- Backup copies is limited to 6000 copies(4 months of backups), the script will start deleting the oldest copy once the number of copies reach 6000
- duplicated backups are hard-linked automatically
There are several directories under /Volume3/backup/colo:
ircc_backups: compressed data backups of Mailman3, Postorius, Hyperkitty, and Mediawiki
ircc_logs: latest log files of the backup scripts
ircc_programs: Program files of Mailman3, Postorius, Hyperkitty, and Mediawiki (Manually backed up)
