@cairoti you should be able to add it as a remote ( not as a storage repository on xcp-ng)

@Andrew, @bvitnik and @DustinB In my tests, I did the following. I did this process twice and it worked. To simulate a hardware failure on the master node, I simply turned it off. If the master pool is down or unresponsive due to a hardware failure, follow these steps to restore operations: Use an SSH client to log in to a slave host in the pool. Run the following command on the slave host to promote it as the new pool master: xe pool-emergency-transition-to-master Confirm the change of the pool master and verify the hosts present in it: xe pool-list xe host-list Even if it is down, the old master node will appear in the listing. Remap the pool in XCP-ng or XO using the IP of the new master node. After resolving the hardware issues on the old master node, start it up. When it finishes booting, it will be recognized as a slave node. In testing, I did not need to run any other commands. However, if the node is not recognized, try typing on it after accessing it via SSH: xe pool-recover-slaves I didn't understand why it worked. It seemed like "magic"!

Ah nice catch! Happy to see it working now

@cairoti, I think the VMs are restarted in their natural name order. I prefix mine with 00, 01, 10, 11, 20, 21, 22 etc., to control the start order.

@cairoti I think this may be like my benchmarks, the benchmarks show decent speed to disk, but migration from server to server to local to server are just SLOW.

@cairoti said in Questions about backup features: In Delta Backup and Continuos Replication (CR), if the “Force full backup” option is selected in Schedule, will the results be identical to those of Simple Backup and Disaster Recovery (DR)? In Continuos Replication (CR), although the first backup is full and the rest are incremental backups of the Delta type, why when deleting the first backup can I later restore other backups without problems? No, that's why we are changing the names to avoid confusion. They are very different things, with only 2 families: full vs incremental. Full will always generate XVAs, while incremental work differently. See: [image: Schema-new-wording-backup-2.png] Because we are smart and when you remove it via XO UI, it will automatically regenerate a full from the penultimate backup.

@AtaxyaNetwork Thanks for your guidance. I can create a lightweight Debian VM with an NFS share for the ISOs. But even so it is strange that the drive is not known by the XO. Maybe other people can comment on this later.