Out of memory when recovering with ReaR

23 views

Skip to first unread message

Cookiefamily

unread,

Jun 14, 2019, 4:08:44 PM6/14/19

to bareos-users

Hello,

When recovering a Test-VM which I intentionally broke to recover it with Bareos and ReaR (first time testing the recovery process), the OOM-Killer kills the bareos-fd as well as other services and the restore aborts.
See https://paste.pics/73e7a398577b3f328d2daa01f5937f86 for a screenshot of the KVM.
This is the output of the bareos director: https://gist.github.com/MiningPickaxe/9079c61d60fc2abde7ad31c3ef1b5499 which obviously errors because the connection dies.

What might be interesting is the line "Error: lib/bsock_tcp.cc:417 Wrote 35 bytes to File Daemon:IP:9102, but only 0 accepted.", It seems like it doesn't even start copying files.

How I can reproduce this:

1. Boot from ReaR-ISO, choose "Recover test01"
2. login as root
3. execute rear recover
4. enter yes for automatic disk layout configuration

When "waiting for job to start" appears do the following on the bareos-director:
1. restore client=test01.FQDN.com-fd
2. select most recent backup
3. mark *

Verify the settings:
JobName: test01.FQDN.com-restore
Bootstrap: /var/lib/bareos/bareos-dir.restore.5.bsr
Where: /
Replace: Always
FileSet: UnixDefault
Backup Client: test01.FQDN.com-fd
Restore Client: test01.FQDN.com-fd
Format: Native
Storage: File
When: 2019-06-09 19:12:24
Catalog: MyCatalog
Priority: 1
Plugin Options: *None*

The VM is a KVM running on a Xeon E3-1270v6 with 1 core, 2gb of Ram (upped it to 4gb now because I ran into the OOM)