A plan step that keeps pinging a recovered machine and its network adapters until replies are steady or time runs out. It is used during failover, failback and DataLab testing.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains Check Networks in context, with comparison tables and the common traps.
Terms in this definition
- Agents (classic) API
First-generation Foundry Agent Service API, based on threads, messages and runs. It is deprecated, replaced by conversations and responses, and retires on 31 March 2027.
- failover
Switching workloads from production VMs over to replicas at the recovery site; replica, CDP replica and storage plans do this. The plan is left in FAILOVER until it is undone, made permanent or followed by failback.
- failback
Moving workloads home from replicas, either onto the original VMs (updated to match the replicas' latest state) or onto VMs somewhere new. Being provisional, it ends with a commit or a roll-back to FAILOVER.
- DataLab
An isolated sandbox for rehearsing plans, based on a virtual lab in Veeam Backup & Replication. Orchestrator boots machines there, runs plan steps and application checks, then reports on the outcome.
Related terms
- Verify Domain Controller Port
Confirms that a recovered domain controller answers on port 389 (LDAP). Put it later in the sequence than Check Networks.
- Verify Global Catalog Port
Checks port 3268 on a recovered VM that has the Global Catalog role. Place it after the Check Networks step.
- VMNIC
A virtual machine's network adapter. Check Networks pings both the machine and each VMNIC, waiting for steady replies or giving up when time runs out.