I have a 2 node cluster and noticed today that Storeage Exec is not blocking files based on the policy. I have removed the policy and re-added, moved the resources to the second node, deleted the policy and recreated, stopped and restarted Storeage Exec....nothing seems to make the policy work. It was just working last week and nothing has changed on the servers. Help!
Update.... I was trying to update Storeage Exec to the latest hotfix (#23) which required me to remove Storage Exec from the cluster resources. When I removed Storeage Exec from the cluster resources (all cluster services running on 1 node) the file blocking started to work. Granted I was not able to install the latest hotfix because it errored out on both nodes. So what that tells me is there is an issue when Storage Exec is running as a cluster resource. I would like to see a Veritas post on this issue.
I will try that and see how it goes. I have hotfix 22 on the server now but hasn't helped with the issue. I'll post back if I get the same results as you did when breaking the cluster
I don't know any other direct way but I look at the file that is mentioned in the Hotfix notes and compare it to what I have on the server.
So in my case, for HotFix 22, I check the file SERptGenU.dll and the version was 5.3.2190.22 The last bit is 22 so its patched upto 22.
I looked at the notes on Hotfix 23, which say to check the file SESnapin.dll and when I check my version of this file it says 5.3.2190.21. Which means I haven't applied hotfix 23 yet.
No luck with turning off storage exec on the cluster resources. I turned it off and then set file blocking policy on the share I was having trouble with but still now luck. I'm able to save a jpg file even though a block graphics file policy is there.
The same file blocking policy works fine when applied to the local C drive.
I'm at a loss now. I have no idea why this isn't working.