Changes

{{HowTo's|[[Standalone]]|[[Network Environment]]|[[Externally Connected Tools]]|[[Attachments]]}} ==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^NG {{IMSMANG}} 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^NG{{IMSMANG}}.

*{{IMSMANG}}-specific backups 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 backups are usable. If it becomes necessary to restore data, regular testing of backups helps ensure that it will be possible to do so.

Finally, 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 backup strategy should include occasioanl tests to ensure that all of and/or Data Entry Forms* changing SQL views in the backups are functioning properlydatabase.

===Backing Up the IMSMA^NG {{IMSMANG}} Database===__NOEDITSECTION__The IMSMA^NG Datebase holds 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.

{{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 Tip1CORRECT.pngBackup IMSMA Data|Backup IMSMA Data]]|border[[Scheduling Backup|captionScheduling Backup of IMSMA database]]}}

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. Even so, regularly scheduled backups are an excellent component of a backup strategy.

[[File:BackingUp Tip2{{note| In a client/server configuration, backups should be made from the server rather than the clients. Similarly, backups can only be restored on the {{IMSMANG}} server.png|border|caption]]}}

===Attachments===__NOEDITSECTION__Attachmes are stored seprately from the IMSMA^NG database {{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 InformationGIS Database===__NOEDITSECTION__Apart from While {{IMSMANG}} stores all coordinate data in the IMSMA^NG PGSQL database and attachment stored on that is backed up with the server{{IMSMANG}} database, {{IMSMANG}} also uses a geodatabase file (IMSMA^NG Backup allows members .gdb), also known as the sandbox, to display the data in the Map Pane inside {{IMSMANG}}. These files should be included with each {{IMSMANG}} backup specific elements from to shorten the time it takes to launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically rebuilds the sandbox during launch of the {{IMSMANG}} if the sandbox is missing, but it can take several hours to do so. After it is backed up, the sandbox can be transferred manually to other freshly installed clients to shorten the time required to build the client including: geodatabase during system launch.

*GIS database (.mdb file)===Maps===__NOEDITSECTION__*{{IMSMANG}} map files (can be loaded on a per-client basis and stored in {{IMSMANG}} Backup, providing an easy way to share maps between clients.mxd, etc)*field report template files*iReport template files*translation In Map Data is also the [[Customise Sub-Themes | sub-theme]] assignments included.properties files

====GIS Dataabase=Data Entry Form Templates and iReport Templates===__NOEDITSECTION__IMSMA^NG also stores corrdinate data on each client computer in a geodatabase file (IMSMA.mdb) {{IMSMANG}} provides the capability to allow data store copies of drafts of Data Entry Form templates and iReport templates to be displayed on a mapthe file system during report design. Even While the published versions of the templates are backed up as part of the {{IMSMANG}} database backup, the files are only included if the file option is missing, IMSMA^NG automatically builds this file aftre selected on the system launch{{IMSMANG}} Backup window. However, Storing these files in the backup is recommended as it can take several hours. To avoid this, each IMSMA^NG backup should include this file to reduce the time makes it takes easier to launch IMSMA^NG after a restoreresume drafting templates and reports.

Likewise, since ===Translations===__NOEDITSECTION__{{IMSMANG}} stores translations of the application in several places. Translations and localisations of data elements are stored in the {{IMSMANG}} database and are backed up with the geodatabase is structured on a per-client basis, database backup. The .properties files used to translate the best way {{IMSMANG}} interface are stored externally to fully update the geodatabase is database, but they can be added to launch the client prior {{IMSMANG}} Backup as an option. If changes are made to backing the .properties files, it is recommended to back them upafter each change as well as each time a full backup is made. Once it is  ==Other Backup Considerations==__NOEDITSECTION__While {{IMSMANG}} Backup backs up all of the files used in the standard configuration of {{IMSMANG}}, there are other files that should also be backed up, users can shorten and/or carefully documented.  * client and server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)* the time required to build background map(s) source files ('''not''' only the geodatabase .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-ons are not backed up by {{IMSMANG}} and information managers should ensure that these external tools are backed up manually transferring it .  ==IMSMA Restore==__NOEDITSECTION__{{Warning| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and copy over existing files. Prior to restoring the {{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 determine which components of an {{IMSMANG}} Backup to newly installed clientsrestore. The components available depend on the options that were selected during backup. Each option behaves slightly differently depending on whether the restore is occurring on a server or a client.

====Maps=Restore on the Server===__NOEDITSECTION__IMSMA<sup>NG<In a client/sup> map fiiles server environment, the {{IMSMANG}} database can be loaded 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 perstand-client basis alone machine) restores the {{IMSMANG}} database and stored the available attachments to the server, replacing any existing data in IMSMA^NG Backupthe {{IMSMANG}} database. When a restore is complete, providing an easy way to share maps between clients{{IMSMANG}} closes and must be restarted.

[[File:Map Tip1CORRECT{{note| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected.png|border|caption]]}}

====Field Report Templates and iReport Templates===={{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}}