After enabling log archiving, you can change the archive destination based on your business needs.
Limitations and considerations
If you use AWS S3 or another object storage service compatible with the S3 protocol as the archive medium, the lag of log archiving, which is specified by the
archive_lag_targetparameter, must be greater than or equal to 60 seconds.Automatic cleanup only supports cleaning up the backup and archive data in the paths currently specified by
DATA_BACKUP_DESTandLOG_ARCHIVE_DEST. After you change the archive destination, the data in the original archive path can only be cleaned up manually. For more information about manually cleaning up backup data, see Manually clean up specified backup or archive data and Manually clear a backup or archive path.
Procedure
Log in to the
systenant or a user tenant as the administrator.Disable log archiving. For more information, see Disable archiving mode.
Reconfigure the log archive destination.
When you reconfigure the archive destination, if the destination directory is an archive directory that has been used by the tenant before, the
formatfile in the directory must exist. Otherwise, the destination directory must be empty.For more information about how to configure the archive destination, see the Configure the archiving destination section in Prepare for log archiving.
Query the
CDB_OB_ARCHIVE_DESTview in thesystenant or theDBA_OB_ARCHIVE_DESTview in a user tenant to verify whether the new archive destination is successfully configured. For more information, see View archive parameters.
What to do next
After you change the archive destination, you must enable log archiving again. For more information, see Enable archiving mode.