Difference between revisions of "Backup and Restore"
| Line 23: | Line 23: | ||
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 IMSMA<sup>NG</sup> data is regularly backed up, but more importantly a multitired backup strategy should be used to eliminate data loss. Consider the following options below when developing a backup strategy for IMSMA<sup>NG</sup>. | 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 IMSMA<sup>NG</sup> data is regularly backed up, but more importantly a multitired backup strategy should be used to eliminate data loss. Consider the following options below when developing a backup strategy for IMSMA<sup>NG</sup>. | ||
| − | |||
*disk mirroring | *disk mirroring | ||
*operating system backups | *operating system backups | ||
| Line 29: | Line 28: | ||
*offsite data storage | *offsite data storage | ||
*IMSMANG-specific backups | *IMSMANG-specific backups | ||
| − | |||
Finally, any data backup strategy should include occasioanl tests to ensure that all of the backups are functioning properly. | Finally, any data backup strategy should include occasioanl tests to ensure that all of the backups are functioning properly. | ||
===Backing Up the IMSMA<sup>NG</sup> Database=== | ===Backing Up the IMSMA<sup>NG</sup> Database=== | ||
| − | |||
The IMSMA<sup>NG</sup> Datebase holds all of the actie data in IMSMA<sup>NG</sup> ranging from published reports to general mine action information. IMSMA<sup>NG</sup> Backup is responsible for storing all of this data under the MySQL database. The MySQL database dump command impliments a complete backup of all the data in the database. The resulting dump.sql file includes the necessary commands to recreate the database with all the existing data. The existing file is stored in a time-stamped directory for easy access. | The IMSMA<sup>NG</sup> Datebase holds all of the actie data in IMSMA<sup>NG</sup> ranging from published reports to general mine action information. IMSMA<sup>NG</sup> Backup is responsible for storing all of this data under the MySQL database. The MySQL database dump command impliments a complete backup of all the data in the database. The resulting dump.sql file includes the necessary commands to recreate the database with all the existing data. The existing file is stored in a time-stamped directory for easy access. | ||
| − | |||
[[File:BackingUp Tip1CORRECT.png|border|caption]] | [[File:BackingUp Tip1CORRECT.png|border|caption]] | ||
| − | |||
Information Managers can create automatic dailiy or weekly backups using MySQL Administration tools. These backups also work simultaneously with IMSMA <sup>NG</sup> Backup; however any backup made outside of IMSMA <sup>NG</sup> needs to be manually restored. | Information Managers can create automatic dailiy or weekly backups using MySQL Administration tools. These backups also work simultaneously with IMSMA <sup>NG</sup> Backup; however any backup made outside of IMSMA <sup>NG</sup> needs to be manually restored. | ||
| − | |||
[[File:BackingUp Tip2.png|border|caption]] | [[File:BackingUp Tip2.png|border|caption]] | ||
| − | |||
===Attachments=== | ===Attachments=== | ||
| − | |||
Attachmes are stored seprately from the IMSMA<sup>NG</sup> database on the server file. However because of their size, it may not be necessary to back up the attachments each time. For this reason, IMSMA<sup>NG</sup> Backup provides the option of excluding attachments when performing a backup. | Attachmes are stored seprately from the IMSMA<sup>NG</sup> database on the server file. However because of their size, it may not be necessary to back up the attachments each time. For this reason, IMSMA<sup>NG</sup> Backup provides the option of excluding attachments when performing a backup. | ||
| − | |||
Including attachments is still reccomended for complete backups. However, if the file size is too large attachments can be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added to the backup file. | Including attachments is still reccomended for complete backups. However, if the file size is too large attachments can be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added to the backup file. | ||
| Line 62: | Line 53: | ||
*iReport template files | *iReport template files | ||
*translation .properties files | *translation .properties files | ||
| − | |||
| − | |||
====GIS Dataabase==== | ====GIS Dataabase==== | ||
IMSMA<sup>NG</sup> also stores corrdinate data on each client computer 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 this, each IMSMA<sup>NG</sup> backup should include this file to reduce the time it takes to launch IMSMA<sup>NG</sup> after a restore. | IMSMA<sup>NG</sup> also stores corrdinate data on each client computer 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 this, each IMSMA<sup>NG</sup> backup should include this file to reduce the time it takes to launch IMSMA<sup>NG</sup> after a restore. | ||
| − | Likewise, since the geodatabase is structured on a per-client basis, the best way to fully update the geodatabase is to launch the client prior to backing it up. Once it is backed up, users can shorten the time required to build the geodatabase by manually transferring it to newly installed | + | Likewise, since the geodatabase is structured on a per-client basis, the best way to fully update the geodatabase is to launch the client prior to backing it up. Once it is backed up, users can shorten the time required to build the geodatabase by manually transferring it to newly installed clients. |
| − | |||
| − | |||
====Maps==== | ====Maps==== | ||
IMSMA<sup>NG</sup> map fiiles can be loaded on a per-client basis and stored in IMSMA<sup>NG</sup> Backup, providing an easy way to share maps between clients. | IMSMA<sup>NG</sup> map fiiles can be loaded on a per-client basis and stored in IMSMA<sup>NG</sup> Backup, providing an easy way to share maps between clients. | ||
| − | |||
[[File:Map Tip1CORRECT.png|border|caption]] | [[File:Map Tip1CORRECT.png|border|caption]] | ||
| − | |||
====Field Report Templates and iReport Templates==== | ====Field Report Templates and iReport Templates==== | ||
| − | |||
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. | 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. | ||
| − | |||
====Translations==== | ====Translations==== | ||
Translations and localizations of data elements are stored in the IMSMA<sup>NG</sup> database and secured with the database backup. Although the properties files used to translate the IMSMA<sup>NG</sup> interface are stored externally to the database, they can be added to the IMSMA<sup>NG</sup> Backup. Be sure to backup all properties files each time a change or a full backup is made. | Translations and localizations of data elements are stored in the IMSMA<sup>NG</sup> database and secured with the database backup. Although the properties files used to translate the IMSMA<sup>NG</sup> interface are stored externally to the database, they can be added to the IMSMA<sup>NG</sup> Backup. Be sure to backup all properties files each time a change or a full backup is made. | ||
| + | |||
| + | {{NavBox Using IMSMA}} | ||
| + | |||
| + | [[Category:Maintaining+ IMSMA]] | ||
Revision as of 20:01, 27 August 2012
| How To |
|---|
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 multitired 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
Finally, any data backup strategy should include occasioanl tests to ensure that all of the backups are functioning properly.
Backing Up the IMSMANG Database
The IMSMANG Datebase holds all of the actie data in IMSMANG ranging from published reports to general mine action information. IMSMANG Backup is responsible for storing all of this data under the MySQL database. The MySQL database dump command impliments a complete backup of all the data in the database. The resulting dump.sql file includes the necessary commands to recreate the database with all the existing data. The existing file is stored in a time-stamped directory for easy access.
Information Managers can create automatic dailiy or weekly backups using MySQL Administration tools. These backups also work simultaneously with IMSMA NG Backup; however any backup made outside of IMSMA NG needs to be manually restored.
Attachments
Attachmes are stored seprately from the IMSMANG database on the server file. However because of their size, it may not be necessary to back up the attachments each time. For this reason, IMSMANG Backup provides the option of excluding attachments when performing a backup.
Including attachments is still reccomended for complete backups. However, if the file size is too large attachments can be deleted manually. Avoid excluding attachemtns from backups since attachmets cannot be added to the backup file.
Backing Up Other IMSMANG Information
Apart from the IMSMANG database and attachment stored on the server, IMSMANG Backup allows members to backup specific elements from the client including:
- GIS database (.mdb file)
- map files (.mxd, etc)
- field report template files
- iReport template files
- translation .properties files
GIS Dataabase
IMSMANG also stores corrdinate data on each client computer in a geodatabase file (IMSMA.mdb) to allow data to be displayed on a map. Even if the file is missing, IMSMANG automatically builds this file aftre the system launch. However, it can take several hours. To avoid this, each IMSMANG backup should include this file to reduce the time it takes to launch IMSMANG after a restore.
Likewise, since the geodatabase is structured on a per-client basis, the best way to fully update the geodatabase is to launch the client prior to backing it up. Once it is backed up, users can shorten the time required to build the geodatabase by manually transferring it to newly installed clients.
Maps
IMSMANG map fiiles can be loaded on a per-client basis and stored in IMSMANG Backup, providing an easy way to share maps between clients.
Field Report Templates and iReport Templates
IMSMANGusers can store copies or drafts of field reports templates and iReports templates to the file system. Select the option on the IMSMANG Backup window to store these files in the backup.
Translations
Translations and localizations of data elements are stored in the IMSMANG database and secured with the database backup. Although the properties files used to translate the IMSMANG interface are stored externally to the database, they can be added to the IMSMANG Backup. Be sure to backup all properties files each time a change or a full backup is made.
