SnapShot access with Windows Mount Points

[mikehhancock]

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

Fiber Channel

iSCSI

All with SnapDrive 6.2

NetApp 3140 running 7.3.3P5

Current workaround is:

1. create new volume 10% larger than existing volume
2. mount a new LUN as a drive letter on the server
3. copy the needed snapshot (nightly.5) volume to volume from within the NetApp: vol copy start [-S|-s snapshot] <vol_source> <vol_destination>
4. open the folder where the file is that I want and copy it over the origional file
5. delete the new volume.
6. This method sux when the volumes are 3-6 TB

Thanks for any insight you can offer,

Mike

[radek_kubka]

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!

Regards,

Radek

[mikehhancock]

Hummmm,

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.

[radek_kubka]

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.

[mikehhancock]

When I drill down to my SnapShot Copies, they all say:

SnapShot Copy Status: Inconsistent SnapShot copy

And I cannot connect to it as a disk.

[shaunjurr]

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.

[radek_kubka]

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:

http://now.netapp.com/NOW/knowledge/docs/snapdrive/relsnap62/pdfs/admin.pdf

lun clone command (from filer CLI) will do the trick, as it doesn't care about consistency check.

Regards,
Radek

[stuartwatkins]

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.

[SARAVANAKUMARRAJU]

Hi did you check the vol options nosnapdir... Set this option to off and try accessing the snapshot directory...