Stay organized with collectionsSave and categorize content based on your preferences.
The backup/recovery appliance automatically calculates and sets default backup
plan compliance settings. Default settings are based on whether the policy is
set to windowed or continuous, the policy type, and recommended best practices.
The default settings calculated meets the needs of most users. Backup plan
compliance settings can be set manually to meet specific requirements. In
addition, a threshold can be set to alert you if your data is approaching a
point where it is out of compliance.
To view or modify backup plan compliance settings, click backup plan policy
compliance settings at the bottom of a policy's page. The default link name isDefault, however, the link name is dynamic and changes according to the
backup plan compliance settings used.
If data exceeds the backup plan compliance settings, a violation is raised and
it remains in effect until you have successfully captured data with a
consistency time that falls within the specified threshold. Because compliance
is time based, a job can fail and restart multiple times but the data remains in
compliance as long as the job eventually captures data with a consistency time
that falls within the boundary of a specified threshold.
Backup plan compliance settings
Policies set toWindowedorContinuousprovide a link to backup plan
compliance settings that have settings for the following:
Turning off backup plan compliance analysis
Using the default backup plan compliance settings
Defining a custom compliance setting. When defining a custom setting for a
windowed policy, consider the time at which the data is snapped
(consistency time), how long the window is open, and the amount of time
required to capture the data.
Setting a warning that sends you a notification if a job is still
running after a specified period of time. Set this to less than the wait
time for raising a violation so you can address issues before a job is in
violation.
To determine whether the data captured is in compliance, a backup/recovery appliance
uses the start of the window, the consistency time of the captured image, and
the violation threshold specified in the backup plan settings dialog. If
successfully captured data has a consistency time that falls within the
window's defined threshold, the data is in compliance.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eBackup/recovery appliances automatically set default backup plan compliance settings based on policy type and best practices, which typically meet most user needs.\u003c/p\u003e\n"],["\u003cp\u003eUsers can customize backup plan compliance settings to address specific requirements, including setting thresholds for data compliance alerts.\u003c/p\u003e\n"],["\u003cp\u003eCompliance is time-based, with violations occurring if data consistency time falls outside specified thresholds, but jobs can recover and remain compliant if they eventually capture data within the threshold.\u003c/p\u003e\n"],["\u003cp\u003eWindowed and Continuous policies include options for managing backup plan compliance, such as disabling analysis, using defaults, or defining custom settings with the ability to configure warning notifications.\u003c/p\u003e\n"],["\u003cp\u003eData compliance is determined by the window's start time, the captured image's consistency time, and the specified violation threshold.\u003c/p\u003e\n"]]],[],null,["# Backup plan compliance\n\nThe backup/recovery appliance automatically calculates and sets default backup\nplan compliance settings. Default settings are based on whether the policy is\nset to windowed or continuous, the policy type, and recommended best practices.\nThe default settings calculated meets the needs of most users. Backup plan\ncompliance settings can be set manually to meet specific requirements. In\naddition, a threshold can be set to alert you if your data is approaching a\npoint where it is out of compliance.\n\nTo view or modify backup plan compliance settings, click backup plan policy\ncompliance settings at the bottom of a policy's page. The default link name is\n**Default**, however, the link name is dynamic and changes according to the\nbackup plan compliance settings used.\n\nIf data exceeds the backup plan compliance settings, a violation is raised and\nit remains in effect until you have successfully captured data with a\nconsistency time that falls within the specified threshold. Because compliance\nis time based, a job can fail and restart multiple times but the data remains in\ncompliance as long as the job eventually captures data with a consistency time\nthat falls within the boundary of a specified threshold.\n\nBackup plan compliance settings\n-------------------------------\n\nPolicies set to **Windowed** or **Continuous** provide a link to backup plan\ncompliance settings that have settings for the following:\n\n- Turning off backup plan compliance analysis\n- Using the default backup plan compliance settings\n- Defining a custom compliance setting. When defining a custom setting for a windowed policy, consider the time at which the data is snapped (consistency time), how long the window is open, and the amount of time required to capture the data.\n- Setting a warning that sends you a notification if a job is still running after a specified period of time. Set this to less than the wait time for raising a violation so you can address issues before a job is in violation.\n\nTo determine whether the data captured is in compliance, a backup/recovery appliance\nuses the start of the window, the consistency time of the captured image, and\nthe violation threshold specified in the backup plan settings dialog. If\nsuccessfully captured data has a consistency time that falls within the\nwindow's defined threshold, the data is in compliance.\n\nWhat's next\n-----------\n\n- Get an overview of [backup plan](/backup-disaster-recovery/docs/concepts/backup-plan)\n- Create a [backup template](/backup-disaster-recovery/docs/create-plan/create-template)\n- Create a [backup policy](/backup-disaster-recovery/docs/concepts/policy-overview)\n- Create a [resource profile](/backup-disaster-recovery/docs/concepts/resource-profiles)\n- Configure [advanced policy settings](/backup-disaster-recovery/docs/create-plan/policy-settings) of an application backed up by the policy\n- [Apply a backup plan to an application](/backup-disaster-recovery/docs/create-plan/apply-backup-temp-overview)"]]
