Duplicate to cloud from a Backup set should disable Verify by default
I've begun experimenting with duplicating disk backup sets to AWS. I've already found that if you verify the backup set, you incur an egress cost, and understand that it's recommended that such duplicates not be verified (anyway, they were already verified when duplicated to disk). If you add a duplicate-to-cloud stage to a scheduled job, verification is disabled by default. This makes sense. However, I've found when you create a duplicate-to-cloud job from a backup set (right-click on the backup set and select Duplicate from the menu), verify is enabled by default. It shouldn't be hard for the wizard to detect if the Verify setting was changed manually when the storage type is selected, and if it wasn't changed, update its state to the correct default behavior.Virtual based backup should not show retired hypervisor / VSphere server
When creating a virtual-based backup for a VM, Backup Exec prompts you for the hypervisor host or management (e.g.vSphere) server to run the backup through. However, the list contains all existing and former hypervisor servers, including retired ones. Retired servers are generally not available for doing backups. That's the reason for retiring them. So, this list should contain only active servers. Since "Retired servers" is a builtin server group in Backup Exec, it shouldn't be that hard to verify whether the hypervisor is in this group or not before putting it in the list.