Yes! You can migrate the farmerswife (fw) database files from one host machine to another, across Windows, Mac and Linux.
In short:
When migrating your existing farmerswife system to a new host machine, copy at least the complete "files", "html_templates", "system", and "scripts" sub-folder (stored within "lib") into the new "farmerswife Server" installation directory.
Always first perform a "Full Backup" from the running fw Server application (use the "Full Backups" button on the running fw Server app), thus creating a complete backup of the "farmerswife Server" app directory (if the "Include Files Folder" setting is enabled, more info below).
In detail:
For minimal downtime, please follow these steps in the following order:
- Install the latest available farmerswife Server version on the new server host machine. Please ensure to consult the upgrade instructions, since older versions of the system need to be upgraded in version steps. We also recommend to not install the fw Server app on the primary OS disk/partition if it can be avoided.
- Perform a "Full Backup" from the fw Server application on the current "Production" farmerswife Server app, creating a complete backup of the "farmerswife Server" directory ("complete backup = if the "Include Files Folder" setting is enabled, which is located in fw Server app > Setup > General > "Include Files Folder" setting). If this is not enabled, you need to ensure to manually copy, or re-mount the location of the "files" folder, or per "Project Folder Locations", or per one of the 12 "Media Library Folder Locations" if licensed and if configured.
- Shut your currently running fw system down, by using the "Quit" button. Ensure to have informed everyone prior to this migration process, which can take between 15 min. and multiple hours.
- Copy the complete "files", "html_templates", "system", and "scripts" sub-folder (stored within "lib") into the new "farmerswife Server" root installation directory on the new host machine.
- If needed, place the new license files (neede e.g. on a local static host IP change) into the "system" folder on the new host machine, thus replacing the old license.txt and license.dat files. Contact fw support if you have not requested it.
- Start up the farmerswife Server app on the new host machine. The system will get upgraded, if a later version was installed on the new host.
- After the upgrade process, start up the farmerswife Server again and go into Setup > General tab to ensure these Settings comply with the new environment:
- Check "Server Port", "File Transfer Port", "Http Port", "Web Client > Port", "API Port", "Url To Server" - are any Firewalls or network rules preventing the access? Also check the "Legacy HTTP Settings" sub-menu settings.
- "Outgoing Mail Server (SMTP)" - send a Test email by going to the sub-menu > Test. Does it work?
- "Backups Every" and "Backups" - are these set to match the new environment?
- "Full Backup Time" and "Full Backups" - are these set to match the new environment?
- "Full Backup Folder" - ensure this setting is grey. If it's red, then a new path needs to be set on a local drive, mounted network drive etc. Ensure the folder names and paths are as short as possible, e.g. like this "/Volumes/fw_FullBackup" or "G:\lfw_FullBackup\
- "PDF Print Export Settings" - if this is enabled, the path to a local "repository" folder needs exit and be selected here. - Log in with a locally installed farmerswife Client application, to verify that system is up and running again. Connect also connect from your LAN and outside of if via the different Access Tiers.
- Modify the Client to Server connection details on each farmerswife Client application to point to the new server machine's local static IP or public static IP or a domain name (if configured). Does the access work?
- Inform your colleagues about the successful migration and that your farmerswife system is up and running again.