Changes

{{IMSMANG}} contains several stores of information that can be backed up. By far, the most critical store component to backup is the {{IMSMANG}} database itself because it contains all of the actual data in {{IMSMANG}} including and published reportstemplates, form templates and geographic data in addition to the typical mine action informationetc. {{IMSMANG}}’s Backup capability backs up the {{IMSMANG}} database by executing a PGSQL database dump command that creates a complete backup of all of the data in the database including any additional tables, views and other customisations. The resulting dump.sql file, which is stored in a time-stamped directory for easy identification, includes the necessary commands to recreate the database with all of the existing data.

{{note| The dump.sql file is stored in text format and can be made smaller for storage or transport using compression tools such as ZIP and RARWinZIP. }}

{{note| In a client/server environmentconfiguration, backups should be made from the server rather than the clients. Similarly, backups can only be restored on the {{IMSMANG}} server

{{IMSMANG}} stores attachments on the server file system separate from the {{IMSMANG}} database. Because of the total file size of some the attachments, it may not be beneficial or necessary to back up the attachments each time. {{IMSMANG}} Backup provides the option to exclude attachments when performing a backup.

For regular, complete backups, it is highly recommended to include attachments. But, if It is also possible to take an IMSMA backup of the size of database and a file backup file is a concern, of the attachments can be manually deleted. This is a better alternative to creating a backup without attachments since attachments cannot be added back to the backup file. Excluding attachments from a the backup routine is an option that should be used with cautionnot recommended.

* GIS database (.mdb filebased geodatabase)* map files (.mxd, etc.)* Data Entry Form template files(not published versions)* iReport template files(not published versions)* translation files (.properties files)

While {{IMSMANG}} stores all coordinate data in the PGSQL database that is backed up with the {{IMSMANG}} database, {{IMSMANG}} also stores coordinate data in a geodatabase file (IMSMA.mdbfile based) on each client computer to allow data to be displayed on the map. This file These files should be included with each {{IMSMANG}} backup to shorten the time it takes to launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically builds rebuilds this file during system launch if the file is missing, but it can take several hours to do so.

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.

{{IMSMANG}} provides the capability to store copies or 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.