Archive logs are required to recover database transactions that have been lost due to an operating system or disk failure. You can apply these archive logs to an online backup in order to recover a database.
The default subclient includes data and logs.
A log backup is always a full backup.
Best Practice: Create a separate subclient for log backups.
Procedure
-
From the CommCell Browser, navigate to Client Computers > client > DB2 MultiNode> instance.
-
Right-click the backup_set, point to All Tasks and then click New Subclient.
The Create New Subclient dialog box appears.
-
On the General tab, in the Subclient name box, enter a name for the subclient.
-
On the Content tab, clear the Data check box.
-
On the IntelliSnap Operations tab, configure the IntelliSnap options.
-
Select the IntelliSnap check box.
-
From the Available Snap Engines list, select the engine that matches your snapshot type. For a list of available engines for your array, see Snapshot Engine.
-
-
On the Storage Device tab, select the name of the Data Storage Policy.
-
Optional: Select the subclient options.
Run scripts before or after the backup
You can choose to run the post-process script even if the backup job failed.
On the Pre/Post Process tab:
-
In the PreSnap Process box, type the full path name for the script.
-
In the PostSnap Process box, type the full path name for the script.
-
To run the post backup process regardless of the job's outcome, select the Run Post Process for all attempts check box.
Use compression to optimize backup storage
On the Advanced Options tab, select the Use Db2 compression check box.
When you select this option, the Commvault software applies the DB2 compression feature to all the backups for this subclient.
Fore more information on DB2 compression, go to the DB2 website, compression and storage.
-
-
Click OK.