Ensure the same content is replicated
Capture all SQL transactions that result in changes to data in the replicated databases on the master Netezza node. Save those transactions in a replication log including changes that insert, delete, or update data. Additionally, capture changes that add, delete, or update information about users. The replication log contents are automatically transmitted to all Netezza subordinate nodes in the replication set.
Survive critical hardware failures
Having a master and one or more subordinates can provide data availability even if a Netezza appliance is offline or unreachable. The subordinate nodes act as “warm standbys” for system failure or for planned downtime at the master node. If data on a Netezza appliance is lost, such as due to a network outage or multiple hardware failures, the replication set has sufficient redundant copies to recover.
Support multiple SQL queries
The replication approach to disaster recovery has an additional benefit. Because multiple copies of the database are distributed across several Netezza appliances, the configuration supports more SQL queries running against the same data. Subordinate nodes also provide concurrent BI and reporting access to synchronized data stores, thus allowing workload distribution, balancing and optimization.
Replicate across networks
User a replication log server to store replication logs and distribute copies across your network to other replication log servers. A replication log server stores the replication log and copies it across the network to other replication log servers. Each replication node, master or subordinate, in the replication services environment requires both a Netezza appliance and a replication log server. The Netezza appliance is the data warehousing device.