lreplicate(8) Lustre Filesystem replication utility lreplicate(8) NAME lreplicate - Utility to replicate a Lustre Filesystem SYNOPSIS lreplicate --source|-s --target|-t --mdt|-m [--user|-u ] [--xattr|-x ] [--verbose|-v] [--statuslog|-l ] [--dry-run] [--abort-on-err] lreplicate --statuslog|-l lreplicate --statuslog|-l --source|-s --target|-t --mdt|-m DESCRIPTION lreplicate can be used to replicate a lustre filesystem (source filesystem) to another target filesystem (any filesystem type). It is required that changelogs be enabled on the source filesystem (see lctl (8)). The source and the target filesystems must be identical before changel- ogs are enabled. If the source filesystem has been populated before turning on changelogs, a utility like rsync may be used to make them identical. OPTIONS --source= The source filesytem which will be replicated. Mandatory if a valid statuslog created during an previous replication operation (--status- log) is not specified. --target= The filesystem to which the source filesystem is replicated. Mandatory if a valid statuslog created during an previous replication operation (--statuslog) is not specified. This option can be repeated if multiple replication targets are desired. --mdt= The metadata device which is to be replicated. Changelogs must be turned on on this device. Mandatory if a valid statuslog created during an previous replication operation (--statuslog) is not specified. --user= The changelog user id. See lctl(8) changelog_register. Mandatory if a valid statuslog created during an previous replication operation (--statuslog) is not specified. --statuslog= A status log file to which the status of replication is saved. At the time of initialization, the state from a previous replication operation which was saved, can be read and reused. If a statuslog from a previous replication operation is specified, the otherwise mandatory options like --source, --target and --mdt may be skipped. By specifying the options like --source, --target and --mdt in addition to the --statuslog option, the parameters in the statuslog can be over- ridden. The command line options take precedence over the ones from the statuslog. --xattr Specify whether extended attributes are replicated or not. The default is to replicate extended attributes. Disabling xattrs will mean that striping information will not be replicated. --verbose Produce a verbose output. --dry-run Shows what the program would do without actually replicating data. --abort-on-err Stop processing upon first error. Default is to continue processing. EXAMPLES Register a changelog consumer for MDT lustre-MDT0000 $ ssh $MDS lctl changelog_register --device lustre-MDT0000 -n 1 Replicate the lustre filesystem /mnt/lustre to /mnt/target. $ lreplicate --source=/mnt/lustre --target=/mnt/target \ --mdt=lustre-MDT0000 --user=1 \ --statuslog replicate.log --verbose Lustre filesystem: lustre MDT device: lustre-MDT0000 Source: /mnt/lustre Target: /mnt/target Statuslog: replicate.log Changelog registration: cl1 Starting changelog record: 0 Errors: 0 lreplicate took 1 seconds Changelog records consumed: 22 After the filesystem undergoes some changes, replicate the changes. Only the statuslog needs to be specified as it has all the parameters passed earlier. $ lreplicate --statuslog replicate.log --verbose Replicating Lustre filesystem: lustre MDT device: lustre-MDT0000 Source: /mnt/lustre Target: /mnt/target Statuslog: replicate.log Changelog registration: cl1 Starting changelog record: 22 Errors: 0 lreplicate took 2 seconds Changelog records consumed: 42 To replicate the lustre filesystem /mnt/lustre to /mnt/target1 and /mnt/target2. $ lreplicate --source=/mnt/lustre \ --target=/mnt/target1 --target=/mnt/target2 \ --mdt=lustre-MDT0000 --user=cl1 --statuslog replicate.log AUTHOR The lreplicate command is part of the Lustre filesystem. Contact http://www.lustre.org/ SEE ALSO lctl(8), lfs(1) Lustre 2009 Apr 08 lreplicate(8)