Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Near NYC
  • Interests
    TV Production and backing up the files from said TV production.

rogerwilcoprod's Achievements


Newbie (1/14)



  1. That's a very good point and all of this is making me start to wonder just how much the guy who set up this whole system really knew about Retrospect and Avid ISIS and how they work together... Regardless, I'll try to remember to update this once our new system is here and set up in the hope that it might help someone else in this situation. With any luck it'll work just fine and I'll have ended up wasting my time with this.... Well, I guess it's not wasting time, but at least I'll have some answers.
  2. That's what I would think too, that there shouldn't be any reason it wouldn't see the network shared drives. The only issue right now is that I don't have a spare system at this moment, but I will actually have one soon so I should be able to test this out by the middle of next week at the latest. I'm thinking maybe when whoever set up the system in the first place tried version 8 of Retrospect they had some issue with it, but maybe it was a bug in an early version of it that was fixed (maybe it affected more than just ISIS servers, but that's the only server we use Retrospect with), but no one realized that because no one bothered trying to upgrade to the newer version. I dunno. But the good news we'll have another system that can handle LTFS on its own by the end of the week, without using Retrospect, and then sometime next week I'll see what happens when I try installing the demo of the latest version of Retrospect and, if anything goes wrong I'll just uninstall it and reinstall 7.7.
  3. Our current LTO drive is setup as a conventional tape drive, although looking at it from a budgetary point of view it might make sense now to get the EzPrep bundle from 1Beyond since it should come in slightly cheaper over the course of a single season of the show so that's what we may end up doing. I do not currently have LTFS drivers installed for the drive we already have (I take it that's a good thing?) so this will be my first foray into the world of LTFS.
  4. The thing is, we have 7.7 installed now and I have been hesitant to upgrade because we're in the middle of backing some things up (of course it had to be when I need to figure this all out), but I don't know what might have changed between 7.7 and any later version that would affect the software's ability to see the shared drives. I mean, I wouldn't think anything would change that because I assume it's accessing everything on a system level and Windows has no problem seeing the drives, but the guy who configured the system (I wasn't around for that, unfortunately) claimed that version 8 wasn't able to see them (something to that effect). Thanks for the link, I will take a look at that. The reason I am hoping to use LTFS isn't for backup sets but actually to just copy files onto the LTO tape in a specific folder structure to use in delivering a show to a network that recently began accepting delivery using LTO/LTFS.
  5. We're a video production company and I'm trying to figure out why no version of Retrospect later than 7.7 can see the drives on our Avid ISIS server (running version 3.1.x with the ISIS client running 3.1.0.x). The reason for this is that we now have the option to deliver our show masters on LTO, but only using LTFS which we can't do with 7.7 and I don't think you can have 7.7 and another version installed at the same time (although if I'm wrong, please do correct me). I know our LTO drive can write LTFS, but when we've tried to install a newer version of Retrospect it no longer sees the drive shares that 7.7 sees. I know this is probably a really obscure topic and I am well aware that our server is not running the latest and greatest version of ISIS, but that's due to the ridiculous cost (something like $18k) to get it upgraded, plus we'd have to upgrade our edit systems, it'd just be a whole thing and we can't do it right now as we're in the middle of post on a show and are on a tight delivery schedule. Plus, our setup (server, edit systems, backup computer with Retrospect) seems to get very finicky whenever we change something so I'm hoping there is a way to write to LTFS, ideally using Retrospect, but not have to upgrade anything else in the whole network. If anyone has any advice, ideas, thoughts, suggestions, etc, I would be very, very grateful.
  6. If that's the problem then I suppose that would explain it, but I'm seeing this happen with backups that were made in 2012, well before I saw any other signs of problems with the heads in the old LTO 5 drive. Would that lead you to believe it may be another issue? Since my original post we've had one backup work as it should as a Normal Backup but two others that we had to run as recycle backups. I'm going to try the offsite version of the one that worked as a normal backup later today, but apparently those two backups were created at different times and as such have different amounts of data on them to begin with, so I don't know if it will really be a fair comparison in terms of whether or not it works.
  7. I should preface this by saying that we can't upgrade to a newer version of Retrospect until we upgrade our server as we're running the latest version that it compatible with our server software (Avid Isis 3.1.x) so we're stuck on 7.7 for the immediate future. Our LTO 5 drive (HP Ultrium 3000 SAS) was giving us increasingly more issues, really slow backups and the end result of all my research was that it appeared the tape heads were giving out so we ended up buying a new LTO 6 drive (HP Ultrium 6250 SAS) which has worked great for new backups on the LTO 5 tapes we have left. The problem that we're running into is that when we try to do a normal backup onto a tape that was initially written by the old drive the new one asks for a new tape, even though there should be plenty of space left on the tape. So if I do a recycle backup it works fine and doesn't require a second tape, but if this is going to happen for all of the old backups then we're going to spend a great deal more time on this than I'd like. When I tried the last one I clicked on the properties of the tape itself and Retrospect showed a media error on the tape I was trying to use for the normal backup, although the logs from when that backup was first created didn't show any errors. Is this a common problem going from a tape written by an LTO 5 drive to trying to write on the same tape with an LTO 6 drive? Or have we just been unlucky in the 2 or 3 that we've tried this with so far? Sorry if that was rambling on a bit, I just wanted to be as clear about the situation as I could. I'm hoping that we'll upgrade our server later this year and then be able to use the newest version of Retrospect but until then I have to find a way to make our current configuration work.
  • Create New...