[Edit: Added that this copy has 28 restore points]
Doing all sorts of testing heading towards my "grand plan" of bullet-proof backups (backups & copies as well as tape copies across 2 sites).
I have a backup copy (2tb full, 28 restore points) to our second site and wanted to test sending that to tape at that site as well - If I can get tape working as I want to at both ends then we can get rid of our Iron Mountain contract that costs us thousands of £/year.
As it's a first run it's creating a Synthetic Full but it seems to be taking far longer than I expected even to just get started. (I'd have thought that as it's a backup copy/reverse incremental it would have just dumped the most recent .VBK file to tape to start with?).
At this point it has been running for 1.5hrs and generated a .VSB file of 4.17Gb (so far) but nothing has started writing to tape as yet but, more importantly, there's absolutely no indication whatsoever of progress, e.g. I don't know if it's going through each .VIB in sequence and, if so, how far in it has got so far (I might have a dig around the current log file to see if there's any info in there).
So, I know things can vary greatly based on hardware but is there a ball-park timescale I can consider?
Using V8 Patch 2 (3 going in this week, v9 on the cards). Tape server is physical, this particular repository is 4 x 4TB SAS in RAID-5 (potentially moving to a 12-disk FC array).
Once it actually gets going I expect performance to be pretty decent, we can max out our LTO-6 drive reading from these disks but I do appreciate that there are lots of IOPS associated with a synth full, it'd just be VERY useful to have a vague clue as to real-world progress...
[New Sig: PLEASE get GFS tape support for incrementals!!!]