2011-08-31 08:34 AM
I cannot access any of the snapshots on a Windows Mount Point. I can't see the hidden ~ directories, cannot access the previous version when I right click on the file, I just cannot access the snapshot I know is on the NetApp. I do not want to restore the entire volume and wipe out all other files just to restore 1 file.
Question is how do I access my SnapShots from the Windows host?
I have verified the same behavior on multiple systems:
Server 2008 R2
Server 2008 R2 on VMware
Server 2003 R2 hardware
All with SnapDrive 6.2
NetApp 3140 running 7.3.3P5
Current workaround is:
Thanks for any insight you can offer,
2011-08-31 09:33 AM
Hi Mike and welcome to the Community!
I cannot access any of the snapshots on a Windows Mount Point. I can't see the hidden ~ directories, cannot access the previous version when I right click on the file, I just cannot access the snapshot I know is on the NetApp.
...because it is a LUN, not a CIFS share - it won't work like that.
To restore a single file, go to SnapDrive interface, select "Connect Disk" & point to the existing snapshot. SnapDrive will do thin LUN cloning in the background (or volume FlexClone if license is present) & mount a LUN clone.
Then you can browse this newly attached drive & do drag&drop restore - simple!
2011-08-31 10:12 AM
Error says Incomplete path or invalid drive location
Here is my path: /vol/DFS_Backups/.snapshot/nightly.5
I was able to select the snapshot and create a SnapShot Copy but was unable to mout that as well. Same error.
2011-08-31 11:30 AM
When connecting the drive via SnapDrive you have to drill down to the actual LUN, which should be visible within the snapshot.
So the path you are quoting looks like incomplete, indeed - there should be a LUN name at the end of it.
2011-09-04 05:36 AM
It looks like you have some basic concepts confused somewhere.
SnapDrive basically is trying to help you do a few things "automagically" that you can easily do by hand on the CLI.
Read up on the "vol" and "lun" commands. There should be no reason to copy things when clones can easily be made. Why your snapshots are not "consistent" is also probably a matter of reading a bit more and finding out where the configuration mistakes are.
2011-09-05 01:45 AM
SnapDrive detects these snapshots were not made by it, hence are OS-inconsistent - that's why it refuses to deal with them.
This doc is worth reading for further info:
lun clone command (from filer CLI) will do the trick, as it doesn't care about consistency check.
2011-09-05 07:50 AM
Yes I agree with Radek, these snapshots were most likely setup on the Netapp SAN rather than through snap manager and therefore will be inconcistant. CIFS/NFS shares can be done this way because they dont need to me consistent, but applications (exchange, SQL etc) need to be managed by snap manager.