
We recommend designing and implementing a virtual machine-based backup policy, which enables IT
Administrators or Backup Administrators to design a simple backup policy in comparison to using file-based
solutions.
If you choose to design and implement a file-based solution, you will encounter some technical difficulties:
Each node has different variable data, such as
Configuration files
Database
Log files
The Controller node and Baremetal host require a synchronized backup to maintain their states.
The Admin node can be occasionally backed up.
The Controller node and Baremetal host require backups on a regular basis.
The complexity involved in performing file-based backup for each node.
Restoring the environment involves additional, manual steps to recover the Management Host.
The MAC address of the systems must be saved so that the restoration occurs seamlessly during a file-
based restore. This is required in case you need to recreate the environment because it was lost due to
corruption or other reasons.
Note: We recommend you use any enterprise backup/restore solution that supports hot backup. We do not
recommend that you implement a cold backup policy because it involves downtime of the private cloud
environment.
Recommended backup schedule
The following table shows our backup frequency recommendations for HP Cloud OS for Moonshot
Management Host.
Component Backup schedule Notes
Admin Node Monthly Perform a full backup operation after a successful cloud deployment.
Controller Node
Baremetal Host
Nightly
Backup of Controller Node and Baremetal Host must occur at the
same time to preserve the system state.
© Copyright 2014 Hewlett-Packard Development Company Page 3
Comentarios a estos manuales