Hi,
I have just created a new schedule for a backup job today (30th) with the effective date defaulted to 30th and specified last day of the month.
The result of this was a first scheduled job of 31/07/05 rather than 30/06/05 as expected.
I then deleted, and created a new schedule, but this time i set the effective date myself as yesterdays date (29th) with the other settings the same as above, and this time it scheduled my job for 30/06/05.
Based on this, last month i amended my job when i changed the effective date, which still didn't update the date, but after this latest result, wondered if maybe i should have refreshed.
Therefore I have just put back the time on the server to 31st May, and created a schedule leaving the default effective date as the 31st. This again didn't work as expected and the first schedule was set for 30/06/06 instead of 31/05/05.
I then created another new schedule but again this time, i set the effective date as the day before, and the schedule correctly picked the end of May (31st) as the first scheduled job.
This would suggest that if you create a "last day of the month" scheduled job ON the last day of the month then the effective date has to be changed to the previous day rather than kept at the default that Backup Exec picks, otherwise it will automatically skip that day and schedule for the end of the next month.
Is this by design?
Thanks
Andrew Perry