...
1 - Preamble
- eas changeset id: TBD <eas-changeset-id>
- sfeas_config changeset id: TBD <sfeas_config-changeset-id>
This deployment will consist of the follow general steps:
...
Place the Web servers into maintenance mode (SF PROD WEB, DR PROD WEB):.
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /var/www/html sudo ./set_eas_mode.sh MAINT |
- SF PROD WEB is in maintenance mode: http://eas.sfgov.org/
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /var/www/html
sudo ./set_eas_mode.sh MAINT |
- DR PROD WEB is in maintenance mode: http://10.255.8.116/
3 - Backup the
...
EAS Databases
Log onto SF PROD DB and back up the EAS databases. The database backup script simply creates an additional daily backup, which are periodically purged from the file system, so there is no need to be concerned about the accumulation of "forgotten" database backups.
| Code Block | ||||
|---|---|---|---|---|
| ||||
sudo -u postgres -i
/home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log
|
- Database was backed up
| Code Block | ||||
|---|---|---|---|---|
| ||||
# You should receive an email notifying you of the status of the backup. The database backup log file is another source of information about the outcome of the backups. Note that an empty database backup log file indicates that the backups were successful.
ls -la /var/tmp/dbbackup.log
cat /var/tmp/dbbackup.log
# The existence of the database backups can also be confirmed directly from the command line:
ls -la /mnt/backup/pg/daily/easproddb.sfgov.org-* |
...
- Database backup was verified
...