Log Staging
-
Assign 775 with read-write permission to the log staging path for the DB2 user and group.You can also use the same permission in multi-instance setups .
-
Keep log staging path for the use of the Commvault software because tampering of logs could result in corruption of archived logs. And, if the logs are corrupted, the roll-forward process might not work properly because DB2 won't be able to process the log file.
-
Optional. Create a shared Log Staging location across HADR nodes, including all primary and standby nodes. In case of takeover, it helps back up the logs generated on a standby client and maintains the log chains that are created. When you perform restore, it restores all the logs even from the standby machine because the log paths are shared and prevents 'Missing Log Error'. This method is useful in case of Delay in Log Shipping to Standby and if the DB2 Config parameter HADR_SYNCMODE is not set to SYNC for immediate log shipping.
Note
Clients that are geographical distributed might not be able to create shared log staging.
For more information how to configure log archive device, see Log Archive Device in the IBM documentation website.