Bootable media: cannot back up to Managed Vault?!? Really??
Post edited, private information posted.
____
Can anyone else confirm this from their own experience? If it is true, WHY?
Contrary to Sumit's statement, the bootable media does in fact 'detect' the centralized vault; I can supply a user ID and password see the vault's contents, but when the backup is attempted, it fails with these errors:
Error code: 1
Module:408
LineInfo:9418a040040a4e4a
Fields:
Message: The feature is not available
Error code: 9
Module:202
LineInfo:9641d5a26ddf9809
Fields:
Message: Failed to check the license key. The key is disabled.
I can back up from bootable media to a windows shared folder, but what is the point of having a deduplicating storage service if I cannot store backups from any kind of client there???
More head-scratching bugs, omissions and design flaws in ABR!
JDC
I am working with one vault which is a centralized, managed vault with deduplication enabled. I'm not sure what you mean by 'Leaving aside mixing 'centralized' and 'centralized managed' vaults' .
The user guide quote matches my experience; I did have to type the path to the vault. The archives within do appear after providing login credentials.
It does seem the managed, centralized vaults are read-only from bootable media, but the user guide does not say that is the case. Assuming it is working as-designed, it is a lousy design.
JDC
Most likely, the media was created from an ABR edition designed for stand-alone machines (Server for Windows, Workstation or Server for Linux). Othewise, the deduplication add-on was not installed on the machine.
I built a new bootable media after upgrading ABR 11 to build 17318 (and installing the deduplication component on the workstation used to build it).
I also created a new centralized, managed vault with dedupe on a second storage node (my primary storage node has crashed, still waiting for support to respond on that one).
I am able to backup from this bootable media to the new centralized/managed/dedupe vault! (at least it is not giving me the same error, progressing normally thru 16 percent right now).
So, I don't know for sure what solved the problem: build 17318, adding dedupe before buidling the media or the new vault. My guess is the addition of dedupe.
Thanks elenal and dev-anon for the clues!
JDC
Oh Yeah...if support tells you something that does not make sense, DONT BELIEVE IT!!