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.

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

For 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. ===GIS Database===__NOEDITSECTION__While {{IMSMANG}} stores all coordinate data in the PGSQL database that is backed up with the {{IMSMANG}} database, {{note| In IMSMANG}} also uses a client-server environmentgeodatabase file (IMSMA.gdb), backups also known as the sandbox, to display the data in the Map Pane inside {{IMSMANG}}. These files should be made from included with each {{IMSMANG}} backup to shorten the server rather than time it takes to launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically rebuilds the clientssandbox during launch of the {{IMSMANG}} if the sandbox is missing, but it can take several hours to do so. SimilarlyAfter it is backed up, backups the sandbox can only be restored on transferred manually to other freshly installed clients to shorten the IMSMANG server}}time required to build the geodatabase during system launch.

===AttachmentsMaps===__NOEDITSECTION__{{IMSMANG stores attachments }} map files can be loaded on the server file system separate from the a per-client basis and stored in {{IMSMANG database. Because of the size of some attachments}} Backup, it may not be beneficial or necessary providing an easy way to back up the attachments each timeshare maps between clients. IMSMANG Backup provides In Map Data is also the option to exclude attachments when performing a backup[[Customise Sub-Themes | sub-theme]] assignments included.

For regular, complete backups, it is recommended ===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 include attachmentsthe file system during report design. But, if While the published versions of the size templates are backed up as part of a the {{IMSMANG}} database backup file is a concern, the attachments can be manually deleted. This files are only included if the option is a better alternative to creating a backup without attachments since attachments cannot be added back to selected on the backup file{{IMSMANG}} Backup window. Excluding attachments from a Storing these files in the backup is an option that should be used with cautionrecommended as it makes it easier to resume drafting templates and reports.

===Backing Up Other IMSMA^NG InformationTranslations===__NOEDITSECTION__In addition to {{IMSMANG}} stores translations of the IMSMANG database application in several places. Translations and attachments localisations of data elements are stored on in the server, {{IMSMANG Backup allows users to back }} database and are backed up certain settings from with the IMSMANG client. These include: * GIS database (.mdb file)* map files (backup.mxd, etc)* field report template files* iReport template files* translation The .properties files ====GIS Dataabase====While used to translate the {{IMSMANG stores all coordinate data in }} interface are stored externally to the MySQL database that is backed up with , but they can be added to the {{IMSMANG database, IMSMANG also stores coordinate data in a geodatabase file (IMSMA}} Backup as an option.mdb) on each client computer to allow data If changes are made to be displayed on the map. This file should be included with each IMSMANG backup to shorten the time properties files, it takes is recommended to launch IMSMANG back them up after each change as well as each time a restore. IMSMANG automatically builds this file during system launch if the file full backup is missing, but it can take several hours to do somade.

Because ==Other Backup Considerations==__NOEDITSECTION__While {{IMSMANG}} Backup backs up all of the files used in the geodatabase is built on a per-client basisstandard configuration of {{IMSMANG}}, it is there are other files that should also recommended to launch the client to fully update the geodatabase prior to backing it up. After it is be backed up, the geodatabase can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase during system launchand/or carefully documented.

====Maps====* client and server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)IMSMA^NG * the background map (s) source files ('''not''' only the .mxd file)* local projection files can be loaded on a per(.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-client basis ons are not backed up by {{IMSMANG}} and stored in IMSMA^NG Backup, providing an easy way to share maps between clientsinformation managers should ensure that these external tools are backed up manually.

==IMSMA Restore==__NOEDITSECTION__{{noteWarning| {{IMSMANG Backup backs up only }} Restore replaces all data in the active map on each client{{IMSMANG}} database and copy over existing files. Other maps previously loaded on a client will need Prior to restoring the {{IMSMANG}} database, information managers should ensure that all necessary data has been backed up. {{IMSMANG}} Restore operations cannot be copied manuallyundone.}}{{HowTo's| [[Restore IMSMA Backup on Server]]|[[Restore IMSMA Backup on Client]]