Backup and Restore - Revision history

Alnaucler at 14:49, 29 May 2017

2017-05-29T14:49:31Z

← Older revision		Revision as of 16:49, 29 May 2017
Line 76:		Line 76:
	{{NavBox IMSMA NG Administration}}		{{NavBox IMSMA NG Administration}}

	[[Category:~~ELR~~]]		[[Category:NAA]]

Alnaucler at 14:17, 29 May 2017

2017-05-29T14:17:31Z

← Older revision		Revision as of 16:17, 29 May 2017
Line 74:		Line 74:
	{{note\| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected.}}		{{note\| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected.}}

	{{NavBox ~~Getting started with~~ IMSMA}}		{{NavBox IMSMA NG Administration}}

	[[Category:ELR]]		[[Category:ELR]]

Alnaucler at 08:22, 10 October 2016

2016-10-10T08:22:52Z

← Older revision		Revision as of 10:22, 10 October 2016
Line 32:		Line 32:

	===Attachments===__NOEDITSECTION__		===Attachments===__NOEDITSECTION__
	{{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 backup.		{{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 backup which 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~~.		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.

	===GIS Database===__NOEDITSECTION__		===GIS Database===__NOEDITSECTION__

Alnaucler at 13:31, 5 August 2016

2016-08-05T13:31:46Z

← Older revision		Revision as of 15:31, 5 August 2016
Line 24:		Line 24:
	{{HowTo's		{{HowTo's
	\|[[Backup IMSMA Data\|Backup IMSMA Data]]		\|[[Backup IMSMA Data\|Backup IMSMA Data]]
			\|[[Scheduling Backup\|Scheduling Backup of IMSMA database]]
	}}		}}

Alnaucler at 17:02, 9 April 2015

2015-04-09T17:02:36Z

← Older revision		Revision as of 19:02, 9 April 2015
Line 39:		Line 39:

	===Maps===__NOEDITSECTION__		===Maps===__NOEDITSECTION__
	{{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.		{{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.

	===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__		===Data Entry Form Templates and iReport Templates===__NOEDITSECTION__

Dionysia at 13:21, 23 March 2015

2015-03-23T13:21:06Z

← Older revision		Revision as of 15:21, 23 March 2015
Line 11:		Line 11:
	*{{IMSMANG}}-specific backups		*{{IMSMANG}}-specific backups

	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.		Moreover, a backup is only as 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.

	Note that an event-based change to the components necessitates a backup '''before''' and '''after''' the change. Event-based changes include events such as:		Note that an event-based change to the components necessitates a backup '''before''' and '''after''' the change. Event-based changes include events such as:

	* upgrading any software on the server		* upgrading any software on the server
	* importing data and/or Data Entry Forms		* importing data and/or Data Entry Forms
Line 27:		Line 26:
	}}		}}

	Information managers can schedule 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.		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.}}		{{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.}}
Line 37:		Line 36:

	===GIS Database===__NOEDITSECTION__		===GIS Database===__NOEDITSECTION__
	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 ~~sandbax~~, 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.		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 sandbox, 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.

	===Maps===__NOEDITSECTION__		===Maps===__NOEDITSECTION__
Line 62:		Line 61:

	==IMSMA Restore==__NOEDITSECTION__		==IMSMA Restore==__NOEDITSECTION__

	{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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.}}		{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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		{{HowTo's

Dionysia at 13:12, 23 March 2015

2015-03-23T13:12:24Z

← Older revision		Revision as of 15:12, 23 March 2015
Line 65:		Line 65:
	{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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.}}		{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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		{{HowTo's
	\| [[~~Restore IMSMA Data from a Backup\|~~ Restore IMSMA Backup on Server]]		\| [[Restore IMSMA Backup on Server]]
	\|[[Restore IMSMA Backup on Client]]		\|[[Restore IMSMA Backup on Client]]
	}}		}}

Dionysia at 13:07, 23 March 2015

2015-03-23T13:07:58Z

← Older revision		Revision as of 15:07, 23 March 2015
Line 26:		Line 26:
	\|[[Backup IMSMA Data\|Backup IMSMA Data]]		\|[[Backup IMSMA Data\|Backup IMSMA Data]]
	}}		}}
	Information managers can ~~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.
			Information managers can schedule 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 configuration, backups should be made from the server rather than the clients. Similarly, backups can only be restored on the {{IMSMANG}} server.}}		{{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.}}

Alnaucler at 12:03, 21 March 2015

2015-03-21T12:03:43Z

← Older revision		Revision as of 14:03, 21 March 2015
Line 28:		Line 28:
	Information managers can 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.		Information managers can 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 configuration, backups should be made from the server rather than the clients. Similarly, backups can only be restored on the {{IMSMANG}} server		{{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.}}
	}}

	===Attachments===__NOEDITSECTION__		===Attachments===__NOEDITSECTION__
Line 64:		Line 63:

	{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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.}}		{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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 Data from a Backup\| Restore IMSMA Backup on Server]]
			\|[[Restore IMSMA Backup on Client]]
			}}
	Backups created using {{IMSMANG}} Backup should be restored using {{IMSMANG}} Restore. {{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.		Backups created using {{IMSMANG}} Backup should be restored using {{IMSMANG}} Restore. {{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.

Line 70:		Line 72:
	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.		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.

	{{note\| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected		{{note\| In a client/server environment, it is recommended to stop the server prior to restoring the database to ensure all clients are disconnected.}}
	}}

	{{NavBox Getting started with IMSMA}}		{{NavBox Getting started with IMSMA}}

	[[Category:ELR]]		[[Category:ELR]]

Alnaucler at 11:59, 21 March 2015

2015-03-21T11:59:25Z

← Older revision		Revision as of 13:59, 21 March 2015
Line 63:		Line 63:
	==IMSMA Restore==__NOEDITSECTION__		==IMSMA Restore==__NOEDITSECTION__

	{{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		{{Warning\| {{IMSMANG}} Restore replaces all data in the {{IMSMANG}} database and 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.}}
	}}

	~~Backups created using {{IMSMANG}} Backup can 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.		Backups created using {{IMSMANG}} Backup should be restored using {{IMSMANG}} Restore. {{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.

	===Restore on the Server===__NOEDITSECTION__		===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.		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		{{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 IMSMA}}		{{NavBox Getting started with IMSMA}}

	[[Category:ELR]]		[[Category:ELR]]