(DP) Support Tip: DP Exchange Integration - passive copies backup when CopyQueueLength parameter =1
(DP) Support Tip: DP Exchange Integration - passive copies backup when CopyQueueLength parameter is 1
DP / Exchange Integration - passive copies' backup fails with below message:
[Minor] From: OB2BAR_E2010_BAR@XXX.com "MS Exchange 2010+ Server" Time: 11/16/2017 10:02:47 PM
Backup will not be performed for database copy XXXX-YYY\ZZZ because its CopyQueueLength parameter is 1.
Copy queue length (logs) - Indicates the number of log files waiting to be copied and inspected. The copy queue length are the transaction logs the passive copy is getting from the active copy.
In a busy Exchange environment there would rarely be a situation where all archive logs are current on the passive copy, so CopyQueueLength would always be > 0. This just means that it is not the current status, but some transactions behind, which can make the backup of a passive database copy without current archive logs unreliable.
DP Integration Guide
Chapter 8: Data Protector Microsoft Exchange Server 2010+ integration
- Active copies as opposed to passive copies:
There is no difference between the active and passive copy, except in the currently active log file (at the active copy side), which is not copied to the passive copy side until the file is filled up (that is, reaches 1 MB). Consequently, if you back up a passive copy, the transactions in the currently active log file are not included.
DP Exchange Integration agent only accepts CopyQueueLenght of 0 and in such cases, backup of passive copy will be performed.
Any higher value of CopyQueueLenght will report the above error and backup of copy will be skipped.
Reason for implementation was that only CopyQueueLenght of 0 represent loss less situation while any other value represent some degree of data loss.
For example Microsoft consider CopyQueueLenght from 1 to 6 as 'Good Availability' with minimum data loss. Higher values represent higher data loss.
If your customer have the above backup error and would be requesting for a fix to allow backup even for CopyQueueLength is > “0”, a fix is made available through omnirc variable that users can define maximum CopyQueueLength and if CopyQueueLength is smaller then this value backup of passive copy will continue (unlike now where backup fail if CopyQueueLength is greater then 0).
where you can set a value between 1 to 6.
Please log a DP SW case to request for this lab fix.