vRanger tried to back up disks that were not selected to be included in the backup job instead of the disks that were selected.
原因
When vRanger makes the call to VMware to get snapshots of certain disks on a VM the incorrect disks get presented to vRanger. This can happen on a VM that has multiple disks but you only want to backup only a certain disk or disks, so through the vRanger console you only select certain drives to be backed up. There is a chance that when the snapshots are requested VMware can transpose the disk selection and attempt to perform backups on the wrong disks.
解决办法
If there are disks on a VM that you do not desire to have backed up you can present those disks as independent (or RDM) to the VM, this will prevent VMware from taking a snapshot of the .vmdk and thus preventing a backup from taking place. In this situation within vRanger you would select all drives to be backed up on the VM, however once VMware tries to take a snapshot of the disks that are independent those disks will fail but the others will still succeed. In this approach you take the factor of chance out of the equation, so when vRanger makes the API call to VMware to get a snapshot taken it is requests all drives initially however since it can't even take snapshot of certain disks they will not be affected.