Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a "tape drive" kind of Store #30

Open
pkgw opened this issue Jun 15, 2017 · 1 comment
Open

Implement a "tape drive" kind of Store #30

pkgw opened this issue Jun 15, 2017 · 1 comment

Comments

@pkgw
Copy link
Contributor

pkgw commented Jun 15, 2017

To support tracking of tape-drive backups of files on-site, we should support a special kind of Store that is not a regular SSH-able host. Instead it is just a symbolic entry representing a set of tapes on which we've written data.

In practice this might be more of a "write-only" store than a "tape-drive" store: the things that make this store different than a pot are not likely to be specific to tapes in any way.

CC @plaplant

@pkgw
Copy link
Contributor Author

pkgw commented Jun 17, 2017

Note that when the Librarian thinks about how many "instances" there are of a given file, in most (virtually all?) cases tape-archive instances shouldn't count. So maybe it would be wiser to have separate constructs that are analogous to Store and FileInstance, but that are not the same, so that we don't have to keep on remembering to implement special logic to ignore tape archive things when they're not relevant. It is hard for me to think of use cases where we'll really want to treat regular and tape-archive Stores, or regular and tape-archive Instances, as being on an equal footing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant