Pre-requisites:
- FireMon ecosystem is Fully Distributed
- FMOS version between 8.15.x and 8.24.x
****************************************************
In order to restore a Database Server in a distributed ecosystem the following steps must be done to avoid also reinstalling any Application Servers as well. During the install restore phase of these instructions, please place your application servers in maintenance mode.
The following must be created or available prior re-installation. If the CA backup isn't available, the DB and AS servers will have to be reinstalled but data can be restored. If there is no FireMon backup, all data is lost. The DB and AS must reinstalled from scratch.
The following must be done on the DB server.
1. At least two recent FireMon backups must be created and stored off server. To make a backup run, fmos backup filename. Where filename is the name you give your backup.
2. The Certificate Authority(CA) must also be backed up and stored off server. To backup the CA run, fmos ca backup filename. Where filename is the name you give the ca file. You will also be asked to create a passphrase. This passphrase must be kept/remembered or the CA backup will be useless!
3. Move both the FireMon backup and the CA backup off of the Database server.
Please do the following steps to restore the Database server. Make sure any Application Servers are in maintenance mode as well.
-
Install FMOS. Select *Existing Deployment* on the Ecosystem Selection page of the Initial Configuration Wizard.
-
Log in to the FMOS command-line interface either using SSH or console.
-
Restore the system configuration file from the regular FMOS backup. Because the machine holds no roles, the database and filesystem portions of the backup will NOT be restored at this time. Do this with: fmos restore /path/to/backup
-
Use the fmos config --edit command to launch a text editor to modify the FMOS System Configuration file.
-
Locate the following line in the file and remove it:
fm_roles: {}
-
Add the following lines to the file:
fm_roles: ca: true db: true es: true
-
Run the following command to apply the FireMon role changes:
fmos redeploy firstboot-early
-
Restore the CA store from the backup file (replace ${FILENAME} with the path to the CA store backup file):
fmos ca restore ${FILENAME}
-
Now, initialize the database instance by applying the secmgr playbook:
fmos redeploy
-
Finally, the regular FMOS backup can be restored as normal with this command: fmos restore /path/to/backup
-
Launch fmos config -e on each application server and modify the following line to reflect new database server name.
firemon_db:
host: newDBname.domain.com
- Run this: fmos ecosystem refresh, on any/all AS to reconnect them to the DB server.
Comments
0 comments
Article is closed for comments.