Almost every organization we meet has backup software. Far fewer can answer, with evidence, whether the systems the business depends on are protected — and whether a restore would work when it matters.
1. Which workloads are actually protected?
Start with a list of the systems you could not operate without: file servers, line-of-business databases, Microsoft 365 mailboxes and SharePoint sites, workstations with local data. Then check each against the backup platform. Systems that are absent from the expected backup platform are the most common gap we find.
2. When was the last successful restore point?
Stale jobs are easy to miss. A job that has quietly failed for weeks looks the same as a healthy one on a dashboard nobody opens. We review restore points and active alarms, not just whether the software is installed.
3. How long is data retained?
Deletion and corruption are often discovered long after they happen. Insufficient retention means the clean copy you need may already have aged out.
4. Is Microsoft 365 included?
Mail, OneDrive and SharePoint are frequently assumed to be “backed up by Microsoft.” Microsoft 365 backup is a separately defined service; make sure yours is explicitly included if that data matters to you.
5. Who gets the alarm, and what happens next?
A failed backup should produce an escalation and a remediation record — not an email that goes to a mailbox nobody reads.
6. Do you know exactly what your plan covers?
You should. We walk every client through exactly what their backup service covers, and we’re always happy to answer questions. As your organization grows, we make sure your protection grows with it.
If you cannot answer these six questions with evidence, a technology assessment will — across identity, endpoints, security and backup.