hi,
i have tape backup job mapped with multiple source jobs. tape job runs longer. during this time source jobs runs.
now tape jobs taking that particular source job goes pending state. and after another source job finishes within same tape job then it start original again.
it shows changes in source backup files detected and it shows double source vbk files. earlier it was say 20 then it shows not 40. so it is taking all backup again to tape. i need only one full backup files for monthly tape backup. why this happens.
i have tape job with standard media full. and in tape job only latest backup chain is selected.
07329969
-
nmp1027
- Lurker
- Posts: 1
- Liked: never
- Joined: Sep 07, 2024 6:20 pm
- Full Name: nmp
- Contact:
-
david.domask
- Veeam Software
- Posts: 2590
- Liked: 606 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: tape backup job
Hi nmp, welcome to the forums.
> i need only one full backup files for monthly tape backup. why this happens.
May I ask, why not use GFS Media Pools with the Monthly Media Set?
Backup to Tape will process all data for a given source job based on the settings you use, but it will try to ensure all backups that meet the minimum requirements based on your configuration are put to tape.
With Tape GFS, you will be able to set a specific day for your Monthly backup to tape and regardless of whether the source job produces a Full or Incremental point, a Full backup will be placed to tape with GFS Media Pools.
I can see that Support had reviewed and explained the behavior within the case (the source jobs produced new fulls while the tape job was running); by design, if the source job added to a Backup to Tape job changes prior to the tape task completing, the tape job will re-queue the task to check the changes and see if the new backups should be put to tape based on the job settings. Only unfinished tasks in the tape job will follow this behavior (i.e., if a source job has already been copied to tape during a job session and then the tape job notices that some tasks require a retry due to new backups, only tasks that have not finished will be queued to check for new backups).
Tape GFS does not have this issue as it will only try to find the restore point that best matches the time period you set for the GFS date.
Consider Tape GFS with the Monthly Media Set enabled, I think this will meet your requirements. Thanks!
> i need only one full backup files for monthly tape backup. why this happens.
May I ask, why not use GFS Media Pools with the Monthly Media Set?
Backup to Tape will process all data for a given source job based on the settings you use, but it will try to ensure all backups that meet the minimum requirements based on your configuration are put to tape.
With Tape GFS, you will be able to set a specific day for your Monthly backup to tape and regardless of whether the source job produces a Full or Incremental point, a Full backup will be placed to tape with GFS Media Pools.
I can see that Support had reviewed and explained the behavior within the case (the source jobs produced new fulls while the tape job was running); by design, if the source job added to a Backup to Tape job changes prior to the tape task completing, the tape job will re-queue the task to check the changes and see if the new backups should be put to tape based on the job settings. Only unfinished tasks in the tape job will follow this behavior (i.e., if a source job has already been copied to tape during a job session and then the tape job notices that some tasks require a retry due to new backups, only tasks that have not finished will be queued to check for new backups).
Tape GFS does not have this issue as it will only try to find the restore point that best matches the time period you set for the GFS date.
Consider Tape GFS with the Monthly Media Set enabled, I think this will meet your requirements. Thanks!
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: No registered users and 131 guests