Installation guide

About backing up your system configuration 15-3
Chapter 15: Initial System Administration
Wave Global Administrator Guide
Special backup/restore considerations on a WaveNet node
If you are backing up or restoring a system configuration on a Wave Server that is a node in a
WaveNet network, note the important information in this section. (See Chapter 25 for complete
information about using WaveNet.)
Warning: Never restore a system configuration from one WaveNet node to another
WaveNet node on the same network. Doing so will introduce inconsistencies in the
network configuration, and the restored node will take the place of the backed-up node
in the WaveNet network. Extensive manual re-configuration will be required to correct
the network configuration.
If a Wave Server was physically connected as a node in a WaveNet network when you backed
up that Server’s system configuration, make sure that the Server is still physically connected
before you perform the restore so that the restored node is automatically re-synchronized with
the other nodes in the network.
After the restore completes, the restored node sends a message to each other node and
re-synchronizes based on the responses received. If the restored node is not connected to the
network or cannot establish connectivity with one or more other nodes, those nodes will be
removed from the WaveNet configuration on the restored node. If this occurs, the WaveNet
configuration must be manually re-created.
Important: Be sure to verify connectivity before you perform the restore—there is a 10 minute
window during which automatic re-synchronization is attempted. After 10 minutes, all of the
other nodes are removed from the WaveNet configuration on the restored node. At that point,
the WaveNet configuration must be manually re-created.
To verify that a Wave Server is physically connected to the WaveNet network
1 Make sure that the Wave Server to be restored is physically connected to the network via a
network cable.
2 From the node to be restored, verify that you can successfully Ping at least one other node
in the network.
Release 2.0
September 2010