Indexing taking a long time

Also ... why are my only support options given to me a) forums b) knowledge base. I have a full fee paying customer ... Should I not have access to some direct support methods like phone numbers and email addresses ?

Apparently it failed at some stage with the following error ...

Also ... Given that I pay a premium for support, I would expect some response on here?

Failed to index vault 'arl:/B2441F8F-905D-446C-B41C-EB602F57BD9D/9AA01DA1-554B-4622-8B57-27F56251CC91'.
Additional info:
--------------------
Error code: 51
Module: 39
LineInfo: af0695fa9d427124
Fields: $module : C:\Program Files (x86)\Acronis\StorageNode\StorageServer.exe
Message: Failed to index vault 'arl:/B2441F8F-905D-446C-B41C-EB602F57BD9D/9AA01DA1-554B-4622-8B57-27F56251CC91'.
--------------------
Error code: 20
Module: 39
LineInfo: 20201bddfb497d24
Fields:
Message: Error occurred while repacking.
--------------------
Error code: 84
Module: 39
LineInfo: bf0456789012370c
Fields:
Message: Deduplication database 'E:\Acronis-Vault\9AA01DA1-554B-4622-8B57-27F56251CC91_d.fdb' of vault 'BWA-Acronis02 Vault' is corrupted.
--------------------

my vmware vault has errored on index task too... different error.

Failed to index vault 'arl:/B2441F8F-905D-446C-B41C-EB602F57BD9D/23697012-C4E3-4B71-A2D9-09697EA2104C'.
Additional info:
--------------------
Error code: 51
Module: 39
LineInfo: af0695fa9d427124
Fields: $module : C:\Program Files (x86)\Acronis\StorageNode\StorageServer.exe
Message: Failed to index vault 'arl:/B2441F8F-905D-446C-B41C-EB602F57BD9D/23697012-C4E3-4B71-A2D9-09697EA2104C'.
--------------------
Error code: 2
Module: 64
LineInfo: 3f26773fab7bd93c
Fields: path : file://tank01.aus.bwa\tank01.aus.bwa-std_acronis-vault\bwa-acronis02-vmware\computers\7C45FC4C-5AAD-6DEE-3438-7FE56DF8F02E.564DD9E2-8E1B-0F71-A44E-7D7DF6A1DB6F\users\S-1-5-21-1244095667-170611375-2505659190-1000\archives\F81FCDB9-FA36-49B6-A8E1-0458CFF9A0F2\5\
Message: Failed to open the archive for reading.
--------------------
Error code: 18
Module: 4
LineInfo: 2ec441f255ed364b
Fields:
Message: This is not the last volume of the backup archive.
--------------------

I to have been recieving the following error each time the indexing task runs.

It would be nice if one of the Acronis Maintenace personal would take a look into this and offer a suggestion on how to fix the problems.

Hello Paul and Aaron!

Thank you for finding time to open the thread regarding this issue! I understand your concern and will do my best to help you.

Unfortunately this information is not sufficient for successful investigation, as it leaves the question of issue cause open. Could you please gather Acronis info from the problem machine and step by step description of the issue, and submit a support request with the information attached. Keep in mind that should there be any procrastination with the reply, you can always specify us the case number. We will do our best to speed up the process.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

I would like to see how this problem plays out. If its been resolved Yana can you post it?
At the moment I cant see how you can use this product if you have more than a TB or two of data, so I think its important to make it public. I see other threads on the subject but they go nowhere as far as I can see
Thanks
Steve

Normal
0

false
false
false

MicrosoftInternetExplorer4

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}

Hello all.

 First post in the forum, but thought it may be important enough for other people having this same slow Indexing problem.

 THE PROBLEM: INDEXING IS PAINFULLY SLOW

 I had the exact same problem. I backed up a single XP machine into the XP Dedup Store I created on a Centralized vault. The vault was created on a QNAP NAS, Raid 5. I had to enable NFS access for Acronis to see it.

 Indexing was taking hours for even a single machine that had an 80Gb "C" drive. No other drives where backed up, just the SYS VOL.

OK...after much searching and investigation I think the problem is SOLVED. At least my Indexing completed in record time, and all Indexing after the initial one are also completing.

 THE SOLUTION:

Ok, Acronis may have fallen down a bit on this one as it is a small fix that has BIG implications!!

 It has to do with the naming convention in the UNC path to your Vault.

 On my QNAP, I created a share "Acronis", I then created a sub-folder labeled "WinXP". (as I will have different dedup vault for diff O/S's).

Back in Acronis, when you create the Vault, your are asked to point to, or browse to the share folder. Pretty simple.

 However, this is the very place where Acronis falls down.

I  choose “Network Folder”

Browse to the Host where my share is

Once you start highlighting your Host, then the share etc, the lower “PATH” box gets filled in accordingly. Watch that “Path” box as you drill down and find your folder.

 You will notice Acronis making changes to any Capital letters you may have in the path.

 If this is the case, that is the culprit to the problem.

 My example:

      \\HOST\Acronis\W2K....... Acronis takes my UNC path and makes a slight change...shown here

        \\host\acronis\W2K

 You will notice that the Capital letters for my “HOST” name, and the “Acronis” root folder has changed, but curiously, not the Subfolder.

Screen Shots attached.

 If this is happening to you, check the UNC path name for upper/lower-case letters, as it may have the same effect it had for me.

 I had to delete and recreate the vault, but this time before committing the path, I "Upper-cased" any letters that ABR lower-cased.

 All is working great now.

 Such a simple fix for such a frustrating error.

 I hope the next release has a bunch if bug fixes, as this version leaves a little to be desired.

@Howard Hood

Short question about this. How fast is now your indexing? I'm trying to index 1.4TB and it is impossible :/. The task fill up all RAM of the server and needs days to end.

Hi Stefan,
Sorry for delay. Just been installing a new NetApp Storage Array so we can move off the QNAP.

I currently have an indexing task running on my Dedup Store. Total size is now at 494Gb which consists of 27 archives and 38 backups.

That is the dedup size. Original data size is calculated @ 835.9Gb so about half of yours. Dedup space savings is approx 59%.
My Dedup Store is 268.1Gb

Indexing has been running for 1 day 21 hours now @97% with 1 hour 24 min remaining.

Although it may seem to be taking a long time, it should complete with out errors. The problem I was having previous to me fixing it was the indexing continually failed to complete. Or was taking so long it wasn't worth the wait. Be SURE that you are only One backup and then have the indexing on that single backup before adding any additional backups to that store.

When I did the FIRST Dedup on only ONE backup, it ran very fast, cannot give exact numbers as i thought it might run as before, yet when I went back and looked about 3 hours later it was almost complete.

In the last 30 min while attempting to write this post, my time remaining is now 56min 33sec. So in 30 min it has progressed considerably. Now at 98%.

I am just so happy that its working albeit it's still not as fast as I would like.
One final note, while my indexing is running my cpu utilization is under 5%, Ram is only using 66Mb, proccess that is running is: "StorgaeServer.exe"

Tks

Howard