RHHI 1.7 Maintaining_Red_Hat_Hyperconverged_Infrastructure_for_Virtualization-en-US and I started my implementation

I prepared all the ansible playbooks.

The Test procedure:

Fail-over

1 - Create a Windows10 VM on the source volume.

2 - Replicate to the DR site.

3 - Execute the fail-over procedure and test if the WM is usable in the target platform.

4 - Detach and Delete the data domain in the target platform without touching the target volume

5 - Make changes to the Win10 VM on the source volume (creating files and installing software)

6 - Replicate again to the DR site then execute another fail-over and see if the modification were synced.

Fail-back

1 - Make changes to the Win10 VM on the target volume (deleting files) and especially creating a snapshot

2 - Detach and Delete the data domain in the source platform without touching the source volume.

3 - Replicate to the source site.

4 - Execute the clean up playbook

5 - Execute the fail-over and WM is usable in the source platform and that the modifications were synced especially the snapshot

Things I need to confirm :

1 - When creating the geo-replication from the primary site to the target site, we get to a point where we have to create "Scheduling regular backups using geo-replication", from my understanding it's like a cron job that starts the geo-replication at a specific time (or day time), and from my testing, the geo-replication starts syncing at that precise time and when its "CRAWL STATUS" reaches "Changelog Crawl" it stops the synchronization. In other terms when the geo-replication reaches the same date as the check-point (the specific time).

The smallest time you can get from the configuration window is 24hours, which means in the event of a disaster, you can at most recover the data from the day before. Is this correct?

Problems encountered during the test:

Fail-over

1 - When executing the fail-over the first time (ansible-playbook dr-rhv-failover.yml --tags "fail_over"), the import of the target data domain failed with the error : An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Error in creating a Storage Domain. The selected storage path is not empty (probably contains another Storage Domain). Either remove the existing Storage Domain from this path, or change the Storage path).]". HTTP response code is 400. I tried manually to import the domain from oVirt's admin console and I got the same error. so I did the following

- I deleted the target volume and the brick and the sub-directory of the brick.

- I recreated the volume from scratch.

- I redid the geo-replication synchronization from the source.

- I executed the fail-over and this time the target data domain was imported correctly and the Win10 VM was started correctly.

2 - I detached then deleted the target data domain without touching the target volume, then I made change to the Win10 VM on the source site, then I created a new schedule of geo-replication, and after the replication I executed another fail-over.

- The Win10 VM started successfully and the changes made were synced.