
535
High availability and load balancing using clusters
Backing up and restoring cluster configurations
when applying the restore in a cluster environment. You can specify the information to be restored or
not to be restored independently in a dialog box that appears during the restore process.
Restoring a cluster configuration
You can restore a cluster if you have an installed license or are using the 30-day grace period. HA/LB is
automatically enabled. Remember to install your HA/LB license before your 30-day grace period
expires.
After a cluster image is backed up, you can restore it at any time, providing that you backed it up with a
password. This lets you get to a predetermined state. The object of restoring in a cluster environment
is to propagate a known configuration to all members of a cluster using the File > Restore menu
command to apply the backup image on a single cluster member.
There are two ways to restore a cluster:
■
On the File menu, select the Restore option
■
Run the System Setup Wizard
In general, system information is never restored in a cluster environment. But, system information is
restored in a standalone environment. System information that is not restored to a cluster includes:
host name, interfaces, and the default gateway.
When restoring an image to a standalone system, the interface information is always restored and you
can correct the information on the Network Interface panel of the System Setup Wizard. Cluster
information is not restored.
Table 14-3
Cluster configuration backup and restore information
Process
Backed
up?
Restored?
Description
Location settings
Yes
Yes
All location configuration information is restored.
Entities are handled in a special manner. No local
interface information is allowed.
Policy
Yes
Yes
All policy configuration information is restored.
Interface
information
Yes
No
The interface information is not restored. Validation
has to ensure that the logical names match those that
are used by the rules.
Cluster name
Yes
No
A cluster name is not restored, but can be reused when
reforming a cluster.
VIPs
Yes
User-determined
VIPs defined by a cluster and used in rules for entities
can be restored.
Process monitoring
Yes
User-determined
You can restore processes that are being monitored and
cause the cluster to indicate a failed state when down.
Failover timeout
Yes
User-determined
N/A
Traffic groups
Yes
User-determined
N/A
Member information Yes
No
To allow restore to occur on new clusters with a
different number of members, the member information
is not restored.
NIC monitoring
Yes
No
This information is associated with members.
Member weight
Yes
No
Member information is not restored.
Ping group
Yes
User-determined
N/A
Содержание Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series
Страница 76: ...76 Managing administrative access Enabling SSH for command line access to the appliance...
Страница 242: ...242 Defining your security environment Controlling full application inspection of traffic...
Страница 243: ...243 Defining your security environment Controlling full application inspection of traffic...
Страница 269: ...268 Limiting user access Authenticating using Out Of Band Authentication OOBA...
Страница 319: ...318 Controlling traffic at the security gateway Blocking inappropriate content with content filtering...
Страница 373: ...372 Preventing attacks Enabling protection for logical network interfaces...
Страница 409: ...408 Providing remote access using VPN tunnels Multicast traffic through gateway to gateway IPsec tunnels...
Страница 509: ...508 Generating reports Upgrade reports...
Страница 553: ...552 Advanced system settings Configuring advanced options...
Страница 557: ...556 SSL server certificate management Installing a signed certificate...
Страница 861: ...860 Index...