News and backup - Revision history

Ttenbergen: Text replacement - "[[Category: " to "[[Category:"

2025-07-30T16:56:15Z

Text replacement - "[[Category: " to "[[Category:"

← Older revision		Revision as of 11:56, 30 July 2025
Line 81:		Line 81:


	[[Category: Batch Files]]		[[Category:Batch Files]]
	[[Category: Data Backup Dependencies]]		[[Category:Data Backup Dependencies]]
	[[Category: Backup]]		[[Category:Backup]]

Ttenbergen at 02:22, 6 April 2023

2023-04-06T02:22:17Z

← Older revision		Revision as of 21:22, 5 April 2023
Line 76:		Line 76:
	== Error checking ==		== Error checking ==
	Just do your backups and assume they work, there is no need for collectors to routinely check that the backups to the regional server are working. [[Data Processor]] in Main office checks regularly that backups are being done, so if backups are not making it to the regional server we will let you know.		Just do your backups and assume they work, there is no need for collectors to routinely check that the backups to the regional server are working. [[Data Processor]] in Main office checks regularly that backups are being done, so if backups are not making it to the regional server we will let you know.

	~~Main office uses [[Backup_Checker.vbs]] to make sure the backups are working.~~

	== Related articles ==		== Related articles ==

Ttenbergen at 17:22, 13 January 2021

2021-01-13T17:22:01Z

← Older revision		Revision as of 12:22, 13 January 2021
Line 16:		Line 16:
	#* again, this gives the main office data to review in case something went wrong with the send.		#* again, this gives the main office data to review in case something went wrong with the send.

	You can additionally back up mid day. In theory you can do this as frequently as you want, but there are draw backs: we only keep the last 20 backups, so if you back up 10 times a day we only have 2 days of backups for you. So, if we found out that we want to know something that happened last week, then if you did 10 a day we would no longer have the data, but if you did 3 a day, we usually would still have the data. So, be reasonable in your backup frequency.		You can additionally back up mid day. In theory you can do this as frequently as you want, but there are draw backs: we only keep the last 40 backups, so if you back up 10 times a day we only have 2 days of backups for you. So, if we found out that we want to know something that happened last week, then if you did 10 a day we would no longer have the data, but if you did 3 a day, we usually would still have the data. So, be reasonable in your backup frequency.

	==Importance of backup to REGIONAL SERVER==		==Importance of backup to REGIONAL SERVER==
Line 33:		Line 33:
	* [[backup.bat]]		* [[backup.bat]]
	** back up to local backup directory c:\ccmdb_data\ccmdb_backups w 20 versions of [[CCMDB_data.mdb]]		** back up to local backup directory c:\ccmdb_data\ccmdb_backups w 20 versions of [[CCMDB_data.mdb]]
	** back up to server w 20 versions of [[CCMDB_data.mdb]] to the regional server		** back up to server w 40 versions of [[CCMDB_data.mdb]] to the regional server
	** check if there is a file [[Regional Server]]\Programs\<hosp>_<ward>\ccmdb.accdb; if so,		** check if there is a file [[Regional Server]]\Programs\<hosp>_<ward>\ccmdb.accdb; if so,
	** '''move''' the file from the regional server to c:\ccmdb_'''program'''		** '''move''' the file from the regional server to c:\ccmdb_'''program'''

Ttenbergen: /* How often should you run News and Backup? */

2021-01-13T17:21:23Z

How often should you run News and Backup?

← Older revision		Revision as of 12:21, 13 January 2021
Line 6:		Line 6:
	The following are the '''minimally required news and backups''' and their reasons:		The following are the '''minimally required news and backups''' and their reasons:
	# at '''beginning of collection with a laptop''' before data entry		# at '''beginning of collection with a laptop''' before data entry
	#*this ensures that you have the newest version of the program		#*this ensures that you have the newest version of the '''program''' and '''any internal data changes (e.g. dropdowns, cross-checks)'''
			# when the email about the [[Cognos]] data arrives
			#* this ensures that you have the newest version of the '''Cognos data'''
	# at '''end of collection day with a laptop''' (whether you send or not)		# at '''end of collection day with a laptop''' (whether you send or not)
	#* very rarely things go wrong during sending; making a backup just before sending means we would be able to restore you to that version if sending corrupts your data		#* very rarely things go wrong during sending; making a backup just before sending means we would be able to restore you to that version if sending corrupts your data

