Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using KMS service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- Configuring deduplication to the cloud with NetBackup CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst storage server for deduplication to the cloud
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
About automated disaster recovery in cloud using CloudCatalyst
Automated disaster recovery (DR), provides a self-describing storage solution over CloudCatalyst. CloudCatalyst with automated DR in cloud is a self-describing storage server. CloudCatalyst without automated DR in cloud is not a self-describing storage server.
Currently, NetBackup supports automated DR in cloud for VMware VM backups and Standard backups.
This topic contains the following sections:
CloudCatalyst backed up the deduplicated data to cloud, but the NetBackup catalog was available only on the on-premises NetBackup server. There, the data cannot be restored from the cloud without the on-premises NetBackup server.
Automated DR in cloud uploads the NetBackup catalog along with the backup images and lets you restore data from the cloud without the on-premises NetBackup server.
You can launch automated DR on demand and recover the backup images from cloud.
Automated DR discovers the backup images that are stored in AWS S3 through the REST APIs, recovers the NetBackup catalog, and restores the images.
You can use command line options from NetBackup that have the function as REST APIs.
Before you install NetBackup, create an instance based on RHEL 7.3 or later (up to RHEL 8.0) in AWS. The recommendation is that the instance has more than 64 GB of memory, 8 CPUs, and IPv4-only network.
The HTTPS port 443 is enabled.
Change host name to the server's FQDN.
Add the following items in the
"External IP" "Server's FQDN"
"Internal IP" "Server's FQDN"
Change the search domain order in the
/etc/resolv.conffile to search external domains before internal domains.
NetBackup should be an all-in-one setup.
Refer to the NetBackup Installation Guide for more information.
After installing NetBackup, you can run the ims_system_config.py script to configure Automated DR.
Use the following command to run the ims_system_config.py script:
python /usr/openv/pdde/pdag/scripts/ims_system_config.py -k <AWS_access_key> -s <AWS_secret_access_key> -b <name_S3_bucket>
If you have configured IAM role in the EC2 instance, use the following command:
python /usr/openv/pdde/pdag/scripts/ims_system_config.py -k dummy -s dummy -b <name_S3_bucket>
Run the nbimageshare command to list and import the virtual machine and standard images and then recover the virtual machines.
The path to access the command is:
For more information about the nbimageshare command, refer to the NetBackup Commands Reference Guide.
The following table lists the steps for automated DR and the command options:
Table: Steps for automated DR and the command options
Log on to NetBackup
nbimageshare -login <username> <password>
List all the backup images that are in the cloud
In the list of images, the increment schedule type might be differential incremental or cumulative incremental.
Import the backup images to NetBackup
Import a single image:
nbimageshare -singleimport <client> <policy> <backupID>
Import multiple images:
nbimageshare -batchimport <image_list_file_path>
The multiple images number must be equal to or less than 64.
Recover the VM as an AWS EC2 instance
nbimageshare -recovervm <client> <policy> <backupID>
After the image is imported to cloud, the image catalog still exists on the cloud. If the image is expired on the on-premises storage, then restoring the image on the cloud fails even though the image catalog exists on the cloud.
If the image expires on the cloud storage, the image catalog in the cloud is removed but the image data in the bucket is not removed.
You can only recover the VM images that full backup images or accelerator incremental backup images to cloud.
Automated DR supports VMware and Standard policy types in NetBackup 8.2 or later in the optimum deduplication and Auto Image Replication scenarios. In the optimum deduplication and Auto Image Replication scenarios, CloudCatalyst, where the images are shared, must have a new installation of NetBackup 8.2.
After the automated DR is configured, the storage server is read-only in the DR mode.
For information on the VM recovery limitations, refer to the AWS VM import information in AWS help.
You can configure the maximum active jobs when the images are imported to cloud storage.
Modify the file path
/usr/openv/var/global/wsl/config/web.confto add the configuration item as imageshare.maxActiveJobLimit.
For example, imageshare.maxActiveJobLimit=16.
The default value is 16 and the configurable range is 1 to 100.
If the import request is made and the active job count exceeds the configured limit, the following message is displayed:
"Current active job count exceeded active job count limitation".
In optimized deduplication or AIR cascading scenarios, only the images in CloudCatalyst that has optimized deduplication or has an AIR target can be shared.
If CloudCatalyst is not set for optimized deduplication or is not an AIR target, you cannot use automated DR. If Amazon Glacier is enabled in CloudCatalyst, you cannot use automated DR.
In these scenarios to disable automated DR:
<install_directory>/etc/puredisk/spa.cfgfile and add the following configuration item:
Regarding the errors about role policy size limitation:
Errors that occur when the role policy size exceeds the maximum size is an AWS limitation. You can find the following error in a failed restore job:
"error occurred (LimitExceeded) when calling the PutRolePolicy operation: Maximum policy size of 10240 bytes exceeded for role vmimport"
You can change the maximum policy size limit for the vmimport role.
You can list and delete the existing policies using the following commands:
aws iam list-role-policies --role-name vmimport aws iam delete-role-policy --role-name vmimport --policy-name <bucketname> -vmimport
The recover operation includes AWS import process. Therefore, a vmdk image cannot be recovered concurrently in two restore jobs at the same time.