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

--run --force #23

Closed
bradspry opened this issue Jan 26, 2016 · 0 comments · Fixed by #27
Closed

--run --force #23

bradspry opened this issue Jan 26, 2016 · 0 comments · Fixed by #27

Comments

@bradspry
Copy link

On a daily rotation powered by cron, scheduled at the same time of every day, automated-ebs-snapshots uses the current time and date to determine if a snapshot is needed. On a daily rotation, if the current time is less than 24 hours since a snapshot was made, then a snapshot does not occur. In my experience, the daily snapshot timing comparisons can be very close, to the second. When the comparison is less than 24 hours, the result is a snapshot appearing to happen every other day.

It would be nice to --force a snapshot, overriding and negating the time comparison, to ensure a snapshot happens.

You can currently route around the issue by setting up seven (7) crons, one for each day of the week, and increment the cron timing each day. On the seventh day however, when cron comes back around to a lesser value, a snapshot does not occur.

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

Successfully merging a pull request may close this issue.

1 participant