Plakar Encrypted Backup Appliance

AWS Storage

encrypted, deduplicated backups you can prove you can restore

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Plakar is an open source backup engine that creates versioned backups with compression, encryption and content addressed deduplication. Snapshots land in a Kloset store where identical data is kept exactly once however many snapshots reference it, so a long retention history costs a fraction of repeated full backups. Every snapshot is independently restorable and independently integrity checkable, and a built in web interface browses snapshots, compares revisions and restores files without the command line.

Why the cloudimg image

The repository encryption passphrase and the web interface token are generated uniquely on the first boot of every instance and written to a root only file, so no shared key ships in the image and no two deployments can read each other's backups. The Plakar server binds to loopback only behind nginx, and the API rejects unauthenticated and wrong token requests. The encrypted repository lives on a dedicated data volume, separate from the OS disk and independently resizable. The image also ships a self test that performs a real backup, restores it to a separate path and compares every file by checksum, so you can verify the appliance end to end at any time. Paired with a step by step deploy guide and 24/7 cloudimg support.

Common uses

  • Scheduled server and application backups with long retention at low storage cost
  • Encrypted offsite snapshots where the key never leaves your own instance
  • Verifiable restores for audit, compliance and disaster recovery drills

Key features

  • Storage efficient encrypted backups with built in deduplication store identical data exactly once, so long retention histories cost a fraction of repeated full backups. The web interface lets you browse snapshots, compare revisions, and restore files without the command line.
  • Every instance generates its own unique encryption passphrase and API token on first boot. No shared key ever ships in the image, the build verifies no secrets survive image capture, and cloudimg cannot decrypt your backups. The repository lives on a dedicated, independently resizable EBS volume behind an nginx reverse proxy.
  • A shipped self test at /usr/local/sbin/plakar-selftest proves the appliance really backs up and really restores by writing data, snapshotting it, restoring to a separate path, and comparing every file by sha256. It also exercises four negative controls including wrong passphrase and bogus snapshot rejection. Backed by 24/7 cloudimg support by email.

See it running

Real screenshots taken while testing this image against its deployment guide.

Plakar Encrypted Backup Appliance screenshot 1 Plakar Encrypted Backup Appliance screenshot 2 Plakar Encrypted Backup Appliance screenshot 3 Plakar Encrypted Backup Appliance screenshot 4

Description

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Backups You Can Prove You Can Restore

Plakar is an open source backup engine that creates versioned, encrypted, deduplicated snapshots in a content addressed Kloset store. Identical data is stored exactly once regardless of how many snapshots reference it, so long retention histories cost a fraction of repeated full backups. Every snapshot is independently restorable and integrity checkable, and the built in web interface lets you browse snapshots, compare revisions, and restore files without touching the command line.

## Who This Is For

  • Infrastructure teams running scheduled server and application backups who need long retention without paying for it in storage
  • Security and compliance teams who require that the encryption key never leaves the customer's instance and that no vendor can decrypt the archive
  • Operations teams running disaster recovery drills who need a restore that can be proven byte for byte rather than assumed

## Application Stack

  • Plakar 1.1.4 installed from the official upstream release binary, checksum verified against the upstream manifest
  • nginx reverse proxy on port 80; the Plakar server binds to loopback only and is never exposed directly
  • Encrypted Kloset repository on a dedicated EBS volume, independently resizable and separate from the OS disk
  • A hardened, fully patched Linux base with plakar-ui and nginx as enabled systemd units

## Zero Shared Secrets, Per Instance Key Generation

A backup appliance that shipped one passphrase for every customer would let anyone holding the image read anyone else's backups. This image ships nothing cryptographic at all:

  • The repository encryption passphrase is generated uniquely on first boot of every instance
  • The web interface API token is generated uniquely on first boot of every instance
  • The repository is created fresh on first boot, not at build time
  • Both secrets are written to a root only file, and the build verifies no key material survives image capture
  • The API rejects unauthenticated requests and wrong tokens

Because the passphrase never leaves the instance, cloudimg cannot decrypt your backups and cannot recover the passphrase for you. Store it somewhere safe on first launch.

## Shipped Self Test Proves End To End Integrity

The image includes a self test at /usr/local/sbin/plakar-selftest. It writes a known dataset, backs it up into the real encrypted repository, restores it to a different path, and compares every restored file by sha256. It then runs a full integrity check and exercises four negative controls: a wrong passphrase must not open the repository, a bogus snapshot ID must not restore, an unauthenticated API call must be refused, and a wrong token must be refused. Run it any time to confirm the appliance genuinely backs up and genuinely restores.

## Getting Started

1. Launch the AMI on an m5.large or larger, opening ports 22 and 80 in the security group

2. SSH in and run: sudo cat /root/plakar-credentials.txt

3. Record the repository passphrase somewhere safe, then open the web interface link shown in that file

4. Point Plakar at the directories you want protected and take your first snapshot

5. Run sudo /usr/local/sbin/plakar-selftest to confirm backup and restore end to end

## Recommended Sizing

  • Compute: m5.large (2 vCPU, 8 GB RAM) for routine server and application backup workloads
  • Storage: repository on its own EBS volume, sized to your retention needs; deduplication keeps costs far below repeated full backups
  • Networking: port 22 for SSH, port 80 for the web interface

## Evaluate Before You Commit

Launch the AMI, run the self test, and take a test snapshot to validate the backup and restore cycle in your own environment. For pre-purchase deployment questions, email support@cloudimg.co.uk.

## 24/7 cloudimg Support

Every deployment is backed by cloudimg engineers available around the clock by email. Support covers deployment guidance, instance sizing, repository and volume layout, scheduling backups, restore and integrity check procedures, TLS termination, and Plakar version upgrades.

Plakar is open source under the ISC licence with no licence fee. The cloudimg charge covers packaging, security patching, image maintenance, and 24/7 support. Plakar is a trademark of its respective owner; cloudimg is not affiliated with or endorsed by the Plakar project.

Related technologies

backup applianceencrypted backupdeduplicationdisaster recoverysnapshot restoredata protectionserver backuplong retentionbackup verificationEBS backup