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

Information Managers can create automatic dailiy ===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 weekly backups using MySQL Administration toolsnecessary to back up the attachments each time. These backups also work simultaneously with IMSMA ^NG {{IMSMANG}} Backup; however any provides the option to exclude attachments when performing a backup made outside of IMSMA ^NG needs to be manually restoredwhich is '''not''' recommended.

[[File:BackingUp Tip2For regular, complete backups, it is highly recommended to include attachments. It is also possible to take an IMSMA backup of the database and a file backup of the attachments.png|border|caption]]

===AttachmentsGIS Database===__NOEDITSECTION__Attachmes are stored seprately from While {{IMSMANG}} stores all coordinate data in the IMSMA^NG PGSQL database on that is backed up with the server {{IMSMANG}} database, {{IMSMANG}} also uses a geodatabase file(IMSMA.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 to shorten the time it takes to launch {{IMSMANG}} after a restore. However because {{IMSMANG}} automatically rebuilds the sandbox during launch of their sizethe {{IMSMANG}} if the sandbox is missing, but it may not can take several hours to do so. After it is backed up, the sandbox can be necessary transferred manually to back up other freshly installed clients to shorten the attachments each time. For this reason, IMSMA^NG Backup provides required to build the option of excluding attachments when performing a backupgeodatabase during system launch.

Including attachments is still reccomended for complete backups. However, if the file size is too large attachments ===Maps===__NOEDITSECTION__{{IMSMANG}} map files can be deleted manuallyloaded on a per-client basis and stored in {{IMSMANG}} Backup, providing an easy way to share maps between clients. Avoid excluding attachemtns from backups since attachmets cannot be added to In Map Data is also the backup file[[Customise Sub-Themes | sub-theme]] assignments included.

===Backing Up Other IMSMA^NG InformationData Entry Form Templates and iReport Templates===__NOEDITSECTION__Apart from {{IMSMANG}} provides the capability to store copies of drafts of Data Entry Form templates and iReport templates to the file system during report design. While the IMSMA^NG published versions of the templates are backed up as part of the {{IMSMANG}} database and attachment stored backup, the files are only included if the option is selected on the server, IMSMA^NG {{IMSMANG}} Backup allows members window. Storing these files in the backup is recommended as it makes it easier to backup specific elements from the client including: resume drafting templates and reports.

*GIS ===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 database (backup. The .mdb file)*map properties files (used to translate the {{IMSMANG}} interface are stored externally to the database, but they can be added to the {{IMSMANG}} Backup as an option.mxd, etc)*field report template files*iReport template files*translation If changes are made to the .properties files, it is recommended to back them up after each change as well as each time a full backup is made.

==Other Backup Considerations==GIS Dataabase====__NOEDITSECTION__IMSMA^NG also stores corrdinate data on each client computer While {{IMSMANG}} Backup backs up all of the files used in a geodatabase file (IMSMA.mdb) to allow data to be displayed on a map. Even if the file is missing, IMSMA^NG automatically builds this file aftre the system launch. However, it can take several hours. To avoid thisstandard configuration of {{IMSMANG}}, each IMSMA^NG backup there are other files that should include this file to reduce the time it takes to launch IMSMA<sup>NG<also be backed up and/sup> after a restoreor carefully documented.

Likewise, since the geodatabase is structured on a per-* client basis, and server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)* the best way to fully update background map(s) source files ('''not''' only the geodatabase is to launch the client prior to backing it up. Once it is 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, users can shorten the time required to build the geodatabase by {{IMSMANG}} and information managers should ensure that these external tools are backed up manually transferring it to newly installed clients.

==IMSMA Restore==Maps====__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^NG map fiiles can be loaded Backup on a per-client basis and stored in Server]]|[[Restore IMSMA^NG Backup, providing on Client]]}}Backups created using {{IMSMANG}} Backup should be restored using {{IMSMANG}} Restore. {{IMSMANG}} Restore allows users to determine which components of an easy way {{IMSMANG}} Backup to share maps between 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.

[[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]]

====Field Report Templates and iReport Templates====IMSMA<sup>NG<{{note| In a client/sup>users can store copies or drafts of field reports templates and iReports templates server environment, it is recommended to stop the file system. Select server prior to restoring the option on the IMSMA^NG Backup window database to store these files in the backupensure all clients are disconnected.}}

====Translations====Translations and localizations of data elements are stored in the {{NavBox 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.Administration}}