VCSA Backup Scheduler and External Oracle Database Schema Change Rollback Interoperability

The goal is to determine whether the VCSA built‑in backup scheduler can be relied upon to capture a transactionally consistent state of an external Oracle/MSSQL database used by vCenter Server, so that a failed schema change can be rolled back by restoring only that backup instead of a full VCSA restore.

The VCSA scheduler backs up the VCSA appliance filesystem and its embedded Postgres database; for external databases it only triggers a pre‑upgrade compatibility check and does not automate vendor‑specific backup tools. There is no documented procedure that guarantees the scheduler will quiesce the external DB or capture a point‑in‑time copy suitable for schema downgrade, and version‑specific behavior between vCenter 7.x, 8.0 and later releases is not fully clarified.

• Is it supported to configure the VCSA backup scheduler to trigger an Oracle RMAN (or MSSQL VSS) backup automatically before a schema change?
• What validation steps are recommended to confirm that a backup taken by the VCSA scheduler includes a transactionally consistent Oracle schema suitable for rollback?
• Are there any documented limitations that prevent using VCSA backup for external DB rollback testing across vCenter versions?