Skip to content

InterLink

gitsync edited this page Nov 17, 2026 · 2 revisions

InterLink links multiple ZNAS servers together. Once linked, you can manage a remote server from your local portal, push ZFS replication between servers without SSH key juggling, and see remote backups and topology in one view.

What InterLink gives you

Capability Description
Remote view (relay) Pick any linked server from the hostname dropdown (top-left, under the logo) — the entire UI switches to that server, live, through your local portal
Push replication Replicate datasets to a peer as a snapshot policy target — credentials handled automatically over HTTPS
Remote VM backups Back up instances to a peer's datastore; browse them on the Backups page of either side
Topology across servers Linked peers appear as remote nodes on the Topology map, connected to the shares/datasets they receive
Alert propagation Live alerts from linked servers surface in your session

Linking two servers

  1. On the receiving server: Settings → InterLink → enable Accept incoming InterLink connections → copy the enrollment token
  2. On the sending server: Settings → InterLink → Add Peer → enter a name, the peer URL (https://<ip>:8443), and the token → Connect

The servers exchange credentials once; everything afterwards runs over mutually authenticated HTTPS. No SSH keys to create, distribute, or rotate.

Remote view (relay mode)

Select a peer in the hostname dropdown to relay into it:

  • All pages — storage, virtualization, terminal, even VM consoles — operate on the remote server
  • Your current page is kept when switching servers if it exists there (e.g. viewing a datastore, then switching, lands on the same datastore page of the peer)
  • Background jobs keep running on their home server; switching views never interrupts them

Push replication via InterLink

Create a snapshot policy on the Protect page with an InterLink replication target: choose the peer and destination dataset, and each scheduled snapshot is pushed after it is taken. Transfers are incremental and resumable; retention on the destination follows the policy.

Replication mode comparison

Feature Local Remote SSH InterLink
SSH key management — Manual None (automatic)
Transport Local SSH HTTPS (TLS)
Resumable Yes Yes Yes
Target must be ZNAS No No Yes
Remote view / relay — — Yes

Health and repair

Manage InterLink tries every link with real signed requests each time you open it. Nothing changes unless you click a repair.

Check What a problem means Repair
Link key The two servers hold different keys, so every request is refused Repair link: needs an admin login on the other server. The link keeps its settings
Link IDs Unlinking from one side won't remove the other Repair link
Reaches us The other server has no way back to this one, often a missing route Fix the route on the network
Certificate The other server's certificate isn't the pinned one, or none is pinned Review certificate or Pin certificate. Accept a change only if you reinstalled or renewed it. Until then, no signed request is sent to that server
Clock Signed requests are refused when clocks differ by more than a few seconds to 30 seconds Fix the time on one server
Your account Your login doesn't exist there Create account
ZFS access Pushes to that server may fail Repair
Incus trust VM and container pushes may fail Sync trust

All links shows how each server reaches every other, including pairs this server isn't part of. Link creates a missing link, with an admin login on the target server. A question mark means this server can't ask that one.

Accounts compares accounts and roles across servers. Create makes a portal login with the same role, with the same password or a new one. Only a password hash is sent. No SSH or file sharing account is made and 2FA isn't copied. A different role is only highlighted: it may be deliberate.

A red Key mismatch in the All links grid has its own Repair button, including for a pair of other servers. It needs an admin login on the server the link points to, and your account must be allowed on the server that holds the link.

Every server needs this version for the full check. An older one shows Older version, and it can't take a repaired key: update it first.

Troubleshooting

"Your account does not exist on that server" now appears only when it's true. For any other failure, the switch says why and offers to open Manage InterLink.

Problem Solution
Enrollment fails Check the token hasn't expired and the peer URL is reachable from the sending server
Peer shows offline Verify the receiving portal is running and port 8443 is open between the servers
Push stalls Check destination pool free space; review the job in Activity & Events on both sides

Clone this wiki locally