How Restore Works

Restoring standalone databases or Data Guard databases with Veeam Explorer for Oracle works in the following manner:

1. Veeam Explorer for Oracle connects to the target server and performs a series of validations. For example, it checks if the target server has enough free space for the restored database.

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 restore 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 required file operations including database and transaction logs copy. The Veeam Oracle Restore Service is removed from the target and the staging server once the restore process is completed.
• For Linux machines, Veeam Explorer for Oracle performs the necessary validations, for example, validating the SSH fingerprints of the target server, without deploying a non-persistent runtime component.

2. Veeam Explorer for Oracle sends a restore 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.
4. The Veeam Oracle Restore Service (for Windows machines) or Veeam Explorer for Oracle itself (for Linux machines) copies the database files and archived redo logs from the mounted file system to the native file system of the target machine and starts the restored database.

Data Guard databases are restored in the following way:

• When using latest state restore or point-in-time restore, the Data Guard configuration is restored by first restoring the primary node. It is then used to restore the remaining nodes and the Data Guard infrastructure.
• When restoring to another server, individual databases from the Data Guard configuration will be restored as standalone Oracle databases, preserving no Data Guard infrastructure.

After the restore operation successfully completes, Veeam Explorer for Oracle unmounts the mounted file system from the target server.