Johannes Meixner

@markbertolin first and foremost: I am not at all a multipath or SAN expert. I have no personal experience with multipath or SAN and I cannot reproduce multipath or SAN...

@pcahyna thank you for your help here - I really need it! I have a question: I failed to find out by Googling for "multipath WWID" how the WWID in...

@pcahyna thank you so much! I don't need hardware specific details. That the WWID/WWN is a hardware value is the important information. So different hardware (in particular different disks) result...

@markbertolin as far as we (@pcahyna and @jsmeix) found out you do a migration onto different hardware with ReaR. Migration onto different hardware does not "just work". For some sufficiently...

Current ReaR does not support to migrate WWIDs. So migrating WWIDs needs to be done manually which means all values disklayout.conf need to be manually adapted to match the new...

Regardless that I am not at all SAN storage expert I am thinking about the following: On the one hand ReaR supports bare metal recovery. For example ReaR supports to...

@pcahyna regarding your https://github.com/rear/rear/issues/2812#issuecomment-1136932550 ``` if your disk(s) die, and you replace them with a perfectly compatible disk(s), the WWIDs still change and there is no way to get the...

My totally offhanded thinking is that migrating WWID/WWN values in disklayout.conf could be done similar as migrating disk device nodes (like '/dev/sda' -> '/dev/sdb' and '/dev/sdb' -> '/dev/sda') in disklayout.conf...

During "rear recover" multipath is activated in the ReaR recovery system with a basic setup via layout/prepare/GNU/Linux/210_load_multipath.sh which in particular loads the dm-multipath kernel module. A "rear -D recover" debug...

@markbertolin see the sections "Testing current ReaR upstream GitHub master code" and "Debugging issues with Relax-and-Recover" in https://en.opensuse.org/SDB:Disaster_Recovery