sync

PLAKAR-SYNC(1) General Commands Manual PLAKAR-SYNC(1)

plakar syncSynchronize snapshots between Plakar repositories

plakar sync[-name name] [-category category] [-environment environment] [-perimeter perimeter] [-job job] [-tag tag] [-latest] [-before date] [-since date] [snapshotID] to | from | with repository

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:

string
Only apply command to snapshots that match name.
string
Only apply command to snapshots that match category.
string
Only apply command to snapshots that match environment.
string
Only apply command to snapshots that match perimeter.
string
Only apply command to snapshots that match job.
string
Only apply command to snapshots that match tag.
Only apply command to latest snapshot matching filters.
date
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).
date
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:

| |
Specifies the direction of synchronization:
Synchronize snapshots from the local repository to the specified peer repository.
Synchronize snapshots from the specified peer repository to the local repository.
Synchronize snapshots in both directions, ensuring both repositories are fully synchronized.
repository
Path to the peer repository to synchronize with.

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

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.

plakar(1)

April 18, 2025 Plakar