| 1 | Source: rsync-backup |
| 2 | Section: utils |
| 3 | Priority: extra |
| 4 | Maintainer: Mark Wooding <mdw@distorted.org.uk> |
| 5 | XS-Python-Version: >= 2.5 |
| 6 | Build-Depends: mlib-dev (>= 2.2.1), debhelper (>= 10) |
| 7 | Standards-Version: 3.1.1 |
| 8 | |
| 9 | Package: fshash |
| 10 | Architecture: all |
| 11 | Depends: python |
| 12 | Description: Calculate a digest of a filesystem. |
| 13 | The `fshash' program generates digests of filesystems. It aims to provide |
| 14 | three properties: |
| 15 | . |
| 16 | * Completeness: the digest describes everything `interesting' about the |
| 17 | filesystem, such that two filesystems which are interestingly different |
| 18 | will have different digests. |
| 19 | . |
| 20 | * Canonicalness: if two filesystems aren't different in any interesting |
| 21 | way, then their digests should be identical. |
| 22 | . |
| 23 | * Readability: given two subtly different filesystems, it should be easy |
| 24 | for a human equipped with digests for them and diff(1) to work out what |
| 25 | the differences actually are. |
| 26 | . |
| 27 | The digests include cryptographic hashes of the files. These can take time |
| 28 | to compute, so `fshash' can keep a cache of hashes. |
| 29 | |
| 30 | Package: rfreezefs |
| 31 | Architecture: linux-any |
| 32 | Depends: ${shlibs:Depends} |
| 33 | Recommends: ssh-server |
| 34 | Description: Freeze filesystems safely under remote control. |
| 35 | Filesystems can be `frozen', i.e., placed in a consistent state, with write |
| 36 | operations delayed. This is useful when taking snapshots, and LVM (for |
| 37 | example) freezes filesystems mounted on a logical volume automatically when |
| 38 | taking a snapshot. This doesn't work if the filesystem is mounted on a |
| 39 | separate machine from the one hosting the block device, e.g., if the volume |
| 40 | is provided by a VM host to its guest, or as a remote block device. |
| 41 | . |
| 42 | The `rfreezefs' program explicitly freezes a filesystem so that a consistent |
| 43 | snapshot can be taken. It goes to considerable lengths to avoid unpleasant |
| 44 | conditions such as deadlocks while filesystems are frozen. |
| 45 | |
| 46 | Package: rsync-backup |
| 47 | Architecture: all |
| 48 | Depends: rsync, openssh-client, fshash |
| 49 | Recommends: lvm2 |
| 50 | Suggests: rfreezefs |
| 51 | Description: Yet another `rsync --link-dest' backup script. |
| 52 | It uses rsync's ability to create hardlinks from (apparently) similar |
| 53 | existing local trees to make incremental dumps efficient, even from remote |
| 54 | sources. Restoring files is easy because the backups created are just |
| 55 | directories full of files, exactly as they were on the source -- and this is |
| 56 | verified using `fshash'. |
| 57 | . |
| 58 | The script does more than just running rsync. It is also responsible for |
| 59 | creating and removing snapshots of volumes to be backed up, and expiring old |
| 60 | dumps according to a user-specified retention policy. |
| 61 | . |
| 62 | The `fshash' package is required on the server and all of the clients. The |
| 63 | `rfreezefs' package may be useful on clients which are VM guests. |