R1Soft Backups failing

PeteS

Well-Known Member
Jun 8, 2017
237
48
28
Oregon
cPanel Access Level
Root Administrator
Hello,

My r1soft backup began failing after recent YUM updates. At first I thought all of this was due to the 66.0.19 cPanel update, but the kernel update coincided with that and seems to be the cause. FYI I was not yet on 7.4 when all this happened, I was still on 7.3.

Aany further details would be welcome.
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,908
2,216
463
Hello,

Can you provide some more details about what in-particular is failing? Do you notice any specific error messages? Have you reported the issue to R1Soft's support team?

Thank you.
 

PeteS

Well-Known Member
Jun 8, 2017
237
48
28
Oregon
cPanel Access Level
Root Administrator
Here is the error report:

9/16/17 11:36:56 AM Manager Failed backup of LVM configuration
9/16/17 11:36:56 AM Manager Failed to execute command 'lvm.static pvs -o pv_fmt,pv_uuid,dev_size,pv_name,pv_mda_free,pv_mda_size,pv_all,seg_all,pvseg_all,vg_all,lv_all --nameprefixes --noheadings --units b --nosuffix --unquoted'
9/16/17 11:36:56 AM An exception occurred during the request. The replication driver was not detected (detail: Could not find a suitable hcpdriver module for your system; Please run "r1soft-setup --get-module " on your Agent to install one. ).

R1soft said:

"The issue which you are able to find it is due to older version of LVM do not understand this and fail.

If you use the configuration file from lvm2 >= 2.02.171 with any earlier lvm, all lvm utilities break with the error: Invalid units specification
The lvm.conf gets loaded into memory at initialization time. Only editing the file does not change the behavior. Commenting or editing that one line and rebooting resolves the issue.
# Default value for --units argument.
============
units = "r"
============
This happens because lvm.conf contains a new value: ( Used to default to "h" )"

All had been working, so I know the driver module was installed, and the LVM config file was ok. Neither I, nor my data center admins can determine why something changed, but the solution was to edit the LVM file and reinstall the backup driver (which required a role-back to the kernel because the modules required to install the backup agent's drivers were dependent on specific headers within an older kernel).

The issue has been resolved, but no one can determine the cause of this. I'm leaning toward the kernel update at this point.