Netezza systems N2001 and N3001 run on RedHat 6 which is past end of support. Bug fixes and security patches are currently only available for RHEL 8 and above. So what can customers still running those systems do to protect them from new vulnerabilities? We've found a way of doing exactly that...

Businesses that are still running Netezza Mako may be running out of space, but don't want the expense of migrating to a new system just yet. But might they consider merging 2 systems into 1 to get double the space and performance? In this blog we explain how.

First instinct when a vendor announces end of life support for a platform is to look at the latest technology offering with a natural assumption being that it will be faster, simpler and cheaper. The reality, however, is that often the current system is performing satisfactorily across all measures and moving off it will result in a lot of pain. What can you do?

Netezza clients are being told that there are no spare parts to be had anywhere for their Mako systems that are going out of support on April 10th of this year. Read why this is wrong, and what you can do to ensure your Mako keeps running whilst you consider your options.

Running older versions of your Netezza software may not result in any specific issues whilst the appliance is being supported by IBM, but that ceases to be the case after the IBM End of Support (EOS) date. Find out why.

In this article we will show how to create and deploy Nagios monitoring for Netezza system components.

There’s a sense of déjà vu with the recent announcement of the release of Cloud Pak for Data System (CP4DS) 1.0.7.8 (a.k.a Hammerhead). It has all the signs of a capitulation on the part of IBM to customers who want to continue with the idea of Netezza being a stand-alone appliance, and not have to share CPU resources with other components in a hyperconverged architecture.

The Netezza Mako N3001-## range reaches end of OEM support in 12 months. Here's a roundup of the products and services we offer to not only extend the life of your Mako but also to drastically reduce the overhead of managing the next generation of Netezza, whether on-premises, or in the Cloud.