Cloud CM-IPMP Guía para resolver problemas descargar pdf (Pagina 59)

6.4 Backup and Restore

During normal operation, all SLEE management and proﬁle data in its own in-memory distributed database. The memory

database is fault tolerant and can survive the failure of a node. However, for management and proﬁle data to survive a total

restart of the cluster, it must be persisted to a permanent, disk-based data store. Open Cloud Rhino SLEE uses the PostgreSQL

database for this purpose.

For scheduled backups it is possible to use PostgreSQL’s

pg_dump

utility to backup the main working memory and working

conﬁguration. It is important to note that database backups made this way can only be restored successfully if the same Rhino

SLEE version is used with the restored database. For making backups that may reliably be used with a different version of the

Rhino SLEE, an export image of the SLEE should be created using the Exporter script (see Chapter 7).

6.4.1 Making PostgresSQL Backups

The PostgreSQL

pg_dump

utility can be used to backup the PostgreSQL database. For example, to backup a main working

memory database named “rhino_mgmt”:

pg_dump ---format=t rhino_mgmt > backup.tar

For more information on the options available to

pg_dump

, please refer to the PostgreSQL documentation.

6.4.2 Restoring a PostgresSQL Backup

Backups made using

pg_dump

can be imported using the

pg_restore

utility, for example:

pg_restore ---format=t --d rhino_mgmt backup.tar

If the database being restored already exists but contains existing data that conﬂicts with the data being imported, add the

-c

parameter to clean the target database before importing, e.g.:

pg_restore --c ---format=t --d rhino_mgmt backup.tar

Open Cloud Rhino 1.4.3 Administration Manual v1.1 50

1 2 ... 54 55 56 57 58 59 60 61 62 63 64 ... 200 201

Sin comentarios

Cloud CM-IPMP Guía para resolver problemas Pagina 59