- 1.0 Notify Users, Obtain Access, and Stop Services
- 2.0 Backup Databases and Configuration Settings
- 2.1 To back up GroundWork databases
- 2.2 To back up system configuration settings
- 2.3 To back up GroundWork Profiles
- 2.4 To back up customized monarch modules
- 2.5 To back up automation scripts and templates
- 2.6 To back up JBoss configuration files
- 3.0 Purge Old Backups
- 4.0 Restart Services
|Command not found|
If you received a message similar to command not found or no such file or directory you may need to set the environment variables for the shell by running the source /usr/local/groundwork/scripts/setenv.sh script. This works in each shell session and only in shells similar to the Bourne shell, like bash. It will not work in either csh or tcsh.
You will need to have the PostgreSQL postgres user password available to perform various commands. This is the same database password that was used for the GroundWork Monitor installation or upgrade.
|Example file name|
Throughout this document we refer to a <timestamp> format. For example 2014-02-05_14-06-10 would be the name of a backup directory or part of a backup file name representing the date and time of a backup.
- Before starting with any system maintenance you will need to notify GroundWork Monitor system users that the system will be unavailable for a short time and that they will need to log out otherwise they will receive error messages and will loose their current session. You can schedule a maintenance window to notify all system users.
- Next, you will need to get shell access to the GroundWork server. You can do this either by opening a shell on the sever or get remote access with through ssh. Make sure that you are user root to execute all commands.
- Stop all services used by GroundWork Monitor with their respective commands:
- Create a backup sub-directory in /usr/local/groundwork/.
This step is a one time action. Skip this step if you have already created a backup directory.
- Change your working directory to backup with the following command:
- Issue the following commands to backup all GroundWork databases:
- From the /usr/local/groundwork/backup directory, issue the following commands to backup the system configuration settings for Foundation and Nagios:
- From the /usr/local/groundwork/backup directory, issue the following commands to backup GroundWork Profiles:
- From the /usr/local/groundwork/backup directory, issue the following commands to backup customized Monarch modules:
- From the /usr/local/groundwork/backup directory, issue the following commands to backup monarch automation scripts and templates:
- JBoss configuration files are all stored in the directory: /usr/local/groundwork/config
- This step covers purging backup data that can be rotated. If you have decided to keep backups for more than a month issuing the following command will purge any backup files older than 28 days. Issue the following command from the /usr/local/groundwork/backup directory:
- Next, you will need to restart all services used by GroundWork Monitor with their respective commands: