Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION, Руководство администратора

Страница: 89 / 184

Configuring BCC for Peer Clusters 89
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
IMPORTANT: Make sure to use a trailing dot in the search-and-replace value. If a trailing dot
is not used, 10.1.1 could be replaced with an IP value such as 192.168.100 instead of
192.168.1.
4 (Optional) Select the Use Regular Expressions check box to use wildcard characters in your
search-and-replace values. The following links provide information on regular expressions and
wildcard characters:
Š
Regular Expressions (http://www.opengroup.org/onlinepubs/007908799/xbd/re.html)
Š Regular-Expressions.info (http://www.regular-expressions.info/)
Š
Wikipedia (http://en.wikipedia.org/wiki/Regular_expression)
Š oreilly.com (http://www.oreilly.com/catalog/regex/)
You can find additional information on regular expressions and wildcard characters by
searching the Web.
5 Click Apply to save your changes.
Clicking OK does not apply the changes to the directory.
6 Verify that the change has been synchronized with the peer clusters by the Identity Vault.
7 Continue with Section 10.4, “Adding Storage Management Configuration Information,” on
page 89 .
10.4 Adding Storage Management Configuration
Information
You can create BCC load and unload scripts for each BCC-enabled resource in each peer cluster.
You can add commands that are specific to your storage hardware. These scripts and commands
might be needed to promote mirrored LUNs to primary on the cluster where the pool resource is
being migrated to, or demote mirrored LUNs to secondary on the cluster where the pool resource is
being migrated from.
You can also add commands and Perl scripts to resource scripts to call other scripts. Any command
that can be run at the Linux terminal console can be used. The scripts or commands you add are
stored in eDirectory. If you add commands to call outside scripts, those scripts must exist in the file
system in the same location on every server in the cluster.
IMPORTANT: Scripts are not synchronized by Identity Manager.
Consider the following guidelines when creating and using scripts:
Š Scripts must be written in Perl or have a Perl wrapper around them.
Š
Log files can be written to any location, but the BCC cluster resource information is logged to
SYSLOG (
/var/log/messages
).
Š
Error codes can be used and written to a control file so that you know why your script failed.
BCC checks only whether the script was successful. If an error is returned from the script, the
resource does not load and remains in the offline state.
Š
The BCC scripts are run from the MasterIP resource node in the cluster.