When in Data Protector media of a StoreOnce software store become expired, the used disk space is not released immediately. The disk space will be released once the media is overwritten or deleted. The housekeeping process running in the background to release the space will start only when the media is no longer used in Data Protector. Housekeeping requires time and the disk space is not released immediately. At the moment it is not possible to control the housekeeping process via Data Protector (see blackout window in StoreOnce hardware systems), however, it should not run during the time of running backups, as it will slow down the data throughput. Using the global variable DeleteUnprotectedMediaFreq at least it is possible how often during the day expired media are deleted as a trigger for the housekeeping process. With the command omnimm -delete_unprotected_media (for syntax see help of the command) you can manually control the deletion process.
NSS Volumes on Linux OES
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/
Installation order of Patches
This question raises up periodically: what is the installation order for the available Data Protector patches? As there are dependencies, which can be reviewed in the description files of the patches, you have to follow the described order from the description file. However, the common rule to install patches is:
- if available: patch bundle,
- Core,
- Cell Server,
- Cell Console,
- Disk Agent,
- Media Agent,
- all remaining updates (i.e. SAP, Oracle, Dokumentation, StoreOnce, et cetera).
Advisory c03753986
With document ID c03753986 on 2013/05/06 an advisory for HP Data Protector 6.11, 6.20, 6.21, 7.0 and 7.01 was released, describing a problem for restores of SAP data files and the file size is different from the SAP data file. When the omnirc parameter OB2SAPALIGN was used on Unix a possible read error is not reported during the backup and in case of restore you may receive an error and are unable to recover the SAP data file (silent data loss).
As a workaround disable the omnirc variable OB2SAPALIGN=0 on the SAP client. The problem will be solved with the next release of HP Data Protector.
The complete advisory can be read here: http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?spf_p.tpst=kbDocDisplay&spf_p.prp_kbDocDisplay=wsrp-navigationalState%3DdocId%253Demr_na-c03753986-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken
Data Protector Webinar – Microsoft Hyper-V
Sorry, this article is not available in your language, as the promoted webinar is available in German only.