Kenn Michael
Well-known member
- Joined
- Dec 28, 2006
- Messages
- 708
- Reaction score
- 0
- Points
- 0
So I've had my 3A unit for a few months now... thanks to all the great responses to my thread here - LTO-3 Still the Way to Go?
Loving the drive and the workflow.
2 Questions:
I'm using Transmit as my FTP app to access the drive, and while it works great, I get server timeout errors if the time it takes for Transmit to send a command to the drive's server till the time it takes the drive to shuttle to the correct spot on the tape.
For example. I have a tape that is half filled and I want to write some data to the next available space. I load the tape in, Transmit connects and I drag a file onto the drive. Transmit waits. The drive shuttles. Finally, when the drive gets to the right spot, Transmit basically says - the server took too long and forget it now. If I drag the file onto the drive at this point, the drive writes it as expected due to the tape being in the right place.
This is probably a Transmit issue, but I was wondering which FTP clients you guys are using with your drives. The same thing happens with pulling files off the tape, and even though I haven't had to do an R3D conform using the drive, I've had situations where pulling shots from non-consecutive parts of the tape completely ruined the automatic process because of the client complaining about server timeouts.
Secondly, I would love it if writing a file to tape didn't change the file created/modified information to the date/time that it was written to tape. Is there any slick way around this save for putting files in .zip or .tar archives before writing to tape?
Thanks!
Loving the drive and the workflow.
2 Questions:
I'm using Transmit as my FTP app to access the drive, and while it works great, I get server timeout errors if the time it takes for Transmit to send a command to the drive's server till the time it takes the drive to shuttle to the correct spot on the tape.
For example. I have a tape that is half filled and I want to write some data to the next available space. I load the tape in, Transmit connects and I drag a file onto the drive. Transmit waits. The drive shuttles. Finally, when the drive gets to the right spot, Transmit basically says - the server took too long and forget it now. If I drag the file onto the drive at this point, the drive writes it as expected due to the tape being in the right place.
This is probably a Transmit issue, but I was wondering which FTP clients you guys are using with your drives. The same thing happens with pulling files off the tape, and even though I haven't had to do an R3D conform using the drive, I've had situations where pulling shots from non-consecutive parts of the tape completely ruined the automatic process because of the client complaining about server timeouts.
Secondly, I would love it if writing a file to tape didn't change the file created/modified information to the date/time that it was written to tape. Is there any slick way around this save for putting files in .zip or .tar archives before writing to tape?
Thanks!
