Backup and Restore - Revision history

Arvind at 08:42, 21 February 2023

2023-02-21T08:42:29Z

← Older revision		Revision as of 08:42, 21 February 2023
Line 1:		Line 1:
	==Description of Backup Procedure for ~~the~~ Client Hosted NEOSYS ~~Server~~==		==Description of Backup Procedure for Client Hosted NEOSYS Servers==

	3 USBs must be maintained and rotated on a weekly basis.		3 USBs must be maintained and rotated on a weekly basis.
Line 9:		Line 9:
	*In case of failure, NEOSYS support staff take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.		*In case of failure, NEOSYS support staff take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.
	*Additionally offsite backup can be set up on NEOSYS server.		*Additionally offsite backup can be set up on NEOSYS server.

			==Description of Backup Procedure for NEOSYS Client Hosting Server==

	NEOSYS backup is a two phase process. It is mandatory that both phases are complete for the process to be considered a backup.		NEOSYS backup is a two phase process. It is mandatory that both phases are complete for the process to be considered a backup.

Arvind: /* Description of Backup Procedure for the NEOSYS Client Hosting Server */

2023-02-21T08:38:58Z

Description of Backup Procedure for the NEOSYS Client Hosting Server

← Older revision		Revision as of 08:38, 21 February 2023
Line 9:		Line 9:
	*In case of failure, NEOSYS support staff take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.		*In case of failure, NEOSYS support staff take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.
	*Additionally offsite backup can be set up on NEOSYS server.		*Additionally offsite backup can be set up on NEOSYS server.

	~~==Description of Backup Procedure for the NEOSYS Client Hosting Server==~~

	NEOSYS backup is a two phase process. It is mandatory that both phases are complete for the process to be considered a backup.		NEOSYS backup is a two phase process. It is mandatory that both phases are complete for the process to be considered a backup.

	1. ~~On the main~~ NEOSYS server ~~host(Schuberg Philis~~ in Amsterdam ~~as of Dec 2010),Every night, the NEOSYS process for selected databases stops serving users at around 1:00 AM to 5:00 AM (local time of the client's main office) and performs~~ the ~~following~~ procedure:		1. NEOSYS server is hosted on Leaseweb in Amsterdam. Following is the backup procedure:

	*~~All~~ the ~~database files are checked for physical corruption~~.		*At 02:21 GMT, live databases are backed up, restored to test and compared with test to verify that the restore was successful.
	*~~All the database files~~ are ~~zipped into a file who's path would be something like C:\DATA.BAK\CLIENTX\MONDAY\BACKUP.ZIP file~~.		*Every hour at 40th minute, live databases are backed up without restore and verification.
	*~~The file having~~ the ~~same name as that of the corresponding day of the week as last week is overwritten.A "backup alert" email indicating success or failure is~~ sent to ~~senior managers at the client, the client’s IT manager and~~ backups@neosys.com.		*Emails for the above backups are sent to backups@neosys.com.
	*An internal log (accessible on each database's Support Menu) is maintained as a record and in case the emails cannot be sent out for some reason.		*NEOSYS support staff check the emails every morning Monday through Friday.
	*NEOSYS support staff ~~in Dubai~~ check the emails every morning ~~Sunday~~ through ~~Thursday~~.		*In the case of failure, NEOSYS support staff take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.
	*In the case of failure, NEOSYS support staff ~~in Dubai~~ take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.
	*The above does not by itself constitute a proper backup because the backup is stored on the same server and physical disk as the actual data.		*The above does not by itself constitute a proper backup because the backup is stored on the same server and physical disk as the actual data.

	2. On ~~the NEOSYS~~ backup server ~~host (in NEOSYS Dubai Office as of Dec 2010 but could be changed without notice to EvoSwitch~~ in Amsterdam).		2. On a separate backup server, also hosted on Leaseweb in Amsterdam:

	*At around ~~02:00-02:30 AM GMT daily~~, NEOSYS~~'s backup~~ server ~~copies (replicates) all~~ the ~~BACKUP.ZIP files from the main NEOSYS~~ server ~~host to itself~~.		*Every hour at around 45th minute, NEOSYS server is rsynced to the backup server.
	*~~An email indicating success or failure~~ is ~~sent to NEOSYS support staff~~ (~~only~~) ~~who deal with it in a similar way~~ to ~~phase 1, except that only NEOSYS management~~ are ~~updated~~.		*Every half hour, NEOSYS server container is copied (lxc) to the backup server. Container backups of 7 days are maintained on the backup server.

	==Backup Procedures==		==Backup Procedures==

Arvind: /* Description of Backup Procedure for the Client Hosted NEOSYS Server */

2023-02-21T08:08:03Z

Description of Backup Procedure for the Client Hosted NEOSYS Server

← Older revision		Revision as of 08:08, 21 February 2023
Line 3:		Line 3:
	3 USBs must be maintained and rotated on a weekly basis.		3 USBs must be maintained and rotated on a weekly basis.

	~~Every night~~, ~~the NEOSYS process stops serving users at around 1:00 AM~~ to ~~5:00 AM (local time of the client's main office)~~ and ~~performs~~ the ~~following procedure:~~		*At 02:21 GMT, live databases are backed up, restored to test and compared with test to verify that the restore was successful.
			*Every hour at 40th minute, live databases are backed up without restore and verification.
	*~~All the database files~~ are ~~checked for physical corruption~~.		*Every hour at 45th minute, USB backup is performed, where the client's NEOSYS server is rsynced to USB.
	*~~All the database files are zipped into a file on the~~ USB ~~who's path would be something like F:\DATA.BAK\CLIENTX\MONDAY\BACKUP.ZIP file.~~		*NEOSYS support staff check the emails every morning Monday through Friday.
	*The file having the same name as that of the corresponding day of the week as that of 3 weeks back is overwritten.A "backup ~~alert" email indicating success or failure~~ is ~~sent to senior managers at~~ the client~~, the client’s IT manager and backups@neosys.com.~~		*In case of failure, NEOSYS support staff take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.
	*An internal log (accessible on each database's ~~Support Menu)~~ is ~~maintained as a record and in case the emails cannot be sent out for some reason~~.		*Additionally offsite backup can be set up on NEOSYS server.
	*NEOSYS support staff ~~in Dubai~~ check the emails every morning ~~Sunday~~ through ~~Thursday~~.
	*In ~~the~~ case of failure, NEOSYS support staff ~~in Dubai~~ take appropriate action and send an email (to the same people who receive the automated backup alert emails) indicating what action has been taken.
	*Additionally offsite backup can be set up on NEOSYS server

	==Description of Backup Procedure for the NEOSYS Client Hosting Server==		==Description of Backup Procedure for the NEOSYS Client Hosting Server==

Arvind: /* Accessing historical snapshots of NEOSYS hosted clients data */

2021-12-22T12:24:51Z

Accessing historical snapshots of NEOSYS hosted clients data

← Older revision		Revision as of 12:24, 22 December 2021
Line 892:		Line 892:

	Inspecting Nagios shows daily backups of NEOSYS hosted clients to nl19 of win3/d. Complete hourly backup is not possible due to limitations of Windows and/or the backup software used. However, there are hourly backups of win3/d/DATA.BAK so NEOSYS process "backups" to win3/d/DATA.BAK (on the same server and disk and therefore not a proper backup) do get properly backed up to a different server once an hour.		Inspecting Nagios shows daily backups of NEOSYS hosted clients to nl19 of win3/d. Complete hourly backup is not possible due to limitations of Windows and/or the backup software used. However, there are hourly backups of win3/d/DATA.BAK so NEOSYS process "backups" to win3/d/DATA.BAK (on the same server and disk and therefore not a proper backup) do get properly backed up to a different server once an hour.

	~~===Historical/Lapsed Clients?===~~

	~~For more info see [[Uninstalling_clients_hosted_on_NEOSYS_Server\|Uninstalling clients hosted on NEOSYS server]]~~

	~~A single copy of lapsed clients last backup .sql.gz file will be kept for as long as possible along with the active client's data.~~

Arvind: /* Historical/Lapsed Clients? */

2021-12-22T12:22:26Z

Historical/Lapsed Clients?

← Older revision		Revision as of 12:22, 22 December 2021
Line 897:		Line 897:
	For more info see [[Uninstalling_clients_hosted_on_NEOSYS_Server\|Uninstalling clients hosted on NEOSYS server]]		For more info see [[Uninstalling_clients_hosted_on_NEOSYS_Server\|Uninstalling clients hosted on NEOSYS server]]

	A single copy of lapsed clients last ~~BACKUP~~.~~ZIP~~ will be kept for as long as possible along with the active client's data ~~and backed up identically.~~		A single copy of lapsed clients last backup .sql.gz file will be kept for as long as possible along with the active client's data.

	Long lapsed clients should be removed periodically from the normal DATA.BAK folder only when space runs out on win3 but a copy should be moved to D:\DATA2.BAK folder on hosts2 which is itself backed up nightly to nl19 which keeps backups for approx six months.

Gregory: /* Accessing historical snapshots of NEOSYS hosted clients data */ fixing wiki nl13 to nl19

2021-02-01T05:34:11Z

Accessing historical snapshots of NEOSYS hosted clients data: fixing wiki nl13 to nl19

Gregory: /* Accessing historical snapshots of NEOSYS hosted clients data */

2021-02-01T05:32:48Z

Accessing historical snapshots of NEOSYS hosted clients data

Show changes

Arvind: /* Getting confirmations for Backup email list */

2019-12-23T07:12:06Z

Getting confirmations for Backup email list

← Older revision		Revision as of 07:12, 23 December 2019
Line 116:		Line 116:

	#After you receive confirmation, send emails to all clients.		#After you receive confirmation, send emails to all clients.
	#*Template email to each client (Thunderbird->Support->Templates->~~BackupConfirmationEmails~~)		#*Template email to each client (Thunderbird -> Support -> Templates -> Backup Confirmation Emails)
	#Create a new spreadsheet after copying previous year's confirmations sheet and rename with current year.		#Create a new spreadsheet after copying previous year's confirmations sheet and rename with current year.
	#*You can find the previous year's confirmation list in ~~C:\Users\Androulla\~~Nextcloud\support\Androulla_Backup Confirmations		#*You can find the previous year's confirmation list in Nextcloud\support\Androulla_Backup Confirmations
	#*Clear the contents and fill in as and when you get the confirmations from clients.		#*Clear the contents and fill in as and when you get the confirmations from clients.
	#*For hosted clients in the 'IT Manager' field, put 'None'		#*For hosted clients in the 'IT Manager' field, put 'None'
Line 126:		Line 126:
	#In the case where a client asks for more than one decision maker, reply that it will be best to have only one decision maker.		#In the case where a client asks for more than one decision maker, reply that it will be best to have only one decision maker.
	#If no reply for two weeks, send email to another person other than the decision maker.		#If no reply for two weeks, send email to another person other than the decision maker.
	#*Order: Another management level user > Main point of contact -> Most active user(~~checked in~~ authorisation file)		#*Order: Another management level user > Main point of contact -> Most active user (check the authorisation file)
	#When all clients confirm, check backup spreadsheet and confirm that it ~~is in sync with~~ System ~~Config~~ file and any personal records that you have kept.		#When all clients confirm, check backup spreadsheet and confirm that it matches the System Configuration file in NEOSYS and any personal records that you have kept.

	==Manual Backup==		==Manual Backup==

Joel: /* Getting confirmations for Backup email list */

2019-12-23T07:04:06Z

Getting confirmations for Backup email list

← Older revision		Revision as of 07:04, 23 December 2019
Line 115:		Line 115:
	NEOSYS Support		NEOSYS Support

	#After you receive ~~coonfirmation~~, send emails to all clients.		#After you receive confirmation, send emails to all clients.
	#*Template email to each client (Thunderbird->Support->Templates->BackupConfirmationEmails)		#*Template email to each client (Thunderbird->Support->Templates->BackupConfirmationEmails)
	#Create a new spreadsheet after copying previous year's confirmations sheet and rename with current year.		#Create a new spreadsheet after copying previous year's confirmations sheet and rename with current year.

Joel: /* Getting confirmations for Backup email list */

2019-12-23T07:03:51Z

Getting confirmations for Backup email list

← Older revision		Revision as of 05:34, 1 February 2021
Line 872:		Line 872:
	It also contains historical snapshots of the backups going back six months.		It also contains historical snapshots of the backups going back six months.

	NEOSYS SUPPORT TEAM MUST AVOID COPYING, MOVING OR RENAMING FOLDERS ON NEOSYS WINDOWS SERVERS because this causes severe duplication and consumption of valuable resources for up to six months on ~~nl13~~. Any exception to this rule must be discussed with NEOSYS IT before implementation.		NEOSYS SUPPORT TEAM MUST AVOID COPYING, MOVING OR RENAMING FOLDERS ON NEOSYS WINDOWS SERVERS because this causes severe duplication and consumption of valuable resources for up to six months on nl19. Any exception to this rule must be discussed with NEOSYS IT before implementation.

	===How to restore?===		===How to restore?===

	~~nl13~~ is only accessible by NEOSYS IT so recovery of any data cannot be done directly by NEOSYS support team and is not a routine procedure.		nl19 is only accessible by NEOSYS IT so recovery of any data cannot be done directly by NEOSYS support team and is not a routine procedure.

	The secondary NEOSYS backup server hosts2 is accessible to NEOSYS support team but contains only the latest snapshot of the current NEOSYS hosted clients as at last night. No historical versions are available.		The secondary NEOSYS backup server hosts2 is accessible to NEOSYS support team but contains only the latest snapshot of the current NEOSYS hosted clients as at last night. No historical versions are available.
Line 882:		Line 882:
	===What snapshots are available?===		===What snapshots are available?===

	As of 2017/05/25 the NEOSYS backup server ~~nl13~~ takes snapshots (of the backups listed in Nagios) as follows using crontab:		As of 2017/05/25 the NEOSYS backup server nl19 takes snapshots (of the backups listed in Nagios) as follows using crontab:

	120 historical hourly backups done at *:10 every hour (5x24 hours)		120 historical hourly backups done at *:10 every hour (5x24 hours)
Line 891:		Line 891:
	===What is backed up?===		===What is backed up?===

	Inspecting Nagios shows daily backups of NEOSYS hosted clients to ~~nl13~~ of win3/d. Complete hourly backup is not possible due to limitations of Windows and/or the backup software used. However, there are hourly backups of win3/d/DATA.BAK so NEOSYS process "backups" to win3/d/DATA.BAK (on the same server and disk and therefore not a proper backup) do get properly backed up to a different server once an hour.		Inspecting Nagios shows daily backups of NEOSYS hosted clients to nl19 of win3/d. Complete hourly backup is not possible due to limitations of Windows and/or the backup software used. However, there are hourly backups of win3/d/DATA.BAK so NEOSYS process "backups" to win3/d/DATA.BAK (on the same server and disk and therefore not a proper backup) do get properly backed up to a different server once an hour.

	===Historical/Lapsed Clients?===		===Historical/Lapsed Clients?===
Line 899:		Line 899:
	A single copy of lapsed clients last BACKUP.ZIP will be kept for as long as possible along with the active client's data and backed up identically.		A single copy of lapsed clients last BACKUP.ZIP will be kept for as long as possible along with the active client's data and backed up identically.

	Long lapsed clients should be removed periodically from the normal DATA.BAK folder only when space runs out on win3 but a copy should be moved to D:\DATA2.BAK folder on hosts2 which is itself backed up nightly to ~~nl13~~ which keeps backups for approx six months.		Long lapsed clients should be removed periodically from the normal DATA.BAK folder only when space runs out on win3 but a copy should be moved to D:\DATA2.BAK folder on hosts2 which is itself backed up nightly to nl19 which keeps backups for approx six months.

← Older revision		Revision as of 07:03, 23 December 2019
Line 86:		Line 86:
	The below procedure is done once every year. A task has been set in Thunderbird to remind Support to begin the procedure in November.		The below procedure is done once every year. A task has been set in Thunderbird to remind Support to begin the procedure in November.

	~~First, you need~~ to send the below email to Steve and ask if any changes are required.		The first thing to do is to send the below draft email to Steve and ask if any changes are required.

	Subject: YOUR URGENT REPLY IS REQUIRED - NEOSYS Backup Confirmations for <Company>, <City>		Subject: YOUR URGENT REPLY IS REQUIRED - NEOSYS Backup Confirmations for <Company>, <City>
Line 115:		Line 115:
	NEOSYS Support		NEOSYS Support

	#After ~~Steve confirms~~, ~~you can begin sending~~ emails to all clients.		#After you receive coonfirmation, send emails to all clients.
	#*Template email to each client (Thunderbird->Support->Templates->BackupConfirmationEmails)		#*Template email to each client (Thunderbird->Support->Templates->BackupConfirmationEmails)
	#Create a new spreadsheet after copying previous year's confirmations sheet and rename with current year.		#Create a new spreadsheet after copying previous year's confirmations sheet and rename with current year.
Line 121:		Line 121:
	#*Clear the contents and fill in as and when you get the confirmations from clients.		#*Clear the contents and fill in as and when you get the confirmations from clients.
	#*For hosted clients in the 'IT Manager' field, put 'None'		#*For hosted clients in the 'IT Manager' field, put 'None'
	#*You can keep a list of all pending clients in a personal ~~txt~~ file / Or mark as 'Pending' in Spreadsheet.		#*You can keep a list of all pending clients in a personal text file and/or mark as 'Pending' in Spreadsheet.
	#If any changes, update the Spreadsheet and change in NEOSYS.		#If any changes, update the Spreadsheet and change in NEOSYS.
	#Set reminders to follow-up on these emails to decision makers once a week		#Set reminders to follow-up on these emails to decision makers once a week.
	#In the case, a client asks for more than one decision maker, reply that it will be best to have only one decision maker.		#In the case where a client asks for more than one decision maker, reply that it will be best to have only one decision maker.
	#If no reply for two weeks, send email to another person other than the decision maker.		#If no reply for two weeks, send email to another person other than the decision maker.
	#*Order: Another management level user > Main point of contact -> Most active user(checked in authorisation file)		#*Order: Another management level user > Main point of contact -> Most active user(checked in authorisation file)