Conversion Storage-Policy/Schedule-Policy to Plan

Hi Markus,

thank you for your response and the clarification. 

I tweaked a little bit with plans by removing all unwanted schedules (including the synthetic one that cannot be seen in the command center). If we are going to move from the existing 1000+ schedule-policies and 50+ storage-policies to plans … this seems to be very much work.

Currently we are investigating the use of plans without using the schedule-policy part of the plan by deactivating the corresponding schedule policy. This would give us a simple replacement for the storage-policy (and this would cause only a limited amount of configuration-work). In this situation we could start the backups via the subclient from the external job scheduler.

In any case we have to keep in mind that the Java-GUI will disappear and “tweaks” for a schedule-policy might not be possible any more. 

Thank you and best regards.

Michael

Hey Michael,

you may set the Additional Setting “‘showSynthFullSchedulesInServerPlan” to see the hidden SynthFull schedule in Command Center as well. This will be the default from 11.36 and later btw.

I recently had a discussion about that with our Development and they at least confirmed it is allowed to use the Java GUI for removing unwanted schedules from Plan-associated Schedule Policies. However, they declined disabling the automatic addition of SyntFull schedule as that is the recommended best practice. Also, note that disabling the Plan-associated Schedule Policy and using a separate Schedule Policy instead which was created via Java GUI may lead to issues. Therefore, I would strongly recommend using the one associated to the Plan.

Currently, when creating a Plan, the SynthFull schedule will automatically be added as an automatic schedule, regardless if it was already removed from the template Plan or not. However, note that this schedule should never kick in as long as you do regular Fulls at least once during the retention time period (like at least one Full per week when using 7 days retention, or at least once every two weeks when using retention of 14 days for example).

We are still fighting hard to get all functionality of the Java GUI over to Command Center, and this should also cover Schedule Policy changes. Until then, the Java GUI will coexist.

BTW: In 11.34.16 there is a change that re-enables the usage of the Java GUI for new installations by default, and there is currently no date or target release announced to disable it again. Prerequisite for disabling the Java GUI will be that all required functionality is available in Command Center.

Regards,

Markus

Hey Markus,

this sounds very good. It is good to know that the synth-full can be shown in the CommandCenter. 

Concernng the “disabled schedule policy” for the plan. We are investigating if we can start the backup via the subclient and not an “old-Stype” schedule policy that might conflict with the plan-stype schedule policy.

Regards.

Michael

Sounds like a “plan” to me :-)