Changes

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.