{"id":5314,"date":"2020-07-07T21:13:48","date_gmt":"2020-07-07T20:13:48","guid":{"rendered":"https:\/\/www.n-able.com\/?p=5314"},"modified":"2021-07-13T13:18:10","modified_gmt":"2021-07-13T12:18:10","slug":"backup-monitoring-part-4-tracking-and-controlling-usage","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/it\/blog\/backup-monitoring-part-4-tracking-and-controlling-usage","title":{"rendered":"Backup Monitoring, Part 4\u2014Tracking and Controlling Usage"},"content":{"rendered":"

One of the most common reasons to monitor devices is to track and control usage. Below I use monitoring and adjustments to backup selection as two methods to potentially control costs, reduce processing times, and shrink backup windows\u2014all while still maintaining data protection for compliance and disaster recovery purposes.<\/p>\n

Tracking fair use policies<\/h3>\n

The SolarWinds\u00ae<\/sup>\u00a0Backup\u00a0Fair Use Policy<\/a>\u00a0outlines the typical fair use limits for an account. The fair use limits for your account could differ, so please consult with your account team if you need clarification. Regardless, let\u2019s assume you want advanced notice that a device is close to or has exceeded a selected size fair use policy. To see this in the\u00a0Backup Management console<\/a>\u00a0you can create new\u00a0dashboard views<\/a>\u00a0using variations of the\u00a0advanced search filters expressions<\/a>\u00a0found below. You can also set up periodic email alerts by setting up daily or weekly\u00a0scheduled email<\/a>\u00a0views to be delivered only when devices meet or exceed the defined criteria.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Expression<\/b><\/td>\n<\/td>\nDescription<\/b><\/td>\n<\/tr>\n
T3 > 500.gibi() AND OT == 2<\/td>\n<\/td>\nTotal selected size greater than 500 GB AND OS type equals server (i.e., servers over fair use policy)<\/td>\n<\/tr>\n
T3 <= 500.gibi() AND OT == 2<\/td>\n<\/td>\nTotal selected size less or equal to 500 GB AND OS type equals server (i.e., servers under fair use policy)<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
T3 > 100.gibi() AND OT == 1 AND OP != “Documents”<\/td>\n<\/td>\nSelected size is greater than 100 GB with a workstation OS and a non-documents profile (i.e. workstations over fair use policy)<\/td>\n<\/tr>\n
T3 <= 100.gibi() AND OT == 1 AND OP != “Documents”<\/td>\n<\/td>\nSelected size is less than 100 GB with a workstation OS and a non-documents profile (i.e. workstations over fair use policy)<\/td>\n<\/tr>\n
<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
(T3 > 500.gibi() AND OT == 2) OR (T3 > 100.gibi() AND OT == 1 AND OP != “Documents”)<\/td>\n<\/td>\nCombined servers or workstations under fair use policy<\/td>\n<\/tr>\n
(T3 <= 100.gibi() AND OT == 1 AND OP != “Documents”) OR (T3 <= 500.gibi() AND OT == 2)<\/td>\n<\/td>\nCombined servers or workstations under fair use policy<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Preventing double selection<\/h3>\n

Another way to help control data size is to deselect, filter, or exclude data to ensure you don\u2019t protect the same data using multiple data sources. For example, a 300 GB\u00a0Hyper-V virtual machine<\/a>\u00a0or MS SQL databases that was also backed up as part of the File System could significantly impact your total selected size, your monthly cost, and the overall duration of your backup window.<\/p>\n

Before applying any\u00a0backup filters<\/a>, it\u2019s very important you review any planned exclusions that will be applied to the files and folders data source. Before adding exclusions, make sure the backups using the application-specific data source are already configured and successfully protecting the data. If they aren\u2019t, it could result in the inability to perform data recovery later.<\/p>\n

 <\/p>\n\n\n\n\n\n\n
Application Data<\/b><\/td>\n<\/td>\nFile Extensions<\/b><\/td>\n<\/td>\nSample Exclusion Path<\/b><\/td>\n<\/td>\nSample Exclusion Path<\/b><\/td>\n<\/tr>\n
Microsoft HyperV<\/td>\n<\/td>\n.vhd<\/p>\n

.avhd<\/p>\n

.vhdx<\/p>\n

.avhdx<\/p>\n

.bin<\/p>\n

.vsv<\/p>\n

.xml<\/p>\n

.vmrs<\/p>\n

.vmcx<\/td>\n

<\/td>\n*\\Virtual Hard Disks\\*\\*.vhd<\/p>\n

*\\Virtual Hard Disks\\*\\*.avhd<\/p>\n

*\\Virtual Hard Disks\\*\\*.vhdx<\/p>\n

*\\Virtual Hard Disks\\*\\*.avhdx<\/p>\n

*\\Virtual Hard Disks\\*.vhd<\/p>\n

*\\Virtual Hard Disks\\*.avhd<\/p>\n

*\\Virtual Hard Disks\\*.vhdx<\/p>\n

*\\Virtual Hard Disks\\*.avhdx<\/p>\n

*\\Snapshots\\*\\*.bin<\/p>\n

*\\Snapshots\\*\\*.vsv<\/p>\n

*\\Snapshots\\*.xml<\/p>\n

*\\Snapshots\\*.vmrs<\/p>\n

*\\Snapshots\\*.vmcx<\/p>\n

*\\Resource Types\\*.vmcx<\/td>\n

<\/td>\n*\\Virtual Machines\\*\\*.vhd<\/p>\n

*\\Virtual Machines\\*\\*.avhd<\/p>\n

*\\Virtual Machines\\*\\*.vhdx<\/p>\n

*\\Virtual Machines\\*\\*.avhdx<\/p>\n

*\\Virtual Machines\\*.vhd<\/p>\n

*\\Virtual Machines\\*.avhd<\/p>\n

*\\Virtual Machines\\*.vhdx<\/p>\n

*\\Virtual Machines\\*.avhdx<\/p>\n

*\\Virtual Machines\\*\\*.bin<\/p>\n

*\\Virtual Machines\\*\\*.vsv<\/p>\n

*\\Virtual Machines\\*.xml<\/p>\n

*\\Virtual Machines\\*.vmrs<\/p>\n

*\\Virtual Machines\\*.vmcx<\/p>\n

*\\Resource Types\\*.xml<\/td>\n<\/tr>\n

Microsoft SQL<\/td>\n<\/td>\n.mdf<\/p>\n

.ndf<\/p>\n

.ldf<\/td>\n

<\/td>\n*\\MSSQL\\DATA\\*.mdf<\/p>\n

*\\MSSQL\\DATA\\*.ndf<\/p>\n

*\\MSSQL\\DATA\\*.ldf<\/td>\n

<\/td>\n*\\MSSQL\\LOG\\*.ldf<\/p>\n

 <\/td>\n<\/tr>\n

Microsoft Exchange<\/td>\n<\/td>\n.edb<\/p>\n

.log<\/td>\n

<\/td>\n*\\Mailbox Database*\\*.edb<\/p>\n

*\\Mailbox Database*\\*.log<\/td>\n

<\/td>\n*\\Mailbox*\\*.edb<\/p>\n

*\\Mailbox*\\*.log<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

I\u2019ve provided some examples of common application data file paths above you could use as a base for building out your customer specific exclusion filters. However, before you apply these\u00a0backup filters<\/a>\u00a0to a device locally, via\u00a0command line<\/a>,\u00a0remote command<\/a>, a\u00a0backup profile<\/a>, or\u00a0RMM backup policy<\/a>, please compare these against your individual backup devices and adjust the file paths as needed.<\/p>\n

You can locate a processed file list either in the local Backup Manager or in the Management Console and use it to reference the file paths for currently protected files.<\/p>\n

 <\/p>\n

\"\"\u200b<\/span><\/p>\n

Figure 1 – Viewing Processed files to help identify possibly exclusion paths<\/em><\/p>\n

This is just the tip of the iceberg when it comes to fine tuning your backup selection and exclusion settings. Check back for our next installment where we cover setting exclusions for drives, volumes, and shares.<\/p>\n

Eric Harless is the Head Backup Nerd at SolarWinds MSP. Eric has worked with SolarWinds Backup since 2013 and has over 25+ years of data protection industry experience in sales, support, marketing, systems engineering, and product management.<\/em><\/p>\n

You can follow Eric on Twitter\u00a0at\u00a0@backup_nerd<\/a>.<\/em><\/p>\n

 <\/p>\n

Other blogs in this series<\/strong><\/p>\n