| 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:
-namestring- Only apply command to snapshots that match name.
-categorystring- Only apply command to snapshots that match category.
-environmentstring- Only apply command to snapshots that match environment.
-perimeterstring- Only apply command to snapshots that match perimeter.
-jobstring- Only apply command to snapshots that match job.
-tagstring- Only apply command to snapshots that match tag.
-latest- Only apply command to latest snapshot matching filters.
-beforedate- Only apply command to snapshots matching filters and older than the specified date. 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).
-sincedate- Only apply command to snapshots matching filters and created since the specified date, included. 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
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
| April 18, 2025 | Plakar |