Cyclades AlterPath BladeManager - Manual (Page 158)

4: BladeManager Web Administration
4-76 AlterPath BladeManager Manual
Backup and Restore Scenarios
For illustration purposes, there are two scenarios in which you can perform
the backup.
• Replicating data to a hot spare machine - You back up the configuration
data and data buffers and restore them to a second BladeManager unit.
This method enables you to keep the network identity of each
BladeManager unit, but maintain the same configuration for both units.
The second unit serves as a spare system.
• Replacing the existing BladeManager - You back up ALL data to an
external server. The BladeManager is then replaced with a new unit to
which all data is restored. The new unit will have the same configuration
as the original unit.
To use the Backup and Restore commands in CLI, see “Backup and Restore
Commands” on page 5-18.
System Recovery Guidelines
In the event that the BladeManager goes down, the system will check the
integrity of the file system during the restart. If a problem is found, then the
system will attempt to repair any damage that may have occurred.
When performing a recovery procedure, if there is too much damage, you
have the option to stop the booting process and take recovery actions through
the serial console as follows:
1. Rebuild system partition
2. Rebuild database
3. Rebuild data log partition
The rest of the configuration process is done through the GUI/web interface.
If the BladeManager goes down, you will still have direct access to ports and
consoles, but you will need to redefine the devices.