How to Run a Quarterly Backup Audit Using Only Built-In Windows Tools. Backup management is a core MSP responsibility, but not every organization can afford dedicated auditing tools. The good news? You don't need them. In this video, we'll show you how to run quarterly backup audits using only native utilities and basic scripts. We'll cover how to verify that your backups are working, meeting retention policy requirements, and can actually be restored when needed. Before we begin, be sure to subscribe to NinjaOne’s IT video hub and our YouTube channel for more tech content like this. Step 1: Create a Quarterly Backup Audit Checklist. Begin by building a quarterly backup audit checklist that addresses each key validation area: Review the last 90 days of backup logs and flag any failed or missed jobs. Confirm that backup retention periods match your policy, such as 30, 90, or 365 days. Off-site & Immutable Copies: Verify your backups follow the 3-2-1 rule: three copies of your data, stored on two different media types, with one off-site or immutable copy. Perform at least one restore to confirm backups are actually usable. Document any issues or deviations from your backup policies. Step 2: Use Built-in Tools to Extract Backup Status. To save time collecting backup logs, use built-in PowerShell commands or command-line tools to automate the process. Here is an example script... This script pulls Windows backup events from the local machine and exports them to a CSV file for easy review and centralized auditing. Important: This script must be run on every endpoint that uses Windows Server Backup. Step 3: Perform a Manual Restore Validation. Running backup jobs isn't enough, you also need to confirm they’re actually restorable. Each quarter run a quick restore test: Restore a file or folder to a sandbox VM or isolated environment. Record the restore time and verify the file’s integrity. Document any errors encountered, and attach screenshots to your quarterly audit summary. Step 4: Validate Retention and Off-site Compliance. Use scripts or manual checks to verify compliance with your data retention policy: For example... This PowerShell command scans the backup directory and flags files that haven't been modified in the last 90 days — helping you determine what can be archived or removed based on your retention policy. For off-site and disaster recovery readiness, confirm that one or more of the following is in place: Cloud backups (e.g., Azure, AWS) Off-site NAS or external drives Immutable storage Track which systems meet the 3-2-1 backup strategy on a dashboard and note any gaps. You don't need paid tools to run effective backup audits. With a simple auditing framework and native tools like PowerShell, you can strengthen your MSP’s data protection strategy, validate backup recoverability, and build client trust. For more steps, check out our official blog post on backup audits linked in the description below.