Changes

*[[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. {{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.}} ===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.

Information Managers can create automatic dailiy or weekly For regular, complete backups using MySQL Administration tools, it is highly recommended to include attachments. These backups It is also work simultaneously with possible to take an IMSMA ^NG Backup; however any backup made outside of IMSMA ^NG needs to be manually restoredthe database and a file backup of the attachments.

[[File:BackingUp Tip2===GIS Database===__NOEDITSECTION__While {{IMSMANG}} stores all coordinate data in the PGSQL database that is backed up with the {{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. {{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 geodatabase during system launch.png|border|caption]]

===AttachmentsMaps===__NOEDITSECTION__Attachmes are {{IMSMANG}} map files can be loaded on a per-client basis and stored seprately from the IMSMA^NG database on the server file. However because of their sizein {{IMSMANG}} Backup, it may not be necessary providing an easy way to back up the attachments each timeshare maps between clients. For this reason, IMSMA^NG Backup provides In Map Data is also the option of excluding attachments when performing a backup[[Customise Sub-Themes | sub-theme]] assignments included.

Including attachments is still reccomended for complete backups===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 system during report design. HoweverWhile the published versions of the templates are backed up as part of the {{IMSMANG}} database backup, the files are only included if the file size option is too large attachments can be deleted manuallyselected on the {{IMSMANG}} Backup window. Avoid excluding attachemtns from backups since attachmets cannot be added to Storing these files in the backup fileis recommended as it makes it easier to resume drafting templates and reports.

===Backing Up Other IMSMA^NG InformationTranslations===__NOEDITSECTION__Apart from {{IMSMANG}} stores translations of the IMSMA^NG application in several places. Translations and localisations of data elements are stored in the {{IMSMANG}} database and attachment are backed up with the database backup. The .properties files used to translate the {{IMSMANG}} interface are stored on externally to the serverdatabase, IMSMA^NG but they can be added to the {{IMSMANG}} Backup allows members as an option. 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 specific elements from the client including: is made.

*GIS database (.mdb file)==Other Backup Considerations==__NOEDITSECTION__*map While {{IMSMANG}} Backup backs up all of the files (.mxdused in the standard configuration of {{IMSMANG}}, etc)*field report template there are other files*iReport template files*translation that should also be backed up and/or carefully documented.properties files

====GIS Dataabase====* client and server '''settings''' including memory settingsIMSMA^NG also stores corrdinate data on each client computer in a geodatabase file * C:\IMSMAng\server\gis\maps\imsma.mxd (IMSMA.mdbif customized) to allow data to be displayed on a * the background map(s) source files ('''not''' only the . Even if the mxd file is missing, IMSMA^NG automatically builds this file aftre the system launch)* local projection files (. However, it can take several hoursprj)* C:\IMSMAng\migration\conf\migration. To avoid this, each IMSMA^NG backup 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 include this file to reduce the time it takes to launch IMSMA^NG after a restoreensure that these external tools are backed up manually.

Likewise, since ==IMSMA Restore==__NOEDITSECTION__{{Warning| {{IMSMANG}} Restore replaces all data in the geodatabase is structured on a per-client basis, the best way {{IMSMANG}} database and copy over existing files. Prior to fully update restoring the geodatabase is {{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 launch the client prior determine which components of an {{IMSMANG}} Backup to backing it uprestore. Once it is backed up, users can shorten The components available depend on the time required to build options that were selected during backup. Each option behaves slightly differently depending on whether the geodatabase by manually transferring it to newly installed clientsrestore 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}}