HP Data Protector: JSONizer error when restoring from StoreOnce
After installing the Data Protector patch bundle 8.13, you may ran into this error when trying to restore data from a HP StoreOnce appliance.
[Normal] From: RSM@dpcm.lab.local "" Time: 04.12.2014 09:13:10
Restore session 2014/12/04-8 started.
[Normal] From: RMA@fileserver.lab.local "D2D_GW1 [GW 6408:0:7255964966039732580]" Time: 04.12.2014 09:13:12
STARTING Media Agent "D2D_GW1 [GW 6408:0:7255964966039732580]"
[Normal] From: RMA@fileserver.lab.local "D2D_GW1 [GW 6408:0:7255964966039732580]" Time: 04.12.2014 09:13:13
Loading medium from slot 192.168.200.101Store_1257902bf_54796efc_04f4_005c to device D2D_GW1 [GW 6408:0:7255964966039732580]
[Major] From: RMA@fileserver.lab.local "D2D_GW1 [GW 6408:0:7255964966039732580]" Time: 04.12.2014 09:13:15
[90:52] 192.168.200.101Store_1257902bf_54796efc_04f4_005c
Cannot read from device (JSONizer error: Device read failure)
[Normal] From: RMA@fileserver.lab.local "D2D_GW1 [GW 6408:0:7255964966039732580]" Time: 04.12.2014 09:13:15
Unloading medium to slot \\192.168.200.101\Store_1\257902bf_54796efc_04f4_005c from device D2D_GW1 [GW 6408:0:7255964966039732580]
[Normal] From: RMA@fileserver.lab.local "D2D_GW1 [GW 6408:0:7255964966039732580]" Time: 04.12.2014 09:13:15
ABORTED Media Agent "D2D_GW1 [GW 6408:0:7255964966039732580]"
[Normal] From: RSM@dpcm.lab.local "" Time: 04.12.2014 09:13:15
Restore Statistics:
Session Queuing Time (hours) 0,00
-------------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 1
Aborted Disk Agents .......... 0
-------------------------------------------
Disk Agents Total ........... 1
===========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 0
Aborted Media Agents ......... 1
-------------------------------------------
Media Agents Total .......... 1
===========================================
Mbytes Total ................. 0 MB
Used Media Total ............. 1
Disk Agent Errors Total ...... 0
This problem is known and it is described in QCCR2A56465. A fix is available (new BMA, CMA, MMA and RMA binaries). Simply open a service request and ask for the fix. Make sure that you add a copy of the session messages or a screenshot to the service request.