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

Operations

Practical Proxmox and ZFS operating lessons.

These are general lessons for virtualized ZFS environments and should be adapted to your own failure model, capacity and recovery needs.

01

Mirrors solve a disk failure, not every failure

A mirror provides device redundancy. It does not protect against accidental deletion, application corruption, operator mistakes, host failure or a site-wide event. Design backups and recovery around the failures you actually need to survive.

02

Reserve capacity before the pool is full

Capacity planning should use real usable storage and leave operational headroom. Full pools make maintenance, snapshots, migrations and recovery harder, so stop new provisioning before the safety margin is consumed.

03

ARC belongs in the memory budget

ZFS uses memory for ARC caching. On a virtualization host, account for ARC alongside guest allocations and the hypervisor's own needs instead of treating all unallocated memory as guest capacity.

04

Scrub and TRIM are maintenance, not backups

Regular scrubs can surface latent read or checksum problems while redundancy is available. TRIM can help supported solid-state storage maintain allocation efficiency. Neither creates an independent recovery copy.

ZFS scrub planning → · ZFS snapshot planning →

05

Test through the guest boundary

Infrastructure validation should include disposable guest workloads and the same provisioning, storage and network paths customers will use. Static configuration review can miss problems that only appear after a guest is created and exercised.

Benchmark method and evidence →

06

High availability is an end-to-end property

Multiple hosts alone do not create useful high availability. Placement, quorum, storage, networking, service discovery and recovery behavior all need to be designed and tested together.

Architecture

Review the current service overview.

DotMoose publishes its current customer-facing hosting and service information on the infrastructure overview.

Infrastructure overview
Storage basics

Start with the failure model.

A mirror, snapshot and independent backup solve different problems.

ZFS mirror guide

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