Guide · Storage

Shared OS Images and Writable Clones: Planning PC Storage

Store the operating system once as a read-only template, and give every PC its own writable disk on top of it. Unchanged data is read from the shared template, and only what a PC changes takes extra space. Nobody shares a writable system disk, so one user's changes never show up on another PC.

How a shared image and a writable clone work

Imagine an accounting office with 50 identical Windows PCs. Installing Windows and the office software 50 times stores the same few tens of gigabytes 50 times. A shared image avoids that: you prepare the system once, and the PCs are built from it.

  • Template version. A prepared system, such as Windows with your office software, is published as a version. A version is a protected, read-only snapshot of the template disk.
  • Writable clone. Each PC is created as a copy-on-write clone of one version. It reads unchanged blocks from the template and writes its own changes to its own disk.
  • One writable disk per PC. The template is never written to, and two PCs never write to the same disk. That is what keeps users apart.
One template version and three writable clones One read-only template version is stored once. Three PCs each have their own writable disk that holds only the data that PC changed. Unchanged blocks are read from the template. Each PC sees a full-size disk. Template version (read-only) Operating system and shared software, stored once PC A: own writable disk Only A's changes PC B: own writable disk Only B's changes PC C: own writable disk Only C's changes Unchanged blocks are read from the template Each PC sees a full-size disk, but space is used only as data is written
One template version, stored once, and a separate writable disk for every PC. On a narrow screen, scroll the diagram sideways.

A capacity example

These numbers are an illustration to show the arithmetic, not a measurement and not a purchasing recommendation. Units are decimal (1 TB = 1,000 GB).

Assumptions: 50 PCs, a base image of 40 GB, and 15 GB of changes per PC (user files, updates, caches). The storage keeps three replicas of everything.

Capacity arithmetic for 50 PCs, with and without a shared base image
StepEvery PC keeps a full copyShared base + clones
Data stored50 × (40 + 15) = 2,750 GB40 + 50 × 15 = 790 GB
With three replicas2,750 × 3 = 8,250 GB790 × 3 = 2,370 GB
If normal use stays at 75% of raw capacity8,250 ÷ 0.75 = 11,000 GB2,370 ÷ 0.75 = 3,160 GB

Not included: snapshot history, metadata, extra template versions, allocation granularity, uneven data placement and the headroom you need to recover from a failed disk. The 75% figure is only an example: the right headroom depends on your failure domains and how quickly you want to recover. Every clone also grows with use, because updates, caches and the page file count as changes.

The numbers to track separately

Four different numbers get confused in storage planning. Keep them apart.

  1. Allocated size. The disk size each PC sees. Disks are thin, so allocating 100 GB does not write 100 GB. Per-owner quotas are counted by allocated size, so handing out large disks uses quota before any data is written.
  2. Data written. What each PC has actually changed since the template. It grows with use.
  3. Snapshot space. Recovery points keep data that has since changed, so they take space, and that space counts against the owner's quota.
  4. Raw capacity. What you need to buy once redundancy is included. Nodekeeper's distributed storage keeps data as replicas or with erasure coding (2+1, 2+2, 4+2 and 8+3 profiles), so raw disk is always larger than the data. The example above uses replicas.
A member storage quota card showing the allocated quota and the space left
A member's storage quota card: the quota is shown by allocated size, with the space left.

When an owner reaches the quota, Nodekeeper warns first, then allows a 24-hour grace period, and then stops the disk. Adding quota or deleting data brings it back. The pool itself grows by adding disks or hosts to the cluster.

Snapshots, replicas and backups solve different problems

What replicas, snapshots and backups each protect against
ReplicasSnapshotsBackups
Protect againstA failed disk or hostA bad update or a mistake on one PCLosing the cluster itself
Where the copy livesInside the clusterInside the clusterOutside it
Bad dataCopied as faithfully as good dataRolled back to the earlier stateRestored from an earlier copy
Takes spaceMultiplies raw capacityChanged blocks since the snapshotSpace in the backup destination
  • Snapshots can be taken by hand or on an hourly or daily schedule with a retention count. Scheduled snapshots are off until you turn them on. Nodekeeper also takes one automatically before every rollback and before a reinstall.
  • Rollback needs the PC switched off and a two-factor confirmation, and it discards everything written after that snapshot. Snapshots are crash-consistent, as if the power had been cut at that moment.
  • Full cloud-PC disk backups give you a copy outside the cluster, which is what protects against losing the storage itself.

Decisions that matter most

1. How many template versions you will maintain

One base image per department or hardware group is easier to look after than one per person. A new template version does not upgrade the PCs that were cloned from an older one, and a version that still has clones depending on it cannot be deleted, so decide how you will move people to a newer version before you publish many of them.

2. How large each PC's disk should be

Choose the disk size when you create the PC. A larger allocation does not create physical space: it uses quota, and the cluster still needs real capacity behind it. Windows extends the C: drive to the full disk size on first boot.

3. Which recovery points you keep, and for how long

Retention drives snapshot space. Keep enough history to cover the mistakes you actually see, and add a backup for the case where the cluster itself is lost.

How Nodekeeper shortens the work

  1. Build a template from your own Windows ISO, or from the Debian or Ubuntu templates, and publish it as a version. A prepared PC can also be saved as a new version.
  2. Create each PC from a chosen version. Nodekeeper makes the clone and its own writable disk, and lists allocated size next to the data written.
  3. Set a quota per owner and watch it in the panel; grow the pool by adding disks or hosts.
  4. Schedule snapshots, roll a PC back when needed, and back up whole cloud-PC disks.
  5. Give each team the access its role needs: every permission can be assigned per user group.

Shared images run on the same central storage that carries your virtual machines and member files, so one panel covers capacity, quotas and recovery for all of them. Windows and Linux office PCs boot from this storage over the network, as explained in What is Windows network boot?.

Shared images and distributed storage are part of the Business plan, licensed per node (each machine that runs Nodekeeper).

Plan central storage for your PCs

Block, file and S3-compatible object storage, quotas and recovery in one place. Start with the storage overview, or talk to us about sizing your pool.

Start Business Trial

30-day trial of Business: monthly subscription, first month $0, card required, once per account, up to 3 nodes. Cancel before day 30 and you are not charged; after that, Business renews at $29 per node per month.

Related

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
[email protected] WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.