Open topic with navigation
Currently in NuoDB, although the backup container does not need to mount either archive or backup volumes, the restore container must mount both the backup volume (the source) and the new archive volume (the target).
To be able to mount the backup volume while a database is still running, the backup volume must be a shared volume.
Note: If you create non-shared backup volumes, you must then manage the shutting down of Storage Managers (SMs) to release the backup volume so it can be mounted by the restore container. For a ‘restore existing database from backup’ operation, this is acceptable. However, for a ‘create a copy of a database from backup’ operation, this requires shutting down the running database in order to make a copy of its backup. To address this, two different restore templates are available.
When performing a restore operation, there are two options available:
To perform a restore operation using a restore template, log into OpenShift UI and do the following:
Note: The restore container uses a PVC to mount the source volume, and the target volume. If the target volume is a new database name, then a new PVC is created, which can subsequently be used once the restore has completed. If the target volume is an existing database name, then the restore can only be scheduled if the SM using that claim is shutdown first, and the restore process will clean out the contents of the target before restoring into that volume.