Wolfgang Link d869a19c9e Cleanup for stateless jobs. ... If a VM configuration has been manually moved or recovered by HA, there is no status on this new node. In this case, the replication snapshots still exist on the remote side. It must be possible to remove a job without status, otherwise, a new replication job on the same remote node will fail and the disks will have to be manually removed. When searching through the sorted_volumes generated from the VMID.conf, we can be sure that every disk will be removed in the event of a complete job removal on the remote side. In the end, the remote_prepare_local_job calls on the remote side a prepare.		2018-05-09 15:10:30 +02:00
..
VZDump	vzdump: add common log sub-method	2017-12-15 12:11:22 +01:00
AbstractConfig.pm	Fix #1480: die if snapshot name is not found before set_lock is used	2017-09-01 09:06:24 +02:00
AbstractMigrate.pm	AbstractMigrate: remove unused obsolete variables	2017-09-20 12:39:11 +02:00
GuestHelpers.pm	GuestHelpers: allow overriding $lockdir in test environments	2017-06-09 12:00:51 +02:00
Replication.pm	Cleanup for stateless jobs.	2018-05-09 15:10:30 +02:00
ReplicationConfig.pm	Revert "Add guest type at find_local_replication_job"	2017-06-29 07:27:16 +02:00
ReplicationState.pm	replication: purge states: verify the vmlist	2017-10-17 14:00:39 +02:00