I have used shared disk libraries in a very asynchronous manner to move backups around on portable media. This works very well.
I am looking to create a shared library that can be active on multiple media agents at once.
There is plenty of documentation for configuring same but what I want to understand is the matter of *CONCURRENT* access via different media agents.
Shared libraries are managed by creating mount paths to the same storage on different MAs. THis is at the FS level and thus concurrency requires distributed file locking of some sort (as well as both MAs having the ability to read that FS)
I imagine I could use NFS although I would still need a coordination process between all elements to ensure the scheduling of IO is sane. Will an NFS-based library work this way? Context : I may not be able to use NFS here, hence the following questions.
But does Simpana have some sort of native ability to manage concurrent access to the same storage?
What about third party clustered FS?
I see a licence option called shared storage. I am not sure what this is. Note : I am NOT talking about clustered media agents (though that is an interesting sub-topic in itself)
Or does Simpana simply enforce serialised access to shared storage, as for tape drives?