Configure the archive subclient for the production database.
There may be times when you want to archive a subset of the table based on the value of one or more columns in the table (for example orders that are older than a certain date).
You can use an SQL query against the table columns to specify a subset of the table to archive.
You can include dependent tables or create new table relationships to ensure that the proper data is archived.
Best Practice: If you enable volume copy on an Oracle Archive instance, use the following subclient guidelines:
-
Create a new subclient that has the same content as the existing archiving subclient.
-
Use the new subclient for new backups instead of the existing subclient.
You can restore the data from existing subclient backups.
Choosing the Archive Format
Use the information in the following table to help determine which archive format to use.
|
Format |
Use Case |
|---|---|
|
Native |
Select this format when you want to reduce the database size, and when you need access to the archived data. |
|
Parquet |
Select this format when you want to retire the database application, but still need to query the data by using open source tools. |
|
XML |
Select this when you want to retire the database application, and to migrate the database to another database type, for example MariaDB. |