Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the Amazon S3 cloud storage API type
- Protecting data in Amazon Glacier for long-term retention
- Protecting data using Amazon's cloud tiering
- About EMC Atmos cloud storage API type
- 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
Protecting data in Amazon Glacier for long-term retention
To protect your data for long-term retention you can back up the data to Amazon (AWS) Glacier using NetBackup. Using NetBackup, you can create a storage server with Glacier storage class. During the backup process, NetBackup internally uses the Amazon's zero-day lifecycle policy to transition data to Glacier. AWS lifecycle policy is a lifecycle rule defined to transition objects to the Glacier storage class in 0 (zero) days after creation. The following diagram illustrates the configuration process:
To configure a cloud storage server for Amazon GLACIER storage class
When you configure a storage server to transition data to Amazon Glacier, consider the following:
Ensure that Amazon Glacier is supported for the region to which the bucket belongs.
Ensure that the selected bucket does not have any existing Amazon lifecycle policy.
For restores, set the retrieval retention period to minimum 3 days.
Selectoption wherever possible to reduce time and cost for image imports.
To retrieve data sent to Glacier, there is an inherent time delay of around four hours per fragment of the backup image. For phase 2 of image imports, this time delay is prevalent for image(s) in the Glacier storage. However, if you enablein the policy, time spent for phase 2 imports reduces drastically from four hours to a few minutes per fragment. Phase 1 imports are faster, irrespective of whether is enabled or not for the policy.
See the NetBackup Administrator's Guide, Volume I to know more about supported workloads and file systems for.
See the NetBackup Administrator's Guide, Volume I to know more about the phases during image imports.
You can reduce restore time by parallel restores. For this, you must backup using multi-streaming that creates multiple images at logical boundaries.
Workload Granular Revovery (GRT) or VMware Single File Restore (SFR), increases the timeout on the master, media, and client to more than 5 hours.
Consider the following limitations:
NetBackup Accelerator feature is not supported for policies of the storage units that are created for Amazon Glacier. Do not select thecheck box.
CloudCatalyst with Glacier is not supported.
You must have the following permissions:
Life cycle policy related permissions:
Object tagging permissions
The bucket owner has these permissions, by default. The bucket owner can grant these permissions to others by writing an access policy.
Also ensure that you also have the required IAM USER permissions. See Permissions required for Amazon IAM user.