Exchange Agent Not Purging Transaction Logs With Circular Logging Disabled - Veritas Backup Exec

This is a discussion on Exchange Agent Not Purging Transaction Logs With Circular Logging Disabled - Veritas Backup Exec ; We are having problems with our Veritas Backup Exec for NT ver 7.3 with the Exchange Agent. With circular logging disabled (unchecked), the transaction logs are not being purged. This seems to only (but not all the time) when we ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Exchange Agent Not Purging Transaction Logs With Circular Logging Disabled

  1. Exchange Agent Not Purging Transaction Logs With Circular Logging Disabled



    We are having problems with our Veritas Backup Exec for NT ver 7.3 with the
    Exchange Agent. With circular logging disabled (unchecked), the transaction
    logs are not being purged. This seems to only (but not all the time) when
    we are also running NSI's DoubleTake mirroring/replication software on the
    box at the same time. Has anyone else seen this problem? I think it may
    have to do with too many processes trying to touch the checkpoint/patch files
    at the same time.

  2. Re: Exchange Agent Not Purging Transaction Logs With Circular LoggingDisabled

    Whch build/version of v7.3 If it's not 2575, I'd STRONGLY suggest that you grab
    the free upgrade. As far as I'm concerned all v7.2 builds and the early v7.3
    builds were all BETA code and still full of bugs.

    BNT73I03 (English/Intel)
    POST2575 (See the readme to determine if any apply)
    SPANFIX
    MEDIAFIX_234341 (You want to get to 2575 just for this one, believe me)

    Katy wrote:

    > We are having problems with our Veritas Backup Exec for NT ver 7.3 with the
    > Exchange Agent. With circular logging disabled (unchecked), the transaction
    > logs are not being purged. This seems to only (but not all the time) when
    > we are also running NSI's DoubleTake mirroring/replication software on the
    > box at the same time. Has anyone else seen this problem? I think it may
    > have to do with too many processes trying to touch the checkpoint/patch files
    > at the same time.



+ Reply to Thread