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

FinallyMoreover, a backup is only as if you are able 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.

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/or Data Entry Forms* changing SQL views in the database. ===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 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.

Information Managers can create automatic dailiy or weekly {{note| In a client/server configuration, backups using MySQL Administration toolsshould be made from the server rather than the clients. These Similarly, backups also work simultaneously with IMSMA ^NG Backup; however any backup made outside of IMSMA ^NG needs to can only be manually restoredon the {{IMSMANG}} server. }}

[[File:BackingUp Tip2===Attachments===__NOEDITSECTION__{{IMSMANG}} stores attachments on the server file system separate from the {{IMSMANG}} database. Because of the total file size of the attachments, it may not be beneficial or necessary to back up the attachments each time. {{IMSMANG}} Backup provides the option to exclude attachments when performing a backup which is '''not''' recommended.png|border|caption]]

===Attachments===Attachmes are stored seprately from the IMSMA^NG database on the server file. However because of their sizeFor regular, complete backups, it may not be necessary is highly recommended to back up the include attachments each time. For this reason, It is also possible to take an IMSMA^NG Backup provides backup of the option database and a file backup of excluding the attachments when performing a backup.

Including attachments ===GIS Database===__NOEDITSECTION__While {{IMSMANG}} stores all coordinate data in the PGSQL database that is still reccomended for complete backupsbacked up with the {{IMSMANG}} database, {{IMSMANG}} also uses a geodatabase file (IMSMA. Howevergdb), also known as the sandbox, to display the data in the Map Pane inside {{IMSMANG}}. These files should be included with each {{IMSMANG}} backup to shorten the time it takes to launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically rebuilds the sandbox during launch of the {{IMSMANG}} if the file size sandbox is missing, but it can take several hours to do so. After it is too large attachments backed up, the sandbox can be deleted transferred manually. Avoid excluding attachemtns from backups since attachmets cannot be added to other freshly installed clients to shorten the time required to build the backup filegeodatabase during system launch.

===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=Translations===__NOEDITSECTION__IMSMA^NG also {{IMSMANG}} stores corrdinate translations of the application in several places. Translations and localisations of data on each client computer elements are stored in a geodatabase file (IMSMAthe {{IMSMANG}} database and are backed up with the database backup. The .mdb) properties files used to allow data translate the {{IMSMANG}} interface are stored externally to be displayed on a map. Even if the file is missingdatabase, IMSMA^NG automatically builds this file aftre but they can be added to the system launch{{IMSMANG}} Backup as an option. However, it can take several hoursIf changes are made to the . To avoid thisproperties files, each IMSMA^NG backup should include this file to reduce the time it takes is recommended to launch IMSMA^NG back them up after each change as well as each time a restorefull backup is made.

Likewise, since ==Other Backup Considerations==__NOEDITSECTION__While {{IMSMANG}} Backup backs up all of the files used in the geodatabase is structured on a per-client basisstandard configuration of {{IMSMANG}}, the best way to fully update the geodatabase is to launch the client prior to backing it up. Once it is there are other files that should also be backed up, users can shorten the time required to build the geodatabase by manually transferring it to newly installed clientsand/or carefully documented.

====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.

==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| [[File:Map Tip1CORRECT.pngRestore IMSMA Backup on Server]]|border|caption[[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 restore. 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.

====Field Report Templates and iReport Templates=Restore on the Server===__NOEDITSECTION__IMSMA<sup>NG<In a client/sup>users server environment, the {{IMSMANG}} database can store copies or drafts be restored only on the server machine so as to prevent accidental deletion of field reports templates and iReports templates to data by client users. Conducting an {{IMSMANG}} Restore on the file system. Select server machine (or a stand-alone machine) restores the option on {{IMSMANG}} database and the IMSMA^NG Backup window available attachments to store these files the server, replacing any existing data in the backup{{IMSMANG}} database. When a restore is complete, {{IMSMANG}} closes and must be restarted.

====Translations====Translations and localizations of data elements are stored in the IMSMA<sup>NG<{{note| In a client/sup> database and secured with the database backup. Although the properties files used server environment, it is recommended to translate stop the IMSMA^NG interface are stored externally server prior to restoring the database, they can be added to the IMSMA^NG Backup. Be sure to backup ensure all properties files each time a change or a full backup is madeclients are disconnected.}}

{{NavBox Using IMSMANG Administration}}

[[Category:Maintaining+ IMSMANAA]]