stoney conductor: VM Backup - Revision history

Michael: /* Communication through backend */

2014-06-27T14:43:25Z

Communication through backend

← Older revision		Revision as of 16:43, 27 June 2014
Line 452:		Line 452:
	The actual KVM-Restore process is controlled completely by the Control instance daemon via the OpenLDAP directory. See [[#OpenLDAP Directory Integration\|OpenLDAP Directory Integration]] the involved attributes and possible values.		The actual KVM-Restore process is controlled completely by the Control instance daemon via the OpenLDAP directory. See [[#OpenLDAP Directory Integration\|OpenLDAP Directory Integration]] the involved attributes and possible values.

	[[File:Daemon-interaction-restore.png\|thumb\|~~500px~~\|none\|Figure 3: Communication between all involved parties during the restore process]]		[[File:Daemon-interaction-restore.png\|thumb\|650px\|none\|Figure 3: Communication between all involved parties during the restore process]]

	You can modify/update these interactions by editing [[File:Restore-Interaction.xmi]] (you may need [http://uml.sourceforge.net/ Umbrello UML Modeller] diagram programme for KDE to display the content properly).		You can modify/update these interactions by editing [[File:Restore-Interaction.xmi]] (you may need [http://uml.sourceforge.net/ Umbrello UML Modeller] diagram programme for KDE to display the content properly).

Michael: /* Current Implementation (Backup) */

2014-06-27T14:41:44Z

Current Implementation (Backup)

← Older revision		Revision as of 16:41, 27 June 2014
Line 359:		Line 359:


	[[File:wrapper-interaction.png\|~~500px~~\|thumbnail\|none\|Figure 2: How the two wrapper interact with the LDAP backend]]		[[File:wrapper-interaction.png\|650px\|thumbnail\|none\|Figure 2: How the two wrapper interact with the LDAP backend]]

	You can modify/update this workflow by editing [[File:wrapper-interaction.xmi]] (you may need [http://uml.sourceforge.net/ Umbrello UML Modeller] diagram programme for KDE to display the content properly).		You can modify/update this workflow by editing [[File:wrapper-interaction.xmi]] (you may need [http://uml.sourceforge.net/ Umbrello UML Modeller] diagram programme for KDE to display the content properly).

Pat: /* Current Implementation (Backup) */

2014-06-27T12:58:47Z

Current Implementation (Backup)

← Older revision		Revision as of 14:58, 27 June 2014
Line 360:		Line 360:

	[[File:wrapper-interaction.png\|500px\|thumbnail\|none\|Figure 2: How the two wrapper interact with the LDAP backend]]		[[File:wrapper-interaction.png\|500px\|thumbnail\|none\|Figure 2: How the two wrapper interact with the LDAP backend]]

			You can modify/update this workflow by editing [[File:wrapper-interaction.xmi]] (you may need [http://uml.sourceforge.net/ Umbrello UML Modeller] diagram programme for KDE to display the content properly).

	* If for some reason something does not work at all, the whole backup process can be deactivated by simply disabling the LDAPKVMWrapper cronjob		* If for some reason something does not work at all, the whole backup process can be deactivated by simply disabling the LDAPKVMWrapper cronjob

Pat: /* Communication through backend */

2014-06-27T12:55:51Z

Communication through backend

← Older revision		Revision as of 14:55, 27 June 2014
Line 118:		Line 118:

	[[File:Daemon-communication.png\|800px\|thumbnail\|none\|Figure 1: Communication between the control instance and the prov-backup-kvm daemon through the LDAP backend]]		[[File:Daemon-communication.png\|800px\|thumbnail\|none\|Figure 1: Communication between the control instance and the prov-backup-kvm daemon through the LDAP backend]]

			You can modify/update this workflow by editing [[File:Daemon-communication.xmi]] (you may need [http://uml.sourceforge.net/ Umbrello UML Modeller] diagram programme for KDE to display the content properly).

	=== Control-Instance Daemon Interaction for creating a Backup with LDIF Examples ===		=== Control-Instance Daemon Interaction for creating a Backup with LDIF Examples ===

Pat: /* Restore */

2014-06-26T14:57:22Z

Restore

← Older revision		Revision as of 16:57, 26 June 2014
Line 398:		Line 398:

	= Restore =		= Restore =
			'''Attention:''' The restore process is not yet defined / nor implemented. The following documentation is about the old restore process.
	== Basic idea ==		== Basic idea ==
	The restore process, similar to the backup process, can be divided into three sub-processes:		The restore process, similar to the backup process, can be divided into three sub-processes:

Pat: /* Current Implementation (Restore) */

2014-06-26T13:58:20Z

Current Implementation (Restore)

← Older revision		Revision as of 15:58, 26 June 2014
Line 599:		Line 599:

	== Current Implementation (Restore) ==		== Current Implementation (Restore) ==
	* Since the prov-backup-kvm daemon is not running on the vm-nodes (c.f. [[stoney_conductor:_Backup#~~State_of_the_art~~]]), the restore process does not work when clicking the icon in the webinterface.		'''Attention''': The restore process is not yet defined / nor implemented. The following documentation is about the old restore process.
	* Resolving the conflicts in the backend and XML description file is not yet done
	** Actually all steps not executed by prov-backup-kvm are not yet properly implemented (c.f. [[stoney_conductor:_prov_backup_kvm#Restore]])
	* The implementation is done, but the last step from the [[#Restore_2 \| restore process ]] is different:		* Since the prov-backup-kvm daemon is not running on the vm-nodes (c.f. [[stoney_conductor:_Backup#Current_Implementation_.28Backup.29]]), the restore process does not work when clicking the icon in the webinterface.
	** The <code>virsh restore</code> command is not executed with the <code>--xml</code> option, the XML from the state file is taken when restoring the machine. Therefore the conflicts are not properly resolved.
	*** --[[User:Pat\|Pat]] ([[User talk:Pat\|talk]]) 09:41, 29 October 2013 (CET): Currently the [http://search.cpan.org/~danberr/Sys-Virt-1.1.3/lib/Sys/Virt.pm Sys::Virt] library does not support the --xml parameter when restoring a domain

	=== How to manually restore a machine from backup ===		=== How to manually restore a machine from backup ===

Pat: /* Current Implementation (Backup) */

2014-06-26T13:54:55Z

Current Implementation (Backup)

← Older revision		Revision as of 15:54, 26 June 2014
Line 351:		Line 351:
	#* Remove the old backup leaf (the "yesterday-leaf"), and add a new one (the "today-leaf")		#* Remove the old backup leaf (the "yesterday-leaf"), and add a new one (the "today-leaf")
	#* After this step, the machines are ready to be backed up		#* After this step, the machines are ready to be backed up
	# Call the ~~BackupKVMWrapper~~.pl script with the machines list as a parameter		# Call the KVMBackupWrapper.pl script with the machines list as a parameter
	# Wait for the ~~BackupKVMWrapper~~.pl script to finish		# Wait for the KVMBackupWrapper.pl script to finish
	# Go again through all machines and update the backup subtree a last time		# Go again through all machines and update the backup subtree a last time
	#* Check if the backup was successful, if yes, set sstProvisioningMode = finished (see also TBD)		#* Check if the backup was successful, if yes, set sstProvisioningMode = finished (see also TBD)

Pat: /* Backup a single machine */

2014-06-26T13:52:47Z

Backup a single machine

← Older revision		Revision as of 15:52, 26 June 2014
Line 20:		Line 20:
	Furthermore there is an control instance, which can independently call these three sub-processes for a given machine. Like that, the stoney cloud is able to handle different cases:		Furthermore there is an control instance, which can independently call these three sub-processes for a given machine. Like that, the stoney cloud is able to handle different cases:
	=== Backup a single machine ===		=== Backup a single machine ===
	The procedure for backing up a single machine is very simple. Just call the three sub-processes (~~snapshot~~, ~~merge~~ and ~~retain~~) one after the other. So the control instance would do some very basic stuff:		The procedure for backing up a single machine is very simple. Just call the three sub-processes (create-, export- and commitSnapshot) one after the other. So the control instance would do some very basic stuff:
	<source lang="c">		<source lang="c">
	object machine = args[0];		object machine = args[0];

Pat: /* Step 12: Finalizing the Backup Process (Control instance daemon) */

2014-06-26T13:52:15Z

Step 12: Finalizing the Backup Process (Control instance daemon)

← Older revision		Revision as of 15:52, 26 June 2014
Line 321:		Line 321:

	==== Step 12: Finalizing the Backup Process (Control instance daemon) ====		==== Step 12: Finalizing the Backup Process (Control instance daemon) ====
	As soon as the Control instance daemon notices, that the attribute '''sstProvisioningMode''' ist set to '''~~retained~~''', it sets the '''sstProvisioningMode''' to '''finished''' and the '''sstProvisioningState''' to the current timestamp (UTC). All interested parties now know, that the backup process is finished, there for a new backup process could be started.		As soon as the Control instance daemon notices, that the attribute '''sstProvisioningMode''' ist set to '''committed''', it sets the '''sstProvisioningMode''' to '''finished''' and the '''sstProvisioningState''' to the current timestamp (UTC). All interested parties now know, that the backup process is finished, there for a new backup process could be started.
	<pre>		<pre>
	# The attribute sstProvisioningState is updated with current time by the fc-brokerd, when sstProvisioningMode is		# The attribute sstProvisioningState is updated with current time by the fc-brokerd, when sstProvisioningMode is

Pat: /* Step 11: Finalizing the Retaing Process (Provisioning-Backup-KVM daemon) */

2014-06-26T13:51:56Z

Step 11: Finalizing the Retaing Process (Provisioning-Backup-KVM daemon)

← Older revision		Revision as of 15:51, 26 June 2014
Line 302:		Line 302:
	</pre>		</pre>

	==== Step 11: Finalizing the ~~Retaing~~ Process (Provisioning-Backup-KVM daemon) ====		==== Step 11: Finalizing the commit Process (Provisioning-Backup-KVM daemon) ====
	As soon as the Provisioning-Backup-KVM daemon has executed the ~~retain~~ command, it sets the '''sstProvisioningMode''' to '''~~retained~~''', the '''sstProvisioningState''' to the current timestamp (UTC) and '''sstProvisioningReturnValue''' to zero to tell the Control instance daemon and other interested parties, that the ~~retaining~~ of ~~all~~ the ~~necessary files~~ to the ~~configured backup location~~ is ~~finished~~.		As soon as the Provisioning-Backup-KVM daemon has executed the commit command, it sets the '''sstProvisioningMode''' to '''comitted''', the '''sstProvisioningState''' to the current timestamp (UTC) and '''sstProvisioningReturnValue''' to zero to tell the Control instance daemon and other interested parties, that the comitting of the changes from the overlay disk-images back to the underlying ones is done.
	<pre>		<pre>
	# The attribute sstProvisioningState is set with the current timestamp by the Provisioning-Backup-VKM daemon, when		# The attribute sstProvisioningState is set with the current timestamp by the Provisioning-Backup-VKM daemon, when
Line 317:		Line 317:
	-		-
	replace: sstProvisioningMode		replace: sstProvisioningMode
	sstProvisioningMode: ~~retained~~		sstProvisioningMode: comitted
	</pre>		</pre>