NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
__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}}.
*disk mirroring
*operating system backups
*hard disk backup
*offsite data storage
*{{IMSMANG}}-specific backups
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 {{IMSMANG}} Database===__NOEDITSECTION__
By far, the most critical component to backup is the {{IMSMANG}} database itself because it contains all of the actual data in {{IMSMANG}} and published templates, etc. {{IMSMANG}}’s Backup capability backs up the {{IMSMANG}} database by executing a PGSQL database dump command that creates a complete backup of all of the data in the database. The resulting dump.sql file, which is stored in a time-stamped directory for easy identification.
{{note| The dump.sql file is stored in text format and can be made smaller for storage using compression tools such as WinZIP. }}
{{HowTo's
|[[Backup IMSMA Data|Backup IMSMA Data]]
|[[Scheduling Backup|Scheduling Backup of IMSMA database]]
}}
{{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.}}
===Backing Up Other IMSMA<sup>NG</sup> InformationAttachments===__NOEDITSECTION__Apart {{IMSMANG}} stores attachments on the server file system separate from the IMSMA<sup>NG</sup> {{IMSMANG}} database and attachment stored on . Because of the total file size of the serverattachments, IMSMA<sup>NG</sup> it may not be beneficial or necessary to back up the attachments each time. {{IMSMANG}} Backup allows members provides the option to exclude attachments when performing a backup specific elements from the client including: which is '''not''' recommended.
===GIS Database===__NOEDITSECTION__
While {{IMSMANG}} stores all coordinate data in the PGSQL database that is backed up with the {{IMSMANG}} database, {{IMSMANG}} also uses a geodatabase file (IMSMA.gdb), also known as the sandbox, to 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 launch {{IMSMANG}} after a restore. {{IMSMANG}} automatically rebuilds the sandbox during launch of the {{IMSMANG}} if the sandbox is missing, but it can take several hours to do so. After it is backed up, the sandbox can be transferred manually to other freshly installed clients to shorten the time required to build the geodatabase during system launch.
===Maps===__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.
====GIS Dataabase=Data Entry Form Templates and iReport Templates===__NOEDITSECTION__IMSMA<sup>NG</sup> also stores corrdinate data on each client computer in a geodatabase file (IMSMA.mdb) {{IMSMANG}} provides the capability to allow data store copies of drafts of Data Entry Form templates and iReport templates to be displayed on a mapthe file system during report design. Even While the published versions of the templates are backed up as part of the {{IMSMANG}} database backup, the files are only included if the file option is missing, IMSMA<sup>NG</sup> automatically builds this file aftre selected on the system launch{{IMSMANG}} Backup window. However, Storing these files in the backup is recommended as it can take several hours. To avoid this, each IMSMA<sup>NG</sup> backup should include this file to reduce the time makes it takes easier to launch IMSMA<sup>NG</sup> after a restoreresume drafting templates and reports.
==Other Backup Considerations==__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/or carefully documented.
* client and 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)
* 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}} and information managers should ensure that these external tools are backed up manually.
==IMSMA Restore==Maps====__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| [[Restore IMSMA<sup>NG</sup> map fiiles can be loaded Backup on a per-client basis and stored in Server]]|[[Restore IMSMA<sup>NG</sup> Backup, providing on Client]]}}Backups created using {{IMSMANG}} Backup should be restored using {{IMSMANG}} Restore. {{IMSMANG}} Restore allows users to determine which components of an easy way {{IMSMANG}} Backup to share maps between clientsrestore. 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<sup>NG</sup>users can store copies or drafts of field reports templates and iReports templates to the file system. Select the option on the IMSMA<sup>NG</sup> Backup window to store these files in the backup. Administration}}
