First i describe my jobs.
I got 6 Jobs where 1 Job is the configuration backup which is not a "real" job.
It goes like this:
Every Monday or ... or Friday start Job at 23:00: // normal mo-fr job, reverse incr.
Do Backup Hyper-V selected VMs (all selected) to Repository using reverse incremental and friday full.
Do Backup Repo to Tape
Every Tuesday or ... or Saturday start Job at 4:00 (its not monday, because of midnight..):
DO configuration backup (file->backup..) to repo
Every Tuesday or ... or Saturday start Job at 4:10 (its not monday, because of midnight..):
Do Tapejob Configuration from Repo to Tape
Every Tuesday or ... or Saturday start Job at 6:00
Do create new mediaset from mediapool monday-friday with retention 6d
manually there are 2 other jobs:
Every user-manual-start() DO // ABC JOB, full backup native
(not yet implemented by Veeam, because i cant run it before prejob) execute hyper-v vm batch on VM which checks SQL using exe file.
Prejob shutdown all VMs in the right reverse startup (by delay from hyper-v manager setting) order.
DO backup hyper-v VMs (all manual selected) to repo
postjob start hyper-v VMs in right startup order (by delay from hyper-v manager setting)
DO tape job for this repo to tape from medial pool ABC with retention 2 months, eject tape
//dunno what todo with mediaset, maybe i set it to create new every backup i think. does not matter anyway i think.
I think thats a detailed enough descr. of my jobs.
Now you see, i got the same data from ABC and mo-fr job. anyway it would be a pleasure to have the ABC job deleted right after its written to tape. much better would be a merge to the main mo-fr repo.
as friday should be a full backup and mo, tue, .. should be full (reverse), too. so its a waste of space.
Maybe i could remove the second (ABC) job and do a tape backup only, but then its not up2date because i run ABC at weekend and the other job on mo-fr.