Thanks Tom. I thought that exact same thing so I completely broomed the VTAPE so there were no other files in the transfer and got the same bad result regardless of what files I used as the source. And looking back through the transfer logs I can see that what it’s doing is actually transferring the same files over and over again. The 136G on the tape is those same 5 files transferring over and over again. I ran multiple tests yesterday with different files and got the same “5x loop”result every time.
After doing 5 duplicates of the VTAPE it does seem to stop the loop but if I add another file to the VTAPE, it transfers that one file and then starts the endless loop on all the files on the VTAPE again. The only way I could get it to just transfer once is to bypass the VTAPE, mount a network drive directly in the source window and then transfer from there. The problem with that path is that it’s excruciatingly slow.
The problem started in v2.0.22 and I was hoping the jump to 2.1.17 I did would do the trick but no dice. Not sure how the cache-a handles indexing the files & tapes etc but I’d be totally game to do a complete factory reset if I could figure out how. I don’t really need any logs of what I’ve previously archived (that data is stored in my catDV system). I’m also totally game to try and update to v3 if that’d fix the problem. Right now the cache-a is only good as a door stop.
Thanks!