Cataloging runs 24/7 and can't be stopped

Hello rkh,

thank you for your posting! Could you please share more details about your setup? What product version is used here? Is Acronis Store Node installed (you are running a cataloging of an centralized managed vault)?

Generally, you can disable the option the following way  https://www.acronis.com/support/documentation/AcronisBackup_11.7/index…

Hi,

I'm running the latest/last version of 11.7.  Vault is on the same machine - everything is local.  About 5 logical drives on different schedules.  I've taken to killing service_process each morning.  Odd thing I just realized is that it's only a problem with drive C:.  After I kill service_process, it fires up again as I suppose the cataloging of the other drives was still pending.  Looking at the log, the cataloging for those other drives finishes successfully.  

Not sure why drive C: would not complete.  It's only about 600Gb of data on C:.

Hello rkh,

it's hard to say what could be the root cause of the issue without the investigation, you may want checking the log of the Agent performing the cataloging for clues (the full activity log can be found in C:\ProgramData\Acronis\BackupAndRecovery\MMS\events.db3) 

Make sure there is enough space for the catalog db (the path can be changed as follows https://kb.acronis.com/content/26428). You can also try recreating the catalog from scratch as follows https://kb.acronis.com/content/42075 

Regarding re-creating from scratch - my assumption is that this is done each time a FULL backup is run.  So if the prior one was corrupt, the next full (barring some other problem) would create a new one from scratch.  Is my assumption accurate?

Hi! The product will try to modify the existing file in that case.

That WORKED!  Thanks so much for the tip!  I had to guess at which folder contained the catalog for C: because I didn't know how to decipher the folder names.  I guessed at the folder whose catalog was 46 GB!

Now the entire full backup process for all drives takes MUCH less time.  I suspect the looping catalog for C: that never finished was impacting the other backups.  One would take 12 hours, now it completes in 2.  So my Friday night full is completed by Saturday morning instead of Saturday evening.  

Thanks again.