For regular, complete backups, it is highly recommended to include attachments. It is also possible to take an IMSMA backup of the database and a file backup of the attachments. Excluding attachments from the backup routine is not recommended.
===Backing Up Other {{IMSMANG}} Information===__NOEDITSECTION__In addition to the {{IMSMANG}} database and attachments stored on the server, {{IMSMANG}} Backup allows users to back up certain settings from the {{IMSMANG}} client. These include: * GIS database (file based geodatabase)* map files (.mxd, etc.)* Data Entry Form template files (not published versions)* iReport template files (not published versions)* translation files (.properties files) ====GIS Database====__NOEDITSECTION__While {{IMSMANG}} stores all coordinate data in the PGSQL database that is backed up with the {{IMSMANG}} database, {{IMSMANG}} also stores coordinate data in uses a geodatabase file (file basedIMSMA.gdb) on each client computer , also known as the sandbax, to allow display the data to be displayed on in the mapMap Pane inside {{IMSMANG}}. These files should be included with each {{IMSMANG}} backup to shorten the time it takes to launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically rebuilds this file the sandbox during system launch of the {{IMSMANG}} if the file sandbox is missing, but it can take several hours to do so. After it is backed up, the sandbox can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase during system launch.
Because the geodatabase is built on a per-client basis, it is also recommended to launch the client on the server to fully update the geodatabase prior to backing it up. After it is backed up, the geodatabase can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase during system launch. ====Maps====__NOEDITSECTION__
{{IMSMANG}} map files can be loaded on a per-client basis and stored in {{IMSMANG}} Backup, providing an easy way to share maps between clients.
{{note| {{IMSMANG}} Backup backs up only the active map on each client. Other maps previously loaded on a client will need to be copied manually.}} ====Data Entry Form Templates and iReport Templates====__NOEDITSECTION__
{{IMSMANG}} provides the capability to store copies of drafts of Data Entry Form templates and iReport templates to the file system during report design. While the published versions of the templates are backed up as part of the {{IMSMANG}} database backup, the files are only included if the option is selected on the {{IMSMANG}} Backup window. Storing these files in the backup is recommended as it makes it easier to resume drafting templates and reports.
====Translations====__NOEDITSECTION__
{{IMSMANG}} stores translations of the application in several places. Translations and localisations of data elements are stored in the {{IMSMANG}} database and are backed up with the database backup. The .properties files used to translate the {{IMSMANG}} interface are stored externally to the database, but they can be added to the {{IMSMANG}} Backup as an option. If changes are made to the .properties files, it is recommended to back them up after each change as well as each time a full backup is made.
===Other Backup Considerations===__NOEDITSECTION__
While {{IMSMANG}} Backup backs up all of the files used in the typical operation of {{IMSMANG}}, there are other customisable files that should also be backed up. These include:
