PLAKAR-SYNC(1) | General Commands Manual | PLAKAR-SYNC(1) |
NAME
plakar-sync
—
Synchronize snapshots between Plakar
repositories
SYNOPSIS
plakar sync | [-name name]
[-category category]
[-environment environment]
[-perimeter perimeter]
[-job job]
[-tag tag]
[-latest ] [-before
date] [-since
date] [snapshotID]
to | from |
with repository |
DESCRIPTION
The plakar sync
command synchronize
snapshots between two Plakar repositories. If a specific snapshot ID is
provided, only snapshots with matching IDs will be synchronized.
The options are as follows:
-name
string- Only synchronize snapshots matching name.
-category
string- Only synchronize snapshots matching category.
-environment
string- Only synchronize snapshots matching environment.
-perimeter
string- Only synchronize snapshots matching perimeter.
-job
string- Only synchronize snapshots matching job.
-tag
string- Only synchronize snapshots matching tag.
-latest
- Only synchronize the latest snapshot.
-before
date- Only synchronize snapshots older than before. Accepted formats include relative durations (e.g. 2d for two days, 1w for one week) or specific dates in various formats (e.g. 2006-01-02 15:04:05).
-since
date- Only synchronize snapshots newer than since. Accepted formats include relative durations (e.g. 2d for two days, 1w for one week) or specific dates in various formats (e.g. 2006-01-02 15:04:05).
The arguments are as follows:
EXAMPLES
Synchronize the snapshot ‘abcd’ with a peer repository:
$ plakar sync abcd to @peer
Bi-directional synchronization with peer repository of recent snapshots:
$ plakar sync -since 7d with @peer
Synchronize all snapshots of @peer to @repo:
$ plakar at @repo sync from @peer
DIAGNOSTICS
The plakar-sync
utility exits 0 on
success, and >0 if an error occurs.
- 0
- Command completed successfully.
- >0
- General failure occurred, such as an invalid repository path, snapshot ID mismatch, or network error.
SEE ALSO
August 6, 2025 | Plakar |