For the configuration and usage of this RAID 1 in your system, what you should actually do would be a Recovery volume which does actually use a Master/Recovery relationship between the drives.
In this case you should just need to remove the recovery drive to copy the data to another system and then put it back to the system and sync it with the Master drive.
While using simple RAID 1, and triggering a degrade state (removing one of the drives), may cause conflicts when the "removed" drive is placed back into the system. Even though it has been formatted, meta data on the drive can still be preserved and this drive can be confused as the drive with the more "updated" information and the rebuild can be done from an incorrect source.
For information on how to enable this, please check these articles:
Thanks for the information.
I am aware of recovery mode and I have tried it as well, but I suppose during testing I got confused by the descriptions of 'continuous' and 'on request' modes.
What I want to achieve is a fully automatic resync of the drives upon inserting the new drive (a fresh drive or the recovery drive in case of recovery mode). This is necessary as the device has no user interface available.
From my testing even continuous mode required a manual triggering of updating the recovery drive with the data from the master drive upon insertion. Again, all configuration was done from the OS tray app. Is continuous mode supposed to always force the data from the master to be copied to the recovery volume or a new drive without the need to reconfigure the array?
Would inserting a fresh drive guarantee a correct resync in RAID1 mode?
From our testing if the drive was just removed from the RAID array (which causes a degrade state) and then placed back to the configuration, the rebuild process will start by itself with no user intervention.
Inserting a fresh drive, would require you to manually set the drive as an spare drive or rebuild to that new drive.