Ttenbergen: Text replacement - " ccmdb.accdb" to " CCMDB.accdb"

2020-07-25T02:27:58Z

Text replacement - " ccmdb.accdb" to " CCMDB.accdb"

← Older revision		Revision as of 21:27, 24 July 2020
Line 57:		Line 57:
	== Testing News and Backup ==		== Testing News and Backup ==
	After initial setup test that the backup works:		After initial setup test that the backup works:
	* open and close ~~ccmdb~~.accdb to update date stamp of file on the client laptop		* open and close [[CCMDB.accdb]] to update date stamp of file on the client laptop
	* execute the News and Backup batch file to perform the process		* execute the News and Backup batch file to perform the process
	* check that ~~ccmdb~~.accdb file with new stamp is on c:\ccmdb_data\ccmdb_backups		* check that [[CCMDB.accdb]] file with new stamp is on c:\ccmdb_data\ccmdb_backups
	* check that ~~ccmdb~~.accdb file with new stamp is on [[Regional Server]]/data/<hsp>_<ward>		* check that [[CCMDB.accdb]] file with new stamp is on [[Regional Server]]/data/<hsp>_<ward>

	== Information about the batch files ==		== Information about the batch files ==

Ttenbergen: Text replacement - "ccmdb.mdb" to "ccmdb.accdb"

2020-06-10T15:55:12Z

Text replacement - "ccmdb.mdb" to "ccmdb.accdb"

Ttenbergen at 17:27, 2 March 2020

2020-03-02T17:27:15Z

← Older revision		Revision as of 12:27, 2 March 2020
Line 26:		Line 26:
	The "'''News and Backup'''" batch file is a batch file on each '''laptop''' which does the following:		The "'''News and Backup'''" batch file is a batch file on each '''laptop''' which does the following:
	* [[batstart.bat]]		* [[batstart.bat]]
	** sets the [[Laptop ~~location~~]]		** sets the [[Laptop identifier]]
	** checks if there is a newer version of [[backup.bat]]; if so, it downloads it		** checks if there is a newer version of [[backup.bat]]; if so, it downloads it
	** calls [[backup.bat]]		** calls [[backup.bat]]
