ERROR: Archive not found on [rear-client@192.168.100.161:rear-client_default/]

[mjhgthb]

• Issue type (Bug / Question / Feature Request / Others?): Question

• Brief description of the issue: I boot a vm from the rescue ISO, as generated by the drlm backup. On the drlm server, I updated the rear-client with the temp VM IP and MAC address ( drlm modclient -i a.b.c.d -M 00:50:56:9e:65:38 -c rear-client) and confirm with (drlm listclient) They are all in the same subnet, no firewalling.

After that I want to "rear recover" in the ISO DR environment to create a clone of my (still running) original rear-client, but I says:

2023-01-30 12:07:17.571387106 ERROR: Archive not found on [rear-client@192.168.100.161:rear-client_default/] Full rear-client log attached here as well.

• Work-around, if any: Not sure..?

• DRLM version (/usr/sbin/drlm -V): Disaster Recovery Linux Manager 2.4.9-git / 2022-12-05

• OS version (cat /etc/drlm/os.conf or lsb_release -a): SLES9.1

• DRLM configuration files output:

  • cat /etc/drlm/local.conf NFS_SVC_NAME="nfs-server" DRLM_INCREMENTAL="yes" DRLM_INCREMENTAL_HIST=6

  • cat /etc/drlm/clients/client_name.cfg all commented out

• DRLM error reporting configuration output (if applicable):

  • more /etc/drlm/alerts/.cfg more: cannot open /etc/drlm/alerts/.cfg: No such file or directory

• Output of:

  • drlm listclient -c client_name Id Name MacAddres Ip Client OS ReaR Version Network Scheduled 100 rear-client 5254009df309 192.168.100.214 RedHat 9.1 2.6/2020-06-17 ens3 true

  • drlm listnetwork -A Id Name Status Server IP Mask Network Ip Broadcast Gateway Interface 1 ens3 disabled 192.168.100.161 255.255.255.0 192.168.100.0 192.168.100.255 ens3

DRLM Client information:

• ReaR version (/usr/sbin/rear -V): 2.6

• OS version (cat /etc/rear/os.conf or lsb_release -a): RHEL9.1

• ReaR configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf): [root@rear-client ~]# cat /etc/rear/local.conf DRLM_MANAGED=y DRLM_SERVER=drlm-server DRLM_ID=rear-client DRLM_REST_OPTS="-H Authorization:$(cat /etc/rear/drlm.token) --capath /etc/rear/cert"

• Hardware platform (uname -i): x86_64

  • In case of i386/i686 or x86_64 platforms, BIOS or UEFI? BIOS

rear-rear-client.log

[proura]

Hi @mjhgthb ,

Nice to see that you are testing DRLM!!!

First of all, in the rescue console can you verify that the client's IP is the new client IP "a.b.c.d"? if not, DRLM will deny access to the files. You can change it manually with the next commands:

ip addr del 192.168.100.161/24 dev ens3  
ip addr add a.b.c.d/24 dev ens3 

[mjhgthb]

Yes the address was correct, but now, trying REAR-only to an smb server, I'm having similar problems. I looks as there is something strange going on inside my test kvm server. No firewalling I can see, but filtering DOES seem to be happening. Moving over to a different test environment now. Please ignore this ticket, it's probably related to the KVM setup here. Many apologies for disturbing.