404
edits
Changes
no edit summary
Moreover, a backup is only as good as the ability 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| Backup Recommendations
The table below outlines the recommended schedule for backing up the IMSMANG database and other files. Note that an event-based change to the components necessitates a backup. Event-based changes include events such as:
* Before upgrading software
* Before importing data
* After importing field reports
* After making SQL changes to the database
Server Client Server and Client
Component Daily Weekly Weekly Event-based change
IMSMANG database ● ● ●
Attachments ● ● ●
GIS database ● ● ●
Maps ● ● ●
Templates ● ● ●
Translation ● ●
}}
===Backing Up the IMSMA<sup>NG</sup> Database===
====Translations====
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==
While IMSMANG Backup backs up all of the files used in the typical operation of IMSMANG, there are other customisable files that should also be backed up. These include:
* map customisations
* base maps
* external reporting tools
===Map Customisations===
IMSMANG does not automatically back up customisations made to maps used in IMSMANG. Users can make changes to the imsma.mxd file, create or modify ESRI style files, add symbology or make many other changes to maps, but these files are not included in the IMSMANG Backup and must be separately backed up and managed.
===Base Maps===
It is recommended that information managers make backups of maps that are imported into IMSMANG for use on client computers. While IMSMANG Backup backs up the maps when they have been imported, these base map files are not managed within IMSMANG and should be backed up manually to allow for customisation and later import.
===External Reporting Tools===
External reporting tools and other add-ons are not backed up by IMSMANG and should be backed up manually. These include any tools using ODBC connections to IMSMANG such as Microsoft Access databases, Microsoft Excel spreadsheets, OpenOffice connections and Crystal Reports. Information managers should ensure that these tools get backed up manually or automatically.
