Table of contents

Create Policy

Last modified
Table of contents
<< PrevNext >>

A right-click on the policy node displays an action to create a policy. This action can also be selected from the right Actions pane.

 

Policies2S.png

 

The following dialog is then presented to the user.

 

Policies4.png

 

To create a policy, specify the following on the ‘General’ tab:

 

  • Name – a unique name for this policy.
     
  • Volume Group – the volume group you wish to create a backup policy for.
     
  • Operation – specify the type of backup you would like to have performed as part of this schedule, including Snapshot, Cloud Snapshot, or Cloud Clone.
     
  • Retention – the number of backup copies to retain as part of this schedule. Checking the ‘all’ box will retain all backup copies until the maximum number of backup copies per volume is reached, at which point the policy will fail with an error. Alternatively, specify a number of backups to retain (between 1 and 64).

 

Note.png Note: Retention applies to backups created via a policy and not to those taken interactively.

 

The ‘Schedule’ tab allows you to define the schedule for the policy.

 

Policies5.png

 

On the schedule tab, specify:

 

  • Settings – including the frequency that the policy should execute, and its start time
    • One Time - the schedule will execute once only.
    • Daily - the schedule will execute every day.
    • Weekly - the schedule will execute every week.
    • Monthly - the schedule will execute once a month.
    • Start - specifies the date and time the policy will start.
       
  • Advanced Settings – including repetition, expiration, and whether or not the schedule is enabled.
    • Repetition - specify how frequently the schedule should repeat, and how long this repetition should occur. Choosing a ‘Repeat’ value will cause the policy to repeat regularly until the specified duration has expired. For example, a policy configured as ‘one time’ with a repeat value of ‘1 hour’ for a duration of ‘1 day’ will run each hour for one day, and then no longer run. 
    • Expiration - specify the time and date that the policy should be made inactive.
    • Enabled - specify whether or not the schedule is active and enabled, i.e. backup jobs will be executed using this policy.

 

The timestamp in the ‘Next Run’ field shows when the policy will execute next.

 

Note.png Note: Only one instance of a given policy can run at any time. If you schedule the policy to repeat in a period of time that is less than the amount of time needed to complete the previous iteration, the next iteration will not start. An iteration of a policy will not start if the previous iteration is still running.

 

Once you click the Accept button the new policy will be added to the list of existing policies in the result pane, and if enabled, the policy will be displayed in the scheduled jobs list along with the time and date of its next run.

Back to Top

 

 

<< PrevNext >>
Page statistics
310 view(s) and 5 edit(s)
Social share
Share this page?

Tags

This page has no classifications.

Comments

You must to post a comment.

Attachments