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:Backup IMSMA Data|Backup IMSMA Data]]|[[Scheduling Backup|Scheduling 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 {{note| In a client-server environmentIMSMANG}} Backup; however, backups should any backup made outside of {{IMSMANG}} will have to be made from the server rather than the clientsrestored manually. SimilarlyEven so, regularly scheduled backups can only be restored on the IMSMANG server}}are an excellent component of a backup strategy.

===Attachments===IMSMANG stores attachments on {{note| In a client/server configuration, backups should be made from the server file system separate from rather than the IMSMANG databaseclients. Because of the size of some attachmentsSimilarly, it may not backups can only be beneficial or necessary to back up restored on the attachments each time. {{IMSMANG Backup provides the option to exclude attachments when performing a backup}} server.}}

For regular, complete backups, it is recommended to include ===Attachments===__NOEDITSECTION__{{IMSMANG}} stores attachmentson the server file system separate from the {{IMSMANG}} database. But, if Because of the total file size of a backup file is a concern, the attachments can , it may not be manually deleted. This is a better alternative beneficial or necessary to creating a backup without attachments since attachments cannot be added back to up the backup fileattachments each time. Excluding {{IMSMANG}} Backup provides the option to exclude attachments from when performing a backup which is an option that should be used with caution'''not''' recommended.

===Backing Up Other IMSMA^NG Information===In addition to the IMSMANG database and attachments stored on the serverFor regular, complete backups, IMSMANG Backup allows users it is highly recommended 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 attachments.properties files ====GIS Dataabase====While IMSMANG stores all coordinate data in the MySQL database that It is backed up with the IMSMANG database, IMSMANG also stores coordinate data in a geodatabase file (possible to take an IMSMA.mdb) on each client computer to allow data to be displayed on the map. This file should be included with each IMSMANG backup to shorten of the time it takes to launch IMSMANG after database and a restore. IMSMANG automatically builds this file during system launch if backup of the file is missing, but it can take several hours to do soattachments.

Because ===GIS Database===__NOEDITSECTION__While {{IMSMANG}} stores all coordinate data in the geodatabase PGSQL database that is built on backed up with the {{IMSMANG}} database, {{IMSMANG}} also uses a per-client basisgeodatabase file (IMSMA.gdb), it is also recommended known as the sandbox, to launch display the data in the client Map Pane inside {{IMSMANG}}. These files should be included with each {{IMSMANG}} backup to fully update shorten the geodatabase prior time it takes to backing launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically rebuilds the sandbox during launch of the {{IMSMANG}} if the sandbox is missing, but it upcan take several hours to do so. After it is backed up, the geodatabase sandbox can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase during system launch.

====Maps====__NOEDITSECTION__IMSMA^NG {{IMSMANG}} map files can be loaded on a per-client basis and stored in IMSMA^NG {{IMSMANG}} Backup, providing an easy way to share maps between clients. In Map Data is also the [[Customise Sub-Themes | sub-theme]] assignments included.

===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__{{note| IMSMANG Backup backs }} 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 are only included if the active map option is selected on each clientthe {{IMSMANG}} Backup window. Other maps previously loaded on a client will need Storing these files in the backup is recommended as it makes it easier to be copied manually}}resume drafting templates and reports.

====Field Report Templates and iReport Templates=Translations===__NOEDITSECTION__{{IMSMANG provides the capability to store copies or drafts }} stores translations of field report templates and iReport templates to the file system during report designapplication in several places. While the published versions Translations and localisations of data elements are stored in the templates {{IMSMANG}} database and are backed up as part of with the IMSMANG database backup, . The .properties files used to translate the files {{IMSMANG}} interface are only included if stored externally to the option is selected on database, but they can be added to the {{IMSMANG }} Backup windowas an option. Storing these If changes are made to the .properties files in the backup , it is recommended to back them up after each change as well as it makes it easier to resume drafting templates and reportseach time a full backup is made.

==Other Backup Considerations==Translations====__NOEDITSECTION__While {{IMSMANG stores translations of the application in several places. Translations and localisations }} Backup backs up all of data elements are stored in the IMSMANG database and are backed up with the database backup. The .properties files used to translate in the standard configuration of {{IMSMANG interface are stored externally to the database}}, but they can be added to the IMSMANG Backup as an option. If changes there are made to the .properties other files, it is recommended to back them that should also be backed up after each change as well as each time a full backup is madeand/or carefully documented.

===Other Backup Considerations===* client and server '''settings''' including memory settingsWhile IMSMANG Backup backs up all of * C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)* the background map(s) source files used in ('''not''' only the typical operation of .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 by {{IMSMANG, there }} and information managers should ensure that these external tools are other customisable files that should also be backed upmanually. These include:

* map customisationsIMSMANG does not automatically back up customisations made to maps used in IMSMANG. Users can make changes to the imsma.mxd file, create or modify ESRI style files, add symbology or make many other changes to maps, but these files are not included in the IMSMANG Backup and must be separately backed up and managed.* base mapsIt is recommended that information managers make backups of maps that are imported into IMSMANG for use on client computers. While IMSMANG Backup backs up the maps when they have been imported, these base map files are not managed within IMSMANG and should be backed up manually to allow for customisation and later import.* external reporting toolsExternal reporting tools and other add-ons are not backed up by IMSMANG and should be backed up manually. These include any tools using ODBC connections to IMSMANG such as Microsoft Access databases, Microsoft Excel spreadsheets, OpenOffice connections and Crystal Reports. Information managers should ensure that these tools get backed up manually or automatically. ==IMSMA Restore==__NOEDITSECTION__{{importantWarning| {{IMSMANG }} Restore replaces all data in the {{IMSMANG }} database and may 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 Backup on Server]]|[[Restore IMSMA Backup on Client]]

Backups created using IMSMANG Backup can be restored using IMSMANG Restore as well as other MySQL tools if necessary. The IMSMANG Restore function can be used on both clients and servers to restore key information in the event of data loss or other restore needs (for example, after an upgrade). 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. ===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.  IMSMANG Restore can also restore the GIS database, field report templates, iReport templates, map files and translation .properties files; however, these are only necessary when running the client on the server or when running in stand-alone mode. {{note| In a client-server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected}}

===Restore on the Client===Except for instances where the {{note| In a client and the /server are on the same machineenvironment, the IMSMANG database cannot be restored to a client-only machine. However, IMSMANG Restore can be used it is recommended to restore client settings including stop the GIS database, field report templates, iReport templates, map files and translation .properties files. This functionality is particularly useful when connecting new clients to a server as this allows information managers prior to prebuild restoring the GIS database and map configurations and simply restore them to the new ensure all clientsare disconnected. On a client machine, IMSMANG Restore acts as a file copying function, copying files included in the backup to the correct location on the client. IMSMANG Restore also attempts to back up any files it is replacing. These backup directories have “_orig” appended to their file names to distinguish them from the new files. }}

{{important| IMSMANG Restore preserves only one backup of these files. Previous _orig directories are replaced with each IMSMANG Restore so care must be taken to preserve these files, if desired, prior to running IMSMANG RestoreNavBox IMSMA NG Administration}}