Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Backup policies created/modified on or after 1st Jan 2011 have incorrect start date.

Created: 22 Jan 2011 • Updated: 09 May 2011
David F's picture
3
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Private fix ready
Tech Note: More Information

 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