NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Introducing NetBackup
- Administering NetBackup licenses
- Registering with Veritas Alta View
- Introducing NetBackup
- 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
Schedule expiration and purging of multi-person authorization tickets
Expiration period is configurable option defines the duration for which a multi-person authorization ticket can be in the Pending state. A ticket expires if it is in the Pending state for more than the configured expiry period.
For multi-person authorization configuration, expiration period can vary from minimum 24 hours to 168 hours. By default, tickets expire after 72 hours.
Purge period is a configurable option defines the duration for which a ticket resides in the tickets database. Purging a ticket ensures that the database does not grow exponentially. Purge period can vary from minimum 3 days to 30 days.
By default, tickets purge after 72 hours. All the Done, Expired, Rejected, and Canceled tickets are purged after the given purge period.
To schedule expiration and purging of tickets
- On the left pane, click Security > Multi-person authorization.
- On the top right, click Configure multi-person authorization.
- In the Schedules section, click Edit.
- Specify the expiration period (in hours) for the Expire ticket after option.
Specify the purge period (in days) for the Purge ticket after option.
- Click Save.
- Click Save.