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 {{IMSMANG}} data is regularly backed up, but more importantly a multitiered backup strategy should be used to eliminate data loss. Consider the following options below when developing a backup strategy for {{IMSMANG}}.

===Backing Up Moreover, a backup is only as if you are able to restore it. As such, any data backup strategy should include plans to test existing backups to ensure that the IMSMA^NG Database===backups are usable. If it becomes necessary to restore data, regular testing of backups helps ensure that it will be possible to do so.

===Backing Up Other IMSMA^NG InformationAttachments===__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.

====GIS Dataabase=Database===__NOEDITSECTION__IMSMA^NG also While {{IMSMANG}} stores corrdinate all coordinate data on each client computer in the PGSQL database that is backed up with the {{IMSMANG}} database, {{IMSMANG}} also uses a geodatabase file (IMSMA.mdbgdb) , also known as the sandbox, to allow 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 be displayed on launch {{IMSMANG}} after a maprestore. Even {{IMSMANG}} automatically rebuilds the sandbox during launch of the {{IMSMANG}} if the file sandbox is missing, IMSMA^NG automatically builds this file aftre the system launch. However, but it can take several hoursto do so. To avoid thisAfter it is backed up, each IMSMA^NG backup should include this file the sandbox can be transferred manually to other freshly installed clients to reduce shorten the time it takes required to build the geodatabase during system launch IMSMA^NG after a restore.

Likewise, since the geodatabase is structured ===Maps===__NOEDITSECTION__{{IMSMANG}} map files can be loaded on a per-client basisand stored in {{IMSMANG}} Backup, the best providing an easy way to fully update the geodatabase is to launch the client prior to backing it upshare maps between clients. Once it In Map Data is backed up, users can shorten also the time required to build the geodatabase by manually transferring it to newly installed clinets[[Customise Sub-Themes | sub-theme]] assignments included.

====Maps=Data Entry Form Templates and iReport Templates===__NOEDITSECTION__IMSMA^NG map fiiles can be loaded {{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 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.

[[File:Map_Tip1===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 .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 made.png|border|caption]]

==Other Backup Considerations==Field Report Templates __NOEDITSECTION__While {{IMSMANG}} Backup backs up all of the files used in the standard configuration of {{IMSMANG}}, there are other files that should also be backed up and iReport Templates====/or carefully documented.

IMSMA^NGusers can store copies or drafts of field reports templates * client and iReports templates to server '''settings''' including memory settings* C:\IMSMAng\server\gis\maps\imsma.mxd (if customized)* the background map(s) source files ('''not''' only the .mxd file system)* local projection files (. Select the option on the IMSMA^NG Backup window to store 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}} and information managers should ensure that these files in the backupexternal tools are backed up manually.

==IMSMA Restore==Translations====__NOEDITSECTION__Translations and localizations of {{Warning| {{IMSMANG}} Restore replaces all data elements are stored in the IMSMA^NG {{IMSMANG}} database and secured with 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 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. Although Each option behaves slightly differently depending on whether the properties files used to translate restore is occurring on a server or a client. ===Restore on the IMSMA<sup>NG<Server===__NOEDITSECTION__In a client/sup> interface are stored externally to server environment, the {{IMSMANG}} database, they can be added 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 IMSMA^NG Backupserver, replacing any existing data in the {{IMSMANG}} database. Be sure to backup all properties files each time When a change or restore is complete, {{IMSMANG}} closes and must be restarted.  {{note| In a full backup client/server environment, it is maderecommended to stop the server prior to restoring the database to ensure all clients are disconnected.}} {{NavBox IMSMA NG Administration}} [[Category:NAA]]