{"id":5368,"date":"2020-07-21T21:44:52","date_gmt":"2020-07-21T20:44:52","guid":{"rendered":"https:\/\/www.n-able.com\/?p=5368"},"modified":"2021-07-13T13:20:10","modified_gmt":"2021-07-13T12:20:10","slug":"backup-monitoring-part-5-tuning-your-backup-selections","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/pt-br\/blog\/backup-monitoring-part-5-tuning-your-backup-selections","title":{"rendered":"Backup Monitoring: Part 5\u2014Tuning Your Backup Selections"},"content":{"rendered":"
\n

In\u00a0part four, I discussed monitoring usage and adjusting backup selections as methods of potentially controlling costs, while still providing reliable data protection. I\u2019ll continue that discussion in this installment by helping you locate duplicate data.<\/p>\n

Excluding DFS replication and data deduplication from System State backup<\/h3>\n

Windows Server OS based devices with DFS Replication or Windows Data Deduplication are configured to automatically backup those components. These selections could significantly increase the selected size of your System State backup. If you want to protect these components the increased size may be fine. But their selection could also be redundant if the data is already selected as part of the Files and Folders backup on this or another protected backup device. To quickly identify backup devices with DFS or Dedupe selections, you can manually look for devices with a System state selected size greater than about 70 GB or use the following\u00a0advanced search filter<\/a>.<\/p>\n\n\n\n\n
\u00a0Expression<\/b><\/td>\n\u00a0Description<\/b><\/td>\n<\/tr>\n
\u00a0S3 > 70.gibi()<\/td>\n\u00a0(System state selected size Greater than 70 Gigabytes)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

You can deselect DFS and Dedupe by editing the System state selections on the Backup tab of the local Backup Manager. Backup devices that have System state set via a profile will need to have that profile removed or adjusted to Keep local settings before local System state exclusions can be made.<\/p>\n

Filtering network paths<\/h3>\n

On Mac and Linux devices mounted SMB\/Samba shares can show up as part of the local file system.\u00a0 When connected, these shares can significantly increase your total backup selected size. To prevent these network mounts from being included in backup you can either deselect the respective shares or set exclusion filters. Please consult the documentation for your specific MacOS or Linux distribution for alternate or additional mount paths.<\/p>\n\n\n\n\n\n
\u00a0Operating System<\/strong><\/td>\n\u00a0Sample Exclusion Path<\/strong><\/td>\n<\/tr>\n
\u00a0MacOS<\/td>\n\u00a0\/Volumes\/*<\/td>\n<\/tr>\n
\u00a0Linux<\/td>\n\u00a0\/mnt\/*<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Ignoring LocalSpeedVaults and seed drives<\/h3>\n

By default, the local Backup Manager is smart enough to identify a configured seed drive or LocalSpeedVault, whether it\u2019s directly attached or connected via a network share. However, when you make configuration changes, move, or reattach this seed drive or LocalSpeedVault to another system with an active Backup Manager, you run the possibility of that device accidentally seeing the volume or share as data to protect. You can set a local, profile, or policy-based exclusion filter to prevent a seed drive or LocalSpeedVault from ever backing up by accident.<\/p>\n\n\n\n\n
\u00a0Data Type<\/strong><\/td>\n\u00a0Sample Exclusion Path<\/strong><\/td>\n<\/tr>\n
\u00a0LocalSpeedVault\u00a0 & Seed Drives<\/td>\n\u00a0*\\storage\\cabs\\gen*\\*<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Excluding USB drives<\/h3>\n<\/div>\n
\n
\n
\n
\n

Windows systems consider USB hard drives fixed disks, which means they\u2019re automatically included when you select the entire file system for backup. If you know the drive letters that will be assigned, then you can adjust your selections to only backup specific volumes, or you can set exclusions to restrict specific drive letters. However, since USB drives are pluggable, you may not know the drive letter. If that\u2019s the case, you\u2019ll need another approach to dynamically identify and exclude them from your backups. With this goal in mind, I\u2019ve designed a sample PowerShell script you can use to inventory a system and set exclusions or registry keys to help prevent the drive from being backed up. If you\u2019re interested in exploring this, please feel free to contact me\u00a0via social media<\/a>.<\/p>\n

Preventing backups of backups<\/h3>\n

You might think having multiple backup applications on the same system doubles your level of protection. But in many cases, it actually costs you more time, money, and bandwidth\u2014and it can actually reduce the chances of a successful backup. This is due to factors such as overlapping schedules, conflict VSS snapshots, improper log handling, and double processing of backup files. Typically, if you have one backup solution working, I recommend you disable the second. At the very least, set schedules to help prevent overlap and exclude the other solution from processing and backing up the backup destination files. You should investigate your backup devices, looking for legacy backup applications, dump disks, tar files, native Windows, SQL .BAK and .BKF files, and disk backup images created by competing commercial backup products and disk imaging solutions.<\/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<\/div>\n

 <\/p>\n

Other blogs in this series<\/b><\/span><\/p>\n