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

===Backing Up Note that an event-based change to the IMSMA<sup>NG<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> Database===or Data Entry Forms* changing SQL views in the database.

The IMSMA^NG Datebase holds ===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 Tip1CORRECTInformation 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|border|caption]]

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

===AttachmentsMaps===__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. In Map Data is also the [[Customise Sub-Themes | sub-theme]] assignments included.

Attachmes are stored seprately from ===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__{{IMSMANG}} provides the IMSMA^NG database on capability to store copies of drafts of Data Entry Form templates and iReport templates to the server filesystem during report design. However because While the published versions of their size, it may not be necessary to back the templates are backed up as part of the attachments each time. For this reason{{IMSMANG}} database backup, IMSMA^NG the files are only included if the option is selected on the {{IMSMANG}} Backup provides window. Storing these files in the option of excluding attachments when performing a backupis recommended as it makes it easier to resume drafting templates and reports.

Including attachments is still reccomended for complete backups===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 . Howeverproperties files used to translate the {{IMSMANG}} interface are stored externally to the database, if the file size is too large attachments but they can be deleted manuallyadded to the {{IMSMANG}} Backup as an option. Avoid excluding attachemtns from backups since attachmets cannot be added 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 fileis made.

===Backing Up Other IMSMA^NG Information===* client and server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)Apart from * the IMSMA^NG database background map(s) source files ('''not''' only the .mxd file)* local projection files (.prj)* C:\IMSMAng\migration\conf\migration.properties and any import scripts* [[Language and attachment stored on the server, IMSMA^NG Backup allows members to backup specific elements from the client includingTranslations#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.

*GIS ==IMSMA Restore==__NOEDITSECTION__{{Warning| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database (.mdb file)*map and copy over existing files (.mxdPrior to restoring the {{IMSMANG}} database, etc)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]]*field report template files|[[Restore IMSMA Backup on Client]]*iReport template files}}*translation 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.properties files

====GIS Dataabase===={{NavBox IMSMA^NG also stores corrdinate data on each client computer 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 this, each IMSMA^NG backup should include this file to reduce the time it takes to launch IMSMA^NG after a restore.Administration}}

Likewise, since the geodatabase is structured on a per-client basis, the best way to fully update the geodatabase is to launch the client prior to backing it up. Once it is backed up, users can shorten the time required to build the geodatabase by manually transferring it to newly installed clinets.    ====Maps====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.  [[FileCategory:Map Tip1CORRECT.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.