When running Data Protector 6.20 together with a media agent installed on Windows 2008 sometimes you might have a bad backup performance. Sure, this was a known problem when DP 6.20 was launched and it was fixed with patch DPWIN_00516. If you still experience bad backup performance I recommend to again read the description for patch DPWIN_00516; there are a new omnirc variable – OB2IPCNOSENDRECVLOOP=1. When doing backups over the LAN, in addition you should set variable OB2SHMIPC=0 gesetzt to further increase you backup speed.
Advisory c03117812
With document ID c02928162 on 2010/07/22 an advisory for HP Data Protector 6.1X and Data Protector 6.2 was released, describing a problem with high memory utilzationwhen using on Windows 2008 R2.
There is a solution which can be requested from Microsoft, in the article you find the corresponding links.
The complete advisory can be read here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03117812&jumpid=em_alerts_us-us_Dec11_xbu_all_all_1535092_102288_software_critical_009_0
Data Protector Cases and HP Support
Software is not free from bugs and a feature in HP Data Protector might not work as expected or will not deliver the expected result. In these cases you will need support from HP to identify, analyse and eventually solve a potential bug. Below you will find the steps to open a new case in a fast and efficient manner.
Support: The easiest way to get HP support for Data Protector is the Software Support Portal – http://support.openview.hp.com/
Howto: A handbook to the SSO portal can be downloaded here: HPSoftwareCustomerSupportHandbook (November 2011). The most current version can be downloaded from HP: http://support.openview.hp.com/pdf/HP_Software_Customer_Support_Handbook.pdf
How to open a case:
1 To open a new case login to SSO portal (http://support.openview.hp.com/) using your passport account and click on “Case Manager”.
2 On the next page choose “Submit a new case” and you will get the following page:
3 Select all the mandatoryoptions. Please keep in mind: “Severity” is set to the lowest priority 4 per default! Depending on your own needs, select a appropriate severity!
4 Within next screen fill in all details (problem description, etc.) to the case. In addition you may upload screenshots and debugs to the case.
5 I recommend to run get_info and to attach the report to the case. The report can be generated using: "c:\Program Files\OmniBack\bin\utilns\get_info.exe" > c:\temp\case.txt (example). In this way support receives all details from your environment which might be needed to solve the case.
Severity:
View Case History: Wihin Case Manager you can monitor your support case. Please go to the Case Manager in the SSO Portal, there you’ll see all open support cases. For the closed ones please click on “all cases for my SAID”.
Special thanks to Robert Sakic who prepared this article.
NSS Volumes on Linux OES with DP 6.20
When you need to backup NSS volumes on a Linux OES server with Data Protector 6.2 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. In this case you need to modify the file /opt/omni/lbin/.util. Search for i.e. -t ext3 or -t reiserfs, you will find it only once. Now you can insert -t nssvol. In this way the disk agent can discover the NSS volumes during the df process and the volumes are listed as separated mountpoints in the GUI. By the way this trick will also work for other filesystems on Linux; you only need to modify .util with the corresponding filesystem. And at the end as Novell consultant from old school I’d like to say: Long lives NSS!
Current Patches DP 6.2
If you own a valid support contract you can download the patches from http://support.openview.hp.com/selfsolve/patches, for login you need the HP Passport account.
Older messages for the patches will be moved to the end of this article.
Update 2011/11/15: A new patch (DPWIN_00531) was released which fix the problems introduced with with patch DPWIN_00528.
- Windows
- Core – DPWIN_00527
- Cell Server – DPWIN_00529
- Cell Console – DPWIN_00530
- Media Agent – DPWIN_00516
- Disk Agent – DPWIN_00515
- Virtual Environment – DPWIN_00531
- HP-UX (Itanium/PA-Risc)
- Core – PHSS_42081
- Cell Server – PHSS_42514
- Cell Console – PHSS_42085
- Media Agent – PHSS_42089
- Disk Agent – PHSS_42087
- Linux
- Core – DPLNX_00154
- Cell Server – DPLNX_00168
- Cell Console – DPLNX_00156
- Media Agent – DPLNX_00158
- Disk Agent – DPLNX_00157
- Solaris
- Core – DPSOL_00448
- Cell Server – DPSOL_00462
- Cell Console – DPSOL_00450
- Media Agent – DPSOL_00452
- Disk Agent – DPSOL_00451
Archive:
Update: With th release of the UNIX patches on 2011/08/16 for all platforms the current patches are available, please note for Unix the PA-Risc/Itanium Patches are not separated any longer.
Update: On 2011/08/03 the patches for Linux and Solaris were released, patches for Unix will be released very soon.
Update: On 2011/08/01 the first patches for Windows were released, patches for the other platforms will be released very soon. I recommend to read the included text files; a description of solved problem can be found in it; especially some new omnirc variables for the media agent.
End of july the first patches for Data Protector 6.2 are expected. At the moment the cell server patch is known to be released, there should also patches available for MA, DA and VEPA. With these patches the problems with poor performance, offline files, VEPA timeouts, barcode scans, Exchange Copy Jobs, … should be resolved.
Update: In September some additional patches were released, the main patch is the VE agent patch which now supports vSphere 5! The patches for windows also includes Core, CS and CC, for all other platforms only CS was released.
Update: For patch DPWIN_00528 a patch warning was issued, do not install the patch until further notice.
Update: For patch DPWIN_00528 a SSP was produced, which solves the problem with GRE and vSphere 5. To get SSPNT620_003 you need to open a case.