Backup policies created or modified on or after 1st January 2011 show an incorrect start date when using Backup Exec System Recovery Management Solution (BESR-MS).
|Article:TECH147977|||||Created: 2011-01-12|||||Updated: 2011-06-15|||||Article URL http://www.symantec.com/docs/TECH147977|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
A backup policy created/modified on or after 1st January 2011 using Backup Exec System Recovery Management Solution (BESR-MS), shows an incorrect start date and do not run according to the schedule that was set. For example, a backup that was configured to start on 12th January 2011 will have a next run of 1st December 2011.
Any policy that was created/modified before 1st January 2011 is not affected by this issue.
NOTE: This only occurs if a policy is created/modified in the first 12 days of any given month. Policies created/modified on or after the 13th are not affected.
Figures 1 and 2 show what is seen in the BESR-MS console and on the client machine.
This issue is resolved in BESR-MS 2010 SP3 (9.0.3) which is available for download through Symantec Installation Manager (SIM).
BESR-MS: Backup policies created/modified on or after 1st Jan 2011 have incorrect start date.
Article URL http://www.symantec.com/docs/TECH147977