Subscribe

"~snapshot " subfolders unreachables

Hello.

I have 2 volumes sv_vol3 & sv_vol1, which are targets of a snapvault relationship (sources are vol3 and vol1).

Snapshots are named "journalier.0", "journalier.1", they are issued from snapvault replication every day.

I recently recreated (from zero) the snapvault relationship (with lrep) for vol3/sv_vol3.

Then, I recreated a share for sv_vol3 (for admins only), in order to access to ~snapshot subfolders.

I can access into "~snapshot", but I can't in subfolders (which are snapshots names - journalier.0).

It works fine for the other volume (sv_vol1) with same CIFS rights...

What do I have to check ?

Tks

Re: "~snapshot " subfolders unreachables

I'm not entirely clear with the above question.

You are saying for sv_vol1 its working and for sv_vol3 it isn't ? Is that correct ?

How many snapshots you see in sv_vol1 ? Can you check with some other Snapshot ?

snap you provide with the o/p of "snap list -V sv_vol3" & "snap list -V sv_vol1"

Also, the respective share output as well.

Re: "~snapshot " subfolders unreachables

You're right, for sv_vol1 its working and for sv_vol3 it isn't.

Volume sv_vol3

  %/used       %/total  date          name

----------  ----------  ------------  --------

  0% ( 0%)    0% ( 0%)  Sep 27 00:35  journalier.0

  0% ( 0%)    0% ( 0%)  Sep 27 00:24  nas03(0135067612)_sv_vol3-base.0 (busy,snapvault)

  0% ( 0%)    0% ( 0%)  Sep 26 00:43  journalier.1

  0% ( 0%)    0% ( 0%)  Sep 24 21:55  journalier.2

  0% ( 0%)    0% ( 0%)  Sep 23 20:05  journalier.3

  0% ( 0%)    0% ( 0%)  Sep 22 21:29  journalier.4

  0% ( 0%)    0% ( 0%)  Sep 21 22:11  journalier.5

  0% ( 0%)    0% ( 0%)  Sep 20 23:13  journalier.6

cifs shares sv_vol3 :

Name     Mount Point                   Description
----     -----------                   -----------

sv_vol3  /vol/sv_vol3


MYC\Domain Admins / Change


Volume sv_vol1

  %/used       %/total  date          name

----------  ----------  ------------  --------

  0% ( 0%)    0% ( 0%)  Sep 27 05:31  journalier.0

  1% ( 1%)    1% ( 1%)  Sep 27 05:19  nas03(0135067612)_sv_vol1-base.0 (busy,snapvault)

  1% ( 0%)    1% ( 0%)  Sep 26 01:06  journalier.1

  1% ( 0%)    1% ( 0%)  Sep 24 22:46  journalier.2

  1% ( 0%)    1% ( 0%)  Sep 23 20:28  journalier.3

  1% ( 0%)    1% ( 0%)  Sep 22 21:10  journalier.4

  1% ( 0%)    1% ( 0%)  Sep 21 20:54  journalier.5

  1% ( 0%)    1% ( 0%)  Sep 20 22:59  journalier.6

  1% ( 0%)    1% ( 0%)  Sep 20 03:46  journalier.7

  4% ( 3%)    4% ( 3%)  Sep 19 23:22  journalier.8

  6% ( 1%)    5% ( 1%)  Sep 17 23:17  journalier.9

  6% ( 0%)    6% ( 0%)  Sep 16 20:31  journalier.10

  6% ( 0%)    6% ( 0%)  Sep 15 20:54  journalier.11

  6% ( 0%)    6% ( 0%)  Sep 14 23:40  journalier.12

  6% ( 0%)    6% ( 0%)  Sep 13 22:11  journalier.13

cifs shares sv_vol1 :

Name     Mount Point                   Description
----     -----------                   -----------

sv_vol1  /vol/sv_vol1


MYC\Domain Admins / Change


Re: "~snapshot " subfolders unreachables

And you trying to achieve this via the same Workstation and same account correct ?

Re: "~snapshot " subfolders unreachables

I tried from my workstation and from servers, with different domain admins accounts.

Re: "~snapshot " subfolders unreachables

My bad.

I meant while you are able to access for vol1 ( you are using the same workstation and account to access vol3 as well ) ? correct ?

From Data ONTAP browsing of .snapshot folder has not trick with it. So I'm just suspecting the way you are accessing it.

Re: "~snapshot " subfolders unreachables

Have you checked the security style for both volumes ("qtree status")?

Is it NTFS for both?

Re: "~snapshot " subfolders unreachables

Yes, it's NTFS for both.

I now have new elements. A new snapshot was created last night (after the replication), and the new snapshot subfolder is reachable (but not other ones)...

Re: "~snapshot " subfolders unreachables

This hints at problems with UNICODE file names. Snapshot is read-only, so if original files did not have UNICODE version of file name, it cannot be generated on the fly.