Sendense Documentation

Which route is my replication sync using, and why?

The pattern's route policy decides per sync: direct when reachable, via SHA otherwise.

Documents Home
Product DocumentationDeployment GuidesOperationsRecovery & DRKnowledge Base
Documentation/Recovery & DR

Reference

Which route is my replication sync using, and why?

The pattern's route policy decides per sync: direct when reachable, via SHA otherwise.

ReadyCurrentreplicationroutingdr

The Short Answer

The replication route policy on the pattern decides, and it is evaluated for every sync. With Automatic (the default), Sendense uses the direct site-to-site route when the target SNA is reachable - verified by a live probe from the source SNA - and otherwise sends that sync through the encrypted appliance connections via SHA.

Via SHA forces the hub route. Direct P2P forces the direct route and fails the sync with an error if the probe fails, rather than silently rerouting.

What That Means Day To Day

  • A temporarily unreachable direct path makes Automatic fall back for that sync; later syncs return to the direct route when reachability is restored.
  • Both routes end the same way: the target SNA receives the stream and passes it to the Sendense Controller for that VM.
  • SHA orchestrates every sync on either route.

Related Docs

Replication Transport And RoutingHow DR replication data moves between sites: the hub-routed path via SHA, the direct site-to-site path, and how routes are chosen.Replication PatternsThe policy layer for controller-backed replication and disaster-recovery target readiness.