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 using Amazon IAM roles with NetBackup
- Protecting data with Amazon Snowball and Amazon Snowball Edge
- 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
- About unified logging
- About legacy logging
- Troubleshooting cloud storage configuration issues
- Troubleshooting cloud storage operational issues
About restoring data from Amazon Glacier
The NetBackup image is stored as set of objects with specified storage class, in this case, GLACIER or GLACIER_DEEP_ARCHIVE storage class. Restore from Amazon Glacier happens in two phases:
The objects are first retrieved at an internal staging location that is maintained by Amazon.
From there, the data is restored at the destination location.
NetBackup supports the following Amazon retrieval types:
Bulk retrieval, which completes within 5-12 hours.
Standard retrieval, which completes within 3 - 5 hours.
Expedited retrieval, which completes within 1-5 minutes.
For more about Amazon S3 storage classes, review Amazon S3 Storage Classes.
If you specify Expedited retrieval, Amazon can sometimes fail the request because of a lack of resources. If this failure happens, you must use Standard retrieval or Bulk retrieval. In this case, the restore job fails (NetBackup status 5: restore failed completely).
The activity monitor displays this message from
bpbrm: Image warming failed 503. The following error is in the
esfs_storage log on the CloudCatalyst server:GlacierExpeditedRetrievalNotAvailable: Glacier expedited retrievals are currently not available, please try again later status code: 503
When you perform a restore, the entire image fragment is restored while only the selected objects are downloaded.
If you use Glacier with CloudCatalyst, you can create
GLACIER_RETRIEVAL touch file on master server in /
usr/openv/netbackup/bin directory with one of three strings in it: bulk, standard, or expedited. You can create this touch file if you do not want to use the Bulk retrieval option.
If you use Glacier then you can use bulk, standard, or expedited. If you use DEEP_ARCHIVE you can use bulk or standard. If no string is defined, NetBackup's default is bulk if the touch file does not exist.
If you use Glacier with non-CloudCatalyst cloud storage servers, only Amazon Standard retrieval is supported.
For more about restoring using Amazon S3, review Restoring Archived Objects.
This section does not apply to CloudCatalyst, only non-CloudCatalyst storage servers.
If the files and folders, you want to restore belong to multiple image fragment consider the following:
One image fragment is retrieved at a time. Only after the selected files and folders part of the first image fragment are downloaded, the next image fragment is retrieved.
The restore time must be considered depending on the number of image fragments. For example, if the files you want to restore are part of two fragments, an additional 6 - 10 hours will be added to the complete restore time.
If you cancel a job after the restore retrieval is initiated, cost is incurred for all the objects that are retrieved on the staging location till the point of cancellation.