How OSVault works with multiple libraries

So, the upcoming 4.20 release of OSVault is planned to support multiple ASACA or DISC Blu-Ray libraries attached to a single server. Some people have had questions about how this will work.

If you have two or more Blu-Ray libraries attached to a single OSVault server, the software will store files on optical media, by default, starting with the first slot of the first library. The libraries are named during installation as library1 or library2.

If you wish to store files on optical media in a different order than this, you can setup "Volume Groups" in the libraries. Each piece of media can belong to the default Volume Group 0, or you can put pieces of media in different Volume Groups. Volume Groups have names you create,
such as "HD Video", "SD Video", "Post Edit", etc.

For example, you could put the first 100 pieces of media in library1 into a volume group called "Post Edit", and the second 100 pieces of media in library1 in a group called "Production", and put the last 100 pieces of media in both libraries in a Volume Group of 200 pieces called "Backup Files". The grouping is very flexible and can be changed at any time.

When you store files in the OSVault server, all files reside in a single name space with subdirectories. OSVault moves individual files to optical media and preserves the naming on the optical media. When a file is migrated (copied) to optical media, the migration command is
scheduled to run on a Volume Group. After a file is migrated it is then purged to free up more hard disk space, but the file still exists on the hard disk but its data space is not there. If you then try to read that file later, the OSVault server will copy the file data back to hard disk space in the same location it was originally. There is a database file on the OSVault server called "archive.files" which keeps track of this mapping of file name to optical location. There is a copy of that database mapping contained in the file name entry on the hard disk, also.