Skip to main content
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog

Loading…

Servers Are Up

Your apps, automation and data on hardware we own. Build a private stack with predictable capacity and access through your dashboard, API or SSH.

SLA with service creditsOwned hardwareUS-based

Make room for your next idea

Explore the capacity, apps and access options that fit your workload. Check current availability and your total before you buy.

Sign up freeView Pricing

Products

  • Linux VPS
  • Windows VPS
  • Cloud & SaaS Services
  • Cloud Storage (Azure)
  • Virtual Datacenter
  • AI & Agent Hosting
  • Containers
  • Instant Apps
  • Software Platforms
  • Network builder
  • Game Servers
  • Pricing

Resources

  • Free Network Tools
  • 2026 Pricing Benchmark
  • Live SVG Badges
  • Latency & Speed Test
  • Guides & Tutorials
  • Documentation
  • API Reference
  • MCP Server
  • CLI & SDKs
  • OpenAPI & llms.txt
  • Use Cases
  • Free Migration
  • Uptime & Reliability
  • Datacenter
  • System Status
  • Network
  • Provider Comparisons Hub
  • Compare Providers

Company

  • About Us
  • Enterprise
  • Security Architecture
  • Trust Center
  • Blog
  • FAQ
  • Compliance
  • Startup Program
  • Open-Source Sponsorship
  • Press & Media Kit
  • Referral Program
  • Help Center
  • Contact Us
© Servers Are Up
TermsPrivacySLARefund PolicyDPAAcceptable Use
Service information
Docs
  • Documentation Hub
  • Choose a Product
    VMs, Containers & Cloud
  • First Linux Server
    SSH, Firewall & Apps
  • Windows Server 2025
    BYOL & Remote Desktop
  • Remote Access
  • Troubleshooting
  • FAQ
  • All Product Guides
    29 Step-by-Step Guides
  • Cloud & SaaS Catalog
    112 Cloud & SaaS Offerings
  • Azure Cloud Storage
    Hot/Cool/Archive & WORM
  • Resource Manager & RBAC
    Groups, Tags & Locks
  • Multi-Model Cloud DB
    JSONB, SQL & pgvector
  • Cloud Identity & ZTNA
    OIDC, SCIM & PIM
  • Key Vault & KMS
    Secrets & Envelope Keys
  • Cloud SIEM, SOAR & DLP
    Posture & Threat Response
  • API Gateway & Cloud DNS
    Edge WAF & DNS Zones
  • Serverless, Workflows & IoT
    Functions, Queues & DAGs
  • SaaS, Governance & Vault
    Budgets & Off-Host GRS
  • Build Web Apps with AI
  • Next.js and React
  • TypeScript and Node.js
  • npm and Tooling
  • Data and APIs
  • Deploy and Operate
  • Tutorials
  • Infrastructure
  • Automation & Regions
  • API Overview
  • API v1 Reference
    Endpoints & 23 Scopes
  • MCP Server
    129 AI Agent Tools
  • Swagger / OpenAPI 3.1
  • API Playground
  • Versioning & Sunset
  • API Token Security
    Authentication & Tokens
  • Instances API
    Compute Resources
  • Networking API
    Networks & Ports
  • Storage API Availability
    Volumes & Backups
  • Webhooks & Events
    Event Notifications
  • Rate Limits & Best Practices
    Throttling & Retries
  • sau CLI Reference
    34 Commands (v0.2)
  • Browser Web CLI
  • SDKs
  • Infrastructure as Code
    Terraform & Ansible
  • Code Examples
  • CLI & SDK Guides
  • Security Guides
  • Security at a Glance
  • Zero Trust Architecture
  • Live Trust Center
  • Compliance
Need help?

Loading documentation...

Documentation/products

Snapshot a server before a change and restore safely

Create point-in-time server snapshots, schedule off-host encrypted backups and verify restores on Servers Are Up without losing data.

Beginner
16 min
Updated 2026-11-12

Deploy Ready-to-Run Infrastructure in Seconds

Linux VMs from $6/mo · Pooled Virtual Datacenters from $12/mo · Use code WELCOME20 for 20% off your first order.

Browse ServersView Pricing

Commands checked on 2026-11-12 with Servers Are Up Platform v1.7, sau CLI 0.2.0, restic 0.17.

What you will have at the end

You will know the exact operational difference between point-in-time hypervisor snapshots (for instant rollback before kernel or application upgrades), encrypted off-host backups (free to your own S3/R2/B2 storage or via catalog backup policies), and immutable WORM Recovery Vaults (/dashboard/recovery-vault), and you will have taken and verified a pre-change snapshot of a live server.

Before you start

  • A running Linux or Windows server on Compute > Servers (/dashboard/instances).
  • A Personal Access Token with snapshots:read, snapshots:write, and instances:read scopes if you want to trigger snapshots from CI/CD or the sau CLI.
  • Five minutes before an OS upgrade, database migration, or firewall refactor.

Steps

1. Flush database buffers cleanly before taking a live snapshot

KVM snapshots capture crash-consistent block state instantaneously, and modern journaling filesystems (ext4, xfs, NTFS) plus PostgreSQL WAL recover cleanly. For maximum safety on busy databases, run a CHECKPOINT and filesystem sync right before snapping:

ssh -i ~/.ssh/id_sau_ed25519 -p 31001 ubuntu@203.0.113.25 \
  "sudo -u postgres psql -c 'CHECKPOINT;' && sync"

2. Create a named snapshot in the console, CLI, or v1 API

