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]]
}}
===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.
===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.
===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 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 the {{IMSMANG}} Backup window. Storing these files in the backup is recommended as it makes it easier to resume drafting templates and reports.
====GIS Dataabase=Translations===__NOEDITSECTION__IMSMA<sup>NG</sup> also {{IMSMANG}} stores corrdinate translations of the application in several places. Translations and localisations of data on each client computer elements are stored in a geodatabase file (IMSMAthe {{IMSMANG}} database and are backed up with the database backup. The .mdb) properties files used to allow data translate the {{IMSMANG}} interface are stored externally to be displayed on a map. Even if the file is missingdatabase, IMSMA<sup>NG</sup> automatically builds this file aftre but they can be added to the system launch{{IMSMANG}} Backup as an option. However, it can take several hoursIf changes are made to the . To avoid thisproperties files, each IMSMA<sup>NG</sup> backup should include this file to reduce the time it takes is recommended to launch IMSMA<sup>NG</sup> back them up after each change as well as each time a restorefull backup is made.
* 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==__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 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. Each option behaves slightly differently depending on whether the restore is occurring on a server or a client.
====Maps=Restore on the Server===__NOEDITSECTION__IMSMA<sup>NG<In a client/sup> map fiiles server environment, the {{IMSMANG}} database can be loaded 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 perstand-client basis alone machine) restores the {{IMSMANG}} database and stored the available attachments to the server, replacing any existing data in IMSMA<sup>NG</sup> Backupthe {{IMSMANG}} database. When a restore is complete, providing an easy way to share maps between clients{{IMSMANG}} closes and must be restarted.
