Backing up and restoring the controller node
A preferred method to recover an IBM® Cloud Manager with OpenStack controller node is with the command, knife os manage update topology topology-file, from the deployer node. Alternatively, you can manually back up a controller node and subsequently use the backup to restore the controller node.
About this task
Important: The following tasks are specific to KVM,
which is the only supported hypervisor for backing up and restoring
the controller node.
Notes:
- If you are not familiar with OpenStack services, do not use the following steps to back up and restore your controller node.
- Avoid modifying any configuration files on the node side. The OpenStack services might crash if they are configured incorrectly. Also, if you update nodes with the deployment server, any manually modified configuration files are overwritten by the cloud configuration on the deployment server.
- If node configuration files are modified directly on the node side instead of updating with the deployment server, you must back up these configuration files and manually restore these files on the nodes.
- Database recovery is not covered in this section. For more information, see Backing up and restoring the OpenStack databases.
- IBM Cloud Manager - Self Service backup and recovery is not covered in this section. For more information, see Backing up and restoring IBM Cloud Manager - Self Service.