With document ID c02928162 on 2010/07/22 an advisory for HP Data Protector 6.11 and Data Protector 6.2 was released, describing a problem when restoring files. There will be more files restored than selected, this may overwrite files not selected for the restore.
There is a solution, installing current patches, for Data Protector 6.2 the patches are expected for end of july..
The complete advisory can be read here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02928162&jumpid=em_alerts_us-us_Jul11_xbu_all_all_1352646_90965_software_critical_005_38
Security Bulletin c02872182
With document ID c02872182 on 2011/06/29 an advisory for HP Data Protector (6.0, 6.10, 6.11 and 6.20) was released, which describes a potential security problem when using Data Protector and in some circumstances a remote execution of arbitrary code may possible.
There is a solution, installation of Data Protector 6.2 and enable the encrypted communication between the Cell Server and all clients of the cell. The Windows operating systems are affected.
The complete advisory can be read here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02872182&jumpid=em_alerts_us-us_Jun11_xbu_all_all_1318416_90181_software_critical_005_38
Current Patches 6.11
Internal Database error – reorganize your IDB
Update: There are still a lot of old Data Protector installations (version 6.0, 6.1) and in all cases I’ve seen there is still the old errror described below. Thats why I updated and enhanced this article from August 2010.
When updating from a former Data Protector (5.X to 6.0 to 6.11) version to current version it might be nessecary to reorganize the internal database. You can check that with the command omnidbutil -chktblspace. If the output is Please run omnidbutil -modifytblspace to make IDB consistent. you are need to run the steps below.
In addition you can do a check using the command omnidbutil -extendinfo. When the maximum size for the database files (dirs.dat, fn1.ext, fnames.dat, …) shows a vlaue of 2097152 instead of 2096128 (2091752/1024=2048 instead of 2096128/1024=2047) your internal database structure has the wrong size. You need to downsize the database files in the case you upgraded your Data Protector to version 6.0 (and later to current version).
Steps to complete:
- Make a backup of the internal database
- Create some directories with enough free space, in our example e: omniback.bak, cdb, mmdb.
- Stop the Data Protector services (
omnisv -stop) - Make an additional backup of your installation (
robocopy "d:\program files\omniback" e:\omniback.bak *.* /e /r:1 /w:1) - Start the Data Protector services (
omnisv -start) - Make some screenshots regarding your fnames extensions and the count of your DCBF folders
- Export of the internal database
omnidbutil -writedb -mmdb e:\mmdb -cdb e:\cdb- Keep in mind: at the end of the export make a copy of the msg and dcbf folders
- Reintialize the internal database
omnidbinit -force
- Check the datafiles size und fix it if needed
omnidbutil -chktblspace(see above, if you receive the error follow the next step)omnidbutil -modifytblspace(limit the datafile size)omnidbutil -chktblspace(do an additional check)
- Import of the internal database
- Create additional DCBF folders (see above) und extend fnames (GUI –> Internal Database –> Usage)
omnidbutil -readdb -mmdb e:\mmdb -cdb e:\cdb- Stop the Data Protector services (
omnisv -stop) - Copy back the msg and DCBF folders
- Start the Data Protector services (
omnisv -start)
- On demand reset the session counter
- omnidbutil -set_session_counter XXX (XXX is a integer value – must be larger than your last session ID)
D2D and Data Protector
For a customer it could be interesting to enhance the backup and recovery strategy and to do the backup (or parts of the backup) to disk first and to copy the data to tape later. The main advantage is the reduced time it will take to recover a single file, as the restore from tape is allways slower. Another point is whe doing the backup for slow servers, tape drives are underutilizied and blocked; no other backups can be done during this time. Backup 2 disk is nothing new with Data Protector and available since years, however when looking at current developments like deduplication, you should have closer look at the different solutions from other vendors. The HP solution might be the most interesting vendor in this situation as software and hardware are very good combined. Other vendors may offer hardware only or even worse can provide bad implemented software, HP is one step ahead and is offering Store Once!
Below you can see how a D2D 2504i is implemented to be used by HP Data Protector. In general the guide below can be used for all HP D2D systems (D2D2502 / D2D2504, D2D4106 / D2D4112, D2D4312 / D2D4324), indepentent if you use iSCSI or FC protocol. As some errors can be done when you implement a D2D system within Data Protector (or any other backup software), it is highly recommended to read the best practice guide first. Only when following the guide you will reach the best backup performance and highest deduplication rate.