When you need to backup NSS volumes on a Linux OES server with Data Protector 7.01 – current patches, it might be the case that the NSS volumes are not listed within GUI and you might receive the following error: 12:1304 The mountpoint/file-system cannot be backed up
. Probally you might receive this error for next version of Data Protector too. The problem was already submitted for DP 6.2 – the solution / workaround can be found here: https://www.data-protector.org/wordpress/2011/11/nss-volumes-on-linux-oes-with-dp-6-20/
Category Archives: Bugs
Data Protector Bugs
DP 7.0 – omnirc – connection abort
With Data Protector 7.0 you may receive the error below during backup. The error has been verified in a case. As a solution you may add OB2INETTIMEOUT=10
to the omnirc file on all involved clients.
Thanks to Dennis Lorentsen, he sent the information.
Error:
[Major] From: BSM@cellmanager.local “test_1″ Time: 01-05-2012 14:15:07
[61:3003] Lost connection to VBDA named “server1.local [/CONFIGURATION]” on host server1.local.
Ipc subsystem reports: “IPC Read Error"
System error: [10053] Software caused connection abort
Site Matters 2
In article Size Matters from 2010 (https://www.data-protector.org/wordpress/2010/06/size-matters/ I informed from a very big backup of a Informix database. Now I was able to get a screenshot from a very big filesystem backup. And once more I can say: Size matters and is backuped with HP Data Protector 😉
The screenshot I did on 2011/09/14, it was a backup from a filesystem on a Windows PC with Data Protector 6.20 (current patches installed).
VEPA DPWIN_00490 / DPWIN_00494
There exists a warning when installing VEPA DPWIN_00490 (re-released in February); you have to follow the installation order, otherwise you may get inconsistencies in your DCBF diretories. The problem will be solved with patch VEPA DPWIN_00494 expected to be available on February 24-th 2011.
UPDATE: patch DPWIN_00494 was released on March 3rd 2011.
Excerpt from patch description:
Patch warning – 11/02/16 – This Critical Warning has been issued by HP.
- DPWIN_00490 introduces behavior that will cause inconsistencies in the DCBF section of Data Protector’s Internal Database(IDB) if installing the VEPA general release patch DPWIN_00490 over the latest CORE, Cell Console and Cell Server patches DPWIN_00475, DPWIN_00477 and DPWIN_00476.
- To work around this behavior so the inconsistencies in the DCBF section of Data Protector’s Internal Database(IDB) be avoided when installing DPWIN_00490 the Data Protector patches should be installed in the below outlined order:
- Install the following CORE, CC and CS Patches:
- CORE Windows DPWIN_00455, HP-UX-PA PHSS_40811, HP-UX-IA PHSS_40812, SOLARIS DPSOL_00408, LINUX DPLNX_00114
- CS Windows DPWIN_00456, HP-UX-PA PHSS_40813, HP-UX-IA PHSS_40814, SOLARIS DPSOL_00409, LINUX DPLNX_00115
- CC Windows DPWIN_00457, HP-UX-PA PHSS_40815, HP-UX-IA PHSS_40816, SOLARIS DPSOL_00410, LINUX DPLNX_00116
- Install DPWIN_00490
- Install the following CORE CC and CS Patches:
- CORE Windows DPWIN_00475, HP-UX-PA PHSS_41363, HP-UX-IA PHSS_41364, SOLARIS DPSOL_00427, LINUX DPLNX_00133
- CC Windows DPWIN_00477, HP-UX-PA PHSS_41455, HP-UX-IA PHSS_41456, SOLARIS DPSOL_00429, LINUX DPLNX_00135
- CS Windows DPWIN_00476, HP-UX-PA PHSS_41453, HP-UX-IA PHSS_41454, SOLARIS DPSOL_00428, LINUX DPLNX_00134
- Install the following CORE, CC and CS Patches:
Problems with VEPA Consolidated Packet – DPWIN_00490
If you install the new VEPA Consolidated Packet – DPWIN_00490 (former DPWIN_00483), it could happen that during the backup the devices are not shown any longer. Within monitor you see the session, however no data are written to drives (I tested tape drives, a filelibrary and a backup job which uses mirrored drives on a filelibrary. The backup job hangs, the rds process shows high utilization. To get rid of the behavior I reinstalled all current patches except DPWIN_00490, afterwards all backups ran again. UPDATE: HP released end of december a site specific patch to address this problem. To get the SSP jst open a case. UPDATE: HP re-released the VEPA patch in February together with an advisory. A fix is expected to be released on February 24th 2011 – VEPA DPWIN_00494.