Final answer:
The problem with the backup is most likely because some of the virtual machines are still on ESX 3.5 hosts.The most likely cause of this backup issue is option D: Some of the virtual machines are on the ESX 3.5 hosts.
Step-by-step explanation:
vSphere Data Recovery (VDR) does not support backups for ESX 3.5 hosts and only works with ESX/ESXi 4.0 and later versions.
So, despite the scheduled backup, any virtual machine that is still on an ESX 3.5 host will not be backed up until it is upgraded to a later version compatible with vSphere.
Options A, B, and C might influence backups, but are not as likely to cause this issue as option D. Generally, VDR supports most commonly used operating systems, can backup virtual machines despite them being on, and does not require a specific agent installed on each virtual machine.
Learn more about ESX 3.5 Host Backup Issues