Data Loss Prevention

 View Only

Scans complete incorrectly after filereader restart - error: The Local Drive for mount is in use

  • 1.  Scans complete incorrectly after filereader restart - error: The Local Drive for mount is in use

    Posted Nov 18, 2015 06:11 AM

    Hi,

     

    We have upgraded to V14.0.1, the Enforce is on Redhat v6.6, Oracle database is on a Redhat database server and we have two discover servers on Windows 2008.

    We are scanning our network shares, data at rest regulart file scans and PST file scans. However, the scans will complete with the following error after a filereader restart has been performed;

    11/12/15 5:54:16 AM INFO Finished 148 items, 301,664,376 bytes; filtered 151 items
    11/12/15 5:54:16 AM INFO Finished 8 items, 2,228,070 bytes; filtered 5 items
    11/12/15 5:56:12 AM INFO Scan started
    11/12/15 5:54:16 AM INFO Finished 8 items, 2,228,070 bytes; filtered 5 items
    11/12/15 5:56:12 AM INFO Scan started
    11/12/15 5:56:12 AM INFO Scan started
    11/12/15 5:56:18 AM INFO Started scanning Share: //10.62.3.236/home$
    11/12/15 5:56:18 AM WARNING Failed to read //10.62.3.236/home$; error: The Local Drive for mount is in use -- l:.
    11/12/15 5:56:18 AM WARNING Failed to complete Share: //10.62.3.236/home$; error: The Local Drive for mount is in use -- l:.
    11/12/15 5:56:18 AM INFO

    Scan finished

    A recent webex with Symantec the engineer discovered that:

      Recent webex shows previous mounts still exists. Deleted the previous mounts and increased the consecutive errors count. Recycled VontuMonitor. Customer will send logs if FR restarts occurs or on morning of Nov 12 (customer's time)

     

    This gave foundation to our theory that when the filereader restarts the mounts are not disconnected correctly and when the tool attempts to remount using the same drive it finds this in use and the scan completes with the above error, as a workaround we used to perform regular restarts of the vontu service on the discover server as this appeared to dismount and then mount the shares correctly.

    The BoxMonitor.HeartbeatGapBeforeRestart was amended to 1hr, this reduced the amount of filereader restarts. (As a soide question what would happen if i exteneded this to some bizzare figure such as 2 weeks? no filre reader restart would mean no failed scans, although probably not advisable)

    However, we are now at a position where our scans are not completing, has anyone seen this issue before?

    Ralph