1 .TH lreplicate 8 "2009 Apr 08" Lustre "Lustre Filesystem replication utility"
3 lreplicate \- Utility to replicate a Lustre Filesystem
6 .B lreplicate --source|-s <src> --target|-t <tgt>
8 .B\t\t\t --mdt|-m <mdt> [--user|-u <user id>]
10 .B\t\t\t [--xattr|-x <yes|no>] [--verbose|-v]
12 .B\t\t\t [--statuslog|-l <log>] [--dry-run] [--abort-on-err]
16 .B lreplicate --statuslog|-l <log>
20 .B lreplicate --statuslog|-l <log> --source|-s <source>
23 .B\t\t\t --target|-t <tgt> --mdt|-m <mdt>
26 can be used to replicate a lustre filesystem (source filesystem) to
27 another target filesystem (any filesystem type). It is required that
28 changelogs be enabled on the source filesystem (see lctl (8)).
30 The source and the target filesystems must be identical before
31 changelogs are enabled. If the source filesystem has been populated
32 before turning on changelogs, a utility like rsync may be used to make
38 The source filesytem which will be replicated. Mandatory if a valid
39 statuslog created during an previous replication operation
40 (--statuslog) is not specified.
44 The filesystem to which the source filesystem is replicated. Mandatory
45 if a valid statuslog created during an previous replication operation
46 (--statuslog) is not specified. This option can be repeated if
47 multiple replication targets are desired.
51 The metadata device which is to be replicated. Changelogs must be
52 turned on on this device. Mandatory if a valid statuslog created
53 during an previous replication operation (--statuslog) is not
58 The changelog user id. See lctl(8) changelog_register. Mandatory if a
59 valid statuslog created during an previous replication operation
60 (--statuslog) is not specified.
64 A status log file to which the status of replication is saved. At the
65 time of initialization, the state from a previous replication
66 operation which was saved, can be read and reused.
68 If a statuslog from a previous replication operation is specified, the
69 otherwise mandatory options like --source, --target and --mdt may be
72 By specifying the options like --source, --target and --mdt in
73 addition to the --statuslog option, the parameters in the statuslog
74 can be overridden. The command line options take precedence over the
75 ones from the statuslog.
79 Specify whether extended attributes are replicated or not. The default
80 is to replicate extended attributes. Disabling xattrs will mean that
81 striping information will not be replicated.
85 Produce a verbose output.
89 Shows what the program would do without actually replicating data.
93 Stop processing upon first error. Default is to continue processing.
98 Register a changelog consumer for MDT lustre-MDT0000
99 $ ssh $MDS lctl changelog_register --device lustre-MDT0000 -n
104 Replicate the lustre filesystem /mnt/lustre to /mnt/target.
105 $ lreplicate --source=/mnt/lustre --target=/mnt/target \\
107 --mdt=lustre-MDT0000 --user=1 \\
109 --statuslog replicate.log --verbose
111 Lustre filesystem: lustre
113 MDT device: lustre-MDT0000
119 Statuslog: replicate.log
121 Changelog registration: cl1
123 Starting changelog record: 0
127 lreplicate took 1 seconds
129 Changelog records consumed: 22
134 After the filesystem undergoes some changes, replicate the \
135 changes. Only the statuslog needs to be specified as it has all the \
136 parameters passed earlier.
138 $ lreplicate --statuslog replicate.log --verbose
140 Replicating Lustre filesystem: lustre
142 MDT device: lustre-MDT0000
148 Statuslog: replicate.log
150 Changelog registration: cl1
152 Starting changelog record: 22
156 lreplicate took 2 seconds
158 Changelog records consumed: 42
162 To replicate the lustre filesystem /mnt/lustre to /mnt/target1 and /mnt/target2.
163 $ lreplicate --source=/mnt/lustre \\
165 --target=/mnt/target1 --target=/mnt/target2 \\
167 --mdt=lustre-MDT0000 --user=cl1
169 --statuslog replicate.log
174 The lreplicate command is part of the Lustre filesystem. Contact
175 http://www.lustre.org/