cancel
Showing results for 
Search instead for 
Did you mean: 

Leap Second

I have been looking for a release from symantec covering this topic.   Does anyone have a reference to Symantec's take on this issue ?

1 Solution

Accepted Solutions
Accepted Solution!

No Impacte on NBU . this is

No Impacte on NBU . this is what i recieved from Symantec when opeend a case:

 


"NetBackup and PureDisk (including NetBackup appliances) use standard UTC time for operation including scheduling and setting of retention levels. 

As such they remain aligned to UTC time in respect of time adjustments such as leap years and leap seconds and there is no requirement to make separate adjustments to any internal "NetBackup clock".

Job scheduling is unaffected by leap years as all job scheduling is either frequency (day/time) or calendar based.  Frequency based backups will run at the same frequency irrespective of calendar dates.  Jobs scheduled for particular times of day or on specific days of the week are also unaffected by leap years and are  fully "leap year compliant."

As backup jobs are scheduled by "start windows" rather than a specific times the exact start time of a backup varies slighty from day to day and leap second variations are absorbed by this slight drift. "

 

View solution in original post

1 Reply
Accepted Solution!

No Impacte on NBU . this is

No Impacte on NBU . this is what i recieved from Symantec when opeend a case:

 


"NetBackup and PureDisk (including NetBackup appliances) use standard UTC time for operation including scheduling and setting of retention levels. 

As such they remain aligned to UTC time in respect of time adjustments such as leap years and leap seconds and there is no requirement to make separate adjustments to any internal "NetBackup clock".

Job scheduling is unaffected by leap years as all job scheduling is either frequency (day/time) or calendar based.  Frequency based backups will run at the same frequency irrespective of calendar dates.  Jobs scheduled for particular times of day or on specific days of the week are also unaffected by leap years and are  fully "leap year compliant."

As backup jobs are scheduled by "start windows" rather than a specific times the exact start time of a backup varies slighty from day to day and leap second variations are absorbed by this slight drift. "

 

View solution in original post