Changes

*{{IMSMANG}}-specific backups

Finally, 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 backup strategy should include occasioanl tests to ensure that all of and/or Data Entry Forms* changing SQL views in the backups are functioning properlydatabase.

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

[[File:BackingUp Tip1CORRECTInformation 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.png|border|caption]]

Information Managers can create automatic dailiy ===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 weekly backups using MySQL Administration toolsnecessary to back up the attachments each time. These backups also work simultaneously with IMSMA ^NG {{IMSMANG}} Backup; however any provides the option to exclude attachments when performing a backup made outside of IMSMA ^NG needs to be manually restoredwhich is '''not''' recommended.

[[File:BackingUp Tip2For 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.png|border|caption]]

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

Attachmes are stored seprately from ===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__{{IMSMANG}} provides the IMSMA^NG database on capability to store copies of drafts of Data Entry Form templates and iReport templates to the server filesystem during report design. However because While the published versions of their size, it may not be necessary to back the templates are backed up as part of the attachments each time. For this reason{{IMSMANG}} database backup, IMSMA^NG the files are only included if the option is selected on the {{IMSMANG}} Backup provides window. Storing these files in the option of excluding attachments when performing a backupis recommended as it makes it easier to resume drafting templates and reports.

Including attachments is still reccomended for complete backups. However==Other Backup Considerations==__NOEDITSECTION__While {{IMSMANG}} Backup backs up all of the files used in the standard configuration of {{IMSMANG}}, if the file size is too large attachments can there are other files that should also be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added to the backup filebacked up and/or carefully documented.

===Backing Up Other IMSMA^NG Information===Apart from the IMSMA^NG database * client and attachment stored on the server, IMSMA^NG Backup allows members to backup specific elements from the client '''settings''' including: memory settings*GIS database C:\IMSMAng\server\gis\maps\imsma.mxd (.mdb fileif customized)*the background map (s) source files ('''not''' only the .mxd, etcfile)*field report template local projection files(.prj)*iReport template files*translation C:\IMSMAng\migration\conf\migration.properties filesand any import scripts   ====GIS Dataabase====IMSMA^NG also stores corrdinate data on each client computer in a geodatabase file * [[Language and Translations#Data language|fallback fonts]] (IMSMA.mdbC:\IMSMAng\java\lib\fonts\fallback) to allow data to be displayed on a map. Even if the file is missing, IMSMA^NG automatically builds this file aftre the system launch. However, it can take several hours. To avoid this, each IMSMA^NG backup should include this file to reduce the time it takes to launch IMSMA^NG after a restore.* ODBC configurations* External toolsLikewise, since the geodatabase is structured on a per: External reporting tools and other add-client basis, the best way to fully update the geodatabase is to launch the client prior to backing it ons are not backed up. Once it is by {{IMSMANG}} and information managers should ensure that these external tools are backed up, users can shorten the time required to build the geodatabase by manually transferring it to newly installed clinets.    ====Maps====IMSMA^NG map fiiles can be loaded on a per-client basis and stored in IMSMA^NG Backup, providing an easy way to share maps between clients.  [[File:Map Tip1CORRECT.png|border|caption]]

====Field Report Templates and iReport Templates=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.

IMSMA<sup>NG<{{note| In a client/sup>users can store copies or drafts of field reports templates and iReports templates server environment, it is recommended to stop the file system. Select server prior to restoring the option on the IMSMA^NG Backup window database to store these files in the backupensure all clients are disconnected.}}