From the
PowerProtect Data Manager UI, you can disable a protection policy to temporarily stop running certain backup schedules of this policy.
About this task
There are several reasons why you might want to disable a protection policy. For example, by disabling a policy, you can:
Edit the policy and determine the impact of your changes before these changes take effect.
Stop backup activity on primary storage if the storage is in maintenance or is temporarily unavailable (for example, during a storage upgrade).
By default, disabling a centralized protection policy stops the primary backup schedules of this policy, including synthetic full schedules, full schedules, and so on. Any replication, cloud tier, and extended retention schedules, however, continue to run while the policy is disabled. You can also perform manual primary backups of a policy that is in
Disabled state by using the
Protect Now functionality in the
PowerProtect Data Manager UI.
Protection jobs running for a disabled policy provides information about jobs that continue to run when a policy is disabled.
You can modify the default behavior to make changes regarding which jobs continue to run when a policy is disabled by using System Level overwrites in the REST API. The
PowerProtect Data Manager Public REST API documentation provides instructions.
When a protection policy is disabled, you can edit the policy in the same manner that you would edit an enabled policy. The advantage of editing a policy in
Disabled state is that you can preview the changes before resuming primary backups of the policy.
Editing a protection policy provides more information about modifying the details of an existing policy.
Steps
From the left navigation pane, select
Protection > Protection Policies.
The
Protection Policies window opens.
Select one or more policies in
Enabled state. You can also select the checkbox at the top of the table to select all policies on the current page.
Click
Disable.
Results
The policy status changes to
Disabled. In
Disabled state:
In progress primary backup jobs that are associated with this policy continue to run until complete. If primary backups are scheduled to run during the time that the policy is disabled, those backups do not run, even when you enable the policy again. When you re-enable the policy, future scheduled backups resume.
All other protection jobs for the policy continue to run according to schedule, unless no primary backup copy exists for the policy. In this case, protection jobs are skipped.
Manual backups of primary schedules can still be performed.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\