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
Guidelines for managing the primary server NetBackup catalog
Consider the following:
Catalog backup can be performed while regular backup activity takes place. It is a policy-based backup. It also allows for incremental backups, which can significantly reduce catalog backup times for large catalogs.
Warning:
Failure to backup the primary server NetBackup catalog may result in data loss if a catastrophic failure occurs to the file systems housing the various parts of the catalog.
Note:
Veritas recommends schedule-based, incremental catalog backups with periodic full backups.
Be cautious in using Accelerator full backups daily as a replacement for daily incremental backups. While Accelerator full backups are quick to run, the catalog size will be a full catalog backup instead of an incremental and can grow quickly in size. Backups of client data that contain millions of small files in combination with the use of Accelerator and frequent full backups can also cause the catalog to bloat.
Store the catalog on a separate file system.
The primary server NetBackup catalog can grow quickly depending on backup frequency, retention periods, and the number of files being backed up. With the catalog data on its own file system, catalog growth does not affect other disk resources, root file systems, or the operating system.
Information is available on how to move the catalog.
See How to calculate the size of your NetBackup image database.
The following directories and files that are related to the catalog can also be moved. Using an SSD device also improves performance:
On a Linux/UNIX host:
/usr/openv/netbackup/db/error
(directory)/usr/openv/netbackup/db/images
(directory)/usr/openv/netbackup/db/jobs
(directory)/usr/openv/netbackup/db/rb.db
(file)
On a Windows host:
C:\Program Files\VERITAS\NetBackup\db\error
(directory)C:\Program Files\VERITAS\NetBackup\db\images
(directory)C:\Program Files\VERITAS\NetBackup\db\jobs
(directory)C:\Program Files\VERITAS\NetBackup\db\rb.db
(file)
Change the location of the NetBackup relational database files.
The location of the NetBackup database files can be changed for better performance. For example, you may want to change the database location if the default location is running short of space. Using an SSD device also can improve performance.
The following directories and files that are related to the catalog can also be moved:
On a Linux/UNIX host:
/usr/openv/tmp
(directory)/usr/openv/var
(directory)/usr/openv/db/data
(directory)/usr/openv/db/staging
(directory)
On a Windows host:
C:\Program Files\VERITAS\NetBackup\Temp
(directory)C:\Program Files\VERITAS\NetBackup\var
(directory)C:\Program Files\VERITAS\NetBackupDB\data
(directory)C:\Program Files\VERITAS\NetBackupDB\staging
(directory)
Refer to the procedure in the section Moving a database after installation in the NetBackup Administrator's Guide, Volume I.
Set a delay to compress the catalog.
The default value for this parameter is 0, which means that NetBackup does not compress the catalog. As your catalog increases in size, you may want to use a value between 10 days and 30 days for this parameter. When you restore old backups, NetBackup automatically uncompresses the files as needed, with minimal performance effect.
Adjust the batch size for sending metadata to the catalog.
This setting affects overall backup performance, not the performance of catalog backups.
See Adjusting the batch size for sending metadata to the NetBackup catalog.
Best practices for primary server NetBackup catalog layout: