Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December15 - Deletes > FoE interoperability with antivirus scanners

FoE interoperability with antivirus scanners

Table of contents
Created by Michael Perez, last modified by Jessica Solis on Dec 15, 2017

Views: 723 Votes: 1 Revisions: 5

Overview

This article provides general information about interoperability with antivirus scanners. In general, SolarWinds recommends, where possible, using one of the supported  antivirus products. If using an unsupported antivirus product, the general advice below should be followed. However, SolarWinds may be unable to resolve support calls arising out of an interaction with such products.

Environment

All Orion Failover Engine versions

Detail

Consult and implement the antivirus manufacturer’s advice, as SolarWinds guidelines will often follow these recommendations.

General Principles

  1. File level antivirus should not be used to protect application server databases such as the Microsoft SQL Server. The nature of database contents can cause false positives in virus detection leading to database application failures and data integrity errors. Performance will also be affected. 
  2. SolarWinds recommends that when implementing Orion Failover Engine, file  level antivirus temp files should not be replicated by Orion Failover Engine. Generally, your file replication application should be configured to avoid replicating any and all antivirus files.
  3. The file level antivirus software running on the primary server must be the same as the software that runs on the secondary server. In addition, the same  file level antivirus must run during both active and passive roles.
  4. The file level antivirus should be configured to use the public, management IP address on the passive server for virus definition updates. If this is not possible, it may be necessary to update virus definitions manually on the passive server.
  5. After installation of Orion Failover Engine, any changes made to the configuration of file level scanning on the active server must be repeated manually on the passive server.
  6. The following Orion Failover Engine directories (C:\Program Files\SolarWinds\FoE\ is the default installation directory) must be excluded from File Level Anti-Virus Scans:
    • C:\Program Files\SolarWinds\FoE\R2\logs
    • C:\Program Files\SolarWinds\FoE\R2\log
    • C:\Program Files\SolarWinds\FoE\R2\FSMTemp
      Note: This directory and its contents are deleted by the File State Manager when not in use.

 

Last modified

Tags

Classifications

Public