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

===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 Tip1CORRECT.png|border|caption]]  Information Managers managers can create automatic dailiy or weekly schedule backups using MySQL PGSQL Administration toolsand build daily or weekly routines that back up the database automatically. These backups also work simultaneously with IMSMA ^NG similarly to {{IMSMANG}} Backup; however , any backup made outside of IMSMA ^NG needs {{IMSMANG}} will have to be restored manually restored.   [[File:BackingUp Tip2.png|border|caption]]  ===Attachments=== Attachmes Even so, regularly scheduled backups are stored seprately from the IMSMA^NG database on the server file. However because of their size, it may not be necessary to back up the attachments each time. For this reason, IMSMA^NG Backup provides the option an excellent component of excluding attachments when performing a backupstrategy.  Including attachments is still reccomended for complete backups. However, if the file size is too large attachments can be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added to the backup file.   ===Backing Up Other IMSMA^NG Information===Apart from the IMSMA^NG database and attachment stored on the server, IMSMA^NG Backup allows members to backup specific elements from the client including:

*GIS database (.mdb file)*map files ({{note| In a client/server configuration, backups should be made from the server rather than the clients.mxdSimilarly, etc)*field report template files*iReport template files*translation backups can only be restored on the {{IMSMANG}} server.properties files}}

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

==Other Backup Considerations==Maps====__NOEDITSECTION__IMSMA^NG map fiiles can While {{IMSMANG}} Backup backs up all of the files used in the standard configuration of {{IMSMANG}}, there are other files that should also be loaded on a per-client basis backed up and stored in IMSMA^NG Backup, providing an easy way to share maps between clientsor carefully documented.

==IMSMA Restore==__NOEDITSECTION__{{Warning| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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| [[File:Map Tip1CORRECT.pngRestore IMSMA Backup on Server]]|border|caption[[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. Each option behaves slightly differently depending on whether the restore is occurring on a server or a client.

{{NavBox IMSMA^NGusers can store copies or drafts of field reports templates and iReports templates to the file system. Select the option on the IMSMA^NG Backup window to store these files in the backup.Administration}}