It appears that there is also a problem with Symantec Backup Exec 10d and 10.1.  Alan, our reader that discovered the APC problem also discovered a problem with his backup software.  Again the software was patched and updated as recommended by Symantec.

Here is what Alan had to say:

Backup jobs previously scheduled for 11:00 PM are now scheduled for 10:00 PM despite 10d and 10.1 reportedly DST compliant http://support.veritas.com/docs/286926. Nor will it allow you to change the time back to the correct time of 11:00 PM. It reports that it will, allows the change, and reports the new time in the summary when the job is resubmitted. But the scheduled time immediately reverts back to 10:00 PM. Restarting the Backup services does not appear to correct this either, so we're now an hour off on all backups and banging our heads on our desks repeating expletives directed at certain vendors.

It looks like Alan is going to have a busy Sunday and maybe even Monday. Good Luck Alan and if you have time keep us updated to your progress on resolving the problems.

Update:
Alan contacted us again with new findings on the Symantec Backup Exec scheduling problem.  He indicated that his older.. unpatched backups are fine. 

Here is what he had to say:

Ok, so now I'm highly annoyed. It turns out that our servers that have not been updated with more recent APC Powerchute (still running 5.2) and Veritas Backup Exec (8.6 instead of 10(d) or 10.1))handled the DST change correctly whereas the newer versions didn't.

I'm beginning to wonder if the move towards java based tools is the underlying issue with the newer "compliant" applications not working as expected.