Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the cloud storage vendors for NetBackup
- About the Amazon S3 cloud storage API type
- Amazon S3 cloud storage vendors certified for NetBackup
- Amazon S3 storage type requirements
- Permissions required for Amazon S3 cloud provider user
- Amazon S3 cloud storage provider options
- Amazon S3 cloud storage options
- Amazon S3 advanced server configuration options
- Amazon S3 credentials broker details
- About private clouds from Amazon S3-compatible cloud providers
- About Amazon S3 storage classes
- Amazon virtual private cloud support with NetBackup
- About protecting data in Amazon for long-term retention
- Protecting data using Amazon's cloud tiering
- About using Amazon IAM roles with NetBackup
- About NetBackup character restrictions for Amazon S3 cloud connector
- Protecting data with Amazon Snowball and Amazon Snowball Edge
- Configuring NetBackup for Amazon Snowball with Amazon Snowball client
- Configuring NetBackup for Amazon Snowball with Amazon S3 API interface
- Using multiple Amazon S3 adapters
- Configuring NetBackup with Amazon Snowball Edge with file interface
- Configuring NetBackup for Amazon Snowball Edge with S3 API interface
- Configuring NetBackup for Amazon Snowball and Amazon Snowball Edge for NetBackup CloudCatalyst Appliance
- Configuring SSL for Amazon Snowball and Amazon Snowball Edge
- Post backup procedures if you have used S3 API interface
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- Configuring cloud storage in NetBackup
- Before you begin to configure cloud storage in NetBackup
- Configuring cloud storage in NetBackup
- Cloud installation requirements
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- Deploying host name-based certificates
- Deploying host ID-based certificates
- About data compression for cloud backups
- About data encryption for cloud storage
- About NetBackup KMS for encryption of NetBackup cloud storage
- About external KMS for encryption of NetBackup cloud storage
- About cloud storage servers
- About object size for cloud storage
- About the NetBackup media servers for cloud storage
- Configuring a storage server for cloud storage
- Changing cloud storage server properties
- NetBackup cloud storage server properties
- About cloud storage disk pools
- Configuring a disk pool for cloud storage
- Saving a record of the KMS key names for NetBackup cloud storage encryption
- Adding backup media servers to your cloud environment
- Configuring a storage unit for cloud storage
- About NetBackup Accelerator and NetBackup Optimized Synthetic backups
- Enabling NetBackup Accelerator with cloud storage
- Enabling optimized synthetic backups with cloud storage
- Creating a backup policy
- Changing cloud storage disk pool properties
- Certificate validation against Certificate Revocation List (CRL)
- Managing Certification Authorities (CA) for NetBackup Cloud
- Monitoring and Reporting
- Operational notes
- NetBackup bpstsinfo command operational notes
- Unable to configure additional media servers
- Cloud configuration may fail if NetBackup Access Control is enabled
- Deleting cloud storage server artifacts
- Using csconfig reinitialize to load updated cloud configuration settings
- Enabling or disabling communication between master server and legacy cloud storage media servers
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup cloud storage log files
- Enable libcurl logging
- NetBackup Administration Console fails to open
- Troubleshooting cloud storage configuration issues
- NetBackup Scalable Storage host properties unavailable
- Connection to the NetBackup CloudStore Service Container fails
- Cannot create a cloud storage disk pool
- Cannot create a cloud storage
- Data transfer to cloud storage server fails in the SSL mode
- Amazon GovCloud cloud storage configuration fails in non-SSL mode
- Data restore from the Google Nearline storage class may fail
- Backups may fail for cloud storage configurations with Frankfurt region
- Backups may fail for cloud storage configurations with the cloud compression option
- Fetching storage regions fails with authentication version V2
- Troubleshooting cloud storage operational issues
- Cloud storage backups fail
- Stopping and starting the NetBackup CloudStore Service Container
- A restart of the nbcssc (on legacy media servers), nbwmc, and nbsl processes reverts all cloudstore.conf settings
- NetBackup CloudStore Service Container startup and shutdown troubleshooting
- bptm process takes time to terminate after cancelling GLACIER restore job
- Handling image cleanup failures for Amazon Glacier vault
- Cleaning up orphaned archives manually
- Restoring from Amazon Glacier vault spans more than 24 hours for single fragment
- Restoring from GLACIER_VAULT takes more than 24 hours for Oracle databases
- Troubleshooting failures due to missing Amazon IAM permissions
- Restore job fails if the restore job start time overlaps with the backup job end time
- Post processing fails for restore from Azure archive
- Troubleshooting Amazon Snowball and Amazon Snowball Edge issues
- Index
About using Amazon IAM roles with NetBackup
An AWS IAM role is an Amazon Web Services (AWS) identity with the permission policy that determine what tasks an identity is authorized to perform. You can use roles to delegate access to users, applications, or the services that normally don't have access to AWS resources. A role is intended to be assumable by anyone who needs it. If a user assumes a role, temporary security credentials are created dynamically and provided to the user.
For example, an application running on the AWS Elastic Compute Cloud (EC2) instances requires the credentials to access the other AWS services like S3 service. With the traditional approach, you provide the fixed credentials access key and secret access key. With IAM roles, temporary credentials are used to connect to the other AWS services.
NetBackup supports the AWS IAM Roles for stream-based backup operations, wherein:
NetBackup uses AWS IAM Role that is attached to the AWS EC2 instances on which media server is configured for all S3 storage communications.
NetBackup fetches the role name and temporary credentials by connecting to the AWS EC2 metadata.
NetBackup master server can be deployed on AWS EC2 instance or on-premises. You must do the required network settings for communication between the master and media server(s).
The NetBackup media server or the CloudCatalyst media server that uses the IAM role to backup data to cloud must be deployed on the AWS EC2 instance.
AWS IAM Role with required permissions must be attached to the NetBackup media server running on the AWS EC2 instance. See Permissions required for Amazon S3 cloud provider user.
Backup data is stored in S3 storage of the same AWS account where the AWS IAM role is created.
NetBackup supports the AWS IAM Role-based authentication for both Amazon and Amazon Gov cloud providers.
You can modify existing cloud storage server (alias) to use AWS IAM role for authentication only using csconfig command.
Use the AWS Management Console to perform IAM Role allocation, modification, and revocation operations. NetBackup does not store any role-specific information.
Ensure that the AWS EC2 instance metadata service is accessible to NetBackup media server. You verify using AWS commands. For example,
To get the role name, run:
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/
To get the credentials, run:
curl http://169.254.169.254/latest/meta-data/iam/security-credentials/role-name
For IPv6 only deployments, AWS IAM Role cannot be used because AWS EC2 instance metadata service is supported only for IPv4.
AWS IAM Role is also supported with CloudCatalyst storage server.
The following diagram illustrates the deployment:
As illustrated in the diagram, to use AWS IAM role with NetBackup:
NetBackup master server can be deployed on-premises or in the cloud.
Backup data is stored in S3 storage of the same AWS account where the AWS IAM role is created.
AWS IAM role is attached to AWS EC2 instance on which CloudCatalyst media server is installed.
Note:
When role is attached to AWS EC2 instance that has access to S3 storage, NetBackup user doesn't need to provide any credentials.
Tip: You get better performance, if the NetBackup clients are deployed in cloud.