Changes

==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 good as the ability 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.

The table below outlines the recommended schedule for backing up the IMSMANG database and other files. Note that an event-based change to the components necessitates a backup. Event-based changes include events such as: * Before upgrading software* Before importing data* After importing field reports* After making SQL changes to the database  Server Client Server and ClientComponent Daily Weekly Weekly Event-based changeIMSMANG database ● ● ●Attachments ● ● ●GIS database ● ● ●Maps ● ● ●Templates ● ● ●Translation ● ●}} ===Backing Up the IMSMA^NG {{IMSMANG}} Database===__NOEDITSECTION__IMSMANG contains several stores of information that can be backed up. By far, the most critical store component to backup is the {{IMSMANG }} database itself because it contains all of the active actual data in {{IMSMANG including }} and published reportstemplates, form templates and geographic data in addition to the typical mine action informationetc. IMSMANG’s {{IMSMANG}}’s Backup capability backs up the {{IMSMANG }} database by executing a MySQL PGSQL database dump command that creates a complete backup of all of the data in the database including any additional tables, views and other customisations. The resulting dump.sql file, which is stored in a time-stamped directory for easy identification, includes the necessary commands to recreate the database with all of the existing data.

{{note| The dump.sql file is stored in text format and can be made smaller for storage or transport using compression tools such as ZIP and RARWinZIP. }}{{HowTo's|[[Backup IMSMA Data|Backup IMSMA Data]]|[[Scheduling Backup|Scheduling Backup of IMSMA database]]

Information managers can augment the IMSMANG Backup capability with other scheduled schedule backups using MySQL PGSQL Administration tools, for example, 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 environmentconfiguration, 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 some 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 backupwhich is '''not''' recommended.

For regular, complete backups, it is highly recommended to include attachments. But, if It is also possible to take an IMSMA backup of the size of database and a backup file is a concern, the attachments can be manually deleted. This is a better alternative to creating a backup without attachments since attachments cannot be added back to of the backup file. Excluding attachments from a backup is an option that should be used with caution.

===Backing Up Other IMSMA^NG Information===In addition to the IMSMANG database and attachments stored on the server, IMSMANG Backup allows users to back up certain settings from the IMSMANG client. These include: * GIS database (.mdb file)* map files (.mxd, etc)* field report template files* iReport template files* translation .properties files ====GIS Dataabase=Database===__NOEDITSECTION__While {{IMSMANG }} stores all coordinate data in the MySQL PGSQL database that is backed up with the {{IMSMANG }} database, {{IMSMANG }} also stores coordinate data in uses a geodatabase file (IMSMA.mdbgdb) on each client computer , also known as the sandbox, to allow display the data to be displayed on in the mapMap Pane inside {{IMSMANG}}. This file These files should be included with each {{IMSMANG }} backup to shorten the time it takes to launch {{IMSMANG }} after a restore. {{IMSMANG }} automatically builds this file rebuilds the sandbox during system launch of the {{IMSMANG}} if the file 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.

Because the geodatabase is built ===Maps===__NOEDITSECTION__{{IMSMANG}} map files can be loaded on a per-client basisand stored in {{IMSMANG}} Backup, it is also recommended providing an easy way to launch the client to fully update the geodatabase prior to backing it upshare maps between clients. After it In Map Data is backed up, also the geodatabase can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase during system launch[[Customise Sub-Themes | sub-theme]] assignments included.

====Maps=Data Entry Form Templates and iReport Templates===__NOEDITSECTION__IMSMA^NG map {{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 published versions of the templates are backed up as part of the {{IMSMANG}} database backup, the files can be loaded are only included if the option is selected on a per-client basis and stored the {{IMSMANG}} Backup window. Storing these files in IMSMA^NG Backup, providing an easy way the backup is recommended as it makes it easier to share maps between clientsresume drafting templates and reports.

===Translations===__NOEDITSECTION__{{IMSMANG}} stores translations of the application in several places. Translations and localisations of data elements are stored in the {{note| IMSMANG Backup backs }} database and are backed up only with the active map on each clientdatabase backup. The . Other maps previously loaded on a client will need properties files used to translate the {{IMSMANG}} interface are stored externally to the database, but they can be copied manuallyadded to the {{IMSMANG}}Backup 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 is made.

==Other Backup Considerations==Field Report Templates and iReport Templates====__NOEDITSECTION__While {{IMSMANG provides the capability to store copies or drafts }} Backup backs up all of field report templates and iReport templates to the file system during report design. While the published versions of files used in the templates are backed up as part standard configuration of the {{IMSMANG database backup}}, the files there are only included if the option is selected on the IMSMANG Backup window. Storing these other files in the backup is recommended as it makes it easier to resume drafting templates that should also be backed up and reports/or carefully documented.

====Translations====* client and server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)IMSMANG stores translations of * the background map(s) source files ('''not''' only the application in several places. 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 localisations of data elements other add-ons are stored in the not backed up by {{IMSMANG database }} and information managers should ensure that these external tools are backed up with the database backup. The .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. 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 mademanually.

==Other Backup ConsiderationsIMSMA Restore==__NOEDITSECTION__While {{Warning| {{IMSMANG Backup backs up }} Restore replaces all of data in the {{IMSMANG}} database and copy over existing files used in . Prior to restoring the typical operation of {{IMSMANG}} database, there are other customisable files 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 also be backed uprestored 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. These include:

===Map Customisations===IMSMANG does not automatically back up customisations made {{note| In a client/server environment, it is recommended to maps used in IMSMANG. Users can make changes stop the server prior to restoring the imsma.mxd file, create or modify ESRI style files, add symbology or make many other changes database to maps, but these files ensure all clients are not included in the IMSMANG Backup and must be separately backed up and manageddisconnected.}}