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
===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]]
}}
For 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.
===Backing Up Other IMSMA<sup>NG</sup> InformationGIS Database===__NOEDITSECTION__Apart from While {{IMSMANG}} stores all coordinate data in the IMSMA<sup>NG</sup> PGSQL database and attachment stored on that is backed up with the server{{IMSMANG}} database, {{IMSMANG}} also uses a geodatabase file (IMSMA<sup>NG</sup> Backup allows members .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 specific elements from 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 client including: geodatabase during system launch.
===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.
===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.
==Other Backup Considerations==GIS Dataabase====__NOEDITSECTION__IMSMA<sup>NG</sup> also stores corrdinate data on each client computer While {{IMSMANG}} Backup backs up all of the files used in a geodatabase file (IMSMA.mdb) to allow data to be displayed on a map. Even if the file is missing, IMSMA<sup>NG</sup> automatically builds this file aftre the system launch. However, it can take several hours. To avoid thisstandard configuration of {{IMSMANG}}, each IMSMA<sup>NG</sup> backup there are other files that should include this file to reduce the time it takes to launch IMSMA<sup>NG<also be backed up and/sup> after a restoreor 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
| [[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.
===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.
