Netezza Performance Server Replication Services 3.0.5.0 release notes

Version 3.0.5.0 addresses fixed issues.

Features

Role reversal for multiple databases
You can now perform role reversal on multiple databases using a single command. Databases can be listed as comma-separated values, and their progress can be tracked using the new nzdr job command.
Support for Netezza Performance Server lowercase settings
NRS now supports environments where Netezza Performance Server uses lowercase as the default for object names. This ensures consistent behavior when managing databases with lowercase naming conventions.
Kafka upgrade for improved stability
This release includes an upgraded version of Kafka, delivering enhanced stability and performance for replication processes.
TLS 1.3 encryption for replication traffic
Replication traffic is now secured using TLS 1.3, providing stronger encryption and improved security compliance.

Fixed issues

  • Commented lines in the backupHostname.txt configuration file are now correctly ignored during processing.
  • Databases that are out of sync or in a transient state can now be deleted using the force option, allowing them to be re-added without issues.
  • When a database is deleted, any pending ad hoc jobs are now automatically removed. This ensures proper storage cleanup and prevents out-of-sync conditions between primary and replica.
  • NRS containers on spare nodes now correctly pick up DNS entries, resolving previous issues with external host lookups during host node e1nx failover.
  • Fixed an issue that affected role reversal on systems restored from legacy Netezza Performance Server backups.
  • The -streams option is now supported in the local_config.json file.

Upgrade paths

You can upgrade directly to NRS version 3.0.5.0 from the following supported versions:
  • 3.0.4.0
  • 3.0.4.1
If your current NRS version is not listed above, you must first upgrade to one of the supported intermediate versions before proceeding to NRS 3.0.5.0.
Note: For detailed instructions on intermediate upgrades, refer to the migration paths provided in the documentation for those specific releases.