Hi all,
When I run the following command -
C:\Program Files\NetApp\SnapDrive\sdcli.exe snap mount -r mosssqlp1 -k F -s sqlsnap__mosssqlp1__recent -d Q
I get the following error -
Initializing...Unable to connect to the virtual disk in snapshot. Error : Not enough storage is available to complete this operation.
Which is quite different from -
Error description: No space left on device.
Which is what I get on a full volume - so its completely understandable. The 'Error : Not enough storage is available to complete this operation' would appear to be a red-herring (ie nothing to do with storage or the SAN per se but some oddball way of Windows 2003 telling me theres some other problem.
The annoying error seems to indicate a possible rpc problem in Windows rather than with SnapDrive itself. The same script on the same machine will happily mount snaps from other machines for backup purposes and I can't really pinpoint why its not mounting these snaps. If it does turn out to be an rpc issue could it be that the domain account on the server under which SnapDrive runs cannot be validated on this box ?
I still haven't got my head around how sdcli talks to the SAN - if I have a backup server mounting snapshots of luns being used on other systems does it need to be able to talk to the system using the luns - why can't it deal direct with the SAN ?
Thanks in advance for any tips or toubleshooting suggestions.
Cheers, Raj.
Hi Raj,
On Nov 16, 2007 2:27 AM, Raj Patel phigmov@gmail.com wrote:
When I run the following command -
C:\Program Files\NetApp\SnapDrive\sdcli.exe snap mount -r mosssqlp1 -k F -s sqlsnap__mosssqlp1__recent -d Q
I get the following error -
Initializing...Unable to connect to the virtual disk in snapshot. Error : Not enough storage is available to complete this operation.
To see what happens here, it might be an idea to do what snapdrive does for you, but then on the ONTAP cli, being:
1) Create a snapshot backed lun: lun create -b <snap>> <newlunname> IIRC 2) Check if an igroup is available that contains just your one system. If not, create it. 3) Map the lun to the needed igroup
If that all happens on the CLI without any problems, you just have excluded the volume as a possible source of the problems ... :)
My suspicion is that you have no available space in your volume due to flexible reservations being high enough to reserve all free space.
Kind regards,
Nils
When in doubt reboot - fixed the issue.
The system was dual homed (nic on the SAN network and a nic on the Data network) - suspect the nics got confused when they came up and started misdirecting rpc traffic.
Cheers, Raj.
-
Nils Vogels -
Raj Patel