AiXVPScost & terms for AI / automation

Contabo Decision guide Updated 2026-11-12

Contabo Object Storage vs Auto Backup for WordPress and n8n

Object Storage and Auto Backup are not substitutes. Object Storage is S3-compatible file storage for copies you place there yourself. Auto Backup is a daily off-server backup of the VPS with 10 days of retention. Snapshots are a third layer: a disk image with 30 days of retention. A WordPress or n8n box needs a plan for all three, not a choice between two product names. The short answer: use snapshots for short-term rollback, Auto Backup for daily VM recovery, and Object Storage for file-level copies, database dumps, and long-term retention. Do not treat a snapshot as an off-site backup, and do not assume Object Storage is a backup schedule. One scope note: this article compares Auto Backup, not Backup Space. Backup Space is a separate Contabo product; the public product page did not yield usable data for this draft, so it is not priced here. A Backup Space-specific page would need its own research pass.

Contabo review Sources
Contabo decision guide — one purchase question, one decision.
Scope. Decision draft. Contabo product facts were checked on the official Contabo pages on 2026-11-12. This is a planning analysis, not a restore test, a paid order, or a provider ranking. Prices, retention, and availability change; verify the configurator and the product pages before relying on either service.

What each product actually is

Snapshots. Contabo describes snapshots as an image of the VPS disk with 30 days of retention. A snapshot is useful before an upgrade, a plugin change, or a risky workflow edit. It restores the whole disk state, including the parts you did not mean to roll back.

Auto Backup. Contabo describes Auto Backup as 10 days of daily off-server backups. It is complementary to snapshots. Restoring a backup overwrites the current data on the VPS, and the VPS is temporarily unavailable during recovery. Auto Backup support is for newer plans; older configurations may need a plan switch, and Storage VPS/Cloud VDS support is described as planned.

Object Storage. Contabo's Object Storage is S3-compatible, starts at €2.49/month, uses a flat rate per tier, includes traffic, and supports files up to 5 TB. It is available to existing Contabo customers through the Customer Control Panel. You decide what to upload and when; Contabo does not schedule your WordPress database dump or n8n workflow export for you.

The comparison

LayerGranularityRetentionRestore behaviorBest use
SnapshotWhole VPS disk image30 daysReverts the disk stateBefore upgrades, plugin changes, risky workflow edits
Auto BackupWhole VPS, daily, off-server10 daysOverwrites current VPS data; temporary downtimeDaily recovery from a bad change or host failure
Object StorageFiles and objects you uploadYou control itYou download or sync the object; not a VM restoreDatabase dumps, uploads, exports, archives, off-site copies

The published retention is not a promise that 10 or 30 days is enough for your business. A WordPress store may need a longer history; an n8n box may need the encryption key and credentials exported with the workflow.

WordPress: what I would put where

For a small WordPress site, I would separate three things:

  • Uploads and media. Sync them to Object Storage on a schedule, or use a plugin that writes media there. Keep a local copy if the site serves the files directly.
  • Database dumps. Export a compressed dump on a schedule and upload it to Object Storage. A disk snapshot is not a database-consistent export.
  • VM recovery. Keep a snapshot before plugin/theme/core updates and enable Auto Backup for daily recovery. Test one restore on a separate server.

The trap is a backup plugin that writes three copies to the same disk. That protects against a bad edit, not against a disk failure or a deleted server. Object Storage gives the off-site copy; Auto Backup gives the VM-level restore.

n8n: what I would put where

For n8n, the data is different:

  • Workflow exports. Export the workflows you cannot recreate and upload them to Object Storage. A database backup alone may not be readable without the matching n8n version.
  • Encryption key and credentials. The encryption key must be stored separately from the database backup. A new key does not decrypt old credentials. Store the key in a password manager or encrypted vault, not as a plaintext object in the same Object Storage bucket.
  • Binary data. If executions carry images or PDFs, keep the payloads in Object Storage or a dedicated volume, not on the root disk.
  • VM recovery. Snapshot before upgrades and use Auto Backup for daily recovery. Test that the workflows, credentials, and database come back together.

The n8n export and migration guide covers the export side. The Contabo billing and backup guide covers the pause-before-backup routine.

What breaks in a restore

Three failures are common:

  • The backup is controlled by the same provider. A snapshot is a provider-side disk image, not an independent off-site copy. A local backup on the same VPS disappears with the server. Account deletion, cancellation, or a provider-side failure can remove both; keep a copy outside the provider.
  • The database and files are from different times. A dump from Monday and uploads from Friday can produce a broken site. Schedule them together or record the mismatch.
  • The credentials are missing. A WordPress site can be rebuilt; an n8n instance without its encryption key may not be able to read its own credentials. Export the key.

Auto Backup's restore overwrites the current VPS data. That is right for a full rollback, but it is not a way to recover one file. Object Storage is better for a single file or a database dump.

What I would set up

For a small WordPress or n8n box, I would use all three layers:

  1. A snapshot before every planned change, with a note of what changed.
  2. Auto Backup enabled for daily VM recovery, if the plan supports it.
  3. A scheduled export of the database, uploads, and encrypted workflow files to Object Storage. Keep the encryption key in a separate password manager or vault, not in the same bucket.
  4. A quarterly restore test on a separate server, with the date and result recorded.

Object Storage starts at €2.49, but the real cost is the export schedule and the restore test. A cheap bucket with no tested restore is not a backup plan.

What this does not decide

This article does not test an Auto Backup restore, an Object Storage restore, or a WordPress/n8n recovery. It does not quote the Auto Backup add-on fee; the configurator does that. It gives the layer assignment and the failure modes to check.

Sources