Deployment and Management Guide for Cisco IoT FND on OVA with Postgres and InfluxDB, Release 5.x.x and Later

HA and DR for Cisco IoT FND with Postgres

Updated: February 4, 2026

Overview

Use this topic to understand high availability (HA) and disaster recovery (DR) options for Cisco IoT Field Network Director (FND) when using a Postgres database.

High Availability (HA) and Disaster Recovery (DR) for Cisco IoT FND with PostgreSQL are designed to ensure that the Cisco IoT FND system remains continuously operational and resilient to failures, such as server crashes, database outages, or even complete data center failures.

Replaces a single‑node database deployment with an enterprise‑grade, distributed PostgreSQL architecture
introduces redundancy at every critical layer database, application, and network access.

Table 1. Feature history
Feature name	Release	Description
HA and DR for Cisco IoT FND with Postgres	Cisco IoT FND Release 5.1.1	HA and DR for Cisco IoT FND with PostgreSQL ensure the system remains operational and resilient against failures, including server crashes, database outages, and data center disruptions.

Benefits

Keeps Cisco IoT FND running even during server, database, or infrastructure failures, ensuring uninterrupted network management.
Database and application components automatically switch to healthy instances without manual intervention, reducing recovery time.
Distributed PostgreSQL replication safeguards critical data and minimizes the risk of data loss during failures or outages.
Supports disaster recovery across multiple sites, allowing operations to continue even if an entire data center becomes unavailable.
Designed for large-scale IoT deployments, providing a robust and scalable foundation that supports future growth and mission‑critical operations.


Aspect	Standalone Setup	HA Setup
Deployment Model	Single Cisco IoT FND with PostgreSQL OVA	Multiple servers deployed across multiple data centers
Database	Single-node PostgreSQL (no HA)	Enterprise-grade distributed PostgreSQL
Failover Capability	No automatic failover	Automatic failover across components
Application Servers	Single FND application server	Redundant, active FND application servers
Traffic Routing	Direct access to a single instance	DNS-based traffic routing to active instance
Failure Handling	Manual recovery required	Automatic takeover by healthy components

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.