Line 35:		Line 35:
	** '''move''' the file from the regional server to c:\ccmdb_'''program'''		** '''move''' the file from the regional server to c:\ccmdb_'''program'''
	** open the wiki to [[Log]] to show what has changed		** open the wiki to [[Log]] to show what has changed
	** copy log file CCMDB_backup_log.txt to the corresponding [[Regional Server]]\data\<~~laptop location~~>; this log would show you when people have run news and backup and if there were errors.		** copy log file CCMDB_backup_log.txt to the corresponding [[Regional Server]]\data\<[[Laptop identifier]]>; this log would show you when people have run news and backup and if there were errors.

	== Setting up the file on a laptop ==		== Setting up the file on a laptop ==
	If the laptop is set up according to [[Laptop Setup]] then the batch files and shortcuts will be copied down as part of the process.		If the laptop is set up according to [[Laptop Setup]] then the batch files and shortcuts will be copied down as part of the process.
	*~~NOTE:~~The only thing to do locally would be to [[#Edit parameters for ~~location \| edit parameters for location~~]].		*The only thing to do locally would be to [[#Edit parameters for identifier]].

	=== Edit parameters for ~~location~~ ===		=== Edit parameters for identifier ===
	# right-click the news-and-backup shortcut and click "edit"		# right-click the news-and-backup shortcut and click "edit"
	#* '''Don't double-click''' because that would run the file		#* '''Don't double-click''' because that would run the file
	#* [[File:News and backup context menu.png \| 150px]]		#* [[File:News and backup context menu.png \| 150px]]
	# go to the line that starts with "set ml=", should be around line 12		# go to the line that starts with "set ml=", should be around line 12
	# change the "somewhere" to the [[Laptop ~~location~~]], i.e. your directory on the regional server, e.g. HSC_H4		# change the "somewhere" to the [[Laptop identifier]], i.e. your directory on the regional server, e.g. HSC_H4
	#* don't add spaces		#* don't add spaces
	#* make sure it's the directory used for the [[Laptop ~~location~~]], for legacy reasons this might not be the main ward now collected on		#* make sure it's the directory used for the [[Laptop identifier]], for legacy reasons this might not be the main ward now collected on
	# menu file save, menu file close		# menu file save, menu file close
	#* [[File:News and backup edit menu.png \| 400px]]		#* [[File:News and backup edit menu.png \| 400px]]
Line 68:		Line 68:

	== Updating the file ==		== Updating the file ==
	BatStart.bat looks for an update to backup.bat in regional server\programs\<~~location~~>; that file will replace the local one.		BatStart.bat looks for an update to backup.bat in regional server\programs\<[[Laptop identifier]]>; that file will replace the local one.

	Make sure [[Batstart.bat#Log]]/[[Backup.bat#Log]] is updated with any changes.		Make sure [[Batstart.bat#Log]]/[[Backup.bat#Log]] is updated with any changes.
Line 77:		Line 77:
	Main office uses [[Backup_Checker.vbs]] to make sure the backups are working.		Main office uses [[Backup_Checker.vbs]] to make sure the backups are working.

			== Related articles ==
			{{Related Articles}}

Ttenbergen: /* Process */

2019-10-03T17:33:49Z

Process

← Older revision		Revision as of 12:33, 3 October 2019
Line 35:		Line 35:
	** '''move''' the file from the regional server to c:\ccmdb_'''program'''		** '''move''' the file from the regional server to c:\ccmdb_'''program'''
	** open the wiki to [[Log]] to show what has changed		** open the wiki to [[Log]] to show what has changed
			** copy log file CCMDB_backup_log.txt to the corresponding [[Regional Server]]\data\<laptop location>; this log would show you when people have run news and backup and if there were errors.

	== Setting up the file on a laptop ==		== Setting up the file on a laptop ==

TOstryzniuk: /* How often should you run News and Backup? */ New and backup - Staff please review

2019-08-27T19:27:55Z

How often should you run News and Backup?: New and backup - Staff please review

← Older revision		Revision as of 14:27, 27 August 2019
Line 5:		Line 5:
	=== How often should you run News and Backup? ===		=== How often should you run News and Backup? ===
	The following are the '''minimally required news and backups''' and their reasons:		The following are the '''minimally required news and backups''' and their reasons:
	* at '''beginning of collection with a laptop''' before data entry		# at '''beginning of collection with a laptop''' before data entry
	** this ensures that you have the newest version of the program		#*this ensures that you have the newest version of the program
	* at '''end of collection with a laptop'''		# at '''end of collection day with a laptop''' (whether you send or not)
	** very rarely things go wrong during sending; making a backup just before sending means we would be able to restore you to that version if sending corrupts your data		#* very rarely things go wrong during sending; making a backup just before sending means we would be able to restore you to that version if sending corrupts your data
	** also, it gives main office data to go on if they have to do any "forensics" on your data if send made a mess at our end; sometimes the [[Data processor]] will re-send data from this backup so you don't have to.		#* also, it gives main office data to go on if they have to do any "forensics" on your data if send made a mess at our end; sometimes the [[Data processor]] will re-send data from this backup so you don't have to.
	* '''after [[sending]]''' but '''before DELETING''' any files from laptop		# '''just before [[sending]]''''
	** again, this gives the main office data to review in case something went wrong with the send.		# '''after [[sending]]''' but '''before DELETING''' any files from laptop
			#* again, this gives the main office data to review in case something went wrong with the send.

	You can additionally back up mid day. In theory you can do this as frequently as you want, but there are draw backs: we only keep the last 20 backups, so if you back up 10 times a day we only have 2 days of backups for you. So, if we found out that we want to know something that happened last week, then if you did 10 a day we would no longer have the data, but if you did 3 a day, we usually would still have the data. So, be reasonable in your backup frequency.		You can additionally back up mid day. In theory you can do this as frequently as you want, but there are draw backs: we only keep the last 20 backups, so if you back up 10 times a day we only have 2 days of backups for you. So, if we found out that we want to know something that happened last week, then if you did 10 a day we would no longer have the data, but if you did 3 a day, we usually would still have the data. So, be reasonable in your backup frequency.

Ttenbergen: /* When to run Required minimally- IMPORTANT */

2019-05-09T22:19:12Z

When to run Required minimally- IMPORTANT

← Older revision		Revision as of 17:19, 9 May 2019
Line 3:		Line 3:
	== Backing up ==		== Backing up ==
	'''To back up, double-click on the "News and Backup" shortcut on your desktop.'''		'''To back up, double-click on the "News and Backup" shortcut on your desktop.'''
	=== ~~When to~~ run ~~Required minimally- IMPORTANT~~ ===		=== How often should you run News and Backup? ===
	~~Run '''while connected to~~ the ~~network~~''' ~~at at the following times (~~'''~~REQUIRED''' - this goes to Regional Server)~~:		The following are the '''minimally required news and backups''' and their reasons:
	#at '''beginning of collection with a laptop''' before data entry ~~(to ensure~~ you have the newest version of the program)		* at '''beginning of collection with a laptop''' before data entry
	#at '''end of collection with a laptop''' (to ~~ensure~~ your data ~~is backed up~~ to the ~~server)~~		** this ensures that you have the newest version of the program
	#'''after [[sending]]''' but '''before DELETING''' any files from laptop ~~- IMPORTANT!!!!!!~~		* at '''end of collection with a laptop'''
	~~#you~~ can additionally back up mid day if you have ~~done~~ a ~~lot of work~~.		** very rarely things go wrong during sending; making a backup just before sending means we would be able to restore you to that version if sending corrupts your data
			** also, it gives main office data to go on if they have to do any "forensics" on your data if send made a mess at our end; sometimes the [[Data processor]] will re-send data from this backup so you don't have to.
			* '''after [[sending]]''' but '''before DELETING''' any files from laptop
			** again, this gives the main office data to review in case something went wrong with the send.

			You can additionally back up mid day. In theory you can do this as frequently as you want, but there are draw backs: we only keep the last 20 backups, so if you back up 10 times a day we only have 2 days of backups for you. So, if we found out that we want to know something that happened last week, then if you did 10 a day we would no longer have the data, but if you did 3 a day, we usually would still have the data. So, be reasonable in your backup frequency.

	==Importance of backup to REGIONAL SERVER==		==Importance of backup to REGIONAL SERVER==

← Older revision		Revision as of 10:55, 10 June 2020
Line 32:		Line 32:
	** back up to local backup directory c:\ccmdb_data\ccmdb_backups w 20 versions of [[CCMDB_data.mdb]]		** back up to local backup directory c:\ccmdb_data\ccmdb_backups w 20 versions of [[CCMDB_data.mdb]]
	** back up to server w 20 versions of [[CCMDB_data.mdb]] to the regional server		** back up to server w 20 versions of [[CCMDB_data.mdb]] to the regional server
	** check if there is a file [[Regional Server]]\Programs\<hosp>_<ward>\ccmdb.~~mdb~~; if so,		** check if there is a file [[Regional Server]]\Programs\<hosp>_<ward>\ccmdb.accdb; if so,
	** '''move''' the file from the regional server to c:\ccmdb_'''program'''		** '''move''' the file from the regional server to c:\ccmdb_'''program'''
	** open the wiki to [[Log]] to show what has changed		** open the wiki to [[Log]] to show what has changed
Line 57:		Line 57:
	== Testing News and Backup ==		== Testing News and Backup ==
	After initial setup test that the backup works:		After initial setup test that the backup works:
	* open and close ccmdb.~~mdb~~ to update date stamp of file on the client laptop		* open and close ccmdb.accdb to update date stamp of file on the client laptop
	* execute the News and Backup batch file to perform the process		* execute the News and Backup batch file to perform the process
	* check that ccmdb.~~mdb~~ file with new stamp is on c:\ccmdb_data\ccmdb_backups		* check that ccmdb.accdb file with new stamp is on c:\ccmdb_data\ccmdb_backups
	* check that ccmdb.~~mdb~~ file with new stamp is on [[Regional Server]]/data/<hsp>_<ward>		* check that ccmdb.accdb file with new stamp is on [[Regional Server]]/data/<hsp>_<ward>

	== Information about the batch files ==		== Information about the batch files ==