Follow these steps to manually failover a disk in Netezza:
Step 1: Check for the disk to be failed over (hwid 1355) and ensure it has a healthy mirror available.
MyServer:/export/home/nz->nzds -id 1355
Data Slice Status SPU Partition Size (GiB) % Used Supporting Disks
———- ——- —- ——— ———- ——
23 Healthy 1421 7 356 79.92 1138,135524
Healthy 1421 6 356 79.84 1138,1355
Step 2: Identify the SPA in which this disk is located.
MyServer:/export/home/nz->nzhw -type Disk | grep 1355
Disk 1355 spa1.diskEncl4.disk6 Active Ok
Step 3: Make sure we have a spare available in the SPA identified in above step.
MyServer:/export/home/nz->nzhw -type Disk | grep Spare
Disk 1582 spa3.diskEncl1.disk12 Spare Ok
Disk 1586 spa4.diskEncl1.disk8 Spare Ok
Disk 1621 spa2.diskEncl3.disk10 Spare Ok
Disk 1622 spa2.diskEncl1.disk10 Spare Ok
Disk 1623 spa1.diskEncl4.disk7 Spare Ok
Disk 1624 spa4.diskEncl4.disk3 Spare Ok
Disk 1625 spa3.diskEncl3.disk7 Spare Ok
Disk 1626 spa1.diskEncl4.disk4 Spare Ok
Step 4: Check the system usage before you manually failover a disk.
MyServer:/export/home/nz->nz_responders
Cur Time Plan # Snippet Time S/P State Busy Dataslices ...
....
Step 5: Failover the disk.
mysqldmin netezza evict-disk 1356
Step 6: Verify that the disk has been assigned to a new SPA and is in the assigning state.
MyServer:/export/home/nz->nzhw -issues
HW ID Location Role State
....
Disk 1355 spa1.diskEncl4.disk6 Failed Ok
Disk 1623 spa1.diskEncl4.disk7 Assigned Ok
Step 7: Monitor the regen status until it is complete.
MyServer:/export/home/nz->nzds -regenstatus
Data Slice Status SPU Partition Size (GiB) % Used Supporting Disks Start Time % Done
....
Once the regen status is complete, the new disk will be fully functional and synced with the rest of your Netezza system.
Manually Failover a Disk in Netezza
Introduction
This guide will walk you through the process of manually failing over a disk in Netezza. This procedure is typically used when a failure occurs with a disk and needs to be addressed immediately.
Requirements
Access to Netezza System Manager (NSM)
Knowledge of the affected disk's details (slot number, node name, etc.)
Steps
Identify the Affected Disk: Use NSM to identify the slot number and node name of the affected disk. You can do this by navigating to the Disks tab, finding your system, and then identifying the disk in question.
Disk Identification in Netezza System Manager
Isolate the Node: To prevent data corruption, isolate the node that contains the affected disk. This can be done by running the following command in NSM:
```
admin isolate [node_name]
```
Remove the Failed Disk: Once the node is isolated, you can safely remove the failed disk using NSM's GUI or command line interface.
- **GUI:** Click on the disk in NSM and select the 'Remove' option.
- **CLI:** Run the following command:
```
admin disk remove [slot_number] [node_name]
```
Insert the New Disk: After removing the failed disk, replace it with a new one. Insert the new disk into the appropriate slot and node.
Add the New Disk: To add the new disk to your system, use NSM's GUI or command line interface.
- **GUI:** Click on the 'Add' button in the Disks tab and follow the prompts to add the new disk.
- **CLI:** Run the following command:
```
admin disk add [slot_number] [node_name]
```
Re-establish Connectivity: Once the new disk has been added, re-establish connectivity between the node and the rest of the system. This can be done by running the following command:
```
admin network link up [node_name]
```
Validate the New Disk: Use NSM to verify that the new disk has been added correctly and is functioning properly.
New Disk Verification in Netezza System Manager
Conclusion
Manually failover a disk in Netezza can be a critical task when dealing with hardware failures. By following these steps, you can safely remove the failed disk, add a new one, and ensure data integrity within your system.