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

Add max archive size setting #28

Closed
arkrohne opened this issue Jun 23, 2017 · 2 comments
Closed

Add max archive size setting #28

arkrohne opened this issue Jun 23, 2017 · 2 comments

Comments

@arkrohne
Copy link
Contributor

Currently, the only way to limit archive size is by the MaximumArchiveDays setting. Having an option to limit the archive to a certain size would simplify storage management considerably.

@ritchiecarroll
Copy link
Member

So there is a setting called DesiredRemainingSpace which is a floating point number representing the amount of space to leave on a drive - the value defaults to 500GB. At least for archive directories this creates a limit, however, if all archive directories are full, the system has no choice but to fall back on its working directory for archiving, which usually fills up quickly - when that's full it backs up to memory.

Anyway, I am agreeing here - this setting is needed...

@ritchiecarroll
Copy link
Member

So the tricky part here is simply trying to figure out where to remove the files from when you have multiple archive output locations, consider the following:

Working Directory=D:\OHWorking\;
ArchiveDirectories={E:\OHArchive\; F:\OHArchive\}

The DesiredRemainingSpace option will automatically move from E:\ to F:\ once E:\ drive space hits the threshold.

Now once F:\ is full you could start engaging deleting files. Logically you remove "oldest files", so these would be removed from E:\.

Now the E:\ drive will have files older than F:\ and newer than F:\, once space is available.

So E:\ becomes the new "rolling" archive location and eventually will only have newer files than F:\ at which point F:\ would now have the oldest files so space is removed from there.

I think that this strategy would work but it might be confusing for someone looking at multiple archive drive locations in that it would never be "sequential" date-wise.

Would also need to think about "how much" to remove as well as "when".

Thoughts?

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

No branches or pull requests

3 participants