Microfocus (HP) Data Protector, Azure backups and archiving

DataProtector can only restore from Azure container blobs that have an access tier of Cool or Hot. This is a pity, because Archive is so much cheaper, particularly if you buy it up-front. If the media you are trying to restore from is in the Archive tier, you will get an error like this:

[Normal] From: RSM@cellmgr.ifost.org.au ""  Time: 16/06/2020 11:06:26 AM
Restore session 2020/06/16-8 started.

[Normal] From: RMA@cellmgr.ifost.org.au "Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]"  Time: 16/06/2020 11:06:27 AM
STARTING Media Agent "Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]"

[Normal] From: RMA@cellmgr.ifost.org.au "Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]"  Time: 16/06/2020 11:06:28 AM
Loading medium from slot \\hpdparchivelongterm.blob.core.windows.net\general\531504b0_5ee2f861_04e4_038f to device Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]

[Major] From: RMA@cellmgr.ifost.org.au "Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]"  Time: 16/06/2020 11:06:29 AM
[90:54]  \\hpdparchivelongterm.blob.core.windows.net\general\531504b0_5ee2f861_04e4_038f
Cannot open device (System error)

[Normal] From: RMA@cellmgr.ifost.org.au "Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]"  Time: 16/06/2020 11:06:29 AM
Unloading medium to slot \\hpdparchivelongterm.blob.core.windows.net\general\531504b0_5ee2f861_04e4_038f from device Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]

[Normal] From: RMA@cellmgr.ifost.org.au "Azure_gw_via_dc1hdp01 [GW 6588:0:16462780082409836283]"  Time: 16/06/2020 11:06:29 AM
ABORTED Media Agent "Azure_gw_via_cellmgr [GW 6588:0:16462780082409836283]"

It’s not a big deal, you just have to find the corresponding blob(s) in the azure portal and bring them out of archive.

If you are reading this blog post because you’ve just seen that error, it’s pretty straightforward to find what you need to fix. The medium it is loading is: \\hpdparchivelongterm.blob.core.windows.net\general\531504b0_5ee2f861_04e4_038f

 ... which corresponds to the name of the name of the blob, except for the _0 on the end. (Azure has limitations on the size of a blob, so Data Protector media can span several blobs.)

 

On the other hand, if you are reading this blog because you are writing procedures for the future, then go to the Media tab, select "All media" and expand the column until you can see the medium id.

Then you can double-check in the Azure portal that it is in the right tier.