You can easily install Archiware P5 backup and archive software on a Lumaforge Jellyfish storage server. Once you’ve done that you can backup to tape or disk or the cloud directly or through another P5 server. Backups are good. Archive are good. Restores are better.
P5 install on the Jellyfish (Linux) How-To:
Note: Thank you to Lumaforge’s CTO Eric Altman who gave me some basic instructions to get me going.
Step One: Download the latest Linux P5 rpm file
Copy the downloaded rpm file to the root folder of your SMB or NFS file share.
Step Two: Install the rpm file
Open Terminal and ssh into your Jellyfish. Login as root or as another appropriate user.
yum localinstall /mnt/Primary/ShareSMB/awpst554.rpm
Step Three: Browse to server on port 8000 to test that the server is up
Or in Terminal and ssh into your Jellyfish and ping your P5 server
cd /usr/local/aw ./ping-server Pinging PresStore application servers... lexxsrv pid: 4840 (server is running) lexxsrv url: http://127.0.1.1:8000/login Pinged 1 from 1 application servers.
Step Four: Decide if the Jellyfish storage will be a P5 client or a server.
Note: If configuring the Jellyfish storage as the main P5 server you may wish to set up a user that only has access to the shared volumes.
For my set up the Jellyfish storage is going to act as a P5 client to a main P5 server on a Mac mini (yes, they are useful for something). The Mac mini is this case is the P5 server and is attached to theOverland tape library via a Promise SANlink2 Thunderbolt Fibre Channel adapter.
Step Five: Set up the Jellyfish storage as a P5 client
Log into your P5 server and add the Jellyfish by the IP known to the P5 server. In this case the P5 server is connected via 1GB to the Jellyfish in Port 1.
Note: You could also choose to plug into the Jellyfish via a 10GB port, but in my setup these 10GB ports are reserved for the edit stations. You should choose what’s appropriate for your setup.
Resource utilization of P5 on the server is low, topping off generally at 1GB of RAM at peak usage. While this does technically take resources from ZFS caching, the impact should be super minimal.
In my observations the CPU never spiked too high while both serving NFS and SMB mount points to multiple Final Cut Pro X workstations even with backups or archive jobs going to tape at the same time.
More Jellyfish P5
See the follow up post on Archiving gotchas with the Jellyfish here
Pingback: P5 on the Jellyfish: Archiving Gotchas | DAM SAN
Pingback: Updating the P5 client on the Jellyfish | DAM SAN