All projectsCase study

Automated Plesk Backup Control

Daily backup presence and freshness control with automatic OK / KO notification.

PowerShellPleskMonitoringWindows
BACKUP PLESK
01

Context

Plesk backups needed to be checked every morning without relying on manual verification.

02

Problem

A backup task can exist while the expected file is missing or stale. Without independent control, the issue may remain invisible until a restore is needed.

03

Solution

A PowerShell automation checks the minimum backup count and verifies that a current-day file exists. The check runs automatically at 05:00 and systematically sends an OK or KO status.

04

Key lesson

A backup is truly reassuring only when its presence and freshness are also monitored.

MISSION Automated Plesk Backup Control
MY ROLE Operations automation
DURATION Daily control
ENVIRONMENT PowerShell · Windows · Plesk
STATUS Automated
01 · BEFORE

Starting point

Backup presence and freshness had to be checked manually.

→
02 · AFTER

What changes

An autonomous check analyzes backups and produces a daily OK / KO status.

PROJECT FLOW LIVE
01 Plesk Backup
02 Fichiers Détection
03 PowerShell Contrôle
04 05:00 Planification
05 OK / KO Alerte
Under the hood

How the project actually works

Architecture, constraints, deliverables and real impact.

04

Main challenge

Do not confuse “backup configured” with “backup actually available today”.

01 Plesk backups
02 PowerShell
03 Presence / date checks
04 Task Scheduler
05 Notification
05

Deliverables

  • Control script
  • Scheduled task
  • OK / KO status
  • Daily notification
06

Impact

A missing or stale backup becomes visible before a restore is actually required.

Designed for real-world use
07

What this project demonstrates

I start from the problem and business flow, then aim for an observable, testable and maintainable solution rather than a demo effect.

← PreviousReal-Time Conversational AI Avatar