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.
- User-defined subclient: Test1
- User-defined subclient: Test2
Distributing the client data using subclients as recommended above, can help improve backup performance by organizing the workload on the client into logical groupings.
As a best practice, it is recommended that you add only a few small databases to each subclient and add larger databases into separate subclients. On a restart condition, the system will back up all databases in the subclient from the beginning. For this reason, you would not want a large database that has completed its backup successfully to be backed up again only because a smaller one has caused a restart to occur.
Managing transaction logs for File System based backup
We recommend you to schedule several log only backups between full backups.
If Archive Delete check box is not selected, the Commvault software does not prune the logs. Here, it is useful to have a method to clean up the archive log directory.
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.
Last modified: 8/29/2018 5:22:16 AM