With cluster replication, how the transactional log is updated when new modifications are replicated?
We running circular transactional log on userfacing server (server 2) and archival style transaction logging on the non-user-facing (server 1) cluster mate.
Our backup strategy is to replicate all changes made in databases, onto a non-user-facing(server1) and then backing it up on tapes with his server’s TL. When restoring a database, this server’s tapes and TL are used.
But in our case, the restore process fails (on txn restore) every time for databases that have not been modified on this non-user-facing server (i.e. databases for which documents were replicated from a userfacing server (server 2)).
We use the Tivoli storage manager tool for backup.
Anyone have a ideas!
Tks Martin