Skip to main content

Acronis BR 11.5 Indexing vault failed

Thread needs solution

I got the below error while indexing the vault, can anyone suggest what can I do to fix it? Thank you so much!!!

Regards,
Alex Hung

---------------------
Log Entry Details
--------------------
Type:                Error
Date and time:       1/26/2017 7:29:09 AM
Backup plan:         [None]
Task:                [None]
Managed entity type: [None]
Managed entity:      [None]
Machine:             HKGCP3-PCB01.dc01.fujixerox.net
Code:                2,555,937(0x270021)
Module:              39
Owner:               fxhkpcb
Message:             
  Storage node error.
Additional info: 
--------------------
Error code: 33
Module: 39
LineInfo: f7d1612d6b579caf
Fields:  $module : storage_server_vsa64_37976
Message: Storage node error.
--------------------
Error code: 98
Module: 39
LineInfo: aeb34f528199bc64
Fields:  $module : storage_server_vsa64_37976
Message: Data store transaction has failed.
--------------------
Error code: 3
Module: 4
LineInfo: f330789b59b3f2f2
Fields:  $module : storage_server_vsa64_37976
Message: Error occurred while writing the file.
--------------------
Error code: 3
Module: 4
LineInfo: 795414836ed3acfc
Fields:  $module : storage_server_vsa64_37976
Message: Error occurred while writing the file.
--------------------
Error code: 3
Module: 4
LineInfo: 7ceb2cdc9fb120c9
Fields:  function : SetEndOfFile, $module : storage_server_vsa64_37976
Message: Error occurred while writing the file.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8e0
Fields:  code : 2147942487, $module : storage_server_vsa64_37976
Message: The parameter is incorrect
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x00270021+0x00270062+0x00040003+0x00040003+0x00040003+0x0000FFF0+0x80070057

--------------------
 

0 Users found this helpful

Would anyone got idea on how to fix it? Or can I delete all the index and rebuild them?

Thank you so much for your help!!

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Alex,

Thank you for your posting! Try to re-index the vault as described here. An update to the current build would be recommended too, as 37976 is rather old one => we've released a lot of fixes and enhancements since then. After updating your installation please create a new vault and check if the issue is solved. 

Thank you, 

Hi Ekaterina,

Thank you for your answer, I've followed what you mentioned (https://kb.acronis.com/content/37800). But it only start the index process and it still stopped after a while. I the log, I still got the same error as I posted previously.

Is there any way to clear all previous index and create them all over again? 
Thank you so much!

Best Regards,
Alex Hung

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Alex,

the last solution we could try is to re-create the vault database. All information about backups in a centralized managed vault is stored in a .fdb file. We can remove the old .fdb and force it's recreation based on the actual vault contents. Please make sure to make a copy of all the files you're going to modify according to the steps described below: 

1. Detach vault in question. 
2. Remove .fdb file from the vault folder if detach generated it. 
3. Attach the vault. 
The ASN database will be re-indexed based on the TIBs residing in the vault directory. 

If this process also fails, I'd recommend raising a support ticket for more indepth investigation.

Thank you,