1 |
Hi, |
2 |
|
3 |
when you want to use zfs send/receive to make incremental backups, do |
4 |
you need to keep all the snapshots you're making the backups from around |
5 |
indefinitely? |
6 |
|
7 |
I haven't found any documentation about how to deal with all the |
8 |
snapshots which would be created over time. Can they be destroyed once |
9 |
the backup is finished? A full backup took about 48 hours, so something |
10 |
faster is needed, and I don't want to end up with hundreds or thousands |
11 |
of snapshots by making new ones every day without being able to ever |
12 |
destroy them. |
13 |
|
14 |
The manpage is entirely confusing: |
15 |
|
16 |
|
17 |
,---- |
18 |
| -i snapshot|bookmark |
19 |
| |
20 |
| Generate an incremental send stream. The |
21 |
| incremental |
22 |
|
23 |
Incremental in which way? |
24 |
|
25 |
| source must be an earlier snapshot in the destination's |
26 |
| history. It will commonly be an earlier snapshot in the |
27 |
|
28 |
I don't want to back up the destination, and I don't care about its |
29 |
history. It's not like I'd be modifying the backup in between the |
30 |
increments. |
31 |
|
32 |
| destination's filesystem, in which case it can be speci‐ |
33 |
| fied as the last component of the name (the # or @ charac‐ |
34 |
| ter and following). |
35 |
|
36 |
Huh? |
37 |
|
38 |
| If the incremental target is a clone, the incremental |
39 |
| source can be the origin snapshot, or an earlier snapshot |
40 |
| in the origin's filesystem, or the origin's origin, etc. |
41 |
`---- |
42 |
|
43 |
There is only one source, which is the current data I want to backup. |
44 |
Should I make an incremental clone on the destination machine? |
45 |
|
46 |
|
47 |
Basically, documentation says that such incremental backups are awesome |
48 |
because you get a 1:1 copy and only need to transfer what has changed |
49 |
after a previous backup as if you would use rsync, but that it's better |
50 |
than that and you can do it in like no time. It doesn't really say how |
51 |
to actually do that and what to do with all the snapshots, though. |
52 |
|
53 |
I also can only guess that enabling compression on the target FS won't |
54 |
work unless compression is enabled at the source, though it would be |
55 |
rather useful to have the backups compressed while the source is not. |
56 |
You could do that with rsync, though, but I don't know how to access the |
57 |
snapshot for that. |
58 |
|
59 |
So how does this work? |