Enabler Backup and Restore - Revision history

Brant at 04:42, 7 October 2014

2014-10-07T04:42:01Z

Robert: Add Restore details to page

2011-02-17T23:00:45Z

Add Restore details to page

← Older revision		Revision as of 23:00, 17 February 2011
Line 11:		Line 11:

	=====Store Server configuration=====		=====Store Server configuration=====
	Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Backup Options Setup ⇒ Select ‘Store Server’ only ⇒ enable ‘Create backups’		* Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Backup Options Setup ⇒ Select ‘Store Server’ only ⇒ enable ‘Create backups’

	[[Image:Enabler_Backups_Figure1.JPG]]		[[Image:Enabler_Backups_Figure1.JPG]]
Line 33:		Line 33:

	=====Store Till configuration=====		=====Store Till configuration=====
	Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Backup Options Setup ⇒ Select ‘Tills’ only ⇒ enable ‘Create backups’		* Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Backup Options Setup ⇒ Select ‘Tills’ only ⇒ enable ‘Create backups’

	[[Image:Enabler_Backups_Figure2.JPG]]		[[Image:Enabler_Backups_Figure2.JPG]]
Line 47:		Line 47:
	======Network Location======		======Network Location======
	As mentioned, the backup path can be set as a network location using a UNC path. A Store Server could be configured to backup to a Till, and the Till configured to backup to the Store Server. <br />		As mentioned, the backup path can be set as a network location using a UNC path. A Store Server could be configured to backup to a Till, and the Till configured to backup to the Store Server. <br />
	EG: Store Server backup path: \\Till01\enbackups\ <br />		* EG: <br />
			Store Server backup path: \\Till01\enbackups\ <br />
	Till backup path: \\Server01\enbackups\		Till backup path: \\Server01\enbackups\
	======Removable Drive======		======Removable Drive======
	Removable USB or Zip drives are ideal for single-till installations (where only a store server is used). USB Drives are cheap, reliable and have more than enough space to hold the backup data. They can also be easily swapped each day and taken away offsite for extra protection. These devices usually display as a local drive. <br />		Removable USB or Zip drives are ideal for single-till installations (where only a store server is used). USB Drives are cheap, reliable and have more than enough space to hold the backup data. They can also be easily swapped each day and taken away offsite for extra protection. These devices usually display as a local drive. <br />
	EG: Backup Path: E:\enablerbackups		* EG: Backup Path: E:\enablerbackups
	======Local Hard Drive======		======Local Hard Drive======
	If no other location is available, there is still merit in backing up to the local hard drive. While this provides no protection against drive failure, it can provide protection against general file corruption or data loss caused by application errors or inappropriate user intervention. <br />		If no other location is available, there is still merit in backing up to the local hard drive. While this provides no protection against drive failure, it can provide protection against general file corruption or data loss caused by application errors or inappropriate user intervention. <br />
	EG: Backup Path: C:\Enabler\backups		* EG: Backup Path: C:\Enabler\backups

	=====How are the Backups stored?=====		=====How are the Backups stored?=====
Line 66:		Line 67:

	The backup will run just before the actual data purge. EG: If the Purge and Backup is scheduled for 02:00am, the backup will run at 02:00am and the purge will run immediately on completion of the backup. Running the backup before the purge means that a backup is available in the event that the data purge leads to corruption, or a purge parameter is set incorrectly so data is inadvertently deleted. <br />		The backup will run just before the actual data purge. EG: If the Purge and Backup is scheduled for 02:00am, the backup will run at 02:00am and the purge will run immediately on completion of the backup. Running the backup before the purge means that a backup is available in the event that the data purge leads to corruption, or a purge parameter is set incorrectly so data is inadvertently deleted. <br />
	Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Scheduler Setup ⇒ Enable ‘Purge & Backup’		* Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Scheduler Setup ⇒ Enable ‘Purge & Backup’

	[[Image:Enabler_Backups_Figure3.JPG]]		[[Image:Enabler_Backups_Figure3.JPG]]
