@ddubois , I'm not sure I understand what you're saying. However, I'll give it a go:
- Split your large backup copy job (yes?) into two backup copy jobs; one for critical/high priority VMs (runs daily) and the other backup copy job will be run weekly.
- Schedule your daily backup copy job to copy every one day with whatever start time you want, e.g., 11:00 PM.
- Schedule your weekly backup job to copy every 7 days with whatever start time you'd like, e.g., 3:30 AM.
If you decide to go this route, I would highly recommend that you have a firm grasp on how much data is being copied on every backup copy job run and how long it takes to complete. This information will help you determine when run the weekly backup copy job. The hope here is that you avoid resource contention on your repository as much as possible.
You may find that you may have to experiment, if possible, to find out what works best for you.