Snapshot verification

[FollowTheWizard]

Hi.

I have the latest version of FreeNAS running on my computer and all the snapshot folders are empty.

My Setup of the NAS is: Two ZFS Volumes with periodic Snapshots every 4 hours and they should last for 4 weeks :) (same times). I can see entries in the ZFS snapshot menu when I am logged in at the web config tool and they differ from '0'.
The Snapshots are setup for the entire volumne with the "recursive" mode.

However, when I try to browse the snapshots over Windows 7 and Windows 8, I only see empty folders.
I tried to delete files and modify them to see if they are storred somewhere, but I couln't find them anywhere.

I already checked the /var/log/messages, if I can find some suspicious entries but I couldn't find an entry for failed snapshots.

Is there an easy way to verify that the snapshot funciton is working correct?

I couldn't find a way how to achieve this. Neither Google did help me nor the FreeNAS Guide :(

Best Regards

 

[warri]

To verify whether snapshots have been made:

Code:

zfs list -t snapshot

This lists all available snapshots and their referred space, but it should give you the same output as the WebGUI. Feel free to post the output in [code] tags for us to have a look if you feel that something is missing.

 

[FollowTheWizard]

I do get a huge list when I enter this command. This is just the end. But I am not able to access those snapshots with windows under " previous version".

Is there a guide what the letters 'w' at the end mean?

Code:

three_500_volume/Jails/btsync_1@auto-20140424.1304-4w                      709K      -  968M  -                                 
three_500_volume/Jails/btsync_1@auto-20140425.0924-4w                      485K      -  968M  -                                 
three_500_volume/Jails/btsync_1@auto-20140425.1324-4w                      671K      -  968M  -                                 
three_500_volume/Jails/btsync_1@auto-20140426.0800-4w                      496K      -  968M  -                                 
three_500_volume/Jails/btsync_1@auto-20140426.1200-4w                      586K      -  968M  -                                 
three_500_volume/three_500_dataset@manual-20140413                        139K      -  213K  -                                 
three_500_volume/three_500_dataset@manual-20140413-2                      107K      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140413.0800-4w                      0      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140413.1200-4w                      0      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140413.1600-4w                  107K      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140414.0800-4w                      0      -  13.9G  -                                 
three_500_volume/three_500_dataset@auto-20140414.1200-4w                      0      -  13.9G  -                                 
three_500_volume/three_500_dataset@auto-20140415.0800-4w                  107K      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140415.1200-4w                  107K      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140416.0936-4w                  107K      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140416.1336-4w                  107K      -  6.62M  -                                 
three_500_volume/three_500_dataset@auto-20140417.0800-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140417.1200-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140419.0800-4w                  107K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140419.1200-4w                  107K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140420.0800-4w                  107K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140420.1200-4w                  107K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140421.0800-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140421.1200-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140422.0800-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140422.1200-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140424.0904-4w                  10.7K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140424.1304-4w                  107K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140425.0924-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140425.1324-4w                      0      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140426.0800-4w                  107K      -  10.7G  -                                 
three_500_volume/three_500_dataset@auto-20140426.1200-4w                  107K      -  10.7G  -                                 
[root@freenas ~]#                                                                                                                  

 

[fracai]

4w means they'll be automatically deleted once they're four weeks old.

 

[warri]

That should be the period a snapshot is kept for (in your case 4 weeks). We can see from the list that snapshots are definitely created for the three_500_dataset and the btsync jail.

As for your browsing problem: Did you follow all steps outlines in the manual for Configuring Shadow Copies?
Especially check if you restarted CIFS or the FreeNAS box accordingly and if the permissions are all configured correctly. I'm not using the shadow copies feature of CIFS myself, so I probably won't be a great help.

 

[alexg]

Make sure your CIFS shares are mapped to your datasets. From manual:

• at this time, shadow copy support only works for ZFS pools or datasets. This means that the CIFS share must be configured on a volume or dataset, not on a directory. Directory support will be added in a future version of FreeNAS®.

I've made this rookie mistake myself and then had to redesign my setup.

 

[DarkerTimes]

Has anyone a solution for this:

My shadowcopy folders are empty:
I have a dataset Private with five more datasets (User1,User2,...). The Private Dataset is a CIFS share. I created a periodic snapshot of the Private Dataset (every 2 h).
Under my Windows client i can see every snapshot as shadow copy, but the folders are empty...

FreeNAS 9.2.1.4, switched back from 9.2.1.5 because this was too buggy^^

EDIT:
after some testing:
a periodic snapshot of User1 and cifs share of User1 is working, i am able to see the shadowcopy :)
the same setup with the Private dataset is not working -> folders empty (i also tried the recursive option, no change -> shadowcopy of datasets in dataset still not working for me)

 

[FollowTheWizard]

@DarkrTimes: That sounds very familiar :)


Hmm the snapshots have been setup before the CIFS service was started. And the two snapshots are on the volumnes. At first I didn't check the recursive "button". But it didn't work for the entire volumne, thus I activated this mode. => no change :(

appropriate permissions must be configured on the volume/dataset being shared by CIFS

How are the permissions relevant for the snapshots?

I basiclly followed the guide from the "TEK SYNDICATE" guys. I only added one user.