Data Migrator and Anti-Virus

[cabraun]

I am curious how many people out there actually use the File System Data Migrator and what your experience with it is. In particular what Anti-Virus product you use and how nicely it plays with DM.

Last Summer we labbed DM for Exchange and File System. Exchange went well and is now in our production environment for a select group of test users. We could never get the FS DM to play nicely with Trend Micro Office Scan AV product. Multiple calls with CV and Trend as well as on-site implementation people have never resolved the issue.

Basically what happens is files are migrated fine but when DM tried to replace the file with the stub Trend says NO WAY JOSE!!! to that operation.

CV says this is a Trend problem and that they have no problems with Symantec or Mcafee etc. They also say that the problem is fixed in the latest version of Trend, but naturally our thought process is, OK it is fixed right now, but what happens a few weeks from now when Trend releases a new scan engine? Does it break again? So sorry we are not willing to risk that.

What are your experiences with DM for FS?

 

[birky]

DMFS works fine with other AV vendors but, it is true that there have been problems with TrendMicro.

I had experience that you weren't able to turn of the scanning of offline files within TM so it was causing a timeout on the recall of migrated files.

 

[dall]

We have also install Trend Office scan on our file server and since then we are unable to run Data Migrator jobs without the file server crashing. What version currently works with Data Migrator, we are on Trend Office Scan 7.3 release 8.320.1003.
Any help would be gratefully received

 

[birky]

You can take a look at KB Article ID: 10947 for info on Trend.

The article applies to TM Server Protect but, may also apply to Office Scan....I've no experience with Office Protect at all so use at your own risk ;-).

In a nutshell with Server Protect you need to do 2 things;-

1) To prevent the TREND OnDemand scan from recalling migrated files this key should be set to block the SpntSvc.exe service.

Create the following registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Platform Information\ControlSet001(<hostname>)\WinFSDataMigrator\NoRecallPrivileges]
String Value: “SpntSvc.exe”

After making registry changes the DMFS services on the machine should be recycled.

2) Based on guidance from the TREND Micro product support team, scan engines based on v 7.370.1007 and forward support a filter to skip items marked as offline files.

This feature is disabled by default. Users can turn this filter on by setting the following registry within the TREND Micro configuration.
Recycle the TREND services after setting the registry key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TmFilter\Parameters
Add “SkipOfflineFile” (DWORD) set to 1 to turn on, 0 for off

 

[birky]

in addition..I personaly don't think that if TM have now actually fixed the issue that it will occur again in a new release....took a while but, at least they got there

In the early days of HSM, many HSM vendors had issues with anti virus software with the main reason being the scanning of offline files causing timeouts on recalls...TM seemed to be a bit slow in responding to the request to be able to switch off the scanning of offline files....I've had a bit of experience with DMFS and haven't had an issue with Norton/Mcafee but, have had problems with TM due to not being able to turn off offline scanning.

 

[dall]

birky,
Thanks for that info, I am passing it onto our AV team to implement.
D.

 

[dall]

Birky,
Just a quick question - the documentation you refer to keeps stating that it will work with "stub recall" which I would take to mean when the migrated file is being accessed. We have no problems with recalling files from a migrated area.

The problem we have is when we try to run a Migrate job to move files away from the file server to offline storage. The migration job appears to be scanning but it is only eating up the file server CPU to the extent that it eventually crashes.

Have you/anyone else seen this occuring elsewhere?

I am requesting the registry change anyhow so I will post the results in the next couple of days.

 

[birky]

hhhmmm...haven't seen any problems with actually migrating, usually just on recalls