Line 72:		Line 73:
	To enable Purge and Backup you can configure it to run immediately after the End of Day (as in Figure 3), or you can manually specify a time for it to run. <br />		To enable Purge and Backup you can configure it to run immediately after the End of Day (as in Figure 3), or you can manually specify a time for it to run. <br />
	'''''Note:'''''		'''''Note:'''''
	''As previously mentioned, this task should be run after the End of Day, but before the Resume Till. It is also recommended that it is scheduled to avoid conflicting with the other tasks, Host Import and Forward Pricing. ''		* ''As previously mentioned, this task should be run after the End of Day, but before the Resume Till. It is also recommended that it is scheduled to avoid conflicting with the other tasks, Host Import and Forward Pricing. ''

			===Restoring Backups===
			If a situation arises where backups must be restored, it is recommended that the operation is discussed with Magenta Support prior to proceeding with the steps below. This is to ensure the correct procedure is used and to avoid overwriting/deleting data.
			====Assisted Restore====
			Backups can be restored using the ‘Restore Backup’ option on File menu in the Back Office.
			* Back Office ⇒ File ⇒ Restore Backup <br />
			'''''Note:'''''
			* ''The restore option will automatically overwrite any files that already exist. This is necessary and desirable if you are running the restore in order to recover from corruption. However, use with care as it is possible to overwrite good data with out-of-date data from the backup!''

			Using the Restore Backup option requires that all Enabler applications are first closed. This includes Nibbler and POS. If other applications are found to be running, a message will be displayed advising them to be closed.

			If Back Office is monitoring Nibbler, Back Office will automatically suspend Nibbler for the duration of the restore and will resume Nibbler when the restore is complete.

			Upon selecting the Restore Backup option in Back Office, the Restore Backup window is displayed (Figure 4).

			[[Image:Enabler_Backups_Figure4.JPG]]

			The list of backup files will show all .ZIP files that are located in the configured Backup Path.

			Select the backup file to restore data from and select the components to restore from that backup file. Click Restore to proceed.

			If LOCAL or LANTRAN databases are restored, the restore process automatically invokes a re-index on the restored databases once the .DBF files have been recovered.

			====Manual Restore====
			The Assisted Restore menu option provides a convenient way to recover an entire backup, or large portions of a backup, however it doesn’t provide a great level of granularity. EG: You can restore the entire Local Database, or none of it. You could not restore single files from within the backup files. If Enabler data or configuration is badly corrupted, it might not be possible to launch Back Office. Therefore, you would need to recover manually

			Files within the backup files may be restored manually using Windows Explorer (Windows XP and above) or tools such as Winzip or PKUnzip. Individual files can be restored to their original locations or copied elsewhere.

			Using the Manual Restore scenario requires that all Enabler applications are first closed. This includes Nibbler, POS and Back Office. If any of the applications are open, the restore may fail.

			'''''Note:'''''
			* ''If you manually restore a database .DBF file, you must re-index the recovered files before starting any Enabler application. This process also requires that all Enabler applications are first closed.''

			* ''If you want to try to restore a backup, just to see if it fixes a problem, you should manually backup the configurations/data that you are about to overwrite from the backup. If restoring the data doesn’t resolve the problem, you should back revert to the most recent data i.e before the restore – remember, the backup is only up to date as at last night (at best)!!!''

			====Restore to a different Enabler version====
			If you restore a database that was backed up from Enabler version 4.xx and you are now running Enabler version 4.xx+y (where y > 0), you would need to manually run a database migration to bring the databases up to date.

			This can be done using the following command from within the Enabler folder at the Windows command prompt:

			C:\Enabler> INFOCTRL MIGRATE

Robert: moved Enabler Backups to Enabler Backup and Restore: Adding Restore functions to page

2011-02-17T22:39:38Z

moved Enabler Backups to Enabler Backup and Restore: Adding Restore functions to page

← Older revision	Revision as of 22:39, 17 February 2011
(No difference)

Robert at 05:43, 16 February 2011

2011-02-16T05:43:38Z

