Are there many good reasons to change from Data Protector on Unix to a different operating system? I do not know many… However, there are customers required to do this step and to migrate to Windows or Linux; often combined with a upgrade to the current version of Data Protector. And here the story starts: there is no path for migration available. The reason is simple, the DCBF folders are not compatible between Unix and Windows nor is there a chance to do an export and import of the internal database. The DCBF folders on HP-UX are stored in big-endian format and on Linux in little-endian format and there is no tool for translation available. What the difference is can be search at your favorite search engine. The article is somehow larger than usual, you’ll need 30 minutes to work through, the article is addressed to experts. At the end of this article you’ll find the link to the export and import
Looking back in 2016 – again a very successfully year for data-protector.org. The Blog was visited 210,000 times (Page Views with about 97,000 visitors) and 54 new articles were released. In total about 269 articles are available. The most popular day was 22.11.2016 with 922 visitors. Since the stats were introduced, the blog was visited about 904,000 times (Page Views with about 261,000 visitors). The most popular articles viewed covered the whitepaper, migration pathes, information about patches and of course older articles. The most popular pages are BRICK and Downloads. The visitors are located in 199 countries, mainly from Germany, United States, India and Brazil. Individual countries from the European Union follow. More than 450 people are subscribers of data-protector.org and get informed about new posts. The most people are referred by Google and Bing; it’s not a surprise, data-protector.org is always listed on the first page in top 10
I already wrote several articles on how to migrate the internal database to a new hardware, new Data Protector version, or new operating system (see link). With the introduction of PostgreSQL as internal database for Data Protector and compared to previous versions (DP 6 and DP 7), some more steps are required to migrate a cell manager to new hardware or operating system. However, if you follow the steps below it will not be a complicated procedure. In the document the migration from DP 9.0x to DP 9.0x on new hardware (or virtual machine) is described. It is assumed that the server name, IP address, installation path, passwords, … stay the same and as it was the case on source server. Hence, some less steps required when compared with a previous article about migration (see link). This document could also be used to migrate from Windows 2008 R2 to Windows
Update 2016/0705: In section installation source it was recommended to use a patched installation source for the upgrade. This method must not be used for upgrades from Data Protector versionen 8.13 and newer, as it will cause serious damages in the internal database (no fix available/possible). For versions older 8.13 it is too recommended not to use a patched installation source due to missing tests by engineering. In this case, please install Data Protector 9.0 first followed by installation of current patch bundle. One exception to use a patched installation source is when doing a new installation (“green field approach” – i.e. Windows 2012 R2 Cluster Cell Server), es there are no depenencies for upgrading internal database. Data Protector 7.0 was introduced on 16.04.2012 and meanwhile superseded by two major releases. On 30.06.2016 the time has come and the support for Data Protector 7.0x ends. Thus, it is time for
Please find below all available downloads from this blog. I’ll be glad if you honor the efforts I spent for the work, every donation counts! Please use the “donate button” on the bottom of the site or using the following link. Link: DONATE Many thanks for your support! BRICK – Backup Related Information Collector and Keeper – Version 2.0 https://www.data-protector.org/wordpress/?s=BRICK EADR for Cell Server – DP 9.06 on Windows 2012 R2 https://www.data-protector.org/wordpress/2016/05/prepare-and-execute-eadr-cell-server-on-windows-2012-r2-data-protector-9-06/ Data Protector Best Practice Guide https://www.data-protector.org/wordpress/?s=best+practice+guide BRICK – Backup Related Information Collector and Keeper – Version 1.20 (Pre 1.10 versions removed) https://www.data-protector.org/wordpress/?s=BRICK OMNILISTFREEDEVS – lists free devices www.data-protector.org/wordpress/?s=OMNILISTFREEDEVS OMNISPEED v2.00 HP-UX / Linux / Windows https://www.data-protector.org/wordpress/2014/03/omnispeed-2-0-data-protector-8-xx-hp-ux-linux-windows/ EADR for Cell Server – DP 8.1X on Windows 2012 R2 https://www.data-protector.org/wordpress/2014/04/eadr-cell-server-dp-8-1x-windows-2012-r2 OMNISPEED – average speed and current speed of running and completed sessions https://www.data-protector.org/wordpress/?s=OMNISPEED+average+speed+and+current+speed Simple Media Vaulting / Off-Site Tape Vaulting https://www.data-protector.org/wordpress/?s=Simple+Media+Vaulting Data Protector 6.2 Scheduler https://www.data-protector.org/wordpress/?s=Data+Protector+6.2+Scheduler Data Protector Migration Unix
On 2016/01/29 HPE released new patches for Linux, Windows and HP-UX. As a requirement you need to have Patch Bundle 7.03 installed. It is strongly recommended to read the full description of each patch. If you own a valid support contract you can download the patch from https://softwaresupport.hp.com. For login you need the HP Passport account. Please keep in mind to install the patches in correct order – see https://www.data-protector.org/wordpress/2013/06/basics-installation-order-patches/. As Data Protector 7.0X will become “End-of-Live” this summer, please consider to plan for a migration to current version. Direct link: – Data Protector 7.03_108 – SMISA for Windows – Data Protector 7.03_108 – StoreOnce Software for Windows – Data Protector 7.03_108 – VMware-GRE for Windows – Data Protector 7.03_108 – VEPA for Windows – Data Protector 7.03_108 – Documentation for Windows – Data Protector 7.03_108 – Disk Agent for Windows – Data Protector 7.03_108 – Cell Console for Windows
Looking back in 2015 – a very successfully year for data-protector.org. The Blog was visited 200,000 times (Page Views with about 95,000 visitors) and 36 new articles were released. In total about 219 articles are available. The most popular day was 10.12.2015 with 1188 visitors. Since introduced the stats the blog was visited about 713,000 times (Page Views with about 187,000 visitors). The most popular articles viewed covered the support matrices, Data Protector migration, information about patches and of course older articles from 2011 to 2014. The most popular pages are BRICK and Downloads. The visitors are located in 181 countries, from Germany and the United States. Meanwhile the countries India, Brazil and Russia have passed individual countries from the European Union. Worldwide 12 countries never visited data-protector.org. More than 370 people are subscribers of data-protector.org and get informed about new posts. The most people are referred by Google and
It again was a very successfully 2014. The Blog was visited 185.000 times (Page Views with about 85.000 visitors) and 54 new articles were released. In total about 185 articles are available. The most popular day was on 06.11.2014 with 1119 visitors. The most popular articles viewed covered the support matrices, Data Protector migration and of course older articles from 2011 to 2013. The most popular pages are Downloads, BRICK and Video Tutorials. The visitors are located in 173 countries, from Germany, US and Europe. Worldwide approx. 20 countries never visited data-protector.org so far. More than 275 people are subscribers of data-protector.org. The most people are referred by Google, which is not a surprise; data-protector.org is at least within the first 10 results when searching for “Data Protector”. Thanks to all valued readers for supporting the site.
There are different ways to add licenses into Data Protector. Copy and paste the license file generated on the licensing portal (http://www.webware.hp.com) as …/Config/Server/cell/lic.dat Copy and paste of a single or several licenses keys into exisiting lic.dat Copy and paste of a single license key using the Data Protector GUI (Clients – Data Protector Cell – right-click – Add License) The first and second method are very easy ways to add licenses. When using the third method, in some cases you may encounter problems, as for cell server running on Windows (HP-UX / Linux not tested) the so called BOM (Byte Order Mark – see http://en.wikipedia.org/wiki/Byte_Order_Mark) is inserted into the lic.dat file. When the BOM is inserted, it might be the case, that the first line in lic.dat is ignored by Data Protector. This applies to the Data Protector versions 8.XX and 9.0X. If the environment is migrated from previous
The migration of the internal database to new hardware or to a new Microsoft Windows operating system was no big deal in the past and before the release of Data Protector 8.xx. With the introduction of PostgreSQL as the new internal database this has been changed and several steps are necessary in order to perform a successful migration. The following is a guide that enables you doing a migration to new hardware, or, for example, the move from Windows 2008 R2 to Windows 2012 R2. For a successful migration, some requirements must be met; furthermore the migration is dependent on various conditions. For the listed instructions no guarantee can be given and it is recommended to perform the migration with an HP partner. For the elaborate article I would be glad to receive some donations. Prerequisites and conditions: The command omnidbcheck -extended shows no errors. For Data Protector version 8.10
Sorry, this article is not available in your language, as the promoted event is available in Germany only.
Data Protector 8.10: With Data Protector 8.10 it is very important to check name resolution before starting the installation. If it’s not possible to resolve the FQDN of the cell server (of course short and revers too), a login prompt will appear when opening the GUI (this is the LDAP logon dialog, which is an additional feature in DP 8.10) and a “permission denied” message afterwards. In documentation it is listed that a working name resolution is a requirement for DP 8.10. If the installation was done without working name resolution for the cell server, a new installation has to be done after name resolution was fixed; a newly generated certificate was not accepted by the GUI. Additional information: With DP 8.10 certificates are used locally to access the GUI, you will be prompted to accept the certificate when launching the GUI for the first time after the installation. In
Data Protector 8.10 has been released. The new version delivers some new features, my favorites are the new advanced scheduler and the file-system backup, which can be resumed. For customers with a valid support contract, the new version can be downloaded here: http://support.openview.hp.com. With Data Protector 8.1 new licenses are required, for updates from previous versions the “InstantOn” license was added to allow sufficient time to migrate the current licenses using: http://webware.hp.com. Announcement: Starting 01. April 2014 Data Protector 6.2X is no longer sold, on 31. December 2014 DP 6.2X becomes end-of-support; so migrate to the latest version of Data Protector. New features in Data Protector 8.1 (excerpt) – additional information can be found in the document “Product Announcements, Software Notes, and References”: Advanced Scheduler – priority based SAP HANA BackInt integration Enhancements for Disaster Recovery New licenses MS Active Directory (LDAP login for GUI) File-System backups able to resume
If it matters, you had better trust on HP Data Protector to get fast backups and to achieve your backup windows. During the implementation of a StoreOnce appliance with a partner of HP, the following performance values were achieved (see pictures below). The environment: a backup of 5 virtual machines and 15 mount points from different virtual and physical server, 20 Data Protector streams in total. The destination was a HP StoreOnce appliance 4420, 2 Catalyst stores used. The 20 GbE network was utilized for 55%, a further increase in backup performance, of course, possible. Unfortunately, no additional server can be used during the migration and therefore no additional source data were available. The HP Data Protector feature source side deduplication will be used once the migration has been finished. I will expect a further increase of backup performance after migration. Sample 1: Network monitor Sample 2: StoreOnce monitor