Natrinsic Supplemental Netezza Documentation
Shutdown or Decommission of Netezza Appliances
Preface & Disclaimer
This document provides a high level overview of the administrative and optionally physical steps to take when shutting down or decommissioning a Netezza appliance.
Natrinsic offers this guide only as a general overview; each customer may have unique requirements which cannot be covered in a general guide and as such Natrinsic does not warrant or guarantee the accuracy or completeness of this documentation. Natrinsic will have no liability for any damages arising from the misuse of any information provided in this document. Natrinsic also does not warrant or guarantee that any external links to third party websites will be active, correct or applicable for your situation.
Comments and Questions
If you require further clarification on the contents of this guide, you may reach us via email at: firstname.lastname@example.org with the subject line “General Support Inquiry”. Within the body of your email, provide your company name, your position and the system identifier of at least one system for which you have a current support contract. (e.g. NZ123456)
Pre-shutdown tasks of the Netezza Appliance
Prior to shutting down your appliance, it is recommended to complete the following database related tasks.
nzhostbackup /home/host/nzhostbackup.<datatimestamp>.tar.gz (system downtime is required)
nzbackup -history (ensure backup sets of critical DBs are secured on a SAN or NFS backup filesystem)
Audit database should be configured via '/nz/kit/bin/adm/nzhistcreatedb [options]' and DBA to review users' activities and historical query statistics
Shutdown of a Netezza Appliance - Platform tasks
Assuming that you have performed the pre-shutdown tasks, execute the following steps to shutdown and power-off
- Collect ‘head -25 /etc/hosts’ for IP addresses of HA1/HA2/VIP/HA1_IMM/HA2_IMM
- ensure no jobs are currently running (review output of nz_responders)
- nzstop (stop Netezza DB)
- ssh 'ha2 service heartbeat stop' (stop standby host heartbeat service / assume HA2 is standby host by default if HA1 is standby host then stop heartbeat from HA1 first)
- service heartbeat stop (stop primary host heartbeat service / assume HA1 is primary host by default if HA2 is primary host then stop heartbeat from HA2 after HA1 heartbeat service is stopped)
- 'chkconfig drbd on;chkconfig heartbeat on' (turn off HA1 drbd and heartbeat daemon at run level settings)
- ssh ha2 'chkconfig drbd on;chkconfig heartbeat on' (turn off HA2 drbd and heartbeat daemon at run level settings)
- ssh ha2 'shutdown -h now' (gracefully shut down standby host then check shutdown progress through IMM remote console if possible)
- shutdown -h now' (gracefully shut down standby host then check shutdown progress through IMM remote console if possible)
Decommissioning of a Netezza Appliance
Assuming that you have completed the pre-shutdown tasks, and platform shutdown tasks, execute the following:
- screen /opt/nz/fdt/storage_diags diskeraser --method clear (can take up to 12 hours per clearing pass)
- screen /opt/nz/fdt/storage_diags diskeraser --method dod3pass (based on client's requirement)
- nzinitsystem -reinit (reinitialize the system and restore the setting to manufacture default)
- nzstart -newsystem (When the nzstart -newsystem brings the system Online the previous data on the SPU disks will not be seen)
- ssh 'ha2 service heartbeat stop'
- service heartbeat stop
- pull out all the disks (containing /nz filesystem for catalog and several backup sets and log files) from both host server to scrap