Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Backups

SFTP backup automation: transfer backups without hard-coding a password

Published August 2026 · 2 min read · Updated 2026-09-05

SFTP backup automation is a secure file-transfer building block, not a complete backup product by itself. A reliable job needs dedicated credentials, non-interactive host-key verification, atomic or clearly named uploads, success/failure monitoring, retention, and periodic restores.

Use a dedicated restricted account/key

Create a credential used only for the backup destination and protect the private key or password outside source control. Restrict the destination account to the required storage path and capabilities where the server supports it.

Do not reuse an administrator SSH key for unattended backups.

Pin server identity non-interactively

Automation should verify the expected SSH host key and keep StrictHostKeyChecking enabled. Record how a legitimate key rotation is approved and deployed.

A DNS hostname is convenient, but host-key verification is what prevents silently sending backups to an impostor after DNS/network compromise.

Make uploads and retention observable

Use timestamped/snapshot-aware paths and avoid treating a partially uploaded file as a valid recovery point. Capture exit status, bytes transferred, duration, and newest successful backup age.

Implement retention on the side that can safely enumerate complete backups; test pruning so it cannot delete all recovery points.

Restore through the same credentials/process

Regularly download a real backup to an isolated destination, verify integrity/decryption, and rebuild the application data needed. Alert if the job has not produced a fresh backup within the expected window.

  • Use dedicated backup credentials.
  • Pin host keys.
  • Detect partial/failed uploads.
  • Test download and restore.

Next step

Automate SFTP backup transfers with scoped keys, host-key verification, retention, logging and failure alerts, then test that the remote copy can restore.

Explore DotMoose backup storage

Keep reading

Related guides.

Backup capacity planning: estimate storage from change rate and retention

Model source size, daily change, compression, deduplication, retention and growth so backup storage is sized from the workload instead of one full-copy estimate.

Read the guide

Backup encryption basics: protect copies at rest and in transit

Choose where backup data is encrypted, how keys are stored and recovered, and how restore operators gain access without putting the only key beside the backup.

Read the guide

Backup recovery drills: prove the restore process before an outage

Run isolated recovery tests, measure restore time, verify application state and record missing dependencies so the backup plan is based on tested recovery.

Read the guide

More backups guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move