I'd recommend you to review existing discussion about How often do i need a full backup?
Also, you can use SureBackup
for recoverability testing.
Regarding monthly job:
Why do you want to keep monthly rollbacks instead of full backups? I assume this related to storage space economy?
Regarding advantages of BCJ:
Let's say your primary full backup became corrupted, in this case the chain of rollbacks related to this full is unusable, so you will be able to restore from the last Friday full (data loss of 1 week).
Your second backup job can offer you only 1 restore point around 1 month ago (data loss from 2 to 4 weeks).
The Backup copy job will create a separate backup chain without impact on the source VMs as it copies data from the source repository, and in case of corruption on primary chain you will be able to restore with the most recent state of VMs.
Also, GFS retention will help to keep full backups monthly if you set it up.
SteveHeller wrote:So this means when I schedule an active full in a reverse incremental job that this active full will stay an active full until the retention policy deletes it, right?