Can Data Lifecycle Manager have precision in the schedule? What causes delay?

Question

I'm not sure if this is a bug or this is some other delay, but my intention is to take the snapshot at precisely 03:00 UTC and the schedule settings show this in the DLM settings, and I know snapshot *completion time* should obviously be after 03:00. However, the 'Started' time listed on the snapshot page in the console says it's 03:36 and the completion event is 03:43, for a snapshot taken with DLM's schedule. What is the point of setting the schedule if it's so off in its start?

Flo from evoila · Answer

(It's been a while since the question was asked. I stumbled on this and found the answer/explanation somewhere else, then.)

The API documentation [CreateRule](https://docs.aws.amazon.com/dlm/latest/APIReference/API_CreateRule.html) actually states the following for `Times`:

> The time, in UTC, to start the operation. The supported format is hh:mm.
>
> **The operation occurs within a one-hour window following the specified time.** If you do not specify a time, Amazon Data Lifecycle Manager selects a time within the next 24 hours.  
> -- [CreateRule](https://docs.aws.amazon.com/dlm/latest/APIReference/API_CreateRule.html)

h4xnoodle · Answer

Even in the sidebar for the DLM configuration page it says

Schedules can run:
    Schedules can be configured to run:

daily at specific times
    weekly on specific days
    monthly on specific dates or days of the week
    yearly at the end or the start of specific months

so much for specific?

Can Data Lifecycle Manager have precision in the schedule? What causes delay?

Add your answer

Relevant content