Discoveries not running due to low disk space

Symptoms

• Discoveries are aborted right after they start, and no new data is collected.
• The discovery log shows a message like “Not enough free diskspace in ‘…vScopeData’ to start a discovery. Minimum required: 10 GB.”
• Administrators receive an email with the subject “Discoveries are not running - vScope is low on disk space”.

Cause

vScope needs at least 10 GB of free disk space on the drive where vScopeData is located to start a discovery. Discoveries are stopped before they start to prevent vScope from running out of disk space.

Old history is removed after 72 hours

If discoveries stay blocked for 72 hours, vScope permanently removes the oldest history to free up disk space. See Automatic Removal of History When Disk Space Is Low.

Resolution

1. Check the free disk space on the drive where vScopeData is located. The path is shown in the email.

2. Increase the disk space, or remove files that do not belong to vScope from the drive. An additional 20 GB usually gives a lot of room for growth.

   Danger

   Never remove or move files in the vScopeData folder manually. This can corrupt the vScope database and cause permanent data loss.

3. vScope checks the disk space every hour. Within an hour, administrators receive an email that discoveries can run again. The next scheduled discovery will start as normal.

For more about how vScope uses disk space, see Disk & Storage.