On 2015/04/27 HP released patch bundle 9.03 for Linux, HP-UX and Windows, it includes approx. 20 fixes. Two major enhancement were made: the activation of the encrypted control communication (optional in the past) and support for the OpenSSL 1.0.1j module. It is strongly recommended to read the full description of the bundle.
If you own a valid support contract you can download the patches from https://softwaresupport.hp.com. For login you need the HP Passport account.
Direct link:
– Windows – DPWINBDL_00903 – Patch Bundle
Werden nur die Patchbundles für DP 8/ 9 annonciert? DP 7 nicht mehr?
Gruß
Frank Sauer
Hi Frank,
yes, I do only inform about DP 8/9 version at the moment.
While DP 7 is still used and supported, I see more and more customers moving to DP 8 and 9, which seems to make the information less important for the readers.
So let’s ask the others: Do you like to see information on patches for most current and former DP versions? Simply comment…
Best regards
Daniel
Hello Daniel,
I appreciate DP 7 as very stable with few bugs. Patch frequency for DP 9 ist quite short. It was quite comfortable to have the announcements on you website, but if I am the only one … 😉
kind regards
Frank
Hi Frank,
will keep it in mind and inform about DP 7 and 8 patches as well.
Best regards
Daniel
For fellow victims who use spaces in their directory names: 9.03 cripples the DP IDB service on Windows, preventing it from starting again.
The IDB (hpdp-idb) service doesn’t start because the ImagePath of the service (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hpdp-idb) was changed from:
D:/Program Files/OmniBack/idb/bin/pg_ctl.exe runservice -N “hpdp-idb” -D “D:/Program Files/OmniBack/server/db80/pg”
to:
“D:\Program Files\OmniBack\idb\bin\pg_ctl.exe” runservice -N “hpdp-idb” -D “D:\Program” -w
Not the first time HP suffers from space-related ‘accidents’… Not like space are new…
The “-w” stands for
Wait for the start or shutdown to complete. The default wait time is 60 seconds. This is the default option for shutdowns. A successful shutdown is indicated by removal of the PID file. For starting up, a successful psql -l indicates success. pg_ctl will attempt to use the proper port for psql. If the environment variable PGPORT exists, that is used. Otherwise, it will see if a port has been set in the postgresql.conf file. If neither of those is used, it will use the default port that PostgreSQL was compiled with (5432 by default). When waiting, pg_ctl will return an accurate exit code based on the success of the startup or shutdown.
So I added the “-w” as well:
D:/Program Files/OmniBack/idb/bin/pg_ctl.exe runservice -N “hpdp-idb” -D “D:/Program Files/OmniBack/server/db80/pg” -w
Now the IDB service starts properly and you’re on your way.
Hi Thomas,
thanks for the information… this was already a problem when upgrading to DP 8.10. However the recommendation is to split the “program files” and “programdata” part.
Best regards
Daniel
Hi Daniel,
“However the recommendation is to split the “program files” and “programdata” part.” is nonsense (because there are some Installations with DB/ Config not in “programmdata” but in “program files”.
So the recommendation has to be: The Patch bundles has to be made aware of spaces in the path-names!
Regards Bernd
Hello Daniel,
me and my colleagues would also be happy to read patch announcments for DP 7 here on data-protector.org.
@Frank: You are not alone 😉
Regards
Jay
Hi Jay,
yes, understood 🙂
Best regards
Daniel
Is there a support for VEPA agent on Win 2012 R2 server in DP 9.03?
Hi Peter,
according to the support matrix, at the moment it’s not supported.
Best regards
Daniel
Will this version integrate with with 3PAR InForm OS 3.2.1 . I having some issues implementing ZDB for VMware and want to confirm that is the sticking point.
Thanks
Duncan
Hi Duncan,
from a colleague I got the information, that you might need to downgrade the VSS provider to get it working.
Best regards
Daniel
Turns out DP 9.03 is not supported for inform 3.2.1, hopefully in DP 9.04 .
Ill look into and try downgrading VSS in the meantime.
Thanks for the information. Great site.
Duncan
Hi Daniel,
Thanks for a very useful reference site.
May I suggest that you put the warning (“You are strongly advised . . .”) in bold red capitals, underlined, and add “If you use ECC, disable it throughout before proceeding.” !! As relative newbies to DP, we were advised by HP to install 9.03 on Cell Manager and Media Agent servers, in order to overcome Copy Job problems in 9.02. Unfortunately, with old ECC in place, most of our weekend full backups failed! We have just had to kill ECC on the Cell Manager, then rename the \Config\Client\config file on every single client, rip DP off every Windows client and reinstall 9.00, and then upgrade all clients to 9.03 (manual upgrade for Solaris clients). So now we’re non-ECC and backups are working, so once we’re fully backed up again the next stage is to gingerly enable ECC on Cell Manager and a client, and try backups & restores again. DP is undoubtedly powerful, but hard work to manage!