Perth Hackfest October 2012/Asynchronous Backup System spec - Revision history

Sarjona: This page will not be migrated to new devdocs

2025-02-07T15:20:30Z

This page will not be migrated to new devdocs

← Older revision		Revision as of 15:20, 7 February 2025
Line 1:		Line 1:
			{{Template:WillNotMigrate}}

	== Purpose ==		== Purpose ==
	The Moodle backup and restore system is a powerful and resource-intensive system. On large, busy sites, the active use of backup and restore can significantly impact successful operation by negatively impacting performance. Often times the necessary workflows of an organization using Moodle requires backup and restore being peformed at the same time as a peak user period (e.g. educational institution setting up a new session while previous session carrying out an exam period).		The Moodle backup and restore system is a powerful and resource-intensive system. On large, busy sites, the active use of backup and restore can significantly impact successful operation by negatively impacting performance. Often times the necessary workflows of an organization using Moodle requires backup and restore being peformed at the same time as a peak user period (e.g. educational institution setting up a new session while previous session carrying out an exam period).

Damyon at 00:53, 20 November 2012

2012-11-20T00:53:25Z

← Older revision		Revision as of 00:53, 20 November 2012
Line 29:		Line 29:
	Alternate spec here:		Alternate spec here:

	[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification\| ASynchronous Backup and Restore Specification]		[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification ASynchronous Backup and Restore Specification]

Damyon at 00:53, 20 November 2012

2012-11-20T00:53:06Z

← Older revision		Revision as of 00:53, 20 November 2012
Line 29:		Line 29:
	Alternate spec here:		Alternate spec here:

	[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification\|ASynchronous Backup and Restore Specification]		[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification\| ASynchronous Backup and Restore Specification]

Damyon at 00:52, 20 November 2012

2012-11-20T00:52:41Z

← Older revision		Revision as of 00:52, 20 November 2012
Line 29:		Line 29:
	Alternate spec here:		Alternate spec here:

	[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification]		[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification\|ASynchronous Backup and Restore Specification]

Damyon at 09:45, 19 November 2012

2012-11-19T09:45:01Z

← Older revision		Revision as of 09:45, 19 November 2012
Line 26:		Line 26:
	== References ==		== References ==
	[https://docs.moodle.org/dev/Perth_Hackfest_October_2012/Backup Hackfest discussion notes]		[https://docs.moodle.org/dev/Perth_Hackfest_October_2012/Backup Hackfest discussion notes]

			Alternate spec here:

			[https://docs.moodle.org/dev/ASynchronous_Backup_and_Restore_Specification]

Mchurch at 14:30, 13 November 2012

2012-11-13T14:30:59Z

← Older revision		Revision as of 14:30, 13 November 2012
Line 23:		Line 23:
	* Create a backup/restore plug-in system to build the different types of backup processing		* Create a backup/restore plug-in system to build the different types of backup processing
	** Build the first asynchronous backup processor as a plug-in		** Build the first asynchronous backup processor as a plug-in

			== References ==
			[https://docs.moodle.org/dev/Perth_Hackfest_October_2012/Backup Hackfest discussion notes]

Mchurch at 14:25, 13 November 2012

2012-11-13T14:25:01Z

← Older revision		Revision as of 14:25, 13 November 2012
Line 1:		Line 1:

	== Purpose ==		== Purpose ==
	The Moodle backup and restore system is a powerful and resource-intensive system. On large, busy sites, the active use of backup and restore can significantly impact successful operation by negatively impacting performance. Often times the necessary workflows of an organization using Moodle requires backup and restore being peformed at the same time as a peak user period (e.g. educational institution setting up a new session while previous session carrying out an exam period).		The Moodle backup and restore system is a powerful and resource-intensive system. On large, busy sites, the active use of backup and restore can significantly impact successful operation by negatively impacting performance. Often times the necessary workflows of an organization using Moodle requires backup and restore being peformed at the same time as a peak user period (e.g. educational institution setting up a new session while previous session carrying out an exam period).
Line 12:		Line 11:
	* Ability to monitor progress and notify completion and other status of operations.		* Ability to monitor progress and notify completion and other status of operations.
	* Ability to disable synchronous backup/restore (live) functions from specified users.		* Ability to disable synchronous backup/restore (live) functions from specified users.

			== Use Cases ==

	== Design Ideas ==		== Design Ideas ==
	* Need a new cron system, if cron is to be used, so that more control over when and how long tasks can run.		* Need a new cron system, if cron is to be used, so that more control over when and how long tasks can run.
	** (Note: ELIS has an improved cron system that could be looked at that can break up long running tasks and allow scheduling)		** (Note: ELIS has an improved cron system that could be looked at that can break up long running tasks and allow scheduling)
			* Queueing system with dispatch intelligence (multiple runs, single runs)
			** Ability to see a schedule list of what is due to run and progress bar, start/end times, email completion success/failure.
			* Could use event API
			* Use capabilities to control who can access backup types (synchronous, ansynchronous, etc.)
			* Create a backup/restore plug-in system to build the different types of backup processing
			** Build the first asynchronous backup processor as a plug-in

Mchurch at 22:18, 12 November 2012

2012-11-12T22:18:32Z

← Older revision		Revision as of 22:18, 12 November 2012
Line 1:		Line 1:
	~~== Introduction ==~~
	~~This page details a proposal to introduce a new plugable backup system that would allow for backup/restore to be handled asynchronously.~~

	== Purpose ==		== Purpose ==
Line 16:		Line 14:

	== Design Ideas ==		== Design Ideas ==
			* Need a new cron system, if cron is to be used, so that more control over when and how long tasks can run.
			** (Note: ELIS has an improved cron system that could be looked at that can break up long running tasks and allow scheduling)

Mchurch at 18:57, 12 November 2012

2012-11-12T18:57:31Z

← Older revision		Revision as of 18:57, 12 November 2012
Line 3:		Line 3:

	== Purpose ==		== Purpose ==
			The Moodle backup and restore system is a powerful and resource-intensive system. On large, busy sites, the active use of backup and restore can significantly impact successful operation by negatively impacting performance. Often times the necessary workflows of an organization using Moodle requires backup and restore being peformed at the same time as a peak user period (e.g. educational institution setting up a new session while previous session carrying out an exam period).

	== Design ==		Also, very large backup operations can time-out in the web environment, preventing operations from successfully completing.

			As a solution, backup and restore could be redesigned in a way that would allow for these operations to be scheduled and handled asynchronously rather than synchronously on-demand. This system would also allow for the prevention of synchronous backups as specified by the site administrators.

			== Requirements ==
			* Ability to run the backup/restore operations in a "managed" (scheduled and queued) way to reduce impact on Moodle performance.
			* Ability to separate the backup/restore operations from synchronous operation on the Moodle server.
			* Ability to monitor progress and notify completion and other status of operations.
			* Ability to disable synchronous backup/restore (live) functions from specified users.

			== Design Ideas ==

Mchurch: Created page with "== Introduction == This page details a proposal to introduce a new plugable backup system that would allow for backup/restore to be handled asynchronously. == Purpose == == Des..."

2012-11-12T18:04:09Z

Created page with "== Introduction == This page details a proposal to introduce a new plugable backup system that would allow for backup/restore to be handled asynchronously. == Purpose == == Des..."

New page

== Introduction ==
This page details a proposal to introduce a new plugable backup system that would allow for backup/restore to be handled asynchronously.

== Purpose ==

== Design ==