- LANforge data lives in various directories under /home/lanforge, and this is a brief explanation of the directories you will want to transfer.
LANforge scenario data for a realm is saved on the manager (typically resource 1).
The LANforge client (GUI) can save reports on various machines where it is running. It does not save scenario data.
- Below are listed the important sub-directories from /home/lanforge,. Each has a note about how important it is to back up. Directories not listed are unlikely to contain LANforge related data.
When in doubt backing up the entire /home/lanforge directory is OK
- DB/
YES this is were all your scenarios are saved
- Desktop/
only if you save things here
- Documents/
only if you save things here
- Downloads/
only if you save things here
- html-reports/
yes if you want the reports
- lf_reports/
yes if you want the data
- local/
unlikely unless you customize strongswan
- report-data/
yes if you want the data
- scripts/
only if you have modified or custom scripts in here
- trb_entities/
trb_profiles/
Table Report Builder saved settings only necessary if you use TRB frequently
- vr_conf/
only if you save virtual router settings, nginx configs or want to save dhcp lease files
- wifi/
only if you have customized wpa_supplicant.conf or hostapd.conf files
Archiving Data
Starting on your old LANforge machine, use the tar command to archive data. Add directories you want to archive to the end of the command. cd /home/lanforge
tar cjf /home/lanforge-bu.tar.bz2 DB html-reports lf_reports report-data
If you run out of space, try using /home/lanforge/check_large_files.bash to help clear room.
Copy the Archive
Copy the archive to the new LANforge:scp /home/lanforge-bu.tar.bz2 lanforge@your-new-machine-ip:/var/tmp
Restore the Data
On the new machine: cd /home/lanforge
tar xvf /var/tmp/lanforge-bu.tar.bz2
sudo service lanforge restart
