From 29f38a04a30c6455d2ce9bd17b033d8e548fd6e7 Mon Sep 17 00:00:00 2001 From: Steve Garon Date: Thu, 23 Apr 2020 09:37:39 -0400 Subject: [PATCH] Fix metadefender cleanup instructions --- docs/install_notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/install_notes.md b/docs/install_notes.md index 075a811..044980e 100644 --- a/docs/install_notes.md +++ b/docs/install_notes.md @@ -2,7 +2,7 @@ **NOTE**: The following instructions are for **MetaDefender Core v4** running on a **Windows** machine. -If your deployment experiences a heavy file load, MetaDefender tends to become slower over time due to the increasing size of its database. In order to overcome this issue, a task can be scheduled to run a PowerShell script ([metacleanup.ps1](../mdcore_install/install_notes.md)) which will temporarily stop the MetaDefender service, delete the database and then restart the service. Every time the script runs, there is a down time of approximately 30-90 secs during which the MetaDefender service is unreachable. If you have multiple deployments of MetaDefender, you can offset the scheduled task for each deployment to minimize service downtime. +If your deployment experiences a heavy file load, MetaDefender tends to become slower over time due to the increasing size of its database. In order to overcome this issue, a task can be scheduled to run a PowerShell script ([metacleanup.ps1](metacleanup.ps1)) which will temporarily stop the MetaDefender service, delete the database and then restart the service. Every time the script runs, there is a down time of approximately 30-90 secs during which the MetaDefender service is unreachable. If you have multiple deployments of MetaDefender, you can offset the scheduled task for each deployment to minimize service downtime. ## Set-up Instructions