Backing Up and Restoring
Cassatt Active Response
Intended for use with Cassatt Active Response Standard Edition, Premium Edition and Data Center Edition V5.1.
This article contains the following topics:
- Scheduling backups
- Determine what to back up
- Backing up the Cassatt Active Response environment
- Recovering the Cassatt Active Response environment after a failure
It assumes you have a procedure in place for backing up the operating system and any other system files outside of the Cassatt Active Response environment.
Scheduling backups
After installing Cassatt Active Response and validating it in a test
environment, and before going into production, you should
back up your Cassatt Active Response environment. Because the safety
of your data is provided to the last backup, you need to
determine the time and frequency of your backups. Consider
doing a backup after any significant configuration change
to your Cassatt Active Response environment. For example, creating or deleting
a tier, modifying any properties on the Controller
Properties tab, and adding or removing a network switch
all suggest the need for a backup.
Determine what to back up
Cassatt Active Response requires minimally that two
file systems be available on a shared storage device: the Cassatt Active Response base file
system and the Cassatt Active Response database file system. During Cassatt Active Response installation, the
installation program prompts you to select these shared file systems and the
installation program then creates the following symbolic links to them:
- /cassatt
- /cassatt/database
I said Cassatt Active Response minimally requires
these two file systems because Cassatt Active Response provides the flexibility
for you to create and leverage other file systems as deemed
appropriate. For example, specifically with regard to backing
up your system, there may be advantages in storing application
images on their own file systems. (For
more information, see Understanding Storage Management in Cassatt Active Response.) If you have other file
systems for use by Cassatt Active Response, include those in your backup procedures.
If you are doing regularly scheduled backups, you should
back up the entire Cassatt Active Response environment. Assuming an implementation that uses the minimum
shared file systems, that backup should include:
- /
- /cassatt
- /cassatt/database
- /var
- /usr/lib/php4
If you have separated the
root file system into multiple file systems, be sure that
the following are included in your backup:
- /opt—includes the Controller software
- /etc—includes system configuration
files
- /root—includes the .ssh directory
and authorization keys
- /lib/modules—includes necessary
kernel modules
Backing up the Cassatt Active Response environment
Follow these steps to back up the Cassatt Active Response environment (full or partial):
- For the duration of the back up, stop all Cassatt Active Response activities associated with:
- Tiers (for example, creation, allocation, deletion)
- Images (for example, provisioning, configuring)
- CLIs (for example, cccapture, ccexport,ccimport)
- Begin your backup, noting these exceptions:
If you are using dual control nodes, back up all of the files listed on the active control node; on the second control node, back up all the files except /cassatt and /cassatt/database.
If your images are already backed up, or you are upgrading to a new version of Cassatt Active Response where the image matrix is not touched, you can save time and disk space by not backing up /cassatt/images. Skipping /cassatt/images saves you time and disk space during backup.
-
Using your site backup procedures, back up the following
file systems to disk or tape:
- Back up any other file systems being used by Cassatt Active Response.
- Back up the database, for example:
sudo -u postgres pg_dump -Ft -b collage > /tmp/databaseBackup.tar
top
Recovering the Cassatt Active Response environment after a failure
The following procedures assume that the Cassatt Active Response environment has been corrupted beyond repair, and a full backup will be used for restoring the Cassatt Active Response environment.
- If necessary, reinstall the OS on the control node(s).
- If you did not reinstall the OS in step 1, use ccuninstall
-a to uninstall any or all of the existing
Cassatt Active Response software.
- Reinstall Cassatt Active Response on the control node(s).
- On any control node, use the cccoreservice command
to stop Cassatt Active Response and then mount the
Cassatt Active Response base file system.
/opt/cassatt/bin/cccoreservice
stop
mount collage-base-filesystem
where collage-base-filesystem is
the mount point for the Cassatt Active Response shared storage location.
If the Cassatt Active Response base file system has been distributed across
multiple file systems, mount each one.
Note: On a single control node, the cccoreservice command
stops the collage-core service.
In a dual-control node configuration, you can execute the
cccoreservice command from either control node, as the command disables
the service in clumanager, which in turn stops the service from running
on both control nodes.
- Restore the Cassatt Active Response base file system
(by default, /cassatt) from backup,
with the following caveat:
Do not restore the the following Cassatt Active Response utility
images (by default in /cassatt/images):
CollageIdle
CollageInventory
CollageDiagnostic
- Restore any other file system being used by Cassatt Active Response.
- Restore the Cassatt Active Response database file
system (by default, /cassatt/database) from the
backup, for example:
su postgres
postmaster -D /cassatt/database &
dropdb collage
createdb collage
pg_restore -d collage /tmp/databaseBackup.tar
psql -d collage -c "analyze"
pg_ctl stop -D /cassatt/database -m fast
exit
- On all control nodes, use the following command to
restart the Cassatt Active Response service:
/opt/cassatt/bin/cccoreservice start
At this point, the Cassatt Active Response environment should be restored to the state when the backup was done. top
|
