Skip to main content

moving managed vault - buld issues and errors at attaching

Thread needs solution

Hello all,

as my backup storage ran out of space I had the plan to expand it.
In the same task I had the intention to move the storage node to another machine.

Background:
My vaults are stored on a QNAP NAS and the new NAS has a quite powerful i3.
And as a VM has better storage performance (up to 240MB/s in my case) I want to have the storage node in that VM.

So as I read in a KB article I

- detached the vault from my storage node
- coped the catalog to the new storage node
- moved the complete vault data to the new location

All went fine....

I installed the most recent version of the storage node (Build 50058) on the new location and then the trouble began:

I attached the vault to the new stroage node and:
- in the data view all is fine
BUT
- in the archive tab no archives are present

I was quite wondering why this is and after some tries I recognized that if I eattached the vault to the "old" storage node all was fine and all archives were showing..

The reason:
The new Build: After I uninstallad it and installed the same version as on the AMS all was fine and my archives were listed.

So the question is:
Must all installed components on all machines in the company be of the same version ?
 

Another issue:
If I attached the vault to the storage node I got several errors telling me that the archive is not accessible or so (I have the exact error message not available, but if it helbs I can check it this evenning).
The errors appear always, even if I reattach teh vault to the same storage node by which the backups were created.

Can I ignroe it or am I in trouble?

 

 

Regards

Sven

 

 

 

 

 

 

0 Users found this helpful

Here is one of the error messages (I get an error message in this manner for each backup in the vault that I want to attach):

--------------------
Details zu den Log-Einträgen
--------------------
Typ:                         Fehler
Datum und Zeit:              12.11.2016 19:28:18
Backup-Plan:                 [Keine]
Task:                        [Keine]
Typ der verwalteten Einheit: [Keine]
Verwaltete Einheit:          [Keine]
Maschine:                   xxx.xxx.xx
Code:                        2.555.912(0x270008)
Modul:                       39
Besitzer:                    ASN User
Nachricht:                   
  Kann das Archiv 'arl:/3CC7FEEE-4736-4048-AF82-0DE2FA684504/8A4A363E-C351-4993-925E-9068C043008A/0871DD93-065F-494A-B22E-975EE6F17EDF' nicht öffnen‚ weil es beschädigt ist.
Zusätzliche Info:
--------------------
Fehlercode: 8
Module: 39
Zeileninfo: 2fd9b95053909fd1
Felder:  $module : storage_server_vsa64_44421
Nachricht: Kann das Archiv 'arl:/3CC7FEEE-4736-4048-AF82-0DE2FA684504/8A4A363E-C351-4993-925E-9068C043008A/0871DD93-065F-494A-B22E-975EE6F17EDF' nicht öffnen‚ weil es beschädigt ist.
--------------------
Fehlercode: 620
Module: 64
Zeileninfo: 6a1198d1b8be2c1d
Felder:  $module : storage_server_vsa64_44421
Nachricht: Daten des Archivs sind ungültig.
--------------------
Fehlercode: 1
Module: 64
Zeileninfo: 98130db273d2480
Felder:  $module : storage_server_vsa64_44421
Nachricht: Das Archiv ist ungültig oder sein Typ wird nicht unterstützt.
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode

Ereignis-Code: 0x00270008+0x0040026C+0x00400001

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

 

Hi Sven,

have you checked 46905: Acronis Backup: Archives Incorrectly Displayed in Vault?

It says that all components should be same version as issues may occur.

You can also try to refresh the vault view. This will rescan all archives and update the metadata.

[Edit]

Found another one: 43144: Acronis Backup Advanced: Managed Vault Is Unavailable after Storage Node Re-Installation

Hello Raphael,

okay the version issue is okay although even a rescan of the vault did NOT bring me the vault view back.
The second article you listed addresses an issue with reinstallation.
But I did no reinstalltion, I installed the stroage node on a second machine.

 

The issue that alarms me more is the  problem with the reattaching.

It does make no difference whether I reattach a properly detached vault to the "old" and unchanged storage node or to the frshly installed one.
I get the upper mentioned messages in the log.

Any idea for this ?

 

Regards

Sven

I'm not sure about attaching a vault to a newly installed storage node, it should behave like a re-installed storage node.

The second KB article is about changed vault/storage node IDs.

However the vaults keep the former Storage Node ID in their metadata as it is not updated automatically. This discrepancy leads to vault access errors.

When you attach the vault to a new storage node the metadata must be updated, this is normally done via Vault Refresh. Another way is to copy over the Catalog Database as you can read in the documentation.

The given error message seems to be a result of an improperly attached vault. Here is a similar issue which could be resolved via Vault Refresh.

 

Hello Raphael,

thanks for the information.

As I wrote ein the starting post I copied the catalog data to the new storage node´s catalog folder.
So this is no explanation.

Another thing that cannot be explained:
Why do I get the same errors if I reattach the detached vault to the storage node that created the vaults.

This cannot be explanied by any of the mentioned or linked issues.....

 

So again:

- error messages are generated if I detach a vault from a storage node (lets name it SN_old), copy the vault data to a new location (let´s name the location LOC_new) and reattach them to SN_old

- error messages are generated if I install a Storage Node on a new machine (letz´s name it SN_new) ciopy the catalog data from SN_old and attach the vault at the location LOC_new

Regards

Sven

 

As I wrote ein the starting post I copied the catalog data to the new storage node´s catalog folder.
So this is no explanation.

Yeah, sorry. Have overseen that in your first post.

So your old SN is #44421 and new one is #50058, I haven't seen any issues that were resolved in the newer build nor known issues that still exists regarding re-attaching a vault.

You should contact the Acronis Support directly.

Some more options might be to detach the vault manually, maybe something is getting stuck to the old SN and cannot released properly, but I can only guess.
42126: Acronis Backup Advanced: Manually Detaching a Managed Vault

Maybe it helps when you manually remove the metadata and let the new SN create a new set.

 

 

 

Thanks Raphael,

well I think the vault is up and running again.
I tried to restore some files and it worked.

It was simply more than surprising that a message like "hey your archive is corrupt" appears during an operation that sould have been ecexuted by people before me.

S.

Agreed, the message is somehow confusing.

It may have something to do with different versions and seems to be corrected automatically. So the message is more likely a warning or informational than an error.