Adding a Backup Plan

Olivia McCormack
Olivia McCormack
  • Updated
Note: This feature is rolling out gradually and may not be available in your account yet.  
Legacy user? Check out Activating your backups for more details.

Oh hey there! This article will walk you through adding a Backup Plan to your Backup Radar account.

Backup Plans is a new, improved, and centralized method for activating and managing your backup results and system alerts, to eventually replace legacy features such as templates, schedules, ticket rules, status calculation, and the Audit page.

Think of a Backup Plan as a container that you create, customize with your expectations (such as scheduling, recovery point objective (RPO), and service-level agreement (SLA) requirements), and group your devices within. 

Interested in a full introduction and overview of Backup Plans before diving into the details? 

Check out our 30-minute Introduction to Backup Plans course.
 
Who can use this feature?
• Administrator users.
• Standard users (who have been granted access).
 

1. In Backup Radar, navigate to Manage > Backup Plans.

2. Click Add Backup Plan.
Click Add Backup Plan.png

 

Step 1: General Info

Configure the following fields to describe and set identifiers for your Backup Plan, and choose the result type it will be ingesting. To save your progress at any point and finish creating your Backup Plan later, click Save (note: a Plan name is required before progress can be saved). When you're done, click Next.
Step 1. General Info.png

a. Plan name (required): Name your plan anything you'd like (e.g. Datto Backup Plan).

b. What results will this plan be ingesting? (required): Choose the result type this plan will be ingesting: Backups or System Alerts.

For more on backups vs. system alerts, check out Backup Type.

c. Description: You can optionally provide any additional details about this plan.

d. Tags: You can optionally assign one or more tags to your plan. This will apply each tag to every backup result ingested by this Backup Plan.

 

Step 2: Vendor & Classification

Configure the following fields and click Next:
Step 2. Vendor & Categorization.png

a. Backup Vendor (required): Choose the applicable backup vendor for the results you would like to be ingested by this plan. If you're unsure, you can double-check this value in the Vendor column on the Activate Backups page.

b. Backup Application (required): Choose the applicable backup application for the results you would like to be ingested by this plan. The options in this menu will be dynamic depending on the backup vendor chosen. If you're unsure, you can double-check this value in the Application column on the Activate Backups page.
 
c. Backup Source (required): Choose your backup source (API or Email) for the results you would like to be ingested by this plan. The available options and potential default selection in this menu will be dynamic depending on the result type, backup vendor, and backup application chosen. If you're unsure, you can double-check this value in the Source column on the Activate Backups page.

d. Classification: For backups only: Select each available backup classification for the results you would like to be ingested by this plan. Note that BCDR applications which support automated replication and verifications (specifically Axcient, Datto BCDR, Slide, and StorageCraft) will have additional classification options. This classification will appear in the Category column on the Daily Activity page.

Screenshot 2025-12-03 at 4.14.35 PM.png Primary Backup:

This is a required selection; it will always display as grayed-out and selected.

Primary backup will be the only option if the source is email, or if the API integration is not a true BCDR backup application.

Screenshot 2025-12-03 at 4.13.01 PM.png Primary Boot Verification:

Screenshot verification of the primary backup. This field will only appear when API is the source and the selected application supports primary verification backup jobs.

You'll need to select this option here in order to include it as criteria while configuring your SLA later in Step 5: Service Level Agreement.

Screenshot 2025-12-03 at 4.13.01 PM.png Primary Verification:

Non-screenshot verification of the primary backup. These are usually file verifications. This field will only appear when API is the source and the selected application supports primary verification backup jobs.

You'll need to select this option here in order to include it as criteria while configuring your SLA later in Step 5: Service Level Agreement.

Screenshot 2025-12-03 at 4.13.01 PM.png Replication:

Redundancy backup of the primary backup.

This field will only appear when API is the source, and the selected application supports primary verification backup jobs.

e. Category: Optionally assign a category to each selected backup classification to choose your desired internal alias for each classification. This alias will appear in the Category column on the Daily Activity page.

Note: If you chose System Alerts as your result type, the Category field will be pre-selected as a System Alert.  

 

Step 3: Additional Filters

To skip additional filtering and ingest all backup jobs from your vendor, first use the Test button to test your logic*, verify your results, and then click Skip this step (or Next) to continue to Step 4: Schedule

