F5 6900, Руководство по платформе

Страница: 62 / 126

Chapter 6
6 - 6
Planning for system recovery
There are three different ways you can plan for a system recovery.
◆ You can maintain a redundant system. In the event of a failure, the
standby unit becomes active and handles incoming traffic.
◆ Another option is to configure a third unit with the same configuration
and store it in a safe place.
◆ A last option, that is not FIPS approved, is to copy the keys to a disk and
put the disk in a safe place.
Configuring a redundant system
The first option is to maintain a redundant system. In the event of a failure,
the standby unit becomes active and handles the incoming traffic. This
chapter describes how to create a redundant system configuration as part of
the initial configuration. After you configure failover properly, every time
you synchronize the configuration of the redundant system, you are
synchronizing card and key information for the security domain.
Configuring an additional unit for recovery
For additional system backup, you can take a third unit, fully configure it,
add it to the security domain, and synchronize the configurations. Remove
the unit from the network and store it in a safe location. If the BIG-IP
system in production is damaged or destroyed, you can take the backup unit
from storage and reconstitute the security domain.
Saving keys on a disk
Another possible method for preserving the keys is not FIPS-approved.
With this option, you generate your keys in software. Copy the keys to a
disk and put the disk in a secure place. Then you can import the keys into
the FIPS HSM. If there is a catastrophic system failure, you can use these
backup keys to create the security domain. This is not a FIPS-compliant
method for backup.