Explanations

This section provides background and context to help you understand how Plakar works and why certain design choices exist. These pages focus on concepts, trade‑offs, and best practices rather than step‑by‑step instructions.

If you’re looking for practical instructions, see the Guides section.

How Plakar Works

Understand the core architecture and data processing pipeline behind Plakar, including Kloset stores, chunking, deduplication, compression, encryption, and snapshot management.

Should you push or pull backups?

Understand the difference between push and pull backup models, and how Plakar supports both.

How many Kloset Stores should you create?

Understand how deduplication, data similarity, and security requirements affect the number of Kloset Stores you should use.

Why multiple backup copies matter

Understand why multiple backup copies drastically reduce the risk of data loss, and how this leads to the 3‑2‑1 backup strategy.

Why you need to backup your SaaS

Understand why cloud services do not replace backups, and why SaaS data requires independent protection.