Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Cloud Administrator's Guide
  3. Troubleshooting
  4. Troubleshooting cloud storage operational issues
  5. Restoring from GLACIER_VAULT takes more than 24 hours for Oracle databases
Veritas NetBackup™ Cloud Administrator's Guide

Restoring from GLACIER_VAULT takes more than 24 hours for Oracle databases

Oracle forms a restore job, so that first the data files are restored (one job per data file) and then every set of archive logs (one restore job per set of logs) associated with the data files is restored. This causes the Oracle restore jobs to run five restore jobs in succession (when one restore job gets over, the next one automatically starts). Since every new restore job with data in a vault in Amazon Glacier cloud storage requires minimum four hours to retrieve the data to bring it on premise, this causes the Oracle data file restore jobs to run for 24 hours or longer.

There are two options to perform the recovery:

Using the NetBackup for Oracle recovery wizard

Increase the Number of parallel streams for restore and recover to the number of backup requests that are required. For example 10. You can set this number higher since Oracle RMAN will only use the required number of streams.

See section About NetBackup for Oracle restores in the NetBackup for Oracle Administrator's Guide.

Using the RMAN template

This procedure takes a longer time that the earlier mentioned method.

  1. Determine the log sequence and thread numbers required for the recovery step (restoring the archive logs). This can be done by looking at Oracle or by looking at the backup jobs.

  2. Create an RMAN script and allocate the required number of channels to perform the restore of the archive logs.

    For example: Consider a "run" block where 8 channels are allocated and restored sequence numbers 1373 - 1380

    RMAN> run

    { allocate channel ch00 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch01 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch02 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch03 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch04 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch05 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch06 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    allocate channel ch07 type 'SBT_TAPE' PARMS 'SBT_LIBRARY=/bp/bin/libobk.so64';

    Restore the archive log from sequence 1373 thread 1 until sequence 1380 thread 1;

    release channel ch00;

    release channel ch01;

    release channel ch02;

    release channel ch03;

    release channel ch04;

    release channel ch05;

    release channel ch06;

    release channel ch07;

    }

  3. Using the NetBackup for Oracle client, start NetBackup Backup, Archive, and Restore interface or create another script to restore the data file or files. If you're restoring more than one data file, you may need to increase the number of streams if each data file is in a different image.

  4. Start the restore of the data files and archive logs to run in parallel.

  5. Perform the recovery of the database or data files using the NetBackup Backup, Archive, and Restore interface or by using another script.

See the NetBackup for Oracle Administrator's Guide.

Feedback

Was this page helpful?
Previous

Restoring from Amazon Glacier vault spans more than 24 hours for single fragment

Next

Troubleshooting failures due to missing Amazon IAM permissions

Feedback

Was this page helpful?