Changes

Backup and Restore

323 bytes added, 11:17, 30 November 2012
no edit summary
IMSMANG contains several stores of information that can be backed up. By far, the most critical store is the IMSMANG database itself because it contains all of the active data in IMSMANG including published reports, form templates and geographic data in addition to the typical mine action information. IMSMANG’s Backup capability backs up the IMSMANG database by executing a MySQL 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.
[[File:BackingUp Tip1CORRECT{{note| The dump.png|border|caption]]sql file is stored in text format and can be made smaller for storage or transport using compression tools such as ZIP and RAR}}
Information managers can augment the IMSMANG Backup capability with other scheduled backups using MySQL Administration tools, for example, and build daily or weekly routines that back up the database automatically. These backups work similarly to IMSMANG Backup; however, any backup made outside of IMSMANG will have to be restored manually. Even so, regularly scheduled backups are an excellent component of a backup strategy.
[[File:BackingUp Tip2{{note| In a client-server environment, backups should be made from the server rather than the clients.png|border|caption]]Similarly, backups can only be restored on the IMSMANG server}}
===Attachments===
IMSMA<sup>NG</sup> map files can be loaded on a per-client basis and stored in IMSMA<sup>NG</sup> Backup, providing an easy way to share maps between clients.
[[File:Map Tip1CORRECT{{note| IMSMANG Backup backs up only the active map on each client.png|border|caption]]Other maps previously loaded on a client will need to be copied manually}}
====Field Report Templates and iReport Templates====
404
edits