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<sup>NG<Note that an event-based change to the components necessitates a backup '''before''' and '''after''' the change. Event-based changes include events such as:* upgrading any software on the server* importing data and/sup> Datebase holds or Data Entry Forms* changing SQL views in the database. ===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 actie actual data in IMSMA^NG ranging from {{IMSMANG}} and published reports to general mine action informationtemplates, etc. IMSMA^NG {{IMSMANG}}’s Backup is responsible for storing all of this data under capability backs up the MySQL {{IMSMANG}} database. The MySQL by executing a PGSQL database dump command impliments that creates a complete backup of all of the data in the database. The resulting dump.sql file includes the necessary commands to recreate the database with all the existing data. The existing file , which is stored in a time-stamped directory for easy accessidentification.

[[File:BackingUp Tip1CORRECT.png|border|caption]]  Information Managers managers can create automatic dailiy or weekly schedule backups using MySQL PGSQL Administration toolsand build daily or weekly routines that back up the database automatically. These backups also work simultaneously with IMSMA ^NG similarly to {{IMSMANG}} Backup; however , any backup made outside of IMSMA ^NG needs {{IMSMANG}} will have to be restored manually restored.   [[File:BackingUp Tip2.png|border|caption]]  ===Attachments=== Attachmes Even so, regularly scheduled backups are stored seprately from the IMSMA^NG database on the server file. However because an excellent component of their size, it may not be necessary to back up the attachments each time. For this reason, IMSMA^NG Backup provides the option of excluding attachments when performing a backupstrategy.  Including attachments is still reccomended for complete backups. However, if the file size is too large attachments can be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added to the backup file.  

===Backing Up Other IMSMA<sup>NG<{{note| In a client/sup> Information===Apart server configuration, backups should be made from the IMSMA^NG database and attachment stored server rather than the clients. Similarly, backups can only be restored on the {{IMSMANG}} server, IMSMA^NG Backup allows members to backup specific elements from the client including: .}}

*GIS ===Attachments===__NOEDITSECTION__{{IMSMANG}} stores attachments on the server file system separate from the {{IMSMANG}} database (.mdb Because of the total file)*map files (size of the attachments, it may not be beneficial or necessary to back up the attachments each time.mxd, etc)*field report template files*iReport template files*translation {{IMSMANG}} Backup provides the option to exclude attachments when performing a backup which is '''not''' recommended.properties files

====GIS Dataabase=Maps===__NOEDITSECTION__IMSMA^NG also stores corrdinate data {{IMSMANG}} map files can be loaded on each a per-client computer basis and stored in a geodatabase file (IMSMA.mdb) {{IMSMANG}} Backup, providing an easy way to allow data to be displayed on a mapshare maps between clients. Even if the file In Map Data is missing, IMSMA^NG automatically builds this file aftre also the system launch. However, it can take several hours. To avoid this, each IMSMA^NG backup should include this file to reduce the time it takes to launch IMSMA^NG after a restore[[Customise Sub-Themes | sub-theme]] assignments included.

Likewise, since the geodatabase is structured on a per-client basis, ===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__{{IMSMANG}} provides the best way capability to fully update the geodatabase is store copies of drafts of Data Entry Form templates and iReport templates to launch the client prior to backing it upfile system during report design. Once it is While the published versions of the templates are backed upas part of the {{IMSMANG}} database backup, users can shorten the time required to build files are only included if the option is selected on the {{IMSMANG}} Backup window. Storing these files in the geodatabase by manually transferring backup is recommended as it makes it easier to newly installed clinetsresume drafting templates and reports.

====Maps====* client and server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)IMSMA^NG * the background map fiiles can be loaded on a per(s) source files ('''not''' only the .mxd file)* local projection files (.prj)* C:\IMSMAng\migration\conf\migration.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-client basis ons are not backed up by {{IMSMANG}} and stored in IMSMA^NG Backup, providing an easy way to share maps between clientsinformation managers should ensure that these external tools are backed up manually.

[[File:Map Tip1CORRECT===Restore on the Server===__NOEDITSECTION__In a client/server environment, the {{IMSMANG}} database can be restored only on the server machine so as to prevent accidental deletion of data by client users. Conducting an {{IMSMANG}} Restore on the server machine (or a stand-alone machine) restores the {{IMSMANG}} database and the available attachments to the server, replacing any existing data in the {{IMSMANG}} database. When a restore is complete, {{IMSMANG}} closes and must be restarted.png|border|caption]]

{{NavBox 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. Administration}}