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
Protecting data in Microsoft Azure Archive for long-term retention
To protect your data for long-term retention you can back up the data to Microsoft Azure Archive Blob storage using NetBackup. Using NetBackup, you can create a storage server with Archive storage tier.
The Archive storage tier is only available at the blob level and not at the storage account level.
Ensure that the following requirements are fulfilled:
You must have a general-purpose storage V2 to use Azure Archive.
Account level tier must be configured to HOT, else backup fails.
Consider the following limitations:
Accelerator and deduplication are not supported with Azure Archive.
If restore or cleanup fails, you need to manually set the tier to archive for corresponding blobs.
Configure the Azure Archive cloud storage server.
Create a disk pool with Microsoft Azure Container.
Storage unit is created using the disk pool.
Verify if the AZR:STORAGE_TIER property is configured for the storage server.
Once storage server is configured, its STORAGE_TIER cannot be changed.
Use the STU in the backup policy or the service lifecycle policy.
During backup, NetBackup first uploads data to HOT Tier and after the data is successfully uploaded, it is moved to the Archive Tier.
The following diagram illustrates the backup flow.
During restore, first image fragments are moved from Archive Tier to HOT tier. Movement of image fragments takes around 3 hrs to 15 hrs. After the image fragments are available in HOT Tier, they are downloaded to local storage. After the restore is complete, the image fragments on the HOT tier are moved back to the Archive Tier.
Image import from Azure Archive storage with TIR is faster.
The following diagram illustrates the restore flow.