Just curious how people are backing up their smoke.
Our tendency is to archive anything that we think might came back, and not everything we do. We've been talking about archiving the project.db files on a nightly basis, but am curious if there's enough info in there to rebuild a timeline.
This is about smoke on linux, but would be curious to hear if anyone is running Time Machine to back up smoke on mac.
I don't know whether you have a older 9400/9500 or the newer Z800 HP computer, but my suggestion is to buy a ESATA sled and install it in one of the empty slots in your computer, with a mounting point in LINuX. If you have phone support the people in Montreal can help you set-up a pathway. Once you've got it setup (hardware/software wise), you can slide in a 500GG or 1TB drive that you can buy online, format it for LINUX and archive away to that drive, and it writes and reads very fast. Admittedly, the drive formatting is a bit of a PITA, as it's not like clicking a software button like it is on a Mac.
I have also seen systems use an external sled and plug a drive into the rear USB port on the computer (I've been told the front usb2 port is slower), and archive that way, but it's painstakingly slow (read/write). I know LT04 tapes are also used, but I have no experience with Tape backups.
I even know a fellow "Smoker" that had his company buy a 12 or 24 TB Rourke Galaxy RAID (in addition to the RAID he uses for current job footage), that he uses as a "temporary" archive RAID. It seems an expensive way to go to me, and you wouldn't exactly want to use that for jobs that aren't coming back for a while IMHO.
I'd like to hear how others deal with Archiving/Restoring projects as well, as it has been my experience that it is something that is often overlooked by the non-technical people in Post Production, in that they're always wanting to put more work through a room (or rooms), but don't allow for time to Archive and/or Restore projects. Most likely because it's not directly billable, although I think it should be (maybe a line item cost of "storage" for future revisions of the clients work?
Well, that's my 2cents, as I have time to kill while commuting to my session. I'm getting "I-phone thumbs"
I have my fire retardant suite on, so flame away (pun intended). -TomT
PS. ARCHIVE EVERYTHING! The job you don't archive is always the one that will need an emergency revision!
First off, I always work with History on.
When I archive I simple unrender my timeline and archive just the final edit sequence. This edit has history so all of my clips are present as well as all of my setups.
My video clips mostly come form P2 on USB hard drives and are linked via Gateway. So I do a Linked Archive that will save the clip metadata, but not the clip and any new material I made in a module Action will get archived. This keeps my archives small for 1080 :30 spots. They end up anywhere from 1 gig to 80 gigs. Our P2 USB drives have backups with the same folder structure. But if you don't care about archive size, then archive as STONE and all of the clips that are linked will be "stored local" and then archived. So that archive will have all clips.
I have never had an issue with archiving or loosing a setup in history.
IF you entire framestore dies.. which just happened to me, there is all kinds of useful metadata in /usr/discreet/project and /usr/discreet/clip... this is where history is saved and the clip pointers. With this info and the project intact, you can relink you media, and reprocess effects through history.
That's how I do it.
Senior Editor - Autodesk Smoke
WTHR-TV Indianapolis,IN, USA