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> --xattr|-x <yes|no>
10 .B\t\t\t --verbose|-v --statuslog|-l <log> --dry-run
14 .B lreplicate --statuslog|-l <log>
18 .B lreplicate --statuslog|-l <log> --source|-s <source>
21 .B\t\t\t --target|-t <tgt> --mdt|-m <mdt>
24 can be used to replicate a lustre filesystem (source filesystem) to
25 another target filesystem (any filesystem type). It is required that
26 changelogs be enabled on the source filesystem (see lctl (8)).
28 The source and the target filesystems must be identical before
29 changelogs are enabled. If the source filesystem has been populated
30 before turning on changelogs, a utility like rsync may be used to make
36 The source filesytem which will be replicated. Mandatory if a valid
37 statuslog created during an previous replication operation
38 (--statuslog) is not specified.
42 The filesystem to which the source filesystem is replicated. Mandatory
43 if a valid statuslog created during an previous replication operation
44 (--statuslog) is not specified. This option can be repeated if
45 multiple replication targets are desired.
49 The metadata device which is to be replicated. Changelogs must be
50 turned on on this device. Mandatory if a valid statuslog created
51 during an previous replication operation (--statuslog) is not
56 The changelog user id. See lctl(8) changelog_register. Mandatory if a
57 valid statuslog created during an previous replication operation
58 (--statuslog) is not specified.
62 A status log file to which the status of replication is saved. At the
63 time of initialization, the state from a previous replication
64 operation which was saved, can be read and reused.
66 If a statuslog from a previous replication operation is specified, the
67 otherwise mandatory options like --source, --target and --mdt may be
70 By specifying the options like --source, --target and --mdt in
71 addition to the --statuslog option, the parameters in the statuslog
72 can be overridden. The command line options take precedence over the
73 ones from the statuslog.
77 Specify whether extended attributes are replicated or not. The default
78 is to replicate extended attributes. Disabling xattrs will mean that
79 striping information will not be replicated.
83 Produce a verbose output.
87 Shows what the program would do without actually replicating data.
92 Register a changelog consumer for MDT lustre-MDT0000
93 $ ssh $MDS lctl changelog_register --device lustre-MDT0000 -n
98 Replicate the lustre filesystem /mnt/lustre to /mnt/target.
99 $ lreplicate --source=/mnt/lustre --target=/mnt/target \\
101 --mdt=lustre-MDT0000 --user=1 \\
103 --statuslog replicate.log --verbose
105 Lustre filesystem: lustre
107 MDT device: lustre-MDT0000
113 Statuslog: replicate.log
115 Changelog registration: cl1
117 Starting changelog record: 0
121 lreplicate took 1 seconds
123 Changelog records consumed: 22
128 After the filesystem undergoes some changes, replicate the \
129 changes. Only the statuslog needs to be specified as it has all the \
130 parameters passed earlier.
132 $ lreplicate --statuslog replicate.log --verbose
134 Replicating Lustre filesystem: lustre
136 MDT device: lustre-MDT0000
142 Statuslog: replicate.log
144 Changelog registration: cl1
146 Starting changelog record: 22
150 lreplicate took 2 seconds
152 Changelog records consumed: 42
156 To replicate the lustre filesystem /mnt/lustre to /mnt/target1 and /mnt/target2.
157 $ lreplicate --source=/mnt/lustre \\
159 --target=/mnt/target1 --target=/mnt/target2 \\
161 --mdt=lustre-MDT0000 --user=cl1
163 --statuslog replicate.log
168 The lreplicate command is part of the Lustre filesystem. Contact
169 http://www.lustre.org/