Backup policies created in BESR-MS on or after 1st January 2011 show an
incorrect start date. For example, a job configured to start today (12th Jan)
shows a next run of 1st December.

Any backup policy that is modified on or after 1st Jan 2011 also shows this
problem.

Backup policies created/modified before 1st Jan are not affected.

This is NOT a display issue. It also affects the backup job itself - it wont run
until the next run time (December in above example).

If I create a policy that is configured to start on 13th Jan, the next run date
will still show as 1st Dec.

A supported hotfix has been made available for this issue. Please contact Symantec Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix