Here is the situation....
We have Primary Server A linked to Standby Server B via HADR.
Primary Server A has recently installed LOGARCHMETH1 to archive logs
and a 2nd homegrown script that compresses the archived logs once in
the archive log directory.
Standby Server B has our old script that moves logs from active to
archive directories and then compresses them every 30 minutes.
The Problem....
Back on our old method of our home grown script moving active to
archive logs every 30 minutes, if we fell out fo sync for 2 hours
because of a network hiccup we could move any archived logs back to
the active log directory on the primary server. We would lightup HADR
and it would catch-up. This prevented us from taking an online backup,
SFTP'ing it over,restoring, and rolling forward HADR Logs.
With LOGARCHMETH1, this doesn't always work as LOGARCHMETH1 will re-
archive the logs too quickly. (i.e. I move over 5 logs, and 2 are read
over to the Standby server - but LOGARCHMETH1 archives off logs 3,4,5
before we complete).
Our Question ...
Because everything is in DB's hands - Log Archiving, HADR, etc.
Shouldn't DB2 be smart enough to know if the Standby HADR server is
trying to rollforward and we need archived Primary Server Logs - to go
to the Primary Archive directory?
Am I missing a setting?
Could it be because LOGARCHMETH1 is not set on the Standby server?
Am I asking too much fo DB2?
Any input would be appreciated.