For standalone Oracle databases running on Windows VMs, you can perform application-based backups from a VSA subclient, then use the Oracle database agent to restore a database.
Application-based backups using the Virtual Server Agent are supported for Microsoft Windows versions of Oracle that are listed in System Requirements for the Oracle Agent.
If the first application-based backup installs a plug-in for Oracle for Windows, the backup fails. Restart Oracle services on the virtual machine where Oracle is running after the application-based workflow completes, and then retry the backup.
For Windows VMs running Oracle, ensure that data and logs are on separate volumes.
You cannot perform application-based backups for Oracle databases that use Automatic Storage Management (ASM) disk groups.
An Application Class 1 license is required for the initial installation and configuration of application plug-ins. After the initial configuration is complete, application-based backups release the Application Class 1 license and consume Application Class Virtual licenses instead.
To perform backups and restores for Oracle for Windows databases, a user account with admin privileges for the application and database is required.
Include Windows virtual machines running Oracle in a separate subclient under a Virtual Server instance.
Perform full or incremental backups for VM groups (subclients) that are configured for application-based backups. Synthetic full backups are not supported. Scheduled synthetic full backups are converted automatically to full backups for VM groups and subclients that are configured for application-based backups.
Archive Log Backups
Oracle for Windows database logs are automatically backed up as part of application-based backups. The following methods provide log protection:
A snap backup of the archive log volume is taken as part of application-based backups.
An automatic log backup schedule is created automatically after you run an application-based backup successfully for the first time. A backup on the Archive Log Subclient runs immediately after the first successful application-based backup.
As part of the automatic log backup schedule, logs are backed up before the archive log destination reaches the available disk space threshold (by default, 70%), or at a regular interval (by default, every 24 hours).
If the Oracle database is in NOARCHIVELOG mode, you must select the Offline Database option on the Content tab of the default subclient properties dialog box for the database to back up the database offline.