I have inherited a system which includes a certain confiuguration of transaction logging, on serveral clustered swerves. Each side of the cluster is set up slightly different and I’m not sure why - one server is set to Circular whilst the other has Archived selected.
I’m inclined to set both to circular but before I do that can anyone think why this has been done? I have consulted the google with little return.
Subject: we can’t answer that
only the person who set it up that way could tell you why it was done that way initially. just lookup the difference between the 2 in admin help and decide which is best for you.
Subject: Transaction logging on a cluster
I can answer this question for you.
You have mentioned the following:
I have inherited a system which includes a certain configuration of transaction logging, on several clustered serves. Each side of the cluster is set up slightly different and I’m not sure why - one server is set to Circular whilst the other has Archived selected.
I’m inclined to set both to circular but before I do that can anyone think why this has been done? I have consulted the google with little return.
This setup is a common occurrence in a clustered environment. Customers often setup clusters servers with transactional logging for one to be Archival and the Other to be circular.
The reason for this is one server running Archival Transactional logging allows for backup and recovery of data while circular style does not allow for backup and recovery of databases. Circular style logging allows for faster restart without having to run consistency checks. Archival also allows for faster restart without consistency check but it does require incremental backups to be run as well as weekly backups to do point in time restores.
Most of my customers will setup the Primary Server with Circular style logging and the failover server setup with Archival where the backups run.
If you are not planning on doing backup, incremental backups or point in time restores than you can run both of them as circular.
Here is a Technote regarding TXN logging:
Title: Notes/Domino Best Practices: Transaction Logging
Doc #: 7009309
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg27009309
Subject: cheers
Mnay thanks Daniel - that makes total sense in our environment. I think I will leave things as they are.