In the web console, open Compute > Servers (/dashboard/instances), select your server, open its Snapshots / Backups tab, and click Create snapshot.

From a terminal or deployment pipeline, use sau snapshots create (which calls POST /api/v1/instances/{id}/snapshots and queues a durable provider command returning HTTP 202 Accepted):

sau snapshots create YOUR_INSTANCE_ID \
  --name "pre-node24-upgrade-2026-11-12" \
  --description "Clean baseline before upgrading Node.js and running Prisma migrations"

sau snapshots list YOUR_INSTANCE_ID

Wait until the snapshot status transitions from PENDING / CREATING to AVAILABLE before starting your risky change.

3. Configure encrypted off-host backups for disaster recovery

Snapshots live near the compute cluster for fast rollback; true 3-2-1 disaster recovery also stores encrypted backups in an independent storage fault domain. You have three built-in options:

  1. Free Encrypted BYO-Storage Backups: On Storage > Storage (/dashboard/storage), connect your own Cloudflare R2, Backblaze B2, Amazon S3, DigitalOcean Spaces, Wasabi, or SFTP target to back up Linux /mnt/data volumes with client-side encryption at $0 platform software fee.
  2. Managed Volume Backup Policies: Quote and attach a managed retention policy for a Linux data volume lineage directly from the CLI:
    sau backups sources
    sau backups quote YOUR_LINEAGE_ID --product backup-standard
    sau backups create YOUR_INSTANCE_ID --notes "Pre-release recovery point"
    
  3. Immutable WORM Recovery Vault: Register servers, Cloud Databases, and Blob containers in Operations > Backup & recovery vault (/dashboard/recovery-vault) (25 GiB included free) with ransomware immutability locks and automated restore drills.

4. Restore when a change fails (or recycle-bin deleted servers)

If an OS upgrade or migration breaks your Linux plan server:

  1. Open Compute > Servers (/dashboard/instances), select the server, locate your pre-node24-upgrade-2026-11-12 snapshot, and click Restore (or call POST /api/v1/instances/{id}/snapshots/{snapshotId}/restore with snapshots:write scope, which queues the restore command with HTTP 202 Accepted).
  2. If someone accidentally deleted a server without --permanent, open Compute > Recycle bin (/dashboard/recycle-bin) before its retention window expires and click Recover.

Check that it works

Confirm your snapshot is listed as AVAILABLE over the API and verify that a database dump or file backup can actually be read back:

curl -fsSL "https://serversareup.com/api/v1/instances/YOUR_INSTANCE_ID/snapshots" \
  -H "Authorization: Bearer sau_your_token_here" | jq '.snapshots[] | {id, name, status, createdAt}'

An untested backup is only a wish—periodically restore a database backup onto a scratch container or trigger a verified restore drill on Operations > Backup & recovery vault (/dashboard/recovery-vault).

What can go wrong

  • Relying solely on local snapshots instead of off-host backups. A snapshot rolls back the entire disk (including every customer order written after the snapshot was taken!). Keep point-in-time database dumps (pg_dump / WAL archiving) in off-host object storage so you can recover code with a snapshot without rolling back customer rows.
  • POST .../snapshots returns 403 Forbidden. Confirm your Personal Access Token includes snapshots:write (not just instances:write) and that no ReadOnly lock is attached to the resource in /dashboard/resource-manager.
  • Guest cron backup fails with PostgreSQL authentication errors when run as root. Run pg_dumpall | gzip as the postgres OS user in /etc/cron.d/ (0 2 * * * postgres /usr/local/bin/backup-db.sh) rather than root.

Good practice

  • Automate sau snapshots create as the very first step of every production infrastructure upgrade script, and prune obsolete pre-upgrade snapshots after 7 days of stable runtime.
  • Protect production backup vaults with WORM immutability in Operations > Backup & recovery vault (/dashboard/recovery-vault) so even a compromised admin token cannot purge recovery points.
  • Store off-host backup encryption passphrases in Access > Key vault & KMS (/dashboard/key-vault).

Where to go next

  • Subscribe to SaaS apps, enforce policy and lock recovery vaults
  • Purchase Azure-backed cloud storage with WORM locks and SAS
  • Install the sau CLI and manage infrastructure from a terminal

Related Articles

Create a scoped API key and send your first v1 request

Read more

Route APIs with Edge WAF, rate limits and Cloud DNS

Read more

Purchase Azure-backed cloud storage with WORM locks and SAS

Read more

Frequently Asked Questions

What does the Snapshot a server before a change and restore safely documentation guide cover?
Create point-in-time server snapshots, schedule off-host encrypted backups and verify restores on Servers Are Up without losing data. It is rated beginner difficulty (16 min) and applies to Servers Are Up infrastructure and workflows.
Can I manage or automate these steps through the Servers Are Up dashboard, REST API v1, or MCP server?
Yes. Every Servers Are Up server includes browser-based SSH, WebRDP, and VNC console access in the dashboard, plus programmatic control via the REST API v1 (/api/v1) and hosted Model Context Protocol server (/api/mcp/v1) using a scoped Personal Access Token.

Need hands-on help with Snapshot a server before a change and restore safely?

Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.

Was this article helpful?

On this page

What you will have at the endBefore you startSteps1. Flush database buffers cleanly before taking a live snapshot2. Create a named snapshot in the console, CLI, or v1 API3. Configure encrypted off-host backups for disaster recovery4. Restore when a change fails (or recycle-bin deleted servers)Check that it worksWhat can go wrongGood practiceWhere to go next