indexing will not end
Hi,
I have the following problem. Since 14 days, the indexing task are running, but the indexing data is consistent going up. I have send a message with this problem to acronis last week and not become a answer.
CaseID: 01573250
I hope anybody can help me.

- Log in to post comments

Yes, its a Dedup Storage Node. I found the problem, it was a restriction problem of the NTFS data file system. It was the 255 characters restriction for directory + file. I change the name of the main-directory and the indexing task of the node works fine to end. :)
But I have one other big problem, the update for the catalog of the Dedup Depot will not work to end. I view only 4 from 21 machines.
The update for the catalog will stop with the following error:
--------------------
Details
--------------------
Typ: Fehler
Datum und Zeit: 21.06.2012 13:15:51
Backup-Plan: [Keine]
Task: [Keine]
Typ der verwalteten Einheit: [Keine]
Verwaltete Einheit: [Keine]
Maschine: acronis.loc
Code: 20.250.685(0x135003D)
Modul: 309
Besitzer: acronis
Nachricht:
Befehl 'Datenkatalogisierung' ist fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 61
Module: 309
LineInfo: 4a8728dc8a1c94f4
Felder: $module : service_process_vsa64
Nachricht: Befehl 'Datenkatalogisierung' ist fehlgeschlagen.
--------------------
Fehlercode: 1
Module: 388
LineInfo: 31f47c49ad4b4ee0
Felder: $module : asn_gtob_indexer_commands_addon_vsa64
Nachricht: SQLite-Bibliotheksfehler: Code '19'.
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode
Ereignis-Code: 0x0135003D+0x01840001
--------------------
- Log in to post comments

Code '19' is SQLITE_CONSTRAINT 19 /* Abort due to constraint violation */
so your storage node is trying to do something funky with the catalog database.
Did you upgrade you storage node (and MMS) to the newest build already?
If yes, then try to delete your catalog and recreate it:
* Make sure you are on the newest build (17438 as of now) - 17437 has a crashbug in the catalog-function!
* Stop the ASN service
* Delete (or better: move away) all files below C:\ProgramData\Acronis\BackupAndRecovery\ASN\Catalog
* Restart the ASN
* in AMC select the Depot in the Depot view, select the Data Tab
* Click "Catalog now"
Depending on the size of your Depot, this might take a while.
- Log in to post comments

thanks for your help, but the problem is still again :(
the next step i do, was the reinstall of acronis and check the depot-disks, with exact the same result. I don't hope the Depot has a problem. Have you any other idea?
I have also a open CASE by Acronis since 15.05.2012, but the reaction of the support is very poor. I hope you can help me.
- Log in to post comments

Did you already validate the complete Depot and additionally test-restore two or three backups? (Especially the ones where cataloging fails)?
If that works right, then it's just another bug in service_process.exe.
If you have problems with validation then your depot might be damaged.
I can't help you with support. Has your case already been forwarded to 2nd level?
- Log in to post comments

yes, the validate of the Depot run completely. I restore one machine to a tib-image. This machine was not in the catalog and the restore works fine.
Yes, the case must be 2nd level. I will write to acronis-support again and hope to become a answer.
- Log in to post comments

Hello Rene,
Thank you for using Acronis Software.
Thanks for your feedback. I have forwarded your comment to our Management Team and we will get this problem addressed.
In Case, that the creation of your Catalog fails, I suggest to delete the existing Catalogs in order to create them new. You will find the locations of these Catalog Databases here. A general oveview of used databases, you will find here.
For your exact Error Message I found an internal case at our development. I updated the SP with my found information, also I asked him to contact you shortly.
If there is anything else, we can do for you, please let me know.
- Log in to post comments