← Older revision		Revision as of 05:43, 16 February 2011
Line 1:		Line 1:
	Created: 31 July 2009. Last Reviewed: ~~31 July 2009~~		Created: 31 July 2009. Last Reviewed: 16 February 2011


	Enabler has Backup and Restore functionality built in to assist with scheduling backups of Enabler data and restoring Enabler data in the case of database corruption or Hardware failure. This Backup and Restore functionality should be used to backup the Enabler data, rather than backing up the data directly using 3rd party applications. If using a 3rd party solution potential issues can arise with Database File locking and other corruption.		Enabler has Backup and Restore functionality built in to assist with scheduling backups of Enabler data and restoring Enabler data in the case of database corruption or Hardware failure. This Backup and Restore functionality should be used to backup the Enabler data, rather than backing up the data directly using 3rd party applications. If using a 3rd party solution potential issues can arise with Database File locking and other corruption.
Line 61:		Line 62:
	====Backup Scheduling====		====Backup Scheduling====
	The backup is run as part of the Data Purge process. If this is not scheduled to run, then the backup will NOT occur. The reason behind this approach is that the Backup generally needs to occur overnight, it needs to happen automatically and it needs to be run after the End of Day but before the Till Resume scheduled events. Normally, the Data Purge is configured to occur between these two events. <br />		The backup is run as part of the Data Purge process. If this is not scheduled to run, then the backup will NOT occur. The reason behind this approach is that the Backup generally needs to occur overnight, it needs to happen automatically and it needs to be run after the End of Day but before the Till Resume scheduled events. Normally, the Data Purge is configured to occur between these two events. <br />

	It is better not to create a separate scheduled event for the backup. This would require timing buffers, which effectively means that the overnight processing requires more time overall to complete. For example, if the backup was to be scheduled separately at 3:00am, you might have to wait until 4:00am to start the purge, just to be sure that the backup was complete – even though the backup might take only 20 minutes. By combining these two events Enabler makes optimum use of the window of opportunity to perform these housekeeping tasks. <br />		It is better not to create a separate scheduled event for the backup. This would require timing buffers, which effectively means that the overnight processing requires more time overall to complete. For example, if the backup was to be scheduled separately at 3:00am, you might have to wait until 4:00am to start the purge, just to be sure that the backup was complete – even though the backup might take only 20 minutes. By combining these two events Enabler makes optimum use of the window of opportunity to perform these housekeeping tasks. <br />

	The backup will run just before the actual data purge. EG: If the Purge and Backup is scheduled for 02:00am, the backup will run at 02:00am and the purge will run immediately on completion of the backup. Running the backup before the purge means that a backup is available in the event that the data purge leads to corruption, or a purge parameter is set incorrectly so data is inadvertently deleted. <br />		The backup will run just before the actual data purge. EG: If the Purge and Backup is scheduled for 02:00am, the backup will run at 02:00am and the purge will run immediately on completion of the backup. Running the backup before the purge means that a backup is available in the event that the data purge leads to corruption, or a purge parameter is set incorrectly so data is inadvertently deleted. <br />
	Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Scheduler Setup ⇒ Enable ‘Purge & Backup’		Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Scheduler Setup ⇒ Enable ‘Purge & Backup’

Robert at 05:42, 16 February 2011

2011-02-16T05:42:12Z

← Older revision		Revision as of 05:42, 16 February 2011
Line 70:		Line 70:
	'''''Note:'''''		'''''Note:'''''
	''As previously mentioned, this task should be run after the End of Day, but before the Resume Till. It is also recommended that it is scheduled to avoid conflicting with the other tasks, Host Import and Forward Pricing. ''		''As previously mentioned, this task should be run after the End of Day, but before the Resume Till. It is also recommended that it is scheduled to avoid conflicting with the other tasks, Host Import and Forward Pricing. ''


	~~================================~~
	~~To guard against data loss, the Enabler backup option should be configured to backup the Enabler store server to either another machine on the network, or to a USB drive attached to the store server.~~

	~~Enabler backups are configured from Local Store Setup-> Transaction Processing / Comms-> Backup Options Setup. The following options can be set when “Create Backups” is turned on.~~


	* Backup pathFull path of backup
	* Days to retain backupsDays before backups are overwritten
	* Backup configurations (Local)Configurations for store server
	* Backup configurations (Central)Configurations for all store machines
	* Backup Lan transactions databaseLANTRAN databases
	* Backup local databaseLOCAL databases
	* Backup lan maintenance databaseLANMNT databases
	* Backup electronic journalsJournal files (\Enabler\Lantran\Journals)

	Whilst backups can be performed to the same drive that Enabler is stored on, this only guards against data corruption and not hard disk failure. That is why it is recommended that backups be performed to a drive external to the Store server (USB, NAS, shared drive).


	~~For the backups to run after “Create Backups” has been turned on, you need to have “Purge & Backup” configured in Scheduler Setup.~~


	~~Whilst it is not necessary to backups tills, as all transactional data and till configs are held on the store server, if you did wish to backup tills, you would only turn on:-~~

	* Backup configurations (Local)
	* Backup local database

