NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
Information managers can augment the {{IMSMANG}} Backup capability with other scheduled 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 environment, backups should be made from the server rather than the clients. Similarly, backups can only be restored on the {{IMSMANG}} server
}}
===Restore on the Server===__NOEDITSECTION__
In a client-/server environment, the {{IMSMANG}} database can be restored only on the server machine so as to prevent accidental deletion of data by client users. Conducting an {{IMSMANG}} Restore on the server machine (or a stand-alone machine) restores the {{IMSMANG}} database and the available attachments to the server, replacing any existing data in the {{IMSMANG}} database. When a restore is complete, {{IMSMANG}} closes and must be restarted.
{{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
}}
