infraanchor
InfraAnchor guides

Practical guides
for everyday IT.

Straightforward checklists to help you review the systems your business relies on and choose a sensible next step.

Browse the checklists ↓
IA
INFRAANCHOR GUIDEBackup & recovery
START HERE
A useful review asks:
01What needs protecting?✓
02Can you restore it?✓
03Who owns the next step?✓
↻Review the plan. Test the process.
Three useful starting points

Review the things
that matter most.

Use these checklists to structure an internal review. Your exact requirements will depend on your environment and business.

01BACKUP & RECOVERY

Could you restore what the business needs?

A backup job that reports success is only part of the picture. Review coverage, ownership and restore readiness together.

  • List the important data, systems and services that need protection.
  • Confirm backup coverage, retention and who checks for failures.
  • Check where copies are kept and who can access or change them.
  • Run a restore test and record the steps, result and time required.
  • Write down recovery priorities and who coordinates the response.
Good next stepChoose one important system and schedule a test restore.
02MICROSOFT 365 & IDENTITY

Are accounts and access still appropriate?

Small changes in roles and people can leave access untidy. A regular review helps keep permissions aligned with how the team works.

  • Confirm multi-factor authentication is enabled for users and administrators.
  • Review administrator roles and remove access that is no longer needed.
  • Check that leavers and dormant accounts are disabled appropriately.
  • Review guest users, external sharing and mailbox forwarding rules.
  • Make sure the process for urgent or emergency access is documented.
Good next stepReview administrator accounts and confirm each one has a current owner.
03SERVERS & NETWORK

Do you know what your core systems depend on?

A current, lightweight inventory makes support, maintenance and future changes easier to plan.

  • Record server, network and cloud services, their purpose and owner.
  • Note operating system versions, support dates and maintenance windows.
  • Map key dependencies, such as identity, DNS, storage and connectivity.
  • Check patching, capacity alerts, remote access and backup status.
  • Capture known risks, documentation gaps and a review date.
Good next stepStart with a simple list of systems and the business services they support.

These checklists are general prompts, not a security audit or a substitute for advice tailored to your systems and obligations.

Want a second pair of eyes?

Let’s talk through
your IT priorities.

Bring your questions or a checklist you’d like help working through.

Talk to InfraAnchor ↗
IA