Creating Subclients
As a best practice, it is recommended that you create separate subclients to back up data that undergo frequent changes.
For example, if the EXAMPLE and USERS dbspaces undergo frequent changes, you can create a separate subclient for each database.
Example:
-
User-defined subclient: Test1
Content: EXAMPLE
-
User-defined subclient: Test2
Content: USERS
Distributing the client data using subclients as recommended above, can help improve backup performance by organizing the workload on the client into logical groupings.
Subclient Content
As a best practice, add large databases to separate subclients and group smaller databases together in another subclient.
During backup operations, if a database fails within a subclient, the system skips the failed database and continues backing up the remaining databases in the subclient.
Although the system continues processing other databases after a failure, placing large databases in separate subclients is recommended. Smaller databases typically complete quickly, and isolating large databases improves manageability, troubleshooting, and performance optimization.
Managing transaction logs for File System based backup
We recommend you to schedule several log only backups between full backups. To create automatic schedule, see Creating an Automatic Schedule for Database Log Backups.
To delete the transaction log files, see Enabling PostgreSQL Archive Log Deletion after Backup. If Archive Delete check box is not selected, the Commvault software does not prune the logs.
If the logs are not pruned from the archive log directory, all the logs will be backed up with full backups. If you do not want to back up the old cycle logs during a newer full backup cycle, set the value of additional setting nDoNotBackupAllLogs to 1.
Better performance for dumpbased backup
To achieve better performance for dumpbased backups, enable Commvault compression. For more information, see Data Compression.
Disk Caching
For more information about disk caching, refer to Disk Caching for Frequent Database Log Backups.