*Doing this will test your Backup Plan filters and display all inactive and active backups that have company assignment and match your Backup Plan criteria.

Step 3. Additional Filters.png

 

To further refine the results ingested by this Backup Plan beyond the filters you've already selected, click Add Condition or Add Group and follow the steps below to begin configuring your criteria:

  1. Configure the following fields as desired and click Next when you're done:
    Step 3. Configure Additional Filters.png
    a. Add Condition: Click to create a new rule for your ingestion criteria.

    b. Add Group: Click to organize your conditions into groups. This is useful if you would like to apply a different boolean (the AND and OR conditions) to certain rules.

    c. Select any of the following options to begin determining which results will be pulled into this Backup Plan:
         Begin defining conditions.png
         1. Email Address: Filter based on the outgoing email address for the backup.
         2. Job Name: Filter by job name.
         3. Device Name: Filter by device name.
         4. Company: Filter based on the assigned device company.
         5. Client ID: Filter by Backup Client ID.
         6. Backup Metadata (Only available for certain* backup integrations): 
              • Backup Method: Drop-down of available backup methods.
              • Key: Keys determined from the API values.
              • Value(s): Values determined from the selected key.
         *We support Acronis, Axcient RMC, Datto BCDR, and MSP Backup (N-able Cove). If you have a backup method (or API keys for an existing backup metadata integration) we don't currently support, we want to hear from you! See Submitting Product Ideas to the ScalePad team for instructions on submitting your request to us.

    d. Copy button.png Copy: Use this button next to any given condition to duplicate it.

    e. Delete button.png Delete: Use this button next to any given condition to delete it.

    f. Reorder handle.png Reorder handle: Click and drag the reorder handle to rearrange conditions into different groups. This has no effect on the order in which conditions are applied.

    g. AND/OR: Choose AND if you require every listed condition to be true for a backup result to be pulled into this Backup Plan. Choose OR if you only require at least one condition to be true for a backup result to be pulled into this Backup Plan.

    h. Screenshot 2025-05-20 at 7.37.02 PM.png Test: Once you have finished building out your criteria, we recommend using the Test button to test your logic. Doing this will test your Backup Plan filters and display all inactive and active backups that have company assignment and match the Backup Plan criteria.

    Note: Backup Plans are applied in a priority order and by default, the most newly-created Backup Plans are the lowest priority. If you don't see a backup in your test results that matches your rules, it might already belong to a higher priority Backup Plan, so it can't be pulled into the new Backup Plan until it's saved and reprioritized.

    You can do this by customizing your priority order on the Backup Plans list view page using the Edit Priority button.
     

     

Step 4: Schedule

Note: If you chose System Alerts as your result type, this step will not apply.  

Configure the following fields and click Next:
Step 4. Schedule.png

a. Timezone (required): Set your desired time zone. This field will default to your local time zone.

b. Backup classifications tabs: These tabs will only appear if you selected Replication backups and a supported BCDR application during Step 2: Vendor & Classification. If you don't see any tabs, all settings on this screen will simply apply to your primary backup.

When these tabs do appear, you can toggle between them to configure your individual schedule settings for each backup classification. If you also assigned categories for your Primary and/or Replication classifications during Step 2: Vendor & Classification, your categories will appear as the top tab labels here (for example, Local Storage and Offsite Storage).

c. Date range (required): Set a start and optional end date for when SLA status data will be displayed on your Dashboards, Reports, and Daily Activity page (if you choose a date in the past, Backup Radar will pull data retroactively).

d. Schedule interval (required): Set your desired schedule (daily, weekly, monthly, or annually), associated day(s) of the week, and/or any unique cadence options as needed. This field will default to a daily schedule.

To reduce ticket noise, you'll want this schedule to match your actual backup frequency. For example, if your backups don't run on the weekend, there's no need for this rule to run on the weekend either.

e. Show advanced mode: In most cases, backups run on regular basis and you can simply set your backup's schedule to match in Backup Radar. However, some backups are scheduled more uniquely to occur on a specific cadence (for example, some backups may run on the third Friday of the month).

Use the Advanced mode feature to set your schedule to match your backup's unique schedule.

f. Expected run days: This is a view-only illustration of your current schedule pattern. Use the arrows to scroll forward and backward to ensure your configurations match your goals.

