- Posts: 185
- Liked: 6 times
- Joined: Jul 25, 2018 4:12 pm
- Full Name: Poweruser
the second job (the tape job) sends out an e-mail, it had success backing up 0 files with 0 data..
what a success ;-)
i think thats an error. okay the job itself may have been run correctly, but there was no actual data to backup a full job AND the previous job throwed an error.
in case of previous job had an error, the tape job MUST send a warning out at least, that previous job had an error.
better send an error instead just a warning.
if you want a full job, it should send a warning. on an incremental it depents, but errors in previous job should at least start a warning.
another thing: during backup it seems that veeam keeps the latest restore point until the new one has been completed. so you get a low disk warning because veeam preserves 2 backups instead of 1during the job.
maybe you should be able to select "keep 0" on disk instead of at least 1. because if you do a tape job, you dont want to waste space afterwards.
- Product Manager
- Posts: 9782
- Liked: 774 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
Let's say your primary job has failed - you receive the failed job email notification anyway (it's more important to fix as you don't have a primary backup on your repository). Secondary job generate failed report only in case it cannot process the data created by primary jobs. Thanks.
Users browsing this forum: No registered users and 5 guests