-
FCP X “Add SAN Location” to any shared storage system
Hi –
as a quick background, Jeff Kirkland has been doing this, but never shared until now. John Heagy of NFL Films discussed this with Jeremy Garchow in April 2013 on Creative Cow, but nothing ever came of it.I have been doing shared storage with FCP-X on the Maxx Digital Final Share system using Sparse Disk Images, as outlined by countless guru’s on the internet and YouTube. It works well, but is a little inconvenient. But it works. With most networks, and most shared storage systems, you simply can’t “Add SAN Location” unless you have Apple XSAN, or so I thought. Which is why, from the beginning of FCP-X, people said that you can’t have shared storage with FCP-X.
Well, you can.
In doing ongoing research, I found a little article by Amanda Burns of Florida Atlantic University, and how she is accomplishing this. Amanda told me today that she is using a NetApp SAN server, but this is unimportant. Any server will work that can support NFS. Maxx Digital Final Share is nothing more than a Mac OS X Server, and has NFS, hidden away.
As Jeff Kirkland has pointed out, Marcel Bresink has created a simple to use application called NFS Manager, that you can download from the internet. It costs $15 euros (I don’t know where the symbol for euros is on my US keyboard – sorry). So, once you have this little app, you can get NFS to work on your Mac server computer. This can be done manually without spending any money, using the terminal and some UNIX commands, but it’s cheap enough to get the Bresink app that Jeff Kirkland has shown in his post, to make things easy.
SO, this is all you do – on your shared drive volume, you manually create folders – one for each project that you want to work with. Wedding1, FeatureFilm7, etc. and in each one of these folders, you manually create TWO sub folders – one called Final Cut Projects, and one called Final Cut Events. So now imagine that you have your 300 projects, with 300 folders, all with folders inside them called “Final Cut Projects”, and “Final Cut Events”.
You have enabled the NFS network on your Mac server computer, and you have your big drive array hooked up to your Mac server computer (or whatever server you are using for your shared storage system).
On your client editing computer that is hooked up to the switch of the server you do this –
GO> Connect To Server>
and enter in the IP address box
nfs://192.168.2.3/volumes/MyBigSharedDriveArray
and your drive mounts on your desktop – just like on any little Mac network. No big deal. Except this time instead of using Apple AFP, you are using NFS.Go into FCP-X, highlight your Macintosh HD, and select ADD SAN LOCATION, and “low and behold”, the network shared volume appears.
Just like it should do in Apple AFP (or SMB) – but obviously Apple doesn’t want this to happen for some reason.So it’s not like Apple has to “fix” something, or invent something – it’s already there. As a matter of fact, NFS was a checkbox choice on older versions of server software, but Apple removed this. Now all you see is AFP and SMB. I wonder why ?
So now, all of a sudden, you can have easy to use shared storage with FCP-X without the aggravation of sparse disk images, and without the expense of specialty shared storage software that makes FCP-X work. Your only expense is 22 bucks to Marcel Bresink.
Amanda Burns at Florida Atlantic University – you are a very smart young lady. This forum sings your praises.
And thank you John Davidson, Mr. FCP-X, for helping me test this out. I am glad that it is working with my 10 Gig Ethernet system.
If anyone wants more of the little details on how to get this to work, feel free to contact me.
Bob Zelin
Bob Zelin
Rescue 1, Inc.
ma*****@****rr.com