What do you get when you rent a Hetzner Cloud server?
You get a virtual machine that can run an operating system and app software. Choose a location, server size and system image, the starting copy of the operating system.
A machine can host a website, the code behind a booking form and a database. You decide what to install, how to keep it updated and how people reach it. Check current regional stock and architecture before you assume a small plan or a particular system image will be available.
How can you plan a first deployment on paper?
Draw two machines. Label one Test and the other Live. The test version should save one fictional repair booking while the live version and its records stay untouched.
- Draw the test address and its connectionsGive the test app a separate address and a disposable database. Leave outgoing messages and payment connections disabled. Draw who can open the test address.
- Trace a restartMark the test time as saved. Start a new copy on paper and check whether it reads the same saved test record from persistent storage.
- Choose where a restore goesDraw a second test destination for a backup containing fictional data only. Identify the record and attachment you would look for, and keep every connection and outgoing action in test scope before any real rehearsal.
When does a Hetzner Cloud server stop costing money?
Hetzner bills the server by the hour up to its monthly cap. The clock keeps running while the server exists, even when it is powered off.
Choose the current location, server size and currency in the price calculator. Include any paid address, extra storage and outgoing traffic beyond the included amount.
Automated backups cost an extra 20% of the server price. Manual snapshots are billed by compressed gigabytes stored per month. When removing a test setup, check remaining storage, addresses and snapshots separately before assuming the charges have stopped.
What do Hetzner backups and snapshots cover?
Both cover the server disk. They leave out attached Volumes, which are separate drives you can add to the server. Keep a separate recovery copy for anything stored on those drives.
Rebuilding an existing server from either copy overwrites its disk. You can create a new server from a copy instead. A disk copy from a running server might be inconsistent, so use the database’s own backup procedure and check that its records can be restored.
| Copy | How it is kept |
|---|---|
| Backup | Automatic daily copies when enabled, with seven rotating slots. Deleting the server removes its backups. |
| Snapshot | A manual copy you keep until you delete it. It stays available if you delete the original server. |
What should you keep if you move away?
Keep the app source, the setup you use to run it, and portable copies of the database and uploaded files. Record the separate services and settings the app expects at startup.
A Hetzner snapshot can help rebuild on Hetzner. If the destination is elsewhere, use the app code and the database and file copies. Read a restored fictional booking on the destination’s isolated version before switching the public address.