Bacchus Security

Maintenance and managed IT

Between projects, who checks a backup, investigates a recurring warning or schedules the next restart? Ongoing support gives these tasks an owner, a timetable and a record.

Design example

Recover a working file when someone deletes the original.

A restore test includes opening the recovered file in the application that uses it. The result determines what maintenance work comes next.

Restore test
  • File opensRecord the recovery procedure
  • File incompleteFix the issue and test again

When to get in touch

  • Updates keep slipping because no maintenance window has been agreed.
  • Several people investigate the same recurring issue from scratch.
  • Configuration records fall behind changes made in production.

Scope of work

  • An agreed inventory of covered equipment and services, with clear ownership.
  • A maintenance schedule and checks tailored to those services.
  • Records of interventions, outstanding issues and decisions that need your input.

Our approach to the work

We start with the tasks you already handle and the times when an interruption is workable. Together we draw up a maintenance schedule, agree who owns each check and set out what happens if an incident falls outside the agreed scope. Support hours are specified in the agreement.

Plan a recovery exercise for network services

What you gain

You know where to send a request and how to follow its progress, including when another supplier needs to act.

Discuss maintenance needs