Revive an Eon DB

Vertica provides the following methods to revive down or terminated Eon Mode databases:

• In-database restore points: create lightweight, copy-free database restore points that enable you to revive a new or existing database to the state at which the restore point was saved. As restore points are based on database metadata and do not require the creation of backup data copies, they have low data overhead and a short creation time. However, because restore points are in-database, they are lost if the database's communal storage is compromised. For more information about in-database restore points, see In-DB restore points.
• Communal storage: revives a terminated database to its last-synchronized pre-termination state using the database's communal storage. Even if you terminate the database, the communal storage still holds the database's data and catalog. To revive the database with this method, you must provision a new database cluster and configure it to use the database's data and metadata stored in communal storage. For details, see Revive with commuanal storage.
• vbr: the vbr backup task saves a backup copy of the entire database or a subset of the data, ideally to a location separate from the database itself. You can then use the vbr restore task to restore the database or specified objects to the backed up state. vbr supports using a backup from one cluster to restore to a different cluster of the same architecture. For more information about vbr-based backups, see vbr backup and restore.