SLApp Helpdesk
Backups

Backups run by the agent you already have

Choose the folders and SQL Server databases to protect and where the copies should go — a folder, a network share, an FTP or FTPS server — and the agent on that machine does the rest on a schedule. Every run is recorded, every failure raises an alert, and a destination that is running out of room is flagged before a backup fails.

Backups
Client: Contoso, Lda.Tab: RunsStatus: Any
JobComputerStartedDurationStatusSizeError
Server filesCTS-SRV0102:00 AM31 minCompleted18.4 GB—
ERP databaseCTS-SQL0102:30 AM12 minCompleted with warnings6.2 GBERP → FTP offsite: could not connect
DocumentsCTS-PC0201:00 AM1 minFailed—NAS Porto: needs 42.0 GB, only 9.1 GB free
Server filesCTS-SRV0103:00 AM—Running——

What's included

  • Nothing new to install — backups run inside the agent already on the Windows server or PC. Choose the computer, add the sources and destinations, set the schedule, and it runs.
  • Several sources and several destinations per job: folders and the databases of the SQL Server on that machine, copied in the same run to local folders, network shares and FTP or FTPS servers.
  • Schedules in the machine's own local time — daily, weekly, monthly or at a fixed interval — with an optional catch-up run if the computer was off at the scheduled time, and a Run now button for the rest.
  • The free space of every destination is checked before copying. A copy that will not fit fails straight away with a clear reason instead of dying half-way, and a destination below the minimum you set (in GB or in %) raises a warning.
  • Alerts by e-mail when a backup fails, when it does not run on time, and when a destination is filling up. A destination that keeps failing while another one works is flagged too, so a missing offsite copy never goes unnoticed.
  • Retention is built in: keep the last N copies and/or the last N days. It only ever removes files the module created, never the newest copy of a series and never anything else in the folder.
  • Copies are checked once they land — the size at the destination, and RESTORE VERIFYONLY for SQL Server backups — and every run keeps a record per source and per destination, with sizes, durations and errors you can copy.
  • Plain .zip files and standard SQL Server .bak files, so you restore with the tools you already use — no lock-in, no proprietary format.
  • Credentials are handled with care: FTP, share and SQL passwords are stored encrypted, are never shown again, and the whole module is for administrators only.

Backups

Folders and SQL Server databases, to a NAS, a share or an FTP site — scheduled, verified and alerted.

Request a demo