Ponnurangam H
Ponnurangam H
@jsmeix Ya,it makes sense, But can we use just the SERIAL as the validator, hope this can never be the same ? What is your thought and BTW i tried...
Yep, sorry my bad, typo mistake here. let me get the logs and outputs for debug
@jsmeix Please find the details and if you need more info on the debug log let me know Source VM output ``` [root@ip-172-31-23-140 rearuser]# lsblk -ipo KNAME,LABEL,UUID,PTUUID,PARTUUID,SERIAL,WWN /dev/nvme0n1 KNAME LABEL...
@jsmeix Any idea on what is wrong from the above logs ?
uuidgen - This is creating a Write protection, but not sure how this is same or wrongly evaluated on the target VM as well
RCA: "For Unknown Reasons, the disk UUID between different VM's are same. This makes ReaR to declare a different new disk as a source and make it RO" ++++ [[...
AWS uses Unique ID's to maintain stability for storage devices across types, Due to this, ReaR thinks that it should not use the disk as the WRITE PROTECT script validation...
@schlomo Yes this is only needed for AWS Environment, may be for other CSP too, it still depends on the how they maintain the disk ID's for consistency. The ID...
@pcahyna The reason is AWS maintains a unique ID for disk types and FS to make sure it never changes when someone upgrade their instance and move from one region...
> This is interesting, I would like to help with the testing and validate it more.