summaryrefslogtreecommitdiff
path: root/faq/why-nonstd-format.mdwn
blob: ee07440178254e1cea9ac8cffa1a9f3026c3e9e1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
[[!meta title="Why is Obnam not using standard file formats, such as tar or cpio?"]]

The standard file formats do not support the kind of advanced features
that Obnam is built for. For example, block level de-duplication,
or abolishing the difference between full and incremental generations. 
It would be possible to build those features on top, say, tar, but
it would mean the tar is just a container for odd bits of data, which
still requires a custom program to restore from.

If you're worried that you might lose your copy of Obnam, and be unable
to restore, two points:

* You can store a copy of Obnam (in source and binary versions) in your
  backup repository.
* Obnam is free software, and it's in Debian. You're pretty much guaranteed
  to be able to find a copy and build a new binary.