There are some considerations that must be accounted for when using Data Guard databases with AppSync. These considerations apply during operations with the protection and repurposing workflows, include mounting, recovery, and restore.
- Protection or repurposing: For a database in an Oracle Data Guard configuration, only a primary database can be protected using the hot backup mode. Standby databases cannot be protected using hot backup mode. Oracle does not allow a Standby database to enter hot backup mode. A Standby database that is in open in Passive/Non-Active Standby mode can be protected without using hot backup, without having to change the open mode of the database. This only applies to Data Guard databases however, and not regular Oracle standalone databases.
- Mount or recovery: Operations like mounting and recovery of copies work the same way for Oracle Data Guard databases as they do for regular Oracle Standalone databases. When a Primary or Standby database is mounted, and then recovered, it loses all its Data Guard properties and behaves like a Standalone Oracle database on the host where it is mounted.
- Restore: For a database in an Oracle Data Guard configuration, the restore operations work the same way as it does for Oracle Standalone databases. Only Primary databases, in a Data Guard environment, can be restored using AppSync. Standby databases cannot be used for restoring purposes.