Similar to what other have said it could probably work, but you need though is volumes and settings where things never get purged.
A better option IMHO is LTFS
https://github.com/LinearTapeFileSystem/ltfs/wiki/ltfs
This basically lets you fuse mount a tape and write to it like a disk you can eject. Downside you have no catalog of waht files are on what tape. Upside nothing gets pruned and when you mount the tape you can just ‘ls’ or ‘find’ your hearts content. This is popular in media where you often have single things like 4k raw that are huge so a whole tape might be ‘one thing’.
At my day job we use IBM Spectrum Archive which uses LTFS + DMAPI + GPFS.
LTFS does the open layout on the tape, DMAPI
https://en.wikipedia.org/wiki/DMAPI supported on GPFS (a parallel filesystem)
Let us ’stub’ files. That is we wrote them to a tape, the inode has in an extended attribute a pointer to the file on tape. So you can ls in the directory and a file might say it’s 10GB, but if you use ‘du’ it says it’s 2MBytes. If you try to read it Specturm Archive triggered by a DMAPI event tells our pair of TS4500 libraries what tape to mount and it reads it back to disk.
In our case we have 26,000TB on tape (x2 replicated) front ended by a 2PB (x2 replicated) cache filesystem.
So in this case the filesystem is the database/catalog and automates getting files back. Effectively turns tape into a NAS.
IMHO use HSM systems like this for archive, use backup systems for recovery. Each can kinda do the other but it’s often not done that well.
If your small scale the open source LTFS + text file is probably enough.
Brock Palen
bro...@mlds-networks.com
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting
> To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/0b75a0ba0766212f5ca37554512513d90d66ae1d.camel%40gmail.com.