An RLINK is stale when the Secondary data volumes do not contain the Primary's data and cannot be brought up-to-date using the SRL. When an RLINK is first created, its initial state is stale.
RLINKs can enter the
STALE state when they are detached either manually (via
vxrlink det) or by the kernel (on the Primary only, if an SRL media error occurs). An RLINK can also become stale if the log overflows. See The srlprot attribute for a description of cases where the log overflows and what can be done to prevent it.
To change the state of an RLINK from stale to active, see Using the automatic synchronization feature and Example—Synchronizing the Secondary using block-level backup.