Better support for GRT on B2D

I have always had lots of problems with B2D devices filling up during GRT backups. I understand what the "Recommendations for using backup-to-disk folders with backup jobs that use Granular Recovery Technology" Help file article is telling me, and comply to the extent I can, but all the Help article really does is somewhat improve the odds that I won't run out of disk space. Nearly all Backup Exec Options include GRT, so in environments where many Options are used, GRT is a part of most of them, so dedicating B2D devices to GRT jobs doesn't help much. The biggest problem is that since B2D files are never deleted, only overwritten as space is needed, it's nearly impossible to make sure enough space is available for IMG folders.

1. I don't know how BEWS decides where to put the IMG folders, but it looks like they are at least usually placed on the same disk as the corresponding B2D files. I'd like to be able to designate a B2D device EXCLUSIVELY for IMG folders. Then it will be more clear when I need to add more space for them, and it will ensure that the space is not taken up by B2D files. GRT devices would represent a single OS folder on one OS partition, and could not be combined into Device Sets.

2. If the IMG portion of a GRT backup job is directed to a GRT B2D device as described above, BEWS can then prune the oldest remaining Overwritable IMG folders belonging to the same Selection List if space runs out during a GRT backup. Or if that's not possible for some reason, then do it before the backup begins. That would bring the odds to close to 100% that the backup will complete.