__FORCETOC__
{{TOC right}}
*[[Standalone]]
*[[Network Environment]]
*[[Externally Connected Tools]]
*[[Attachments]]
==Backing Up And Restoring Data==
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 backup strategy should be used to eliminate data loss. Consider the following options below when developing a backup strategy for IMSMA<sup>NG</sup>.
*IMSMANG-specific backups
FinallyMoreover, a backup is only as good as the ability to restore it. As such, any data backup strategy should include occasioanl tests plans to test existing backups to ensure that all of the backups are functioning properlyusable. If it becomes necessary to restore data, regular testing of backups helps ensure that it will be possible to do so.
===Backing Up the IMSMA<sup>NG</sup> Database===
The IMSMA<sup>NG</sup> Datebase holds 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 actie active data in IMSMA<sup>NG</sup> ranging from IMSMANG including published reports , form templates and geographic data in addition to general the typical mine action information. IMSMA<sup>NG</sup> IMSMANG’s Backup is responsible for storing all of this data under capability backs up the MySQL IMSMANG database. The by executing a MySQL database dump command impliments that creates a complete backup of all of the data in the databaseincluding 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. The existing file is stored in a time-stamped directory for easy access.
[[File:BackingUp Tip1CORRECT.png|border|caption]]
Information Managers managers can create automatic dailiy or weekly 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 also work simultaneously with IMSMA <sup>NG</sup> similarly to IMSMANG Backup; however , any backup made outside of IMSMA <sup>NG</sup> needs IMSMANG will have to be restored manually restored. Even so, regularly scheduled backups are an excellent component of a backup strategy.
[[File:BackingUp Tip2.png|border|caption]]
===Attachments===
Attachmes are stored seprately from the IMSMA<sup>NG</sup> database IMSMANG stores attachments on the server filesystem separate from the IMSMANG database. However because Because of their the sizeof some attachments, it may not be beneficial or necessary to back up the attachments each time. For this reason, IMSMA<sup>NG</sup> IMSMANG Backup provides the option of excluding to exclude attachments when performing a backup.
Including attachments is still reccomended for For regular, complete backups, it is recommended to include attachments. HoweverBut, if the size of a backup file size is too large a concern, the attachments can be manually deleted manually. Avoid excluding attachemtns from backups This is a better alternative to creating a backup without attachments since attachmets attachments cannot be added back to the backup file. Excluding attachments from a backup is an option that should be used with caution.
===Backing Up Other IMSMA<sup>NG</sup> Information===
Apart from In addition to the IMSMA<sup>NG</sup> IMSMANG database and attachment attachments stored on the server, IMSMA<sup>NG</sup> IMSMANG Backup allows members users to backup specific elements back up certain settings from the IMSMANG client including. These include: *GIS database (.mdb file)*map files (.mxd, etc)*field report template files*iReport template files*translation .properties files
====GIS Dataabase====
IMSMA<sup>NG</sup> While IMSMANG stores all coordinate data in the MySQL database that is backed up with the IMSMANG database, IMSMANG also stores corrdinate coordinate data on each client computer in a geodatabase file (IMSMA.mdb) on each client computer to allow data to be displayed on a the map. Even if This file should be included with each IMSMANG backup to shorten the file is missing, IMSMA<sup>NG</sup> time it takes to launch IMSMANG after a restore. IMSMANG automatically builds this file aftre the during system launch. Howeverif the file is missing, but it can take several hours. To avoid this, each IMSMA<sup>NG</sup> backup should include this file to reduce the time it takes to launch IMSMA<sup>NG</sup> after a restoredo so.
Likewise, since Because the geodatabase is structured built on a per-client basis, it is also recommended to launch the best way client to fully update the geodatabase is to launch the client prior to backing it up. Once After it is backed up, users the geodatabase can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase by manually transferring it to newly installed clientsduring system launch.
====Maps====
IMSMA<sup>NG</sup> map fiiles 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.png|border|caption]]
====Field Report Templates and iReport Templates====
IMSMA<sup>NG</sup>users can IMSMANG provides the capability to store copies or drafts of field reports report templates and iReports iReport templates to the file systemduring report design. Select 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 IMSMA<sup>NG</sup> IMSMANG Backup window to store . Storing these files in the backupis recommended as it makes it easier to resume drafting templates and reports.
====Translations====
IMSMANG stores translations of the application in several places. Translations and localizations localisations of data elements are stored in the IMSMA<sup>NG</sup> IMSMANG database and secured are backed up with the database backup. Although the The .properties files used to translate the IMSMA<sup>NG</sup> IMSMANG interface are stored externally to the database, but they can be added to the IMSMA<sup>NG</sup> IMSMANG Backupas an option. Be sure If changes are made to backup all the .properties files , it is recommended to back them up after each change as well as each time a change or a full backup is made.
