Where Does Greenbone Store Configs and Reports?
Where self hosted Greenbone keeps configs and reports on Linux servers. Full paths are listed below.
Last updated
Greenbone is open vulnerability scanning with server storage. The database holds targets, schedules, and results. Feed data sits beside it with NVT updates.
Same database plus feeds means same coverage. Exact paths vary by Docker versus source installs. Keep feeds updated before audits. For moves, stop services first to avoid partial dumps. Partial copies miss credentials that break authenticated scans. When in doubt, verify paths inside the app before trusting a remembered folder. Screenshots of settings help when support asks for reproduction steps later.
Where Greenbone Scanner stores this, by platform
/var/lib/greenbone (database plus feeds, paths vary)
Targets and results live in the server database with feeds beside it. Back up both together stopped. Match releases before restore. Feeds need updating after moves.
Frequently asked questions
How do I migrate Greenbone to a new server?
Back up the Greenbone database plus data directory with services stopped, then install the same release on the new server before restore. Targets follow the database. Mixed releases can refuse old schemas, so match versions first.
Does Greenbone back up scan results?
Yes, in the server database per scan with results attached. The host holds a working copy plus feed cache. Views rebuild after restore. Export PDF reports from scans for records, since the data directory alone is working state.
Notice an outdated path? Let us know.