When Data Protector MsSQL FULL and TRANS backups are running simultaneously one of them fails

If you are one of the HP DataProtector 6.11 customers and you have scheduled MsSQL transaction log and full backup to start simultaneously you will experience the below issue. We found this after an upgrade to latest 6.11 in November 2010 and a hotfix was build for us on 19. November 2010. We are running with this patch for 8 weeks successfully.

Cell Manager patch level:

Patch levelPatch description
DPWIN_00455Core Component
DPWIN_00456Cell Manager Component
DPWIN_00478Disk Agent
DPWIN_00460Media Agent
DPWIN_00457User Interface

Client SQL Server patch level:

Patch levelPatch description
DPWIN_00455Core Component
DPWIN_00455Core of Integrations component
DPWIN_00478Disk Agent
DPWIN_00460Media Agent
DPWIN_00480MS SQL Integration
DPWIN_00455Cluster Server

 

Symptoms:

When DP MS SQL FULL and TRANS backups are running simultaneously one of them can fail with the following error:

[Major] From: BSM@<cell manager> "<barlist>"  Time: <date> <time>
[61:3003] Lost connection to OB2BAR Backup DA named "<instance name>" on host <SQL Agent host>
 
Solution:
 
Open a support request with HP and request the Data Protector Lab Support hotfix with QXCM Number - QCIM2A27402, file name QCIM2A27402_TM1.zip.
 
Patch content:
 
The patch contains an updated sql_bar.exe for the MsSQL Server backup agent.
 
Workaround:
 
Without the patch you can schedule your backup jobs to run at different times e.g. Run the transaction log backup every full hour and the full backup 10 minutes later (when transaction log has been completed).
Bewertung: 
Noch keine Bewertungen vorhanden