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
Data Protector A.10.10 (Build 134) has been released on September 17, 2018. The new version is another full install to simplify the upgrade and installation process.This will be the default for all future Data Protector versions. Data Protector 10.10 does not require any previous version to install the latest version of Data Protector in a new environment. Direct upgrades from Data Protector 8.1x. 9.0x, 10.0x to version 10.10 are possible – there is no need to install Data Protector 10.00 or 10.0x as an upgrade step. Data Protector 10.10 is a fully featured Media Kit and therefore currently not available in the Software Support Online (SSO) Portal for download.
On Aug 01, 2018, Micro Focus has adjusted the support timeline for Data Protector 9.0x once more. All dates have been extended by 6 months, so the committed support for Data Protector 9.0x ends instead of the Dec 31, 2018 now on Jun 30, 2019. For a quick overview all dates are visualized in the following figure.
Following you can find the most frequently searched URL’s, we try to keep this as up to date as possible. Disclaimer: The preceding links refer to external websites of third parties on whose contents we have no influence. Therefore, we can not assume any liability for these external contents. The respective provider or operator of the pages is always responsible for the contents of the linked pages. The linked pages were checked for possible legal violations at the time of linking. Illegal content was not recognizable at the time of linking. However, a permanent content control of the linked pages is not reasonable without concrete evidence of an infringement. Upon notification of violations, we will remove such links immediately.