518
edits
Changes
Version 6.0
==Backing Up And Restoring Data==__NOEDITSECTION__
The most important aspect of maintaining a properly functioning IMSMANG system is backing up and restoring data.
Regular data backups are essential for maintaining the integrity of the system in case of sytem failure, software errors or accidental data deletion. Not only should information managers mandate that all IMSMA<sup>NG</sup> data is regularly backed up, but more importantly a multitired multitiered backup strategy should be used to eliminate data loss. Consider the following options below when developing a backup strategy for IMSMA<sup>NG</sup>.
*disk mirroring
* After making SQL changes to the database
Server Client Server and Client<br>Component Daily Weekly Weekly Event-based change<br>IMSMANG database ● ● ●<br>Attachments ● ● ●<br>GIS database ● ● ●<br>Maps ● ● ●<br>Templates ● ● ●<br>Translation ● ●<br>
}}
* translation .properties files
====GIS DataabaseDatabase====__NOEDITSECTION__
While IMSMANG stores all coordinate data in the MySQL database that is backed up with the IMSMANG database, IMSMANG also stores coordinate data in a geodatabase file (IMSMA.mdb) on each client computer to allow data to be displayed on the map. This file should be included with each IMSMANG backup to shorten the time it takes to launch IMSMANG after a restore. IMSMANG automatically builds this file during system launch if the file is missing, but it can take several hours to do so.