Robert at 05:36, 16 February 2011

2011-02-16T05:36:56Z

@@ Line 33: / Line 33: @@
 =====Store Till configuration=====
 Back Office &rArr; Local Store Setup &rArr; Transaction Processing/Comms &rArr; Backup Options Setup &rArr; Select ‘Tills’ only &rArr; enable ‘Create backups’
 It is recommended that only the Local Enabler data be backed up on a Till.  This ensures there will be no Database Locking issues if the till attempted to backup the transactional databases at the same time as the store server.
 ================================

Robert at 05:27, 16 February 2011

2011-02-16T05:27:26Z

← Older revision		Revision as of 05:27, 16 February 2011
Line 11:		Line 11:
	=====Store Server configuration=====		=====Store Server configuration=====
	Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Backup Options Setup ⇒ Select ‘Store Server’ only ⇒ enable ‘Create backups’		Back Office ⇒ Local Store Setup ⇒ Transaction Processing/Comms ⇒ Backup Options Setup ⇒ Select ‘Store Server’ only ⇒ enable ‘Create backups’

			[[Image:Enabler_Backups_Figure1.JPG]]

	======Backup path======		======Backup path======

Robert at 05:25, 16 February 2011

2011-02-16T05:25:22Z

@@ Line 1: / Line 1: @@
 Created: 31 July 2009. Last Reviewed: 31 July 2009
-'''Enabler Backups'''
+===Enabler Backups===
 To guard against data loss, the Enabler backup option should be configured to backup the Enabler store server to either another machine on the network, or to a USB drive attached to the store server.

Trevor: New page: Created: 31 July 2009. Last Reviewed: 31 July 2009 '''Enabler Backups''' To guard against data loss, the Enabler backup option should be configured to backup the Enabler store server t...

2009-07-31T04:56:53Z

New page: Created: 31 July 2009. Last Reviewed: 31 July 2009 '''Enabler Backups''' To guard against data loss, the Enabler backup option should be configured to backup the Enabler store server t...

New page

Created: 31 July 2009. Last Reviewed: 31 July 2009

'''Enabler Backups'''

To guard against data loss, the Enabler backup option should be configured to backup the Enabler store server to either another machine on the network, or to a USB drive attached to the store server.

Enabler backups are configured from Local Store Setup-> Transaction Processing / Comms-> Backup Options Setup. The following options can be set when “Create Backups” is turned on.

* Backup pathFull path of backup
* Days to retain backupsDays before backups are overwritten
* Backup configurations (Local)Configurations for store server
* Backup configurations (Central)Configurations for all store machines
* Backup Lan transactions databaseLANTRAN databases
* Backup local databaseLOCAL databases
* Backup lan maintenance databaseLANMNT databases
* Backup electronic journalsJournal files (\Enabler\Lantran\Journals)

Whilst backups can be performed to the same drive that Enabler is stored on, this only guards against data corruption and not hard disk failure. That is why it is recommended that backups be performed to a drive external to the Store server (USB, NAS, shared drive).

For the backups to run after “Create Backups” has been turned on, you need to have “Purge & Backup” configured in Scheduler Setup.

Whilst it is not necessary to backups tills, as all transactional data and till configs are held on the store server, if you did wish to backup tills, you would only turn on:-

* Backup configurations (Local)
* Backup local database