Johannes Meixner

Did you try out the example of COPY_AS_IS_EXCLUDE_TSM that could reduce much what TSM needs inside the ReaR recovery system? This COPY_AS_IS_EXCLUDE_TSM example is shown in default.conf in our GitHub...

I assume it is solved because "no news is good news". (If not, reopen it with additional information.)

@StefanFromMunich I am not a Oracle Linux user so I cannot actually help with issues that seem to be specific for Oracle Linux. In general support here at ReaR upstream...

Whoops! I falsely thought it is about Red Hat but actually it is Oracle Linux Server. So @StefanFromMunich when you have an Oracle Linux Server support contract you may better...

@StefanFromMunich FYI regarding ``` We are therefore planning to replace the two SATA disks from the original computer with two new SATA disks. We then want to perform a disaster...

@ramzcode see in usr/share/rear/conf/default.conf the section about ``` Write-protection during "rear recover" for OUTPUT=USB and OUTPUT=RAWDISK ``` for ReaR 2.7 online at https://github.com/rear/rear/blob/rear-2.7/usr/share/rear/conf/default.conf#L566 In the ReaR recovery system you find...

@ramzcode I don't know how such disk IDs can be same on different VMs, except it is actually the same disk that is assigned to different VMs. In particular when...

I cannot guess what actually goes on on your systems so I need ReaR debug log files: One from "rear -D mkrescue/mkbackup" and one from "rear -D recover" plus two...

Regarding using 'SERIAL' see https://github.com/rear/rear/pull/2703#issuecomment-961845716

By the way: It is WRITE_PROTECTED_ID_TYPES not WRITE_PROTECTED_IDS_TYPE