g. Recovery Point Objective (RPO): You can optionally set your RPO to match the outer limits of data loss that can be tolerated before causing harm to your business. Your RPO is essentially your maximum acceptable amount of lost data in the event of a system failure. The minimum RPO that can be assigned to a Backup Plan is 30 minutes.

If you want your RPO to be different depending on the day of the week, click the Switch to Days of Week button.png button to customize each day as needed.

You'll need to set up your RPO here in order to include it as criteria while configuring your SLA later in Step 5: Service Level Agreement.

Note: If you have a backup that typically starts and completes on different calendar days, the following applies to you:

Your SLA window cannot be stretched longer than one calendar day, and this can trigger false Screenshot 2025-06-09 at 2.51.02 PM.png Out of compliance results if your backup typically spans multiple days.

For example, a backup that starts at 4pm on Monday and typically takes 12 hours to complete would end at 4am on Tuesday. If you set SLA definition requirements based on a standard 12:00am to 12:00am SLA window, your backup would falsely display as Screenshot 2025-06-09 at 2.51.02 PM.png Out of compliance even though it eventually completed on Tuesday.

If you have a backup that typically starts and completes on different calendar days, we recommend that you choose only RPO and not SLA criteria when setting up your SLA definition requirements by doing the following:

1. When setting your schedule in Step 4:
   • Ensure that you define your RPO.
   • Skip defining your SLA window and leave it as the default time frame (12:00am to 12:00am).

2. When defining your SLA definition requirements in Step 5:
   • Select f. Recovery Point Objective is met.
   • Do not select c. [ ] successful results in a single calendar day or e. Last result is successful in a single calendar day.

 

 

Step 5: Service Level Agreement

Note: If you chose System Alerts as your result type, this step will not apply.  

