Sync Operations
Sietch's sync capabilities allow you to transfer encrypted data between vaults - even when internet connectivity is unavailable or unreliable. This page explains the different sync methods and how to use them effectively.
Understanding Sync Methods
Sietch offers multiple ways to synchronize your vaults:
Direct TCP Sync
Fast and reliable vault synchronization over local networks or direct connections.
LibP2P Sync
More robust sync with NAT traversal for more complex network situations.
Sneakernet
Physical transfer of vault chunks via USB drives or other media - for airgapped machines or highly restricted networks.
Basic Sync Command
sietch sync
The core command for synchronizing your vault with peers.
Options:
Option | Type | Description |
---|---|---|
--peer | string | Peer address to sync with |
--direction | string | Sync direction: pull , push , or both (default) |
--resilient | flag | Enable resilient mode for unstable connections |
--paths | string | Specific paths to sync |
--dry-run | flag | Preview sync without changes |
# Sync with a peer on the local network
sietch sync --peer 192.168.1.42
Finding Peers
sietch discover
Automatically find other Sietch vaults on the local network.
- Uses UDP broadcast messages to find peers
- Works on local networks without internet
- Shows vault IDs and IP addresses of discovered peers
Options:
Option | Type | Description |
---|---|---|
--timeout | duration | How long to search (default 5s ) |
--json | flag | Output in JSON format |
sietch peer
Manually manage known peers.
# Add a known peer
sietch peer add 192.168.1.42
Trust is Critical
Offline Sync (Sneakernet)
For airgapped machines or censored networks, Sietch supports transferring data using physical media:
sietch export
Export vault chunks for offline transfer.
Sync Strategies
Common Sync Patterns
Star Topology
One central vault syncs with multiple peers, creating a hub-and-spoke pattern.
# Run on the central vault
sietch peer list # View all connected peers
sietch sync --all # Sync with all known peers
Mesh Network
Every vault syncs with multiple others, creating redundancy.
# Add multiple peers
sietch peer add 192.168.1.40
sietch peer add 192.168.1.41
sietch peer add 192.168.1.42
# Sync with each
sietch sync --peer 192.168.1.40
sietch sync --peer 192.168.1.41
sietch sync --peer 192.168.1.42
Checkpoint Sync
Periodic syncs on schedule to ensure data redundancy.
# In a cron job or scheduled task
sietch sync --peer 192.168.1.42 --paths /critical-data/
Advanced Sync Features
sietch sync-status
Check the sync status of your vault.
This command shows:
- Last successful sync time with each peer
- Number of pending changes
- Sync health metrics
sietch resolve-conflicts
Handle sync conflicts between vaults.
How Conflict Resolution Works
Troubleshooting Sync Issues
- Connection refused: Check if peer is running and accessible; verify IP addresses
- Sync halts midway: Use
--resilient
flag for unstable connections - Permission denied: Check vault permissions
- Encryption errors: Ensure both vaults have necessary encryption keys
Learn how the Security Model protects your data during sync operations.