Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the Amazon S3 cloud storage API type
- About protecting data in Amazon for long-term retention
- Protecting data using Amazon's cloud tiering
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- Configuring cloud storage in NetBackup
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- About the NetBackup media servers for cloud storage
- Configuring a storage server for cloud storage
- NetBackup cloud storage server properties
- Configuring a storage unit for cloud storage
- Changing cloud storage disk pool properties
- Monitoring and Reporting
- Operational notes
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting cloud storage configuration issues
- Troubleshooting cloud storage operational issues
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:
Increase the
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.
This procedure takes a longer time that the earlier mentioned method.
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.
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;
}
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.
Start the restore of the data files and archive logs to run in parallel.
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.