Novell Sentinel Rapid Deployment 6.1, Installation Manual

Page: 56 / 84

56 Sentinel 6.1 Rapid Deployment Installation Guide
no
vd
ocx
(e
n)
17
Sep
te
m
be
r 20
09
5.4 Backing Up Information

Events should be archived regularly. The backup media should be stored in a secure offsite
facility.
Periodically do the following:
 Export all the ESM configurations and save them. When the environment is relatively
stable, you can generate a full ESM export including the entire tree of ESM components.
This captures the plug-ins as well as the configuration of each node. The resulting
.zip
file should be backed up and archived as a normal file.
If the changes such as updating plug-ins or adding nodes are made to ESM later, you must
export the configuration and save it again.
 Save all the report, rules, and actions in Solution Designer.

Back up the entire installation directory, instead of particular sections, so there is no risk
of manual mistakes and so the process is quicker.

Back up the database. For more information on backing up the PostgreSQL database, see
PostgreSQL: Backup and Restore (http://www.postgresql.org/docs/8.1/static/
backup.html)
.

Back up the
/opt/novell/< install_directory >/config
directory.

For sensitive data, use one of the following methods to encrypt the data backup:

Encrypt the data itself if the application that creates the data supports encryption. For
example, database products and third-party tools support data encryption. Use backup
software that is able to encrypt data as you back it up. This method has performance and
manageability challenges, especially for managing encryption keys.

Use an encryption appliance that encrypts sensitive backup media as data is backed up.
 If you transport and store media offsite, use a company that specializes in media shipment and
storage. Make sure that your tapes are tracked via bar codes, stored in environmentally friendly
conditions, and are handled by a company whose reputation rests on its ability to handle your
media properly.

Load Recovery Certificates. The Novell Sentinel service by default is not configured for the
Recovery agent. During server configuration via YaST, ensure that the Recovery agent path is
configured. This path should contain the list of certificates that the service can load for the
users to select from. For more information, see “
Certificate Management for Sentinel 6.1 Rapid
Deployment Server ” in the Sentinel 6.1 Rapid Deployment Reference Guide .
YaST contains modules for the basic management of X.509 certificates. This mainly involves
the creation of CAs, sub-CAs, and their certificates. For more information about how to
manage and update certificates, see
the Managing X.509 Certification (http://www.novell.com/
documentation/sles10/sles_admin/data/cha_yast_ca.html) in the SUSE Linux Enterprise Server
10 Installation and Administration Guide (http://www.novell.com/documentation/sles10/
sles_admin/data/bookinfo_book_sles_admin.html) .

If you want to back up filters and workflows you must back up specific tables. You must build
your system in a control-based fashion, For example, create specific sets of content that
implement a desired control. You can then store these content in a Solution Pack, which can
then be backed up. This ensures that a lot of other information is captures along with filters and
Active Views.