You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 28, 2021. It is now read-only.
I'm reporting a potential issue I see with the ebs-snapper tool and its ability to exclude/ignore volumes or instances from the backup. As far as I can see, it is only possible to exclude or ignore volumes/instances using a config in the Dynamo DB table. Because instance ids and volume ids change so frequently, I'd advise moving the ignore configuration to an instance or volume tag. Otherwise you'll have invalid ignore configuration until the instance id/volume id has been updated.
Thanks
The text was updated successfully, but these errors were encountered:
webmin88
changed the title
Ignore Configuration issue
Bug: Ignore Configuration issue
Jan 3, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm reporting a potential issue I see with the ebs-snapper tool and its ability to exclude/ignore volumes or instances from the backup. As far as I can see, it is only possible to exclude or ignore volumes/instances using a config in the Dynamo DB table. Because instance ids and volume ids change so frequently, I'd advise moving the ignore configuration to an instance or volume tag. Otherwise you'll have invalid ignore configuration until the instance id/volume id has been updated.
Thanks
The text was updated successfully, but these errors were encountered: