Backup and Restore (BAR) will be supported for managed OTF tables, and the archived tables cannot be dropped. This implementation follows a backup-in-place model; hence, the Archived Managed OTF tables will be protected from DROPs.
The in-place backup is a mechanism to manage the protection of the user object store data through the corresponding dictionary and metadata that exists in the Teradata Database Engine.
The external Catalog data or the actual OTF table’s data from the object store will not physically be read by the backup processes, and that will not be archived.
Backup Strategy
- Backup Count Configuration: When backups are initiated on managed OTF tables, DSA sets the backup count in the SQLE metadata to avoid inconsistencies between the backup set and the data stored in the object store.
- Default Backup Exclusions: In VantageCloud Lake, Backup-As-a-Service (BaaS) will exclude Managed OTF tables from the default backup configuration. For Managed OTF tables, it is recommended to adopt a partial backup strategy tailored to their specific requirements.
Disaster Recovery is not supported in the current phase.