NetBackup™ Web UI Administrator's Guide
- Introducing the NetBackup web user interface
- Section I. Managing security
- Monitoring and notifications
- Managing role-based access control
- Configuring RBAC
- Role permissions
- Global > NetBackup management
- Global > Security
- Global > Storage
- Global > NetBackup management
- Manage access
- Configure an external certificate for the NetBackup web server
- Security events and audit logs
- Managing security certificates
- Managing user sessions
- Managing master server security settings
- About trusted master servers
- Creating and using API keys
- Configuring authentication options
- Managing hosts
- Troubleshooting the web UI
- Section II. Managing storage and backups
- Configuring storage
- Managing protection plans
- Managing protection plans for Microsoft SQL Server
- Usage reporting and capacity licensing
- Configuring storage
- Section III. Veritas Resiliency Platform
- Section IV. Managing credentials
Using copy-only snapshot backups to affect how differentials are based
When you use both full backups and snapshot backups to protect SQL Server, the previous snapshot backup expires after the next snapshot backup is created. If you require a point in time restore before the latest backup, the differentials are based on a snapshot backup that no longer exists. Alternatively, NetBackup lets you create copy-only backups that are out-of-band so the backup does not reset the differential baseline. Differential backups are then based on the last full backup.
If a failure occurs and is detected immediately, you can restore the last full backup. Then you can replay the necessary transaction logs to achieve recovery. However, if a failure is not detected until after the next full backup, then there are no snapshot backups available to restore (see Figure: Recovering after an error when using full and copy-only backups). When you use copy-only backups, each differential is instead based on the last full backup that is not copy-only. You can restore the last full backup, restore the latest differential backup, then restore the necessary transaction log backups before the error occurred.