I can see the snapshots from the MMC, but I cannot mount them.
Is it possible that my snapshots are inconsistent or corrupt? Is there a consistency checker for snapshots? I would expect this to be obvious when I issue a snap list...
-----Original Message----- From: Glenn Walker [mailto:ggwalker@mindspring.com] Sent: Thu 10/11/2007 8:59 PM To: Skip Norman; toasters@mathworks.com Subject: RE: cannot mount snapshots
Nah - qtree is fine. SnapDrive has always looked for the share to be at the volume level, LUN can be in volume root or qtree root.
Can you see the snapshots from the MMC?
Looks like you've got some other issue, as expected (NetApp support would have been able to remedy the CIFS share location issue pretty quickly).
-----Original Message----- From: Skip Norman [mailto:snorman@alexza.com] Sent: Thursday, October 11, 2007 11:25 PM To: Glenn Walker; toasters@mathworks.com Subject: RE: cannot mount snapshots
Yes, the LUN is in a qtree; however, the CIFS share was created at the volume level. This is exactly the error I receive...but does this mean that the LUN is not supposed to be in a qtree? We currently have several other systems setup in this manner without any problems.
Thanks.
-----Original Message----- From: Glenn Walker [mailto:ggwalker@mindspring.com] Sent: Thu 10/11/2007 5:43 PM To: Skip Norman; toasters@mathworks.com Subject: RE: cannot mount snapshots
The LUN in a qtree? Any error message?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb27000
Glenn
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Skip Norman Sent: Thursday, October 11, 2007 7:38 PM To: toasters@mathworks.com Subject: cannot mount snapshots
Has anyone come across snapshots that could not be mounted by snapdrive 4.2.1? I currently have a case open with support, but this is bugging the life out of me...
My current scenario is a windows 2003 sp2 server with 2 LUN's, one for a scientific application called waters empower (D:) and the other for the oracle database that is associated with it (E:). A backup script of the scientific application runs nightly and calls a script that creates a snapshot while the database is in hot backup mode. All of this seems fine and dandy until I try to mount the snapshot to backup the contents to tape.
Using sdcli I should be able to execute the following command via a script to mount the snapshot in preparation for writing it to tape: sdcli snap mount -k d -s snap0 -d y
I have done some testing in which I tried to mount these snapshots from a remote server running snapdrive 4.2.1 as well and it was also unsuccessful. I also created a separate lun in which I took some snapshots of and I was able to mount it (this eliminates a problem with snapdrive on the machine and means to me that there is something happening to the snapshots that make them unmountable.)
What can I look for to see what is wrong with my snapshots? Snap list shows them to be normal...
Any thoughts would be appreciated.