• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2475
  • Last Modified:

Netapp 3140: Why did the volume go offline?

The volume containing our exchange LUN went offline today.  A consultant brought it back online and remounted the LUN.  But he said he did not know what caused the Volume to go offline.  How would one approach finding the root cause of this?  Thank you.
0
amigan_99
Asked:
amigan_99
  • 3
  • 2
1 Solution
 
Paul SolovyovskyCommented:
There are several reasons the LUN can go offline, most of the time this is caused by:

1. Volume in the OS running out of space - Evident in OS
2. LUN is fragmented and due to fragmentation runs of out of space on Netapp volume
3. LUN and snapshots run make run out of space on Netapp volume  

There should be logs one why this happened, if the consultant can't figure out you may want to seek additional help.

For item #2 run space reclamation from Snapdrive.  As the Netapp LUN is actually a file inside of a Netapp volume (hence the "filer" terminology) it may get fragmented especially if you're running sql/exchange logs or backups that get added and deleted frequently.

For #3 Review your snapshots and and storage used on the Netapp volume.

What type of data is on this volume? Are you using snapdrive?
0
 
Paul SolovyovskyCommented:
Also run a quick check

in CLI run "rdfile /etc/messages" if happened recently, otherwise it may be messages.0, messages.1 file.  This should have the error that caused it dismount
0
 
amigan_99Author Commented:
Looks like I asked this before getting the full story from the engineer who fixed this.  What happened was that the LUNs disappeared from the Exchange server.  So he took the volumes offline and then put them back online.  Then he went into the Exchange server and remapped the LUN.  So seems more like a snap drive problem or something like that.  There were some errors evidently in Windows complaining about "signature"?  There was enough space at the LUN and Volume levels.  Any thought on why drives might disappear from a Windows VM causing Exchange to lose access to its database?  Thank you both for the pieces you've already contributed.  I am sure I will use that too.
0
 
Paul SolovyovskyCommented:
Typically signature errors happen when you inadvertently map a LUN to two different servers and they give it their own singnature.  I've never had this issue with Snapdrive, make sure you have host utilities on the server, if using iscsi you need the appropriate patches and iscsi tools as well.  If running snapmanager make sure you don't have snapshots that are getting stuck and no FC or iscsi connectivity issues.
0
 
amigan_99Author Commented:
A snapshot issue is a distinct possibility.  At 04:31 there was a snap shot deletion.  And the LUNs went offline at 04:33.  Now there have been many successful automated snapshot deletions prior to this.  So that time association could just be coincidence.  We use iSCSI.  Will run thought your other suggestions.  Thanks again Paul.  You rock.
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now