Planning Workstation and Server Backup Coverage

Start by mapping where data actually lives

Before configuring or reviewing backup, walk through where business-critical data is actually stored. It is common to find files saved locally on a workstation that were assumed to be on the server, or a department using a folder structure nobody documented. This mapping exercise, done honestly, is the single most valuable step in backup planning because it exposes what the current backup configuration is actually missing.

Server backup priorities

• File servers holding shared documents used across the business
• Line-of-business application servers and their databases
• Domain controllers, since Active Directory failure affects every user's ability to log in
• Any Hyper-V host running the virtual machines above, backed up at the host level as covered in Hyper-V backup best practices

Workstation backup priorities

Workstation backup is often treated as an afterthought compared to servers, but it matters more than it gets credit for. Staff regularly save work locally, whether out of habit or because a file was being worked on offline, and that data does not exist anywhere else if the workstation fails or is hit by ransomware.

• Confirm whether staff actually save to the server or to Microsoft 365, or whether local saving is common in practice
• Back up user profiles and local data folders on every workstation, not just servers
• Pay particular attention to remote and hybrid staff devices, which are easy to miss in an office-centric backup plan

Microsoft 365 is its own coverage category

Mailboxes, OneDrive, SharePoint, and Teams data live outside the server and workstation environment entirely, and Microsoft's native retention tools are not a substitute for an independent backup. If a coverage review only looks at servers and workstations, Microsoft 365 gets missed by default, not by decision. This is covered further in what Acronis Cyber Protect Cloud actually does for a small business.

A simple coverage worksheet

Applying the 3-2-1-1-0 standard once coverage is mapped

Once the coverage map is complete, apply a consistent backup standard across everything on it rather than a different ad-hoc approach for each system. The 3-2-1-1-0 backup rule gives a practical structure: three copies, two media types, one off-site, one immutable, and zero errors on a tested restore, applied to every location identified in the coverage worksheet above.

Reviewing coverage annually

Backup coverage should be reviewed at least once a year, and after any significant change such as a new server, a new line-of-business application, or a shift to more remote work. New systems get added to a business regularly, and each one is a potential gap if backup planning does not keep pace.

Frequently asked questions