If you have removed the directory on which the original snapshot was taken, it appears to me that you will be out of luck with using SyncIQ for restoring.  If that directory still exists, and you want to restore only some subdirectory, this can be specified with   isi sync policies {create or modify} ... --source-include-directories /path/to/subdirectory  For local SyncIQ jobs, the target path must be outside the source path, so one cannot restore a lost directory "in-place".  hth -- Peter 
I am working on restoring large amounts of data from snapshotIQ snapshots.  Many of the directories are not 'huge' in the sense of size, but are massive in terms of number of files; ranging anywhere from a few thousand files, to the extreme of 500+ million files.  Because of this, these restores take a VERY long time.  Unfortunately, for most of these the snapshot was taken at the parent level (something I am going to re-evaluate, lesson learned), so I cannot use SnapRevert because I dont want to revert every sub-directory under the snapshot.  So I am left with copying the directories manually out of the snapshots.   (/ifs/data/.snapshot/....)  looking at the Isilon's cp man page, there are two OneFS unique switches, -c (clones) and -B (use large buffers).  I did some testing with -c with a test directory and it appears that I cannot use -c and -R (recursive) together, so that doesn't appear to be an option for me.  I am curious about -B, it says "Use larger buffers when copying data to regular files to reduce system calls".  I'd like to know the full impact if I use -B; will it speed up my copy jobs with millions of 'smallish' files?  What's the impact on the cluster?  alternatively, rsync is another option and is obviously more robust than cp, but I am concerned about time and not sure if rsync would be faster.      thanks in advance for any information/recommendations
restoring data from snapshots