Missing PVs in LVM configuration can make BMR backups fail (4036876)

Bare Metal Recover backups can fail if there are missing Physical Volumes in an LVM configured volume group. The backup errors will be similar to the following:

Information 2013/06/20 19:12:46 560 Data Plugin system-name Generating disk configuration information (may take a while) ...
Job Message 2013/06/20 19:12:53 560 Data Plugin system-name Finished with exit code 0
Information 2013/06/20 19:12:53 560 Data Plugin system-name ERROR: child process exited abnormally
Information 2013/06/20 19:12:53 560 Data Plugin system-name Cannot query physical volume attributes for wn.
Information 2013/06/20 19:12:53 560 Data Plugin system-name ERROR: Cannot create disk information file.

and

Error 2013/06/20 19:12:53 560 Data Plugin system-name System Image backup failed
Error 2013/06/20 19:12:53 560 Data Plugin system-name Failed to handle incomming msg from BB agent
Error 2013/06/20 19:12:53 560 Data Plugin system-name Failed to enter msg loop
Error 2013/06/20 19:12:53 560 Data Plugin system-name Failed to backup system images

When disks are removed from a system, usually via fdisk, but LVM is not updated to reflect this, a PV will display like:

[root@mgvm-centos57 ~]# pvdisplay | grep 'PV Name'
 Couldn't find device with uuid aPT6wU-Jysh-HahY-RbGz-2Wca-o11G-2LoS1o
 PV Name               /dev/sda2
 PV Name               unknown device

This will cause the the BMR backup to fail.

The Volume Group reporting the missing disk must be modified. This must be done by a Linux System Administrator. The general syntax of the required comamnd would be:

`vgreduce --removemissing --force [VG name]`