View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere MFT. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.
- Posts: 8
- Joined: Tue Jul 17, 2018 9:14 am
Out of the box, GoAnywhere MFT is shipped with an Apache Derby database to make setting up your trial simple and cost-effective. The embedded Apache Derby database is a nice sandbox or development type database but for production environments HelpSystems recommends externalizing the GoAnywhere MFT database. We support all the major database flavors including SQL Server, MySQL, Oracle, MariaDB, PostgreSQL, and DB2/400.
The Apache Derby is a file-based database residing on the same server as GoAnywhere MFT, which in some cases could negativity impact performance since the application will require more thread utilization on the same server (both application and database would require threads for an action). Externalizing to a separate database will prevent the use of double threads and then a DBA can schedule a Database backup on a regular basis. It also should be noted that when the Apache Derby database performs backups or maintenance, it will temporarily take down the GoAnywhere application in order to run these processes (all tables are locked and cannot be written to).
One other thing to note is that if you are thinking about clustering your GoAnywhere MFT instances in the future, taking advantage of High-Availability, this requires the use of an externalized database. At that point you would need to migrate off of the Apache Derby database in order to use.
As iterated above, HelpSystems recommends moving your GoAnywhere MFT database to an external database as best practice.
Return to “Knowledge Center”