10.02, and recovery software Website HP Data Protector software is automated and recovery software for single-server to enterprise environments, supporting or tape storage targets. It provides cross-platform, online backup of data for, and operating systems. For business- and mission-critical applications, HP Data Protector Zero Downtime Backup leverages array-based solutions to offload processing from the server and perform backup operations on a copy of the production data. HP Data Protector Instant Recovery retrieves data from the replicated images on disk for recovery to specific points in time. HP Data Protector originated as OmniBack. The last version to use the OmniBack name was version 4.1, which was retired in 2004. Contents.
History When acquired in 1989, the latter had already developed a backup system entitled the 'OmniBack Network Backup System,' which was available on the market at the time. HP continued to develop this product under the 'OmniBack' name for the purpose of backing up individual files and raw disk partitions. A related but distinct product 'OmniBack/Turbo' was developed for backing up databases. In 1996 HP released OmniBack II 2.0 and merged OmniBack II and OmniBack/Turbo into a single product, although it was still impossible to create a single job which would contain a database and a file system backup. A Windows NT port was released with version 2.3.
Version 2.55 was released in 1997 and included support for HP-UX and IBM AIX. With version 5.0, the OmniBack name was dropped. Since then, the product has been called HP Openview Storage Data Protector and HP StorageWorks Data Protector.
The product is now called HP Data Protector software. HP announced the release of HP Data Protector 9.0 (as a part of its Adaptive Backup & Recovery initiative) in May 2014, and released it in July 2014.
It was released in July 2014 along with two companion products: HP Data Protector Management Pack and HP Backup Navigator. Architecture The HP Data Protector architecture is based on the concept of a cell: a network environment that contains a Cell Manager, clients, and backup devices. The Cell Manager is the main system that centrally controls and manages the cell. It contains a database, runs the core software, and runs the backup and restore sessions, writing session information to the database. A client can be any system within the cell.
Clients that are to be backed up require the installation of a Disk Agent. Clients that control the backup and restore data require the installation of a Media Agent.
For multi-site operations, the Data Protector Manager of Managers (MoM) allows local administrators to control data backup and restore, but providing centralized enterprise monitoring and media management. In this configuration, multiple Data Protector cells are grouped, configured and managed from the MoM. Data deduplication HP Data Protector offers capabilities with the ability to compare blocks of data being written to a backup device with data blocks previously stored on the device. For data deduplication, HP Data Protector allows any disk-based data storage to be the target storage. Tape drives cannot be used as deduplication targets because of their sequential nature opposed to the block-oriented nature of disk-devices. Virtual server protection HP Data Protector supports backup and restore of virtual servers, including protection for the whole Virtual machine and its application data. Supported virtual environments include VMware, Windows 2008 Hyper-V (Limited), Microsoft Virtual Server 2005 and HP Integrity Virtual Machines.
Citrix XenServer support is no longer officially provided. Centralization encryption HP Data Protector includes automated key management for software and Linear Tape-Open LTO-4 Encryption. Users have the choice of client-based encryption for data security, or they can use the encryption functionality in LTO-4 (and later generation) tape drives.
Data Protector Notebook Extension In November 2009, HP began offering HP Data Protector Notebook Extension. HP Data Protector Notebook Extension enables users to back up and recover data while working remotely and offline. With HP Data Protector Notebook Extension, data is captured and backed up automatically each time a user changes, creates or receives a file. These processes are transparent to the user and do not impact laptop or desktop performance. The data is then stored temporarily in a local repository pending transfer to the network data vault for full backup and restore capabilities. Key features include end-user single-click recovery, encryption and compression techniques.
Metodos numericos para ingenieros chapra. Granular Recovery Extensions Granular Recovery Extensions are components that sit inside other applications and provide the operator of that application with a way of triggering a large restore and then selecting the individual items that need to be restored without requiring assistance from the backup administrator. For example, the granular recovery extension appears as an extra item in the console of Vcenter, lets a VMware administrator restore a file and finally provides an interface for selecting files out of that vmdk file. The SharePoint GRE allows administrators to recover a single document, collection or folder directly via the SharePoint GUI.
(Granular Recovery for SharePoint 2010 was introduced in version 7.0.) References. Retrieved 2010-06-28. (PDF) (Press release). Retrieved 2010-06-28. John Cox (3 Apr 1989). Network World. Retrieved 27 August 2011.
![Hp data protector quick specs Hp data protector quick specs](/uploads/1/2/3/8/123810510/623301065.jpg)
![Protector Protector](/uploads/1/2/3/8/123810510/824956301.jpg)
(Press release). Retrieved 2010-06-28. Network World. 20 July 1992. Retrieved 27 August 2011. Retrieved 2010-06-28.
Network Technologist.com. Archived from on 14 July 2011. Retrieved 28 June 2010. (PDF) (Press release). Retrieved 2010-06-28. Staimer, Marc (2009-03-25). Retrieved 2010-06-28.
Retrieved 2010-06-28. 14 April 2010. Archived from on 7 June 2010. Retrieved 28 June 2010. Retrieved 2010-06-28. Raffo, Dave (2009-11-18). Retrieved 2010-06-28.
Wexler, Steve (2009-11-25). Retrieved 2010-06-28. External links.
. HP Data Protector IDB Purge best practices Commands that purge obsolete data from the HP Data Protector (DP) software Internal Database (IDB), to maintain the IDB in good condition Table of contents Introduction.2 Scope. 2 Three step guide to use this white paper. 2 How to identify if a DP IDB needs filenames purging?. This document presents some Data Protector commands that can help keep your Internal Database healthy.
This white paper is complementary to the white paper HP Data Protector software cell manager planning and sizing. Please also follow the recommendations therein to facilitate reliable Data Protector operation. The global file is located on the DP Cell Server under: Windows (default) C: Program Files OmniBack Config Server Options global HP-UX/SUN Solaris/Linux (default) /etc/opt/omni/server/options/global The daily check triggers an “IDB Purge Required” notification if:.
The time elapsed since the last IDB filename purge exceeds Days Last Purge days (default, 180 days). Manual discovery A filenames purge preview status report can be manually created either using the DP command line interface (CLI) or the GUI. DP CLI: omnirpt –report dbpurgepreview. DP GUI: Reporting context, right click on “Reports” and select “Add Reporting Group.” Choose a name and click on “Finish.”.
DailyMaintenanceTime=08:30 Method 2 Run the command omnicc -debug 20 CHECK.txt, and look at the output debug file which will:. Be in (default)/tmp on HP-UX. Be in (default) C: Program Files OmniBack tmp on Windows.
Have file name ending with CHECK.txt. Look through the output file for name=DailyMaintenanceTime and see the value: For example if you see value=12:00 daily maintenance is running at 12:00 hrs value=99:99 daily maintenance is disabled value=None daily maintenance is disabled value=20:30 daily maintenance is running at 20:30 hrs If Daily Maintenance is not running In case Daily Maintenance is disabled consider the following steps: In the global file set a time for the daily maintenance to run. Mpos purge Note: This purge is available by default on DP 6.1, but for DP 5.5 and 6.0 it requires one of the following patches or their successor. Windows HP-UX PA Risc HP-UX IA 64 Data Protector 5.5 DPWIN00396 PHSS38726 PHSS38727 Data Protector 6.0. Look at the file (default location): on windows C: Program Files OmniBack log server purge.log on HP-UX /var/opt/omni/server/log/purge.log See Appendix C for an example of the update to purge.log of a completed filenames purge. If the purge has not finished, but you need to run backups simply stop the purge with omnidbutil -purgestop and use DP as normal. Frequently Asked Questions about filenames purge Question 1: Will the force option cause the filenames purge to remove protected data?
Answer 1: No, a force purge will not remove any protected data from the DP IDB. A purge without the force option looks for obsolete records for a hostname and only purges those records if there are more than 1000000 obsolete entries. When doing this, it is good practice after stopping DP (omnisv -stop) to look for any remaining DP processes that may be running and close them before restarting DP (omnisv -start) On HP-UX proceed as follows:. Close all DP GUIs. Windows default location of global file: C: Program Files OmniBack Config Server Options HP-UX location of global file: /etc/opt/omni/server/options The value for the number of days used by the daily maintenance omnidbutil -purge - messages command is determined by the setting value of KeepMessages in the global file.
Appendix C Example update to purge.log after a completed forced filenames purge 1/12/2009 2:37:09 PM ASM.5312.4976 'sm/asm/asmpurge.c /main/dp56/1':470 A.06.00 bDPWIN00385 Purge session started. 1/12/2009 2:37:09 PM ASM.5312.4976 'sm/asm/asmpurge.c /main/dp56/1':480 A.06.00 bDPWIN00385 Filename purge session started.
REPORTDATA 0 0 6 REPORTDATA 0 0 6 REPORTDATA 0 1161430 32 1/12/2009 3:20:02 PM ASM.5312.0 'db/dc/dcpurge/dcpurge.c. GUIs are closed. When run, this purge updates the RDS.log file.
On Windows the RDS.log file is, by default, C: Program Files OmniBack db40 datafiles catalog. On HP-UX the debug.log file is: /var/opt/omni/log Example of messages seen at the command line omnidbutil -purgefailedcopies DONE! Example of the update to RDS.log. Help menu, Help Topics. Search tab for searching. Contents tab is the equivalent of an Administrator’s Guide.
Chapter 5 of the HP Data Protector Concepts Guide, which is available from the DP GUI, help menu, Online documentation. The omnidbutil main page: On HP-UX this can be accessed by ”man omnidbutil”. Nothing herein should be construed as constituting an additional warranty.
Hp Data Protector 8 Manuals
HP shall not be liable for technical or editorial errors or omissions contained herein.