Loading...
Loading...
After daylight savings time change, backups are starting at incorrect times, relative to customers local time.
The schedule that the backups are set to run on was created or last edited on a computer in a different time zone to the Avamar server. Avamar schedules "inherit" their native time zone from the computer they are created on. More specifically, from the Java Runtime Environment's time zone on the computer which is running the Avamar Administrator UI. When daylight savings shifts occur, the schedule obeys the rules of its native time zone . This can result in the schedule not accounting for DST simultaneously as the Avamar server or UI does, and so relative to the local time, the schedule appears to be running an hour slow or fast. In the screenshot above, we can see that the native time zone of the schedule is Asia/Jerusalem. The schedule also shows the next run time in the schedules native time zone, and the next run time in the local time zone for the Avamar Administrator UI (in this case, an hour earlier than the time in Jerusalem). An example: In 2017, Los Angeles entered daylight savings time on the March 12. By contrast, London entered daylight savings time on the March 26. If the Avamar is located in the UK, but someone from LA edits or creates a schedule on it, that schedule then update its native time zone to LA. This means that on the 12th, the schedule updates to reflect the changes to daylight savings time in LA. However to a UK-based Avamar Admin, it appears as though the backups have suddenly started running an hour earlier than they were previously.
This is by design - it allows Avamar to be managed from multiple time zones without disrupting the scheduled backups. Care should be taken when editing schedules from an Avamar Administration instance in a different time zone to the schedules native time zone. If necessary, the schedule's native time zone can be edited from the command line using the "mccli schedule edit" command using the --tz flag to set the time zone. For example, this command changes the "Default Schedule" native time zone to that of Paris: mccli schedule edit --domain=/ --name=Default Schedule --tz=Europe/Paris See the mccli programmer guide for more details regarding this command.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.