Dear visitor,
on Februar 15, 2017 Daniel Braun, the owner and mastermind of this website passed away unexpectedly. This is an unbelievable shock and loss for everybody.
Complex Schedules in Data Protector
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 in time using omnidbutil -migrate_schedules.
Webinar [en] – Introducing Data Protector 10.03
We already reported about the updated release of Data Protector 10.03, now Microfocus presents a webinar with a live demo of all new features as well as the new documentation portal. To attend the webinar a free registration at BrightTALK™ is required.
Wednesday, 03.05.2018 um 5:00 pm (UTC+2/MESZ)
All details as well as the option to register can be found in the following BrightTALK announcement.
Continue reading “Webinar [en] – Introducing Data Protector 10.03” »
dp.tips deactivation
As update to the post https://www.data-protector.org/wordpress/2016/04/dp-tips/ please note that the short-URL dp.tips will be deactivated in near future.
The only usable URL will be https://data-protector.org – please update your favorites accordingly.
Effectively manage omnirc options
Data Protector is highly customizable product with a wide range of configuration options. While the any global options applies to the whole Cell, the omnirc configuration file allows the user to tweak a specific client or just a module on that client system. It you have to manage a large amount of individual clients this can become a management challenge to make sure the right omnirc options are present on the right the client system.
Over the years several ways to deal with this has been found, e.g. the script omnircsync.pl (available in the download section) using the util_cmd -setomnirc push functionality. This functionality is adopted with the release of Data Protector A.10.03 into the product. We want to share some pretty handy use cases and examples of the new omnicc -update_omnirc command.
It allows to push one omnirc option (key/value pair) at a time and you can select a specific operating system type, client systems with a specific agent installed or a set of hosts in a comma separated list or from a input file.
omnicc -update_omnirc omnircName -value omnircValue
[{ {-module moduleName1 [,moduleName2,..]} |
{-client_os osName1 [,osName2,..]} |
{inputFile | {-hosts hostName[,hostName2,..]}} }]
Options:
moduleName = da, ma, cc, mssql70, oracle8, vepa, (as found in cell_info file)
osName = gpl, microsoft, sun, ... (as found in cell_info file)
Webinar [de] – DPzWs 2018/04
Sorry, this article is not available in your language due to the fact that the following Webinar is only in German language available.
Continue reading “Webinar [de] – DPzWs 2018/04” »