Page Comparison

Maintenance Activity

The A maintenance activity defines the actual set of maintenance actions to perform, for example - perform required for a specific goal. An example of such an activity is "Perform Secure Backup on device X".
It will also contain Additionally, the maintenance activity contains other specific definitions for the action, like . This may include for instance which certificate to use should be used for the Secure Backup or ,  or which deployment policy to use should be used for a configuration sync operation.

Maintenance

...

Plan

A maintenance activity such as backup or sync is defined inside a plan - , e.g. a backup plan or sync plan - a plan cannot contain two types , a sync plan etc. A plan only contains a single type of activities.
A plan contains common definitions for all the activities - included within it, such as the scheduling definition, email and syslog addresses to report to, and so onetc.
A plan cannot be enabled if it does not must contain at least one activity in order for it to be enabled.

Maintenance Task

A maintenance task is the execution of the an operation on the a device - for example, . An example of a maintenance task would be a secure backup activity on devices QA1 and QA2 will execute which executes two backup tasks , - one for each device.

Using Patterns for Device and Domain Names

Whenever device or domain patterns are allowed - for example, when choosing which devices or domains to backup - use an asterisk to designate a pattern or a comma to list values

Here are some valid examples when choosing a device:

...

...

Maintenance Window

The A maintenance window defines the range of hours where a period of time during which maintenance plans are allowed to run.
It The definition of a maintenance window consists of two parameters in 24h format (e.g. 22:00) - the maintenance

• Maintenance window start

...

• time 
• Maintenance window end time

...

A maintenance window may be defined separately for each Maintenance Plan. Alternatively, the installation may use a default system value (see maintenance configurable parameters for more information)
Maintenance Plans will not execute outside the maintenance window,.
If, when the Maintenance Window has ended, some of the plan's tasks were are still waiting to execute when the maintenance window ended, they will be marked as canceled cancelled and the plan execution will end - executing . Executing tasks will not be interrupted.

...

The error policy controls what happen when a task fails (during either validation or during execution)
When the error policy is "Halt" - all waiting tasks will be canceled cancelled and will not execute - executing . Executing tasks will not be interrupted.
When the error policy is "Ignore" - other remaining tasks will continue to execute as normal.

How to

...

Execute Maintenance Plans

There are three ways methods to run execute a maintenance plan, the plan must be first enabled for all three ways to work.
Note that regardless of the method used, to execute a plan it must first be enabled.

1. Scheduled run - enter : Enter a value in the plan's schedule field, the . The format is identical to the same as the one that is used used for scheduling a report
2. Via REST API - Check : Consult the Backup REST API or Sync REST API pages for more details
3. Ad-hoc - :  By clicking "Execute" on the Plan Details Page
   
   

Using Patterns for Device and Domain Names

Whenever device or domain patterns are allowed within a plan (e.g. when choosing which devices or domains to backup), DPOD accepts an asterisk to designate a pattern, or a comma to list values

Some examples for device selection are listed below: