This post is more than 5 years old
51 Posts
0
789
April 5th, 2016 02:00
icap backup accelerator node
Hello after upgrading to onefs 8.0 it seems that isilon want to use the backup accelerator node to send file to the icap server...
I don't understand why isilon want to use the backup accelerator node now... In version 7 we doesn't have this
regards
No Events found!
johnsonka
130 Posts
0
April 5th, 2016 05:00
Hello!
In order to use policy scans from OneFS (i.e. running the AVScan job) you need all nodes to be able to access the ICAP server. the jobengine uses all available nodes to run. This behavior has been consistent from OneFS 6.5 and newer.
If you run on-access scanning (i.e. scan-on-open or scan-on-close) you may have a cluster with nodes that cannot access the ICAP server and it'll run just fine. Let me know if this helps!
Aglidic
51 Posts
0
April 5th, 2016 02:00
hum i just saw something, maybe the isilon backup node is shown as an accelerator node and that's why we have this error.
I will make another try of scanning my filesystem after remooving the backup node
Aglidic
51 Posts
0
April 6th, 2016 04:00
Hello,
yes we have make test and we just permit the backup accelerator node to access the icap server and no error anymore.
exactly the on access scan is not concerned by this "issue"
regards