Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Deduplication Guide
  3. Managing deduplication
  4. About MSDP storage rebasing
Veritas NetBackup™ Deduplication Guide

About MSDP storage rebasing

During an initial backup, NetBackup writes the data segments from a backup to as few container files as possible. Read performance is best when the data segments from a client backup are close to each other on deduplication storage. NetBackup consumes less time finding and reassembling backed up files when their segments are near each other.

However, the data segments in a backup may become scattered across the disk storage each time the client is backed up. Such scattering is a normal consequence of deduplication.

NetBackup includes a process, called rebasing, that helps to maintain the data segments in as few container files as possible. Rebasing improves performance for the operations that read from the storage, such as restores and duplications. NetBackup writes all of the data segments from a backup into new container files even though the segments exist on storage already. Future backups then refer to the new copies of those segments rather than the old copies until any changes because of future rebasing. Deduplication rates for the backup jobs that perform rebasing are lower than for the jobs that do not rebase the data.

After the rebasing, NetBackup reclaims the storage space that the rebased data segments used.

Table: Types of rebasing describes the rebasing operations.

Table: Types of rebasing

Type

Description

Normal backup rebasing

The rebasing that occurs during a backup if the normal rebasing criteria are met, as follows:

  • The container has been rebased within the last 3 months.

  • For that backup, the data segments in the container consume less space than the FP_CACHE_PERIOD_REBASING_THRESHOLD value. The FP_CACHE_PERIOD_REBASING_THRESHOLD parameter is in the pd.conf file.

    See MSDP pd.conf file parameters.

Backup rebasing occurs only for the full backups that pass through the normal MSDP backup process. For example, the NetBackup Accelerator backups do not pass through the MSDP backup process.

NetBackup reports backup job completion after the rebasing is completed.

Periodic backup rebasing

The rebasing that occurs during a backup if the periodic rebasing criteria are met, as follows:

  • The container has not been rebased within the last 3 months.

  • For that backup, the data segments in the container consume less space than the FP_CACHE_REBASING_THRESHOLD value. The FP_CACHE_REBASING_THRESHOLD parameter is in the pd.conf file.

    See MSDP pd.conf file parameters.

Backup rebasing occurs only for the full backups that pass through the normal MSDP backup process. For example, the NetBackup Accelerator backups do not pass through the MSDP backup process.

NetBackup reports backup job completion after the rebasing is completed.

Server-side rebasing

The storage rebasing that occurs on the server if the rebasing criteria are met. Server-side rebasing includes the deduplicated data that does not pass through the normal MSDP backup process. For example, the NetBackup Accelerator backups do not pass through the MSDP backup process.

Some parameters in the contentrouter.cfg file control the server-side rebasing behavior.

See MSDP server-side rebasing parameters.

Feedback

Was this page helpful?
Previous

About managing MSDP storage read performance

Next

MSDP server-side rebasing parameters

Feedback

Was this page helpful?