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
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.
The Patch Bundle A.10.04 (Build 182) for Data Protector 10 has been released on May 22, 2018. Data Protector A.10.03 was released as a full install therefore the cumulative patch 10.04 can only be installed on top of A.10.03. A direct upgrade from A.10.00, A.10.01 or A.10.02 is not possible! It is recommended to install it on all Installation Servers (IS) and the Cell Managers (CM). Then push the new packages from the IS to all Data Protector client systems to get the latest fixes into effect. This patch can also be installed locally on Windows Data Protector client systems. In this case only components that were locally installed on the client will be updated. Linux and UNIX clients still require an Installation Server while updated packages can be extracted from the Linux or UNIX Installation server manually.
Transitioning to the new Consolidated Scheduler, introduced with Data Protector A.10.00, can be a challenge. Especially when customized schedules have been used in the Legacy Scheduler to overcome former product limitations. A common example are manually modified schedule files to execute jobs at the last weekend of the month. Data Protector A.10.03 improves the overall upgrade experience from previous versions such as 8.1x and 9.x. During the upgrade existing Legacy- and Advanced Scheduler schedules are migrated into the new Consolidated Scheduler. Once the upgrade is complete a summary is displayed by the installer. Details on schedule migration are logged into the file migration.log on the Cell Manager. Successfully migrated schedule files (Legacy Scheduler) are kept in the corresponding directories on the Cell Manager but are renamed to SpecName.migrate. Empty schedule files are skipped. This allows manual modifications to any non-successfully migrated schedule files and re-run the schedule migration at a later point