NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
*{{IMSMANG}}-specific backups
Moreover, a backup is only as good as the ability if you are able to restore it. As such, any data backup strategy should include plans to test existing backups to ensure that the backups are usable. If it becomes necessary to restore data, regular testing of backups helps ensure that it will be possible to do so.
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
{{HowTo's
|[[Backup IMSMA Data|Backup IMSMA Data]]
|[[Scheduling Backup|Scheduling Backup of IMSMA database]]
}}
Information managers can schedule backups using PGSQL Administration tools, for example, 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.
{{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.}}
===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 backupwhich is '''not''' recommended.
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. Excluding attachments from the backup routine 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 sandbaxsandbox, 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.
===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__
==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 Data from a Backup| Restore IMSMA Backup on Server]]
|[[Restore IMSMA Backup on Client]]
}}
{{note| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected.}}
{{NavBox Getting started with IMSMANG Administration}}
[[Category:ELRNAA]]
