How It Works

In this article

    When you start the instant recovery session in Veeam Explorer for Oracle, the following happens:

    1. Veeam Explorer uses backup files to publish the database on the target production server directly from backup.
    2. While the published database is online, Veeam Explorer starts to create a copy of the database on the target Oracle server.
    3. All changes in database files that occur after publishing are saved in cache.
    4. After all database files are copied to the target server, Veeam Explorer uses archived redo logs to synchronize changes in database files.
    5. After the synchronization, you can switchover to the up-to-date copy of the database on the production server. Depending on the option you choose, the switchover starts manually, automatically according to a specified schedule or immediately after synchronization. During switchover, Veeam Explorer does the following:
    1. Stops the published database.
    2. Uses redo logs to synchronize differences between the published database and the copied database files.
    3. Drops the published database.
    4. Starts the recovered database.

    Instant recovery session is resilient to network disruption, backup server or mount server crash. If anything disrupts the restore process, the restore process stays in the waiting mode and performs 10 automatic retries every 5 minutes. If the retries fail, you can launch retry after the server or network is up.

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.