corePHP
269-979-5582 Free Coffee Talk
Our Services

Monitoring & Backup Services

A backup you have never restored is a rumour. We test ours.

Monitoring
Uptime, integrity, change
Backups
Off-site, held apart from the server
Restores
Drilled on a schedule
Alerting
Tuned, so it means something
Why people add monitoring

Outages a customer reported first, and backups that have never once been restored.

Two things reliably start this conversation. Somebody outside the business noticed the site was down before anyone inside did, or a restore was needed and the backup turned out to be older, smaller or more broken than anyone assumed.

A customer told us the site was down

Checks from outside your network, at an interval that catches a real outage, going to a person rather than to an inbox nobody reads.

We have backups and have never restored one

An untested backup is a hope. We run restore drills on a schedule and time them, so the recovery window is a measured number instead of an assumption.

Files changed and nobody noticed

File integrity and change monitoring, which is usually how a compromise is caught before it becomes an incident.

Our alerts cry wolf

Alerting tuned so it means something when it fires. An alert everyone has learned to ignore is worse than no alert at all.

We will restore your latest backup and time it.

That single test tells you more about your recovery position than any policy document. Free, and you get the result whether or not it is good news.

What is included

What monitoring and backup covers.

99.9%  ·  28 days
Uptime monitoring

Checks from several locations so a regional network fault is not mistaken for your site being down. You hear it from us, not from a customer.

Live
Integrity and change monitoring

Watching for file changes, defacement and injected content, which is usually the first sign of a compromise and is easy to miss by eye.

  nightly   ok
  off-site  ok
  restore  tested
  retention 90d
Off-site backups

Backups held somewhere other than the server they came from. A backup on the same machine is not a backup, it is a copy.

restore drill
  snapshot 03:00
  back in 6m 12s
  checksums match
Restore drills

We restore from backup on a schedule and confirm it worked. A backup nobody has restored is a rumour, and the day you need it is the wrong day to find out.

Open
Alerting that means something

Thresholds tuned so an alert is worth waking up for. Alerting that cries wolf gets muted, and a muted alert protects nothing.

Aug
CLICKS
2,140
LEADS
61
Retention and reporting

How far back you can go, and a record of what was captured and what was tested, so the answer is not a guess.

The work

Sites we watch today.

15,000+Sites built since 2000800+Sites under our care today25+Years, same two founders
Questions

Straight answers.

How often do you back up?

Nightly at minimum, verified daily at 4 A.M. EST, with more frequent points for transactional sites.

Where are backups stored?

Off the server, in separate infrastructure. A backup on the same box is not a backup.

Do you test restores?

Yes, on a schedule. An untested backup is a rumour.

What do you monitor?

Uptime, certificate expiry, malware signatures, error rates and performance regressions.

Ready to talk about it?

Tell us what you are building. You will speak to the engineer who would do the work.

A real number in two business days, from an engineer. No sales deck, and no call just to book another call.