Optical Prime Destroy Cluster Disk in a Project

Overview

The Optical Prime Live Optics software can identify and differentiate locally attached disks and disk clusters within individual devices using unique LUN naming IDs and disk serial numbers assigned to disks and any applicable clusters.  In rare instances, there may be a need to break a cluster disk and list each node of the cluster as a local disk for each device.  This is a change in the capacity statistics within the Live Optics project.  This change will not affect the disk performance statistics (IOPS, latency, throughput, etc).

The Live Optics portal has added a feature that will allow you to destroy a cluster disk and list each disk node as a local disk for its server.  This feature should make it easier to repair any incorrect disk associates with a project.

Below are the instructions for how to destroy a cluster disk in a Live Optics project.

Prerequisite Information

• The Live Optics project has already been created from one or more Live Optics collector runs
• Access to a Live Optics account should already be complete before beginning the following steps.

 Access Performance View of project

• Locate project to view and click on the name at the top
• Once the project opens, click on the Performance View tab

Open Live Optics Cluster Disk Modal

• To destroy a cluster disk from a Live optics project, locate the cluster disk under "Shared Cluster Disks and click onto it.  In the right window under the details of the selected cluster disk, click the "Modify Disk" link.

Click "Destroy" button to remove cluster

• To create a breakup the cluster disk and add its drives back to each server as a local disk, click the "Destroy" button at the bottom of the modal window and click "Yes" when prompted for confirmation. 

• Click "Yes".

Review new cluster disk

• Once the disk cluster has been "destroyed", a prompt will show up that the operation was successful.  The destroyed cluster will no longer appear in the "Shared Cluster Disk" list, the disk nodes in the cluster will be changed for each server involved, and the project will recalculate its statistics.