Skip to main content

Failed to index archive and create snapshot

Thread needs solution

Hi,

After we finished a simple full backup. We found that the vault cannot show the backup archive list. The backup log showed the following error list:

And here is 1 of the error details. Most of their error code is same (Error code 245 & 26).

--------------------
Log Entry Details
--------------------
Type:          Warning
Date and time: 11/11/2015 3:11:45 AM
Backup plan:   Daily Full Ticketing System File Backup
Task:          Simple backup (Full)
Code:          10,551,541(0xA100F5)
Module:        161
Owner:         metroplex@H8MPBK1
Message:       
  Failed to index archive 'Log_Backup' with ID '4FC41439-84E3-4329-A042-7604ACB97E02'.
Additional info: 
--------------------
Error code: 245
Module: 161
LineInfo: 6b233907fd5acb13
Fields:  $module : disk_bundle_vs_38350
Message: Failed to index archive 'Log_Backup' with ID '4FC41439-84E3-4329-A042-7604ACB97E02'.
--------------------
Error code: 129
Module: 67
LineInfo: 882bba6e760225b2
Fields:  $module : disk_bundle_vs_38350
Message: Internal error: Cannot create an input stream with ID 'C51F0F7C-C898-44C4-B2AA-4C3624F00604'.
--------------------
Error code: 129
Module: 67
LineInfo: 882bba6e760225b2
Fields:  $module : disk_bundle_vs_38350
Message: Internal error: Cannot create an input stream with ID 'C51F0F7C-C898-44C4-B2AA-4C3624F00604'.
--------------------
--------------------
 

Anyone meet this issue before and fixed successfully?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Metlex,

Thank you for your posting! First of all please update to the latest build 43994, as we had major improvements for this in the current builds.

Thank you,

Hi Ekaterina,

 

Thanks for your advice.

Unfortunally, the error still here after we upgrade.

Should we re-install the application?

 

Regards,

Metlex

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Metlex,

Thank you for cooperation! Please re-index archive via cmd command as descrived in the following article: https://kb.acronis.com/content/37800

As the last solution re-add faulty vault to the Storage Node as in Solution 2: https://kb.acronis.com/content/45551

Thank you,

Hi Ekaterina,

 

We tried to use both method and the issue still occurred. 

First we use the command: acrocmd reindex vault --service=asn --host=localhost --loc=bsp://localhost/vault

The task finished in 1 second.

For next action, we tried to delete our tape vault and re-create the vault again.

After the upper process, we ran the backup task at midnight and the error msg ahow in log again.

We tried to check the log, seems the job want to create the index to our faded tape drive (we changed our LTO 6 tape drive since that is malfunction)

Is this any relationship??

 

Regards,

Metlex

Hello Metlex,

Each tape-based vault is associated with one or several drives of a tape device. If you've changed the tape drive without making changes to the product, you will get these types of issues.

Please run the "Detect tape device" operation one more time and then create a vault tied to this new drive.

Hi Igor,

thanks for your comment.

We tried to use "Detect tape device" but the error code is still here.

We decide to re-install the software and rescan the pervious tape.

Thanks for all for solution.