Accelerator notes and requirements
Note the following about the NetBackup accelerator:
NetBackup accelerator must be properly licensed. For the latest information on licensing, contact your NetBackup sales or partner representative.
Supports the disk storage units only. Supported storage includes Media Server Deduplication Pool, NetBackup appliance, cloud storage, and qualified third-party OST storage. For supported storage types, see the NetBackup Enterprise Server and Server - Hardware and Cloud Storage Compatibility List at the following URL: https://www.veritas.com/support/en_US/article.100040093
Storage unit groups are supported only if the storage unit selection in the group is Failover.
Supports full backups and incremental backups.
For every policy that enables the Use Accelerator option, the following backup schedules are recommended at a minimum: A full backup schedule with the Accelerator forced rescan option enabled. Another full backup schedule without the Accelerator forced rescan option enabled. See Accelerator force rescan for Cloud object store (schedule attribute).
If a previous backup of the policy, bucket and query does not exist on the backup host or scale-out server, NetBackup performs a full backup, and creates a track log on the backup host or scale-out server. This initial backup occurs at the speed of a normal (not accelerated) full backup. Subsequent Accelerator backups using the same backup host or scale-out server use the track log for accelerated backup speed.
Note:
When you first enable a policy to use accelerator, the next backup (whether full or incremental) is in effect a full backup. It backs up all objects corresponding to Cloud objects queries. If that backup was scheduled as an incremental, it may not be completed within the backup window.
NetBackup retains track logs for future accelerator backups. Whenever you add a query, NetBackup does a full, non-accelerated backup for the queries that are added to the list. The unchanged queries are processed as normal accelerator backups.
If the storage unit that is associated with the policy cannot be validated when you create the policy, it is validated later, when the backup job begins. If accelerator does not support the storage unit, the backup fails. In the bpbrm log, a message appears that is similar to one of the following: Storage server %s, type %s, does not support image include. Storage server type %s, does not support accelerator backup.
Accelerator requires that the storage have the
OptimizedImageattribute enabled.The Expire after copy retention can cause images to expire while the backup runs. To synthesize a new full backup, the SLP-based accelerator backup needs the previous backup.
To detect changes in metadata, NetBackup uses one or more cloud APIs per object/blob. Hence, change detection time increases with the number of objects/blobs to be processed. You may observe backups running longer than expected in cases with little or no data change but a large number of objects.
If in your environment, for a given object, the metadata or tag is always changed (added/removed/updated) with its data. Evaluate using incremental without accelerator over incremental with accelerator from a performance and cost viewpoint.
While creating a Cloud object store policy with multiple tag-based queries, you can use a few simple rules to get the best effect with accelerator. Use the query builder in the policy creation page, and create separate queries, one query per tag. The accelerator-based policies perform best in this configuration.
NetBackup has two ways to determine whether an object is considered for incremental backup or not.
The object's modification time.
Any changes in the tags and user attributes.
These metadata checks are not required for the organization environments where the metadata of the objects do not change after the objects are created. You can use the option in the policy to avoid these metadata checks, which lead to faster change detection and faster accelerated backup.