Changes

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.

Information managers can schedule backups using PGSQL Administration tools 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.}}

{{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.

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.

{{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.

While {{IMSMANG}} Backup backs up all of the files used in the typical operation standard configuration of {{IMSMANG}}, there are other customisable files that should also be backed upand/or carefully documented. These include:

* non-standard projection filesclient and server '''settings''' including memory settings* map customisations{{IMSMANG}} does not automatically back up customisations made to C:\IMSMAng\server\gis\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 (if customized)* the background map(s) source files are ('''not included in ''' only the {{IMSMANG}} Backup and must be separately backed up and managed.mxd file)* base mapslocal projection files (.prj)It is recommended that information managers make backups of maps that are imported into {{IMSMANG}} for use on client computers* C:\IMSMAng\migration\conf\migration. While {{IMSMANG}} Backup backs up the maps when they have been imported, these base map files are not managed within {{IMSMANG}} properties and should be backed up manually to allow for customisation any import scripts* [[Language and later import.Translations#Data language|fallback fonts]] (C:\IMSMAng\java\lib\fonts\fallback)* ODBC configurations* external reporting External 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 information managers should ensure that these external tools get are backed up manually or automatically.

 {{Warning| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and may 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 can should be restored using {{IMSMANG}} Restore as well as other PGSQL tools if necessary. The {{IMSMANG}} Restore function can be used on both clients and servers to restore key information in the event of data loss or other restore needs (for example, after an upgrade). {{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.

{{IMSMANG}} Restore can also restore the GIS database, Data Entry Form templates, iReport templates, map files and translation .properties files; however, these are only necessary when running the client on the server or when running in stand-alone mode. {{note| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected}} ===Restore on the Client===__NOEDITSECTION__Except for instances where the client and the server are on the same machine, the {{IMSMANG}} database cannot be restored to a client-only machine. However, {{IMSMANG}} Restore can be used to restore client settings including the GIS database, Data Entry Form templates, iReport templates, map files and translation .properties files. This functionality is particularly useful when connecting new clients to a server as this allows information managers to prebuild the GIS database and map configurations and simply restore them to the new clients.{{HowTo's|[[Restore IMSMA Data from a Backup|Restore IMSMA Data from a Backup]]}} On a client machine, {{IMSMANG}} Restore acts as a file copying function, copying files included in the backup to the correct location on the client. {{IMSMANG}} Restore also attempts to back up any files it is replacing. These backup directories have “_orig” appended to their file names to distinguish them from the new files.  {{Warning| {{IMSMANG}} Restore preserves only one backup of these files. Previous _orig directories are replaced with each {{IMSMANG}} Restore so care must be taken to preserve these files, if desired, prior to running {{IMSMANG}} Restore}} And because the client restore works as a file copy function, it is also possible to manually copy the desired files into the correct locations without running {{IMSMANG}} Restore. This can be a helpful shortcut when a full restore is not necessary.

{{NavBox Getting started with IMSMANG Administration}}

[[Category:ELRNAA]]