@olivierlambert Sussed it! The remote storage must not contain any encrypted data using the old algorithm! That's where I went wrong I think!

Feature Request: Would it be possible to specify a delay between "Number of retries if VM backup fails"? Last night there was an internet outage that affected many of my clients s3 backups. I noticed that the retries I had specified all happened immediately after the internet failure with no delay between them. Because the internet was not restored they all failed too. It would be good to set a delay between retries to allow time for the internet to be restored. Today I manually restarted all the failed backups.
Thanks.

I will backup again without deleting the snapshot and then attempt a differential restore.
I will update this thread when done.

Thank you,
I will consider that as a way forward.

I started with XCP 1.0 a few years ago then 1.1 and 1.6 'till xenserver 6.2 became open source. Been with xenserver ever since. I run a small (one man band) company providing IT and sysadmin support to fourteen small to medium sized companies. All are virtualized on various versions of xenserver. All are using standalone servers. Some more recent ones use bcache local storage with redundant mdadm array as backing device and ssd as caching device. /dev/bcache0 then becomes local repository so all vms in repo benefit from ssd caching. Citrix pissed me off with the release of xs7.3 so I am really pleased to find this fork. Having started with XCP 1.0 it feels like coming home.
I came into IT nearly 20 years ago having spent the previous 30 years in electronic engineering. I am self taught. I have to say I found electronics easier...

@dvdhngs
Run lvscan to see if there are any active logical volumes. If there are run vgchange <group name> -an to deactivate all logical volumes. Now try to stop the array.

@frank-s Hello again. My issue is resolved. I was using used disks which had previously been used with mdadm. Although I applied "mdadm --zero-superblock" to every partition and the device itself before deleting the partition tables and dd zeroed the first 50 Gigs of the drives, the installer didn't like it. Maybe I should also have zeroed the end of the drive??? Anyway I zeroed out the entire drive (both of them) with dd and the installer worked like a charm. I also tested upgrade which also worked flawlessly.
Thank you for the great work you are doing. Over the years I have spent many many hours loading xenserver with bootable raid. This is going to make life so much easier...

@Danp Thanks for pointing me in the right direction. I was following an older howto where --global was not specified. That was my first problem - now fixed!
Second problem was that I had installed into the root directory of Centos7 so the paths for creating the links were different. Once I had found the correct paths and created the links all was good.
Thanks again.
Frank.

@DustinB OK. I think I'm between a rock and a hard place! Thanks for the advice.

@DustinB Yes, by reducing the retention. I have thought about that but I'm afraid that the merge might happen after the backup and because there is insufficient space the backup would fail again. I don't want the system to force a full backup because I follow this backup with a mirror backup to s3 and the internet upload is limited in speed.

@DustinB These are delta backups. I'm just wondering if the delete button in the restore page is just that - delete which would break the chain or if a merge is used which would preserve the chain.

Good Morning, I am using XOCE Xen Orchestra, commit adc5b, Master, commit adc5b. I have backups failing on one of my servers because of insufficient free space on the NFS remote. If, in the backup/restore page I delete some of the older backups, will that break the chain or will it use merge to preserve the integrity of the chain?
Thanks.

@olivierlambert Sussed it! The remote storage must not contain any encrypted data using the old algorithm! That's where I went wrong I think!

I have just updated one of my xen-orchestra instances to Xen Orchestra, commit 47ee8 Master, commit 5dbb5. When I look at my s3 remote there is an exclamation mark next to the encryption icon. The mouseover tells me to create a new remote with the recommended algorithm chacha20-poly 1305. I created a new remote to the same repository, but the exclamation mark is still there. The algorithm remains at aes-256-ccm. Can you advise on how to proceed please?

@MathieuRA Thank you!

Feature Request: Would it be possible to specify a delay between "Number of retries if VM backup fails"? Last night there was an internet outage that affected many of my clients s3 backups. I noticed that the retries I had specified all happened immediately after the internet failure with no delay between them. Because the internet was not restored they all failed too. It would be good to set a delay between retries to allow time for the internet to be restored. Today I manually restarted all the failed backups.
Thanks.

@abudef Yes, data blocks is enabled on the remote.

@abudef I just had a backup failure. This triggered a full (key) backup on the next run which transferred 165GiB. When I rdpd into the vm I could see that the vm contained 345GiB of data including the system drive. I conclude, therefore that compression is working for full key backups at a ration of around 2:1.
I hope this helps.