by monstermania » Fri Dec 02, 2016 8:17 am people like this post
Hi fellow suffers, we are waiting for that feature a long, long time. The last times i've updated ASAP to new versions of B&R. And everytime we had some problems after the update. So, before i update to B&R 9.5 i wait a little bit longer. Can someone confirm that cleaning support now working as expected?
by mike.r » Thu Jan 05, 2017 6:51 am people like this post
Hi, after using b&r 9.5 for a while, I have this situation: Tape job used 8 tapes, after writing to tape 8 (last tape), the drive liked to be cleaned. B&R tape job recognized that, sent a tape alert to logfile and ended the job with a warning.
Result: Tape job ended succsessfully Drive still likes to be cleaned
This is kind of OK, but it would have been better, if b&R had put in the cleaning tape (after writing to tape8) and continue / end the job after cleaning.
by Dima P. » Thu Jan 19, 2017 4:53 pm people like this post
When enabled, cleaning check is performed at the beginning of every tape job. If cleaning tape is missing or locked, tape job will proceed. However, VBR logs a cleaning request and cleans the drive at the beginning of any tape job targeting this drive.
by BrendaS » Fri Feb 10, 2017 8:15 pm people like this post
What currently happens with a standalone tape drive when in the middle of a backup, the drive requests a cleaning.
Will the backup abort if I insert a cleaning tape when it requests the next tape ? Ideally, I'd like it to do a clean and then have it complain not a valid tape, insert a data tape and then continue on it's merry way when I insert the next tape in the sequence, but I'm not game to try it considering I'm ten tapes into a backup (yeah, I know I need a library, but we work with what we've got).
by DDIT » Mon Mar 20, 2017 9:30 am people like this post
I have been using the automated drive cleaning with Veeam 9.5 for a few weeks. Whilst it works well and save me the manual administration of cleaning the drive, it still marks the current tape job as 'warning'.
I understand this happens because the check for cleaning is done at the start of each job. Is there a reason why the cleaning check and actual cleaning cannot be done at the end of the job that reports it? And therefore finish as 'successful'.