How Are the Installation Folders Structured?
vScope is a locally installed, self-contained software that does not require external dependencies.
Java Runtime Environment (JRE)
The JRE installed by vScope is local to vScope and does not affect system-wide Java installations.
vScope Data
By default, vScope installs the required components in:
C:\Program Files\vScopeServer
(Windows, vScope Server)C:\Program Files\vScopeProxy
(Windows, vScope Proxy)/var/lib/vscope
(Linux)
The vScope data folder contains:
- Settings – Small configuration files (a few MB in size).
- Logs – Rolling logs, typically under 50 MB.
- Database – Stores inventoried assets. Size depends on environment size, scan frequency, and retention settings.
vScope Database
The vScope database stores both current and historical asset data, enabling time-based asset tracking. The database folder is located at:
projects\default\modeldb
- The primary database folder is named
kevas3
Transaction Logs
Stored in kevas3\logs
, transaction logs track every database revision. These logs are essential for:
- Database backups.
- Restoring data to a specific point in time.
- Migrating to a newer database version.
Transaction logs are usually much smaller than the database itself. Do not delete these logs.
Critical Data Files
The following folders are critical for database integrity and should not be modified manually:
kevas3\dedups
kevas3\snapshots
Snapshots
The kevas3\snapshots
folder contains monthly database snapshots for historical data retention.
- vScope retains data for multiple years by default.
- Large environments may see significant folder growth.
- Performance is not affected by snapshot size.
- Snapshots are not backups.
To reduce disk usage, consider lowering the retention period.
Estimating Space Savings
To estimate space savings by reducing retention by one year:
- Navigate to
kevas3\snapshots
. - Sum the size of the 12 most recent folders.
- Folder names are in increasing hexadecimal format (
XXXX
).