Backup & Restore
Q: How are the backups validated?
A: Backup validation is an integral feature of the ZDLRA and executed implicitly.
Q: How are missing backups detected?
A: The Trivadis Intelligent Backup (TIB) solution creates critical events if a backup is missing within a defined interval and retention. Failed backups create events as well. These events are propagated to the platform monitoring.
Q: Can the customer initiate a database backup manually or on-demand?
A: No.
Backups are fully automated scheduled in order to provide the required RPO/RTO.
Q: How do I restore a database?
A: Database restore is a so called day-2 action on level PDB. Check the restore PDB section.
Q: What is the restore approach in an ADVANCED setup with Data Guard?
A: In a first step, a point-in-time restore (PITR) from backup is initiate on the Primary PDB. Secondly, the Standby PDB will be restored from service. With this approach the backup system will be relieved for the 2nd step, and even more important, this method is more reliable than restore from backup. As a consequence, consider some higher load (I/O, CPU) on the Primary PDB while restoring the Standby PDB.
Q: What happens with the database backups if a database is deleted?
A: The backup sets will be deleted from the backup appliance (ZDLRA) after the retention. Means, if you delete a CDB today, our workflow sets the backup deletion timestamp (sysdate+10) in our metadata repository. A daily job deletes the databases resp. the backups from the ZDLRA. In other words, the backup will out-age according the retention period of 11 days).
Q: How long will the database backup remain available after de-activation of the backup?
A: In case of backup de-activation on CDB level (day-2 action) the restore database day-2 action will return an error message (stating "backup option not activ"). Nevertheless, the backup will remain on the backup appliance according the backup retention (see above), and can be restored upon service request within the retention period (charged separately).