Hi Jack,
Your procedure looks correct, it matches with the
example given on the NOW documentation. Check this link:
Thanks,
Reena
Gupta
Hi Reena,
Could you reply this toaster email thread? I think you've
already have the steps to do this procedure.
thanks,
-linda
Linda Wu
Sr. Manager, Prod. Mgmt & TME,
Windows File Services
NetApp
Office: (408) 822-3560
Email: wu@netapp.com
I've been searching
this listserv as well as NOW.NETAPP resources to detemine if there was any easy
way to preclude certain file types (e.g., .mp3) from being written to given
volumes. It seems the answer was not natively, but it could be done
through a business partner product which would be set up as a screening server,
much like the AV virus scanning server.
I'm thinking maybe
it can be done natively by just not implementing the screening servers. My
thoughts follow. Comments would be appreciated.
display current setup:
fpolicy
create empy screening profile called
restrict_filetypes
fpolicy create restrict_filetypes screen
limit this profile to volume fre (for my
testing)
fpolicy vol inc add restrict_filetypes fre
limit this profile to filetype xxx (for my
testing)
fpolicy ext inc add restrict_filetypes xxx
limit this profile to activities of create and
rename (allow delete)
fpolicy monitor add restrict_filetypes -p cifs -f
create,rename
in absence of screening server, required will deny
the access rather than default of permit it
fpolicy options
restrict_filetypes required on
display the profile
fpolicy show
restrict_filetypes
enable the profile, -f forces it because there are
no screening servers
fpolicy enable restrict_filetypes -f
undo it all
fpolicy disenable
restrict_filetypes
fpolicy destroy
restrict_filetypes