Good morning,
I'm wondering if anybody has experience the below behavior, and how they managed to avoid it happening.
We had several LUNS on one SQL Failover cluster instance and wanted to remove a couple.
We performed the following steps.
1) Located the service we wished to remove the LUNS from and expanded it. 2) Checked that any dependencies were removed. 3) Right clicked each of the LUNS we wished to remove and selected "Take this resource offline"
Once all the LUNS were set to "OFFLINE" we right clicked on one of these LUNS and selected "Remove from SQL Server (Instance)".
What happened next was VERY worrying... every single "OFFLINE" LUN within the service removed itself and went back to "Available Storage".
While this was the intended outcome, we are extremely concerned as to how every LUN removed itself at once... We are doubly concerned that we might have lost the ONLINE LUNS, or that LUNS which were intended to be left were also removed.
Has anybody else seen this behavior? Is there a way to prevent this?
Regards,