sry but exactly this is not described in the user guide, i read it many times.
Again the problem, hopefully a little bit easier shown:
Backup_Job 1 - Forward Inkr. with Active Fulls on Monday -> 14 RP -> daily running
Backup_Job 2 - Forward Inkr. with Active Fulls on Tuesday -> 14 RP -> daily running
Backup_Job 3 - Forward Inkr. with Active Fulls on Wednesday -> 14 RP -> daily running .... and so on
-> they all are in the SAME
Backup to Tape Job with one Media Pool (...always continue using crurrent media set, Protect Data for 8 Weeks)
-> Full and Incrementals stored in the same Media Pool
-> this Job runs after the daily Backup_Jobs X
So all the vbk's and vib's are stored for 8 weeks on tape, thats fine, but after 8 weeks when the first tapes expiring, they contain vkb's and all the following tapes, that are not expired until now, containing vib's which i dont get recovered because they need the depending vbk's! There is no check or Logic whether the vbk is still needed or not
- it will be hard expired on deadline.I thought it was the same Logic as on B2D
where a vbk never expire (or will be deleted) in a CHAIN - but isn't it??
In brief: all files erased from the tape but left in repository will be copied to tapes again during the next run of tape job.
So i have 14 RP (Corresponds to 2 weeks) on B2D
and 8 Weeks on Tape
- the tape job cannot copy the missing files and also its not the problem...