NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Registering the data collector
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Busy file settings properties
- Client attributes properties
- Client settings properties for UNIX clients
- Client settings properties for Windows clients
- Data Classification properties
- Default job priorities properties
- Encryption properties
- Exchange properties
- Exclude list properties
- Fibre transport properties
- General server properties
- Global attributes properties
- Logging properties
- Media properties
- Network settings properties
- Port ranges properties
- Preferred network properties
- Resilient network properties
- Restore failover properties
- Retention periods properties
- Scalable Storage properties
- Servers properties
- SharePoint properties
- SLP settings properties
- Managing credentials for workloads and systems that NetBackup accesses
- Managing deployment
- Managing host properties
- Section IV. Configuring storage
- Overview of storage options
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- Create a universal share
- Managing media servers
- Configuring storage units
- Managing tape drives
- Managing robots and tape drives
- Inventorying robots
- Managing volumes
- Managing volume pools
- Managing volume groups
- Staging backups
- Troubleshooting storage configuration
- Section V. Configuring backups
- Overview of backups in the NetBackup web UI
- Managing protection plans
- Managing classic policies
- Protecting the NetBackup catalog
- Catalog backups
- Managing backup images
- Pausing data protection activity
- Section VI. Managing security
- Security events and audit logs
- Managing security certificates
- Managing host mappings
- Configuring multi-person authorization
- Managing user sessions
- Configuring multifactor authentication
- Managing the global security settings for the primary server
- About trusted primary servers
- Using access keys, API keys, and access codes
- Configuring authentication options
- Managing role-based access control
- Disabling access to NetBackup interfaces for OS Administrators
- Section VII. Detection and reporting
- Detecting anomalies
- About backup anomaly detection
- Malware scanning
- Usage reporting and capacity licensing
- Detecting anomalies
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Administering NetBackup
- Management topics
- Managing client backups and restores
- About client-redirected restores
- Section X. Disaster recovery and troubleshooting
- Section XI. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
- About the NetBackup database installation
- Post-installation tasks
- Using the NetBackup Database Administration utility on Windows
- Using the NetBackup Database Administration utility on UNIX
Estimating catalog space requirements
NetBackup requires disk space to store its error logs and information about the files it backs up.
The disk space that NetBackup needs varies according to the following factors:
Number of files to be backed up
Frequency of full and incremental backups
Number of user backups and archives
Retention period of backups
Average length of full path of files
File information (such as owner permissions)
Average amount of error log information existing at any given time
Whether you have enabled the database compression option.
To estimate the disk space that is required for a catalog backup
- Estimate the maximum number of files that each schedule for each policy backs up during a single backup of all its clients.
- Determine the frequency and the retention period of the full and the incremental backups for each policy.
- Use the information from steps 1 and 2 to calculate the maximum number of files that exist at any given time.
For example:
Assume that you schedule full backups to occur every seven days. The full backups have a retention period of four weeks. Differential incremental backups are scheduled to run daily and have a retention period of one week.
The number of file paths you must allow space for is four times the number of files in a full backup. Add to that number one week's worth of incremental backups.
The following formula expresses the maximum number of files that can exist for each type of backup (daily or weekly, for example):
Files per Backup × Backups per Retention Period = Max Files
For example:
A daily differential incremental schedule backs up 1200 files and the retention period for the backup is seven days. Given this information, the maximum number of files that can exist at one time are the following:
1200 × 7 days = 8400
A weekly full backup schedule backs up 3000 files. The retention period is four weeks. The maximum number of files that can exist at one time are the following:
3000 × 4 weeks = 12,000
Obtain the total for a server by adding the maximum files for all the schedules together. Add the separate totals to get the maximum number of files that can exist at one time. For example, 20,400.
For the policies that collect true image restore information, an incremental backup collects catalog information on all files (as if it were a full backup). This changes the calculation in the example: the incremental changes from 1200 × 7 = 8400 to 3000 × 7 = 21,000. After 12,000 is added for the full backups, the total for the two schedules is 33,000 rather than 20,400.
- Obtain the number of bytes by multiplying the number of files by the average number of bytes per file record.
If you are unsure of the average number of bytes per file record, use 132. The results from the examples in step 3 yield:
(8400 × 132) + (12,000 × 132) = 2692800 bytes (or about 2630 kilobytes)
- Add between 10 megabytes to 15 megabytes to the total sum that was calculated in step 4. The additional megabytes account for the average space that is required for the error logs. Increase the value if you anticipate problems.
- Allocate space so all the data remains in a single partition.