10 pts.
 SQL Server 2005 SP2 backup failing
This is my first post and thanks in advance for any replies. I have a backup that failed midway (about 120G of 230G) into the backup twice in the last 2 weeks. Each time, the first error that gets reported in the Application log has been, "BackupMedium::ReportIoError: write failure on backup device '\server_namedb_dump.bak'. Operating system error 1398(There is a time and/or date difference between the client and server.)." Also, on both occassions, the last Application event reported prior to the actual start of the backup job has been, "The time stamp counter of CPU on scheduler id x is not synchronized with other CPUs." The backup is between 2 different servers, one being a 16 processor 3.4Ghz Intel Xeon w/ 16G and a 16 processor 2.4Ghz Intel Xeon w/ 16G and both servers have the power scheme setting to always on. So, I don't think it's an issue with processors entering into a power saving mode by slowing down processor speed and possibly getting out of whack for this reason. But, I'm open to other inputs on this. 90% of the time this completely reliable... when it occurrs over the weekend and you come in on Monday it makes for an interesting Monday morning. Again, thanks for any help, Andy

Software/Hardware used:
ASKED: February 23, 2009  7:54 PM
UPDATED: February 23, 2009  9:13 PM

Answer Wiki:
Within a Windows domain the time on the machines has to be within a couple of minutes of each other. If one of the computers is drifting its time you'll have problems talking between the machines. It is recommended that domains use the time sync features of the computers to ensure that the times match between all the machines.
Last Wiki Answer Submitted:  February 23, 2009  8:44 pm  by  Denny Cherry   64,520 pts.
All Answer Wiki Contributors:  Denny Cherry   64,520 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _