Skip to main content
commvault.com commvault.com
Solved

Log commit jobs after disabling log caching

  • April 3, 2026
  • 6 replies
  • 70 views
Paul G
Explorer
Forum|alt.badge.img+1

Hi,

After updating our environment to 11.40.42 I saw repeated log commit jobs failing with the following error.

Sweep job has failed on Media Agent [XXXXXXXX]. Error [0xECCC000D:{I2::FileSweepScanner::Scan(684)} + {I2::SweepScanner::GenerateCollectFileForMountPath(269)} + {CQiFile::Open(95)} + {CQiUTFOSAPI::open(77)/ErrNo.13.(Permission denied)-Open failed, File=\\?\UNC\XX.XX.XX.XX\MountPoints\XXXXXXXX\Disk08\63WA3P_12.04.2024_11.32\CV_MAGNETIC\CV_APP_DUMPS\SDT\00DF80E8-D0C5-47B8-939E-E5BBC4908E99\collecttot2.cvf, OperationFlag=0x810A, PermissionMode=0x80}]

I found that log caching was turned on at the plan that is used for the client. As we do not want to use log caching, I disabled the option on the t-log schedule in the plan.

I now see that normal transaction log backups are running for the client instead of the log commit jobs. However, I still get a log commit job every 2 hours which keeps failing with this error.

How do I get rid of the log commit job? A full backup has been made since I disabled the log caching option. I don't mind losing the logs from the few days this was still enabled and failing.

Thanks in advance.

Paul

Best answer by Sunil

Hi ​@Sunil,

The error is strange. I just checked the path with the error and included it here with a bit less masking.

Masked details are highlighted bold. I have changed the IP addresses to X.X.X.1 for MA1 and X.X.X.2 for MA2. The actual name of the disk library is changed to DiskLib.

File=\\?\UNC\X.X.X.2\MountPoints\DiskLib\Disk08\63WA3P_12.04.2024_11.32\CV_MAGNETIC\CV_APP_DUMPS\SDT\00DF80E8-D0C5-47B8-939E-E5BBC4908E99\collecttot2.cvf

 

Disk08 is part of the disk library and has 2 paths.

  • MA1: G:\DiskLib\Disk08 (Read/write permissions)
  • MA2: \\X.X.X.1\MountPoints\DiskLib\Disk08 (Read permissions)

The error is generated on MA1. However, the error points to the file on a share path that points to MA2. I don't understand why the error is pointing to a file path on the MA2 IP while the path should point to MA1.

The file should either be reachable via MA2 through share path \\X.X.X.1\MountPoints\DiskLib\Disk08 or via MA1 via G:\DiskLib\Disk08.

Do you have any idea why this may be happening?

Also, is there a way to just drop these logs files as I don't care about them. The logs contained are now almost 2 weeks old and we have made full and normal T-log backups in the meanwhile.

Kind regards,

Paul Germanus

 

 

You can create the following additional setting on the media agent where the Log commit job is launching.
Under MSSQLAgent section.

SweepAfterThisTime

Value will be epoch timestamp before which you want to cleanup the dumps.

6 replies

Sunil
Vaulter
Forum|alt.badge.img+16
  • SunilVaulter
  • Vaulter
  • April 4, 2026

Hi ​@Paul G ,

One last log commit job runs after disabling log caching operation to sweep up any logs that are already deposited on the library. I think it’s the last log commit job that’s failing in your case.

What is the underlying storage? Is it hyperscale?

 

Thanks,

Sunil-

    Paul G
    Explorer
    Forum|alt.badge.img+1
    • Paul GExplorer
    • Author
    • Explorer
    • April 7, 2026

    Hi ​@Sunil,

    No, the storage is not hyperscale. The disk library are mount paths where 50% of the paths is mounted read/write on MA1 and 50% read/write on MA2. MA1 has read access via CIFS to the mount paths on MA2 and vice versa of MA2.

    Kind regards,

    Paul

    Sunil
    Vaulter
    Forum|alt.badge.img+16
    • SunilVaulter
    • Vaulter
    • April 7, 2026

    Hmm... is the log commit operation happening on the MA where the mount path is mounted as Read only?

     

    Thanks,

    Sunil-

     

    Paul G
    Explorer
    Forum|alt.badge.img+1
    • Paul GExplorer
    • Author
    • Explorer
    • April 8, 2026

    Hi ​@Sunil,

    The error is strange. I just checked the path with the error and included it here with a bit less masking.

    Masked details are highlighted bold. I have changed the IP addresses to X.X.X.1 for MA1 and X.X.X.2 for MA2. The actual name of the disk library is changed to DiskLib.

    File=\\?\UNC\X.X.X.2\MountPoints\DiskLib\Disk08\63WA3P_12.04.2024_11.32\CV_MAGNETIC\CV_APP_DUMPS\SDT\00DF80E8-D0C5-47B8-939E-E5BBC4908E99\collecttot2.cvf

     

    Disk08 is part of the disk library and has 2 paths.

    • MA1: G:\DiskLib\Disk08 (Read/write permissions)
    • MA2: \\X.X.X.1\MountPoints\DiskLib\Disk08 (Read permissions)

    The error is generated on MA1. However, the error points to the file on a share path that points to MA2. I don't understand why the error is pointing to a file path on the MA2 IP while the path should point to MA1.

    The file should either be reachable via MA2 through share path \\X.X.X.1\MountPoints\DiskLib\Disk08 or via MA1 via G:\DiskLib\Disk08.

    Do you have any idea why this may be happening?

    Also, is there a way to just drop these logs files as I don't care about them. The logs contained are now almost 2 weeks old and we have made full and normal T-log backups in the meanwhile.

    Kind regards,

    Paul Germanus

     

    Paul G
    Explorer
    Forum|alt.badge.img+1
    • Paul GExplorer
    • Author
    • Explorer
    • April 9, 2026

    I have created a case with support and update this call once I have a solution.

      Sunil
      Vaulter
      Forum|alt.badge.img+16
      • SunilVaulter
      • Vaulter
      • Answer
      • April 10, 2026

      Hi ​@Sunil,

      The error is strange. I just checked the path with the error and included it here with a bit less masking.

      Masked details are highlighted bold. I have changed the IP addresses to X.X.X.1 for MA1 and X.X.X.2 for MA2. The actual name of the disk library is changed to DiskLib.

      File=\\?\UNC\X.X.X.2\MountPoints\DiskLib\Disk08\63WA3P_12.04.2024_11.32\CV_MAGNETIC\CV_APP_DUMPS\SDT\00DF80E8-D0C5-47B8-939E-E5BBC4908E99\collecttot2.cvf

       

      Disk08 is part of the disk library and has 2 paths.

      • MA1: G:\DiskLib\Disk08 (Read/write permissions)
      • MA2: \\X.X.X.1\MountPoints\DiskLib\Disk08 (Read permissions)

      The error is generated on MA1. However, the error points to the file on a share path that points to MA2. I don't understand why the error is pointing to a file path on the MA2 IP while the path should point to MA1.

      The file should either be reachable via MA2 through share path \\X.X.X.1\MountPoints\DiskLib\Disk08 or via MA1 via G:\DiskLib\Disk08.

      Do you have any idea why this may be happening?

      Also, is there a way to just drop these logs files as I don't care about them. The logs contained are now almost 2 weeks old and we have made full and normal T-log backups in the meanwhile.

      Kind regards,

      Paul Germanus

       

       

      You can create the following additional setting on the media agent where the Log commit job is launching.
      Under MSSQLAgent section.

      SweepAfterThisTime

      Value will be epoch timestamp before which you want to cleanup the dumps.

        Terms & ConditionsAccessibility statement