Chapter 5. Special topics 139
? Both Director servers process alerts.
? Useful when sending alerts to ESM that has the ability to detect and delete duplicates.
Redundant management servers without alert duplication (no CAS)
The following list provides reasons why this option can be useful:
? Multiple IBM Systems Director management servers manage the same set of endpoints.
? Only one IBM Systems Director management server processes alerts.
– Secondary IBM Systems Director management server monitors the primary
management server.
– Secondary IBM Systems Director management server only processes alerts if the
“primary” management server is unavailable.
? Useful for customers with an aversion to duplicate notification.
5.3.4 Conclusion
IBM Systems Director can be deployed in a highly available configuration ensuring hardware
critical alerts are always processed. Although IBM Systems Director does not support typical
clustering technologies, it can be deployed in a redundant server configuration, using
customized scripts and Event Automation Plans to ensure critical alerts are always
processed.
5.4 Backup and restore of the management server
This section provides instruction for the backup and restore of CSM and IBM Systems
Director management server.
To protect the CSM and IBM Systems Director configuration data, both products are provided
with commands to back up and restore in the event of corruption and disaster recovery.
Backup is also required to replace a defective management server, to move a management
server to a different machine, to upgrade a management server's operating system, and
finally to migrate management software.
5.4.1 IBM Cluster Systems Management (CSM) backup and restore
Before starting the transformation of the CSM cluster into Systems Director, a good
precaution method is to take a backup of the CSM management server. In case you are
facing issues during the transformation and you need to roll back, then this backup is a must.
csmbackup
The csmbackup command copies persistent CSM data from the management server and
stores the data in the directory specified. This command almost replicates the CSM state of
the management server. The command backs up the nodes, node groups, conditions and
responses, and condition and response associations. Customization scripts and DCEM
scripts are also copied.
Note: For both CSM and IBM Systems Director, there is no requirement to take client
backups.
140 IBM CSM to IBM Systems Director Transformation Guide
By default, the backup files are placed in the /var/opt/csm/csmdata directory of the
management server, but to ensure that backup files are not lost in case of hard disk failure,
copy the backup files to external disk, tape, or an nfs mounted file system.
The csmbackup -r command can be run with the following parameters:
? DeviceHwCtrl
? DeviceGroup
? Sensor
? EventResponse
? Condition
? Association
? ManagedNode
? NodeGroup
? DmsCtrl
? User file name
These parameters back up data associated with its resource class. You can create a condition
that monitors when one of the resource classes changes by monitoring 'ConfigChanged >= 0'
on a specified resource class, then set up a response that runs the following script:
csmbackup -r Resource_Class> -d directory
To back up information to the default backup directory /var/opt/csm/csmdata, enter:
csmbackup
To back up all node groups to a mounted file system, enter (see Example 5-1):
csmbackup -d /work/csmbackup
Example 5-1 The csmbackup command
p5570lp01(root)/> csmbackup -d /work/csmbackup
Backing up CSM data, this could take a few minutes.
CSM backup data completed.
Please read /work/csmbackup/tasks.csmbak for CSM backup/restore information
p5570lp01(root)/>
After the backup is done you should archive this directory and keep it in a safe place in case
you need to roll back. Another backup method would be to take a full system backup using the
smit mksysb command. Of course, this method is much more time consuming.
csmrestore
In an unpleasant event when you have to roll back the configuration of your CSM cluster, you
can restore from the backup using the command csmrestore.
The csmrestore command restores the files that were copied by the csmbackup command into
the specified directory or the default directory /var/opt/csm/csmdata. The CSM management
Note: The command does not back up all data on the management server because some
information needs to be copied to a backup storage device manually. However, additional
files can be stored by the csmbackup command using the -f flag.
Chapter 5. Special topics 141
server must be completely installed and configured by the administrator in advance; the
csmrestore command does not install any CSM code on the management server.
The csmrestore command only restores the nodes, node groups, devices, device groups,
conditions and responses, and condition and response associations on the management
server. Customization scripts and DCEM scripts are also restored.
To restore data using the csmrestore command, CSM must be installed on the replacement
or upgraded management server in the same manner that CSM was installed on the
management server that ran the csmbackup command.
To restore information from the default backup directory /var/opt/csm/csmdata, enter:
csmrestore
To restore data from any other directory, use the -d flag (see Example 5-2):
csmrestore -d /work/csmbackup
Example 5-2 The csmrestore command
[p5570lp01]#csmrestore -d /work/csmbackup
Restoring node definitions backed up on AIX 6.1.6 CSM version 1.7.1.6...
Remove all existing nodes to restore saved nodes? (Y/N): y
Defining CSM Nodes:
p6lp02: Changing Mode from: "Managed" to: "PreManaged".
p6lp03: Changing Mode from: "Managed" to: "PreManaged".
2 nodes have been defined successfully.
Restoring nodegroups backed up on AIX 6.1.6 CSM version 1.7.1.6...
Remove all existing nodegroups to restore saved nodegroups? (Y/N): y
Restoring hardware device definitions backed up on AIX 6.1.6 CSM
Remove all existing hardware devices to restore saved hardware devices? (Y/N): y
Restoring hardware device groups backed up on AIX 6.1.6 CSM version 1.7.1.6...
Remove all existing hardware device groups to restore saved groups? (Y/N): y
Restoring condition information backed up on AIX 6.1.6 CSM version 1.7.1.6...
Restoring Event Response information backed up on AIX 6.1.6 CSM
Restoring sensor information backed up on AIX 6.1.6 CSM version 1.7.1.6...
Restoring condition/response association backed up on AIX 6.1.6 CSM
Restoring least-privilege (LP) information backed up on AIX 6.1.6 CSM
Restoring CSM user customization scripts...
Restoring csmconfig information backed up on AIX 6.1.6 CSM version 1.7.1.6...
Restore of CSM data completed.
There are several files in the /work/csmbackup directory that contain
information on the state of the system when it was backed up.
You may find it useful to look at these files. They include:
/work/csmbackup/config.csmbak
/work/csmbackup/tasks.csmbak
[p5570lp01]#
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.