Good Evening - We have implemented journaling on our active/active MS cluster. We used version 5.3 as this version was developed to support it. Our TSM server is Solaris 8 running 5.2.4. This is a 4 node cluster with a total of 12 virtual nodes spread across the 4 nodes.
However, sometimes the journal works and sometimes we receive the following message in the beginning of a backup and then of course, it does the normal incremental. We do see in the event viewer where the backup gets done, it says it validated and marked the journal for that drive and that it will use it on the next backup. However, when the next backup starts, sometimes we receive the following and thus, the cycle starts again. However, on dates like the 15th through the 19th, we were fine. The 14th was the same as the below. I do have an open ticket it, but I figured I would throw this out there to see if anyone has any insight. 01/20/2005 20:29:11 jnlDbCntrl(): Restarting journal for fs 'T:' per client request. 01/20/2005 21:00:18 jnlDbCntrl(): Restarting journal for fs 'V:' per client request. 01/20/2005 22:30:11 jnlDbCntrl(): Restarting journal for fs 'Z:' per client request. 01/21/2005 00:03:21 jnlDbCntrl(): Restarting journal for fs 'X:' per client request. 01/21/2005 05:50:31 jnlDbCntrl(): Restarting journal for fs 'X:\MOUNTVOL11' per client request. 01/21/2005 09:31:16 jnlDbCntrl(): Restarting journal for fs 'Z:\MOUNTVOL9' per client request. 01/21/2005 18:11:53 jnlDbCntrl(): Restarting journal for fs 'T:' per client request. 01/21/2005 18:11:57 jnlDbCntrl(): Restarting journal for fs 'X:' per client request. 01/21/2005 18:11:59 jnlDbCntrl(): Restarting journal for fs 'Z:' per client request. 01/21/2005 18:11:59 jnlDbCntrl(): Restarting journal for fs 'V:' per client request. Any help will be appreciated. Thanks! -- Terry
