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.
