NetBackup™ Backup Planning and Performance Tuning Guide
- NetBackup capacity planning
- Primary server configuration guidelines
- Media server configuration guidelines
- NetBackup hardware design and tuning considerations
- About NetBackup Media Server Deduplication (MSDP)
- MSDP tuning considerations
- MSDP sizing considerations
- Accelerator performance considerations
- Media configuration guidelines
- How to identify performance bottlenecks
- Best practices
- Best practices: NetBackup AdvancedDisk
- Best practices: NetBackup tape drive cleaning
- Best practices: Universal shares
- NetBackup for VMware sizing and best practices
- Best practices: Storage lifecycle policies (SLPs)
- Measuring Performance
- Table of NetBackup All Log Entries report
- Evaluating system components
- Tuning the NetBackup data transfer path
- NetBackup network performance in the data transfer path
- NetBackup server performance in the data transfer path
- About shared memory (number and size of data buffers)
- About the communication between NetBackup client and media server
- Effect of fragment size on NetBackup restores
- Other NetBackup restore performance issues
- About shared memory (number and size of data buffers)
- Tuning other NetBackup components
- How to improve NetBackup resource allocation
- How to improve FlashBackup performance
- Tuning disk I/O performance
Disabling the sharing of NetBackup reservations
In NetBackup, shared reservations are enabled by default.
See Sharing reservations in NetBackup.
In most cases, sharing reservations results in better performance.
However, it may be helpful to disable sharing reservations in the following case:
Many duplication jobs are running (using a storage lifecycle policy, or Vault, or bpduplicate), and
Many read media are shared between different duplication jobs
In this case, without shared reservations, one job runs and other jobs requiring the same media are queued because they cannot get a reservation. With shared reservations, the jobs can start simultaneously. However, with a limited set of resources (media/drive pair or disk drives), resources may bounce or "ping-pong" between different jobs as each job requests the resource.
For example, assume the following:
Two duplication jobs, job 1 and job 2, are duplicating backup images. Job 1 is duplicating images 1 through 5, and job 2 is duplicating images 6 through 9. The images are on the following media:
Table: Media required by jobs 1 and 2
Media used by job 1 | Media used by job 2 |
---|---|
Image 1 is on media A1 Image 2 is on media A2 Image 3 is on media A2 Image 4 is on media A2 Image 5 is on media A3 | Image 6 is on media A2 Image 7 is on media A2 Image 8 is on media A2 Image 9 is on media A3 |
In this example, both jobs require access to media A2. Without shared reservations, if job 1 gets the reservation first, job 2 cannot start, because it needs to reserve media A2. A2 is already reserved by job 1. With shared reservations, both jobs can start at the same time.
Assume, however, that only a few drives are available for writing. Also assume that job 1 begins first and starts duplicating image 1. Then job 2 starts using media A2 to duplicate image 6. Media A2 in effect bounces between the two jobs: sometimes it is used by job 1 and sometimes by job 2. As a result, the overall performance of both jobs may degrade.
You can use the following procedure to disable the sharing of reservations.
To disable the sharing of reservations
- Create the following file:
On UNIX
/usr/openv/netbackup/db/config/RB_DO_NOT_USE_SHARED_RESERVATIONS
On Windows
install_path\Veritas\NetBackup\db\config\RB_DO_NOT_USE_SHARED _RESERVATIONS