NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Introducing NetBackup
- Administering NetBackup licenses
- Introducing NetBackup
- Registering the data collector
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Managing credentials for workloads and systems that NetBackup accesses
- Add a credential for CyberArk
- Managing deployment
- Section IV. Configuring storage
- Overview of storage options
- Configuring storage units
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- Managing media servers
- Managing tape drives
- 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 multi-factor 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
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Disaster recovery and troubleshooting
- Section X. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
About fragmentation
Table fragmentation can impede performance. When rows are not stored contiguously, or if rows are split into more than one page, performance decreases because these rows require additional page accesses.
When an update to a row causes it to grow beyond the originally allocated space, the row is split. The initial row location contains a pointer to another page where the entire row is stored. As more rows are stored on separate pages, more time is required to access the additional pages.
Reorganizing may also reduce the total number of pages that are used to store the table and its indexes. It may reduce the number of levels in an index tree. Note that the reorganization does not result in a reduction of the total size of the database.
The General tab completely rebuilds the database, eliminating any fragmentation, and free space. This option may result in a reduction of the total size of the database.
option on theMore Information