{"id":4032,"date":"2018-05-09T12:00:43","date_gmt":"2018-05-09T11:00:43","guid":{"rendered":"https:\/\/www.data-protector.org\/wordpress\/?p=4032"},"modified":"2018-06-16T10:10:24","modified_gmt":"2018-06-16T09:10:24","slug":"complex-schedules-data-protector-10-03","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2018\/05\/complex-schedules-data-protector-10-03\/","title":{"rendered":"Complex Schedules in Data Protector"},"content":{"rendered":"

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<\/a>.<\/p>\n

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\u00a0migration.log<\/strong> on the Cell Manager.<\/p>\n

Successfully migrated\u00a0schedule files (Legacy Scheduler) are kept in the corresponding directories on the Cell Manager but are renamed to SpecName.migrate<\/strong>. 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<\/strong>.<\/p>\n

<\/p>\n

While most of the schedules should be migrated without user intervention, manually created or modified schedules might cause issues during the migration. Here is an example of the migration.log<\/strong> where one backup and two copies fail to migrate. Usually those schedules need to be re-created in the Consolidated Scheduler.<\/p>\n

pausing quartz scheduler...ok\r\n\r\nMigrating old schedules\r\n\r\nmigrating pre 10.0 advanced scheduler schedules...ok\r\n\r\nmigrating backup schedules...\r\n[\u2026]\r\n \u00a0\u00a0 migrating schedule OB2 BACKUP_FS...failed. error: Schedule(s) couldn\u2019t be migrated. Please refer to Data Protector documentation and recreate the schedule(s).\u00a0\r\nmigrating object copy schedules...\r\n[\u2026]\r\n\u00a0\u00a0\u00a0 migrating schedule COPY_FS_MONTHLY...failed. error: error parsing schedule buffer\r\n\u00a0\u00a0\u00a0 migrating schedule COPY_FS_WEEKLY...failed. error: error parsing schedule buffer<\/pre>\n
Similar to the Advanced Scheduler the Consolidated Scheduler is integrated into the Internal Database (IDB). Direct modifications to schedule files are not possible.<\/p>\n
Custom schedule with a single specification<\/h3>\n
The schedule file for BACKUP_FS contains a manually modified schedule that executes an Incr1 backup every Sunday at 02:00 with an exception of the last Sunday of the month where it is executed as Full.<\/p>\n
\"\"<\/p>\n
\n\n
\n    
\n        
\n            \"Icon\"\n        <\/div>\n        
\n            
\n                BACKUP_FS schedule file<\/a>\n                \n                    <\/i> 0\n                    <\/i> 153 downloads\n                <\/span>\n            <\/h3>\n            ...\n        <\/div>\n        
\n            Download<\/a>\n        <\/div>\n    <\/div>\n\n<\/div>\n