Changes

__FORCETOC__{{TOC right}}==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 {{IMSMANG}} data is regularly backed up, but more importantly a multitiered backup strategy should be used to eliminate data loss. Consider the following options below when developing a backup strategy for {{IMSMANG}}.

===Backing Up Moreover, a backup is only as if you are able to restore it. As such, any data backup strategy should include plans to test existing backups to ensure that the IMSMA^NG Database===backups are usable. If it becomes necessary to restore data, regular testing of backups helps ensure that it will be possible to do so.

The IMSMA^NG Datebase holds all of the actie data in IMSMA^NG ranging from published reports Note that an event-based change to general mine action information. IMSMA^NG Backup is responsible for storing all of this data under the MySQL database. The MySQL database dump command impliments components necessitates a complete backup of all '''before''' and '''after''' the change. Event-based changes include events such as:* upgrading any software on the server* importing data and/or Data Entry Forms* changing SQL views in the database. The resulting dump.sql file includes the necessary commands to recreate the database with all the existing data. The existing file is stored in a time-stamped directory for easy access.

===Backing Up the {{IMSMANG}} Database===__NOEDITSECTION__By far, the most critical component to backup is the {{IMSMANG}} database itself because it contains all of the actual data in {{IMSMANG}} and published templates, etc. {{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. The resulting dump.sql file, which is stored in a time-stamped directory for easy identification. {{note| The dump.sql file is stored in text format and can be made smaller for storage using compression tools such as WinZIP. }}{{HowTo's|[[File:BackingUp Tip1.pngBackup IMSMA Data|Backup IMSMA Data]]|border[[Scheduling Backup|captionScheduling Backup of IMSMA database]]}}

File:BackingUp Tip1Information managers can schedule backups using PGSQL Administration tools 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.png

Attachmes are stored seprately from the IMSMA^NG database ===Attachments===__NOEDITSECTION__{{IMSMANG}} stores attachments on the server filesystem separate from the {{IMSMANG}} database. However because Because of their the total file sizeof the attachments, it may not be beneficial or necessary to back up the attachments each time. For this reason, IMSMA^NG {{IMSMANG}} Backup provides the option of excluding to exclude attachments when performing a backupwhich is '''not''' recommended.

Including attachments is still reccomended for For regular, complete backups. However, if the file size it is too large highly recommended to include attachments can be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added It is also possible to take an IMSMA backup of the database and a file backup fileof the attachments.

===Backing Up Other IMSMA^NG InformationMaps===__NOEDITSECTION__Apart from the IMSMA^NG database {{IMSMANG}} map files can be loaded on a per-client basis and attachment stored on the serverin {{IMSMANG}} Backup, IMSMA^NG Backup allows members providing an easy way to backup specific elements from share maps between clients. In Map Data is also the client including: [[Customise Sub-Themes | sub-theme]] assignments included.

*GIS database (.mdb ===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)*map files (system during report design.mxdWhile the published versions of the templates are backed up as part of the {{IMSMANG}} database backup, etc)*field report template the files*iReport template are only included if the option is selected on the {{IMSMANG}} Backup window. Storing these files*translation in the backup is recommended as it makes it easier to resume drafting templates and reports.properties files

====GIS Dataabase====* client and server '''settings''' including memory settingsIMSMA^NG also stores corrdinate data on each client computer in a geodatabase file * C:\IMSMAng\server\gis\maps\imsma.mxd (IMSMA.mdbif customized) to allow data to be displayed on a * the background map(s) source files ('''not''' only the . Even if the mxd file is missing, IMSMA^NG automatically builds this file aftre the system launch)* local projection files (. However, it can take several hoursprj)* C:\IMSMAng\migration\conf\migration. To avoid this, each IMSMA^NG backup properties and any import scripts* [[Language and Translations#Data language|fallback fonts]] (C:\IMSMAng\java\lib\fonts\fallback)* ODBC configurations* External tools: External reporting tools and other add-ons are not backed up by {{IMSMANG}} and information managers should include this file to reduce the time it takes to launch IMSMA^NG after a restoreensure that these external tools are backed up manually.

Likewise, since ==IMSMA Restore==__NOEDITSECTION__{{Warning| {{IMSMANG}} Restore replaces all data in the geodatabase is structured on a per-client basis, the best way {{IMSMANG}} database and copy over existing files. Prior to fully update restoring the geodatabase is {{IMSMANG}} database, information managers should ensure that all necessary data has been backed up. {{IMSMANG}} Restore operations cannot be undone.}}{{HowTo's| [[Restore IMSMA Backup on Server]]|[[Restore IMSMA Backup on Client]]}}Backups created using {{IMSMANG}} Backup should be restored using {{IMSMANG}} Restore. {{IMSMANG}} Restore allows users to launch the client prior determine which components of an {{IMSMANG}} Backup to backing it uprestore. Once it is backed up, users can shorten The components available depend on the time required to build options that were selected during backup. Each option behaves slightly differently depending on whether the geodatabase by manually transferring it to newly installed clinetsrestore is occurring on a server or a client.

====Maps===={{NavBox IMSMA^NG map fiiles can be loaded on a per-client basis and stored in IMSMA^NG Backup, providing an easy way to share maps between clients.Administration}}

[[FileCategory:Map_Tip1.png|border|captionNAA]] ====Field Report Templates and iReport Templates==== IMSMA^NGusers can store copies or drafts of field reports templates and iReports templates to the file system. Select the option on the IMSMA^NG Backup window to store these files in the backup.  ====Translations====Translations and localizations of data elements are stored in the IMSMA^NG database and secured with the database backup. Although the properties files used to translate the IMSMA^NG interface are stored externally to the database, they can be added to the IMSMA^NG Backup. Be sure to backup all properties files each time a change or a full backup is made.