IREPL(1)

IREPL(1) 💅

Okay so welcome to the irepl manual page, bestie — manual section 1, User Commands, an iRODS iCommand. ✨

NAME 🌸

irepl — an iRODS iCommand

SYNOPSIS 🎀

irepl [-aMPrTvV] [-n replNum] [-R destResource] [-S srcResource]
      [-N numThreads] [-X restartFile] [--purgec] dataObj|collection ...

DESCRIPTION 🦋

Replicate a file in iRODS to another storage resource. That's the whole mission, no cap.

The -X option specifies that the restart option is on and the restartFile input specifies a local file that contains the restart info. If the restartFile does not exist, it will be created and used for recording subsequent restart info. If it exists and is not empty, the restart info contained in this file will be used for restarting the operation.

Note that the restart operation only works for uploading directories and the path input must be identical to the one that generated the restart file.

The -T option will renew the socket connection between the client and server after 10 minutes of connection. This gets around the problem of sockets getting timed out by the firewall as reported by some users.

The -R option cannot be used to target a destination resource that is a child resource within a resource hierarchy. Doing so will result in a DIRECT_CHILD_ACCESS error. Child resources are managed and their replication policy is handled by their hierarchy.

Note that if -a and -U options are used together, it means update all stale copies.

Note that if the source copy has a checksum value associated with it, a checksum will be computed for the replicated copy and compare with the source value for verification.

Note that replication is always within a zone. For cross-zone duplication see irsync which can operate within a zone or across zones.

To specify a specific replica to use as a source for replication, use -n and indicate the replica by its replica number. If that replica cannot be used as a source for replication for any reason, replication will fail.

To specify that a replica in a specific resource hierarchy should be used as a source for replication, use -S and indicate the root resource of the hierarchy. If no replica in the hierarchy can be used as a source for replication for any reason, replication will fail.

-S and -n are incompatible options.

Options are: 🛠️

• -a — all - if used with -U, update all stale copies
• -P — output the progress of the replication.
• -U — Update (Synchronize) an old replica with the latest copy. (see -a)
• -M — admin - admin user uses this option to backup/replicate other users files
• -N — number specifies the number of I/O threads to use, by default a rule is used to determine the best value.
• -r — recursive - copy the whole subtree
• -n — replNum - specifies the number of the source replica to use for replication.
• -R — destResource - specifies the destination resource to store to. This can also be specified in your environment or via a rule set up by the administrator.
• -S — srcResource - specifies the source resource of the data object to be replicated. Must refer to a root resource.
• -T — renew socket connection after 10 minutes
• -v — verbose
• -V — Very verbose
• -X — restartFile - specifies that the restart option is on and the restartFile input specifies a local file that contains the restart info.
• --purgec — Purge the staged cache copy after replicating an object to a COMPOUND resource
• -h — this help

Also see 'irsync' for other types of iRODS/local synchronization.

---

okay that's the whole page, bestie — iRODS Version 5.0.2, source irepl iRODS-5.0.2, dated January 1980, manual IREPL(1). byeee 💖