Summary
This is major number issue. Major number used by KVM is in conflict with host's LVM major number.
Symptoms
The following condition may be encountered with Linux KVM but not only, the backup job log could contain errors such as:SNBSNP3069E 9704: Failed to seek device /dev/: Invalid argument
SNBSNP3069E 9704: SnapCMInterface::backup_apps:backup_apps( RC(-1)
SNBAPH_381E Exception in message (BACKUP_VSS) to module (sssnap), reqrc (-1)
SNBAPH_126E Func(backup_): Exception (AHException: <AHException.AHException instance at 1951124485> )
SNBSVH_990E APPH backup request failed with exception: An error occurred in BACKUP message processing. (rc = 21001).
SNBSVH_900X Exception: Application info not available
SNBSVH_926E Job definition resolution for node(smtp7-1) failed with exception: com.syncsort.bex.db.JobDefException: Application info not available
The snap module logs will also show the same errors:
SNBSNP3066D 9704: lvm_query succeeded, file_system_device_path = "/dev/"
SNBSNP3066D 9704: osrelease_D:check_minimum_os_release: Version release check passed, requested 2.6.16.54-0.2.4, found 3.10.0-514.21.1.el7.x86_64
SNBSNP3066D 9704: osrelease_D:check_minimum_os_release: Version release check passed, requested 3.10.0-327, found 3.10.0-514.21.1.el7.x86_64
SNBSNP3066D 9704: EVMS is not enabled
SNBSNP3069E 9704: Failed to seek device /dev/: Invalid argument
SNBSNP3069E 9704: SnapCMInterface::backup_apps:backup_apps( RC(-1)
SNBSNP3066D 9704: BACKUP_APPS: REQUEST_STATUS SOCK[1] RC[-1]
SNBSNP3066D 9704: Command TOK_VSS_BACKUP processed successfully
Output of lsblk can show a device with a Major number that is detected as LVM, however in reality it is not an LVM device.
Resolution
This issue has been corrected in DPX 4.5.1 for earlier versions please contact technical support and reference internal Jira DPSUST-3961 to acquire a hotfix for the snap module.