netcup snapshots & the Server Control Panel (SCP)

Before you do something risky on the server – a big update, a delicate config change – you want a point you can return to in minutes. That’s exactly what netcup snapshots are for. This tutorial shows you the Server Control Panel (SCP) and how to use snapshots properly – and where their limit lies.

What are we building?

You get to know the netcup Server Control Panel (SCP) – the web interface to your server – and create a snapshot there: a complete image of your server disk, to which you return in a few minutes if a mishap happens. By the end you know when a snapshot is your rescue – and why it’s still no substitute for a real backup.

Prerequisites

• A netcup server, e.g. your first VPS.
• Your SCP credentials – they are in the netcup welcome email and are different from your SSH login.

Step by step

Step 1: Log into the SCP and find the server

Open servercontrolpanel.de and log in with your SCP credentials. You land in the server list; a click on your server opens the overview with product, status and hardware. At the top you see the tabs through which you control everything – snapshots are under “Media”.

Step 2: Create a snapshot

Go to Media → Snapshots. Under Create snapshot you fill in:

• Name: name it after the why, not the date alone – e.g. before-update-2026-07. That way you later know what it was for.
• Description: one sentence of context (optional, but helpful).
• Disk: usually vda (your system disk).
• Type: here lies the most important decision – see below.

Offline or online snapshot?

• Offline snapshot: the server is briefly shut down for the capture. This guarantees a consistent state – the right choice when databases are running, and when you can afford the brief downtime.
• Online snapshot: capture while running, without downtime. Convenient, but with active writes (e.g. a database mid-write) the image can be inconsistent.

A click on Create starts the process; depending on the amount of data it takes a few minutes. It runs in the background – the creation date and type then appear in the list above once it’s done. Best schedule the brief downtime of an offline snapshot for a quiet time; after that your return point is set and you can tackle the planned change.

Step 3: Restore a snapshot

If something went wrong, you find the snapshot in the list under Snapshots; in the Actions column there’s Restore.

Step 4: The other safety lines in the SCP

The SCP has more than snapshots – good to know for an emergency:

• Display (VNC console): direct screen access to the server, even when SSH refuses – the safety line from the SSH tutorial.
• Rescue system: boots the server into an emergency Linux to repair a broken installation.
• Media → Images / DVD drive: install a different operating system.

When things go wrong

Maintenance & backups

• Snapshot ≠ backup – the most important point. A snapshot lives at netcup, under your account, in one slot and is meant as a momentary snapshot. If the account, the data center or your access fails, it’s gone too. It’s a quick safety net, not an off-site backup.
• Snapshot before every risky action. Before big updates, migrations or delicate config changes: snapshot first, then start. Afterwards you can calmly replace it with the next one.
• Snapshots age. A months-old snapshot brings you back to a long-outdated state – when in doubt, worse than no snapshot. Renew it specifically before every larger action; a fresh return point is worth more than an old one.
• For real safety you need both. Complement the snapshot with encrypted off-site backups – how that works is shown in the tutorial on backups with Restic. Rule of thumb: snapshot for the quick return, Restic for “my server is gone”.