Where Does Boundary Store Targets and Sessions?
Where self hosted Boundary keeps config in database on Linux servers. See the folder table below. More below.
Last updated
Boundary is access broker with server storage. The database holds targets, roles, and session logs. Workers cache connections locally per job.
Same database means same perimeter. Exact paths vary by Docker versus binary installs. Keep backups on schedule. One missing table restores targets without history. For moves, stop workers first to avoid split sessions during copies. 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 Boundary Access stores this, by platform
/var/lib/boundary (database, paths vary by install)
Targets live in the server database with session logs. Back up the database stopped. Match releases before restore. Workers cache locally.
Frequently asked questions
How do I migrate Boundary to a new server?
Back up the Boundary database 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. Keep admin keys separate.
Does Boundary back up session history?
Yes, in the server database per session with credentials brokered at connect time. The host holds a working copy plus worker cache. Views rebuild after restore. Export HCL configs from settings for records, since the data directory alone is working state.
Notice an outdated path? Let us know.