Now that you've set your schedule and RPO, your next step is to define your SLA window and compliance requirements.

  1. Configure the following fields and click Next:
    Step 5. Service Level Agreement.png 
    a. Backup classifications tabs: These tabs will only appear if you selected Replication backups and a supported BCDR application during Step 2: Vendor & Classification. If you don't see any tabs, all settings on this screen will simply apply to your primary backup.

    When these tabs do appear, you can toggle between them to configure your individual SLA settings for each backup classification. If you also assigned categories for your Primary and/or Replication classifications during Step 2: Vendor & Classification, your categories will appear as the top tab labels here (for example, Local Storage and Offsite Storage).

    b. General settings: Select Treat warnings as successful results to require warnings to be treated as successful for the purpose of determining whether the SLA is in compliance.

    c. SLA window: By default, a Service Level Agreement (SLA) window is the full day (12:00am to 12:00am). To refine this further (e.g. if you only want tickets for backups that fail compliance during business hours), set your SLA window to match the time frame during which you want tickets to be generated for non-compliance of SLA (you'll set your SLA compliance requirements later).

    Note: Your SLA window cannot span more than one calendar day.  

    If your SLA falls out of compliance during your SLA window, a ticket will be generated.

    If your SLA falls out of compliance outside of your SLA window, a ticket will not be created, but the event will still be logged in your Dashboard, Reports, and Daily Activity screens.

    d. [ ] successful results in a single calendar day: Use this option to define SLA compliance as a particular number/ percentage (at least 1) of successful results in a single calendar day. When selected, this field will default to 1 successful result.

    e. %#.png: Toggle between percentage or whole number as your number format.

    f. Last result is successful in a single calendar day: Select this option to require a successful last result.

    g. Recovery Point Objective is met: Note: This option will only appear (and be auto-selected) if an RPO was configured during Step 4: Schedule (clicking this checkbox will display a read-only view of your selected RPO). Leave this option selected to define your backup results as out of compliance if any RPO fails within any given SLA window for that day.

    h. A successful verification in the last [ ] day: This option will only appear if you selected a supported BCDR application and Primary Verification during Step 2: Vendor & Classification.

    Select this option to require a successful primary verification (non-screenshot verification; usually a file verification) within your chosen number threshold (at least one day).

    i. A successful boot verification in the last [ ] day: This option will only appear if Primary Boot Verification was selected in Step 2: Vendor & Classification

    Select this option to require a successful primary boot (screenshot) verification within your chosen threshold (at least one day).

    j. SLA Compliance Ticket Creation: Select this checkbox if you want Backup Radar to create a ticket if your SLA is out of compliance (you'll define your ticket profile later).

    k. Show advanced settings: If you want early notification of your SLA being at risk of breaching your compliance requirements, click Show advanced settings.png and set up your SLA at-risk criteria as desired using the options below.

Step 5. SLA at-risk criteria.png

1. To capture data when insufficient successful results have been received by the time a certain portion of your SLA window has elapsed, select this option and set your percentage or number threshold (at least 1).

2. %#.png: Toggle between percentage or whole number as your number formats.

3. To capture data when a certain number of results report a certain result, select this option and set your threshold (at least 1) and result. You can select the In a row option if you've chosen more than one result for your threshold.

4. This option will only appear if you set an RPO in Step 4: Schedule

To capture data when RPO is not met within a certain percentage of RPO time, select this option and set your percentage.

5. SLA At-Risk Ticket Creation: Select this checkbox if you want Backup Radar to create a ticket if your SLA is at risk of non-compliance based on your selected criteria.
 

Step 6: Ticket rules

Note: This step will only appear for backups where you enabled SLA Compliance Ticket Creation or SLA At-Risk Ticket Creation in Step 5: Service Level Agreement, or if you selected System Alerts in Step 1: General Info. Otherwise, feel free to skip to the Review step.

For backups:

Configure the following and click Next when you're done:
Step 6. Ticket rules.png

a. Ticket creation summary: Review a summary of your SLA compliance criteria and make sure everything looks right. If you need to make any changes, just hop back to Step 5: Service Level Agreement.
b. Ticket profile: Select the ticket profile that you would like Backup Plan to use for all tickets generated by this Backup Plan. For a step-by-step guide to creating a new ticket profile, check out Setting up Ticket Profiles.

For system alerts:

  1. Toggle the System Alert Ticket Creation option on if you'd like Backup Radar to create ticket when a system alert fails or meets other conditions. Otherwise, click Next and skip to the Review step.
    Step 4. Ticket rules (System Alerts).png
     
  2. Configure your ticket rules and click Next when you're done:
    Step 4. Ticket rules (System Alerts-2).png
    a. Select this option if you'd like Backup Radar to create ticket when the last result exceeds your specified period of time.
    b. Ticket profile: Select the ticket profile that you would like Backup Plan to use for all tickets generated by this Backup Plan. For a step-by-step guide to creating a new ticket profile, check out Setting up Ticket Profiles.
     

Step 7: Review

You're almost done! Review your changes and click Finish when you're done.

Step 7. Review.png
a. Edit: Click the Edit button.png button next to any of the sections to jump back to that step and make changes.
b. Enable backup plan: Select this option to activate this Backup Plan immediately upon finalization. Otherwise, you can enable it manually from the Backup Plans page later.

 

Note: After a Backup Plan is activated, it will begin ingesting data from any activated device, whether or not the backup was activated through a Backup Plan, a template, or manually (via standalone backup) through the Activate Backups page.

Note: This may take several minutes for new Backup Plans.

If you have both a Backup Plan and a template with criteria that would match the same backup result active in your account at the same time, the Backup Plan will take priority and ingest the data.

 

Note: When a Backup Plan ingests new device data, the system will detect and automatically assign one of the following two device types:
• Mailbox (devices that are identified to potentially be a mailbox).
• Server (devices that are NOT identified to potentially be a mailbox).

You can manually re-define any result as a Workstation (or re-define any incorrectly-assigned device type) by visiting the Edit Backups page, selecting your desired backup(s), and clicking Bulk Edit > Configuration > Device Type.

Device types affect your pricing (see Monitoring your licenses for more details), so be sure to adjust your usage as needed so your billing is accurate. Backup results that have already been assigned to a device type prior to the launch of Backup Plans will not have their device type changed when ingested by a Backup Plan.

 

What's next?

Next up, you might want to check out About the Backup Plans list view page for details on how to do things like edit, manually activate or deactivate, set prioritization order for, and delete your Backup Plans. 

 
Any feedback? Join the conversation in the Backup Plans community group.
✉️ Any questions? Reach out to our friendly, neighborhood support team by submitting a support ticket.
🎙️ Interested in attending a live Q&A session with our Product Adoption team? Sign up to attend Backup Radar Office Hours and get real-time answers to your questions.
📣 Feedback on this article? Let us know in the comments below!

Related to

Was this article helpful?

11 out of 11 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.