How Publishing Works

Publishing Oracle databases with Veeam Explorer for Oracle works in the following manner:

1. Veeam Explorer for Oracle connects to the Veeam Mount Service and the target server and performs a series of validations. Some aspects of the validation process vary depending on the operating system of the Oracle machine.

• For Windows machines, Veeam Explorer for Oracle deploys the Veeam Oracle Restore Service on the target server and, if you publish your data up to a specific transaction, on the staging server. This non-persistent runtime component checks the valid rights assignments required for database recovery, gets information about the databases, and later performs the required database operations. The Veeam Oracle Restore Service is removed from the target and the staging server once you unpublish the database.
• For Linux machines, Veeam Explorer for Oracle performs the necessary validations without deploying a non-persistent runtime component. In addition, starting from Veeam Backup & Replication 12.1, Veeam Explorer for Oracle validates the SSH fingerprints of the target server.

2. Veeam Explorer for Oracle sends a publishing command to the Veeam Mount Service running on the mount server associated with the backup repository. The service connects to the backup repository and prepares the mounting operation.
3. The Veeam Mount Service mounts the necessary file system to the target Oracle machine. Mounting is done to the C:\VeeamFLR directory for Windows machines or the /tmp directory for Linux machines. For more information, see How Mounting Works.

The Veeam Oracle Restore Service (for Windows machines) or Veeam Explorer for Oracle itself (for Linux machines) opens the database from the mounted file system, so that you can perform the required operations with Oracle tools.

All changes to the database that occur after publishing are saved in the publishing write cache, whose location depends on the operating system of the Oracle machine.

• For Windows machines, the publishing write cache is stored on the mount server. You can view and change the write cache location in the mount server settings. For more information, see the Specify Mount Server Settings section of the Veeam Backup & Replication User Guide.
• For Linux machines, the publishing write cache is stored in the /var/tmp folder on the target server.

Once the publishing operation is completed, you can export the modified database as an Oracle RMAN backup. For more information, see Exporting as RMAN Backup.