configuration ntp on all servers

Phebe_Mertes at aotx.uscourts.gov Phebe_Mertes at aotx.uscourts.gov
Thu Nov 19 14:29:27 UTC 2009


NTDP when it uses a time server, will do small increments to slowly change
the time.

First, an hour off suggests you are not utilizing or have the wrong tzdata
installed.

Second, you can assign the rhel pool time servers to allow your servers to
query a time server so they all become synchronized.

in rhel, system-config-date allows you to set time zone, daylight savings
and date. I do not recommend this if you are trying to not do a fast time
change on your database logs. If you have little activity at 0200 hrs, then
this might be a good time to use this.



                                                                                                          
  From:       "Stainforth, Matthew (SD/DS)" <Matthew.Stainforth at gnb.ca>                                   
                                                                                                          
  To:         General Red Hat Linux discussion list <redhat-list at redhat.com>                              
                                                                                                          
  Date:       11/19/2009 07:05 AM                                                                         
                                                                                                          
  Subject:    RE: configuration ntp on all servers                                                        
                                                                                                          
  Sent by:    redhat-list-bounces at redhat.com                                                              
                                                                                                          





> > What happens to the logs if they suddenly tell you that you have to
> go
> > to the past?
> >
> > That is my question.
>
> An hour off is pretty serious. If it's really that bad, you have a
> problem.
> Least intrusive: jump it at 02:00, or jump it in maybe five minute
> intervals
> once or twice a day. I'd lean towards the former.

That could be even worse.  My biggest concern would be the effect on redo
logs.  I don't know how oracle handles time jumps into the past but my fear
would be if you ever had to apply those redo logs then they could be
applied in the wrong order so recovery from backup would be impossible for
any time span that contained a backward jump.

I agree with Rob Marti, check with the DBAs to see if the operation is safe
but my guess is they'll say no.  If it were me, I would schedule an outage
to bring the time back to normal and then enable NTP.

Matt

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list






More information about the redhat-list mailing list