-
Notifications
You must be signed in to change notification settings - Fork 1
/
zfs_replicate_s3.txt
50 lines (40 loc) · 1.38 KB
/
zfs_replicate_s3.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Notes on replicating zfs snapshots to Amazon S3/Glacier
AWS connection (via boto):
* S3 Key ID (required)
* S3 Secret (required)
* endpoint (boto3 only)
AWS Bucket (via boto)
* bucket name
* region (defaults to us-east-1)
* Data upload must be to STANDARD or STANDARD_IA
* Data can be migrated based on prefix and after a time period
* Glacier data takes min. 4 hours to restore
Data is stored in a bucket in key/value format.
* Key may have '/', in which case treated like folders, essentially filename
* Value (data) can be up to 5TB in S3, 40TB in Glacier
Proposed layout:
* Create bucket if needed (exception on error)
* Add lifecycle rule:
* prefix=glacier/ days=0 transition=GLACIER
* ${BUCKET}
/${HOSTNAME}
/${POOLNAME}/map.json
/lockfile
/glacier
/${HOSTNAME}/${POOLNAME}/<keyname> -- maximum 5tb
<keyname> must be unique for glacier/${HOSTNAME}/${POOLNAME}
map.json:
* Array of datasets
* Array of snapshots
* Recursive (boolean)
* Name of snapshot
* Compression type
* Encryption type
* Date (in seconds since epoch)
* Array of key components
* glacier/<keyname>
* SHA1 checksum of component
Notes on ZFS replication
* Basic replication is zfs send | zfs recv
* Replication can be recursive
* If recursive, ensure that destination is not a child of source