SMS: Changes to SMS Backup Schedule Require Up to 24 hours to Take Effect (235785)
The information in this article applies to:
- Microsoft Systems Management Server 2.0
- Microsoft Systems Management Server 2.0 SP1
- Microsoft Systems Management Server 2.0 SP2
This article was previously published under Q235785 SYMPTOMS
The schedule for the Backup SMS Site Server task can be changed at any time; however, the process that reads the schedule and performs all changes operates only once each day. Therefore, any changes made to the backup schedule can require as long as 24 hours to take effect.
WORKAROUND
To immediately start the Backup SMS Site Server task in Microsoft Systems Management Server (SMS) 2.0 Service Pack 1, manually start the SMS_SITE_BACKUP service. Doing so forces the process to cycle through the instructions in the SMSbkup.ctl file. The service then automatically shuts down. The SMSbkup.ctl file can be found in the SMS\inboxes\smsbkup.box folder.
In both SMS 2.0 and SMS 2.0 Service Pack 1, to force SMSdbmon to reread the backup schedule and, if appropriate, start an immediate backup, follow these steps:
- In Notepad, open the following file:
- Locate the following string:
- Change the date located directly after the backup string to a date more than one week old.
- In the Service Manager, stop and restart the SMS_SQL_MONITOR (SMSdbmon) service.
Regardless of how the backup schedule is configured, this process forces SMSdbmon to read the schedule and run the backup process.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Systems Management Server version 2.0. MORE INFORMATION
Please refer to the SMS Administrator's Guide for additional information on how to stop and start SMS components, including the Backup service (SMS_SITE_BACKUP).
| Modification Type: | Minor | Last Reviewed: | 6/14/2005 |
|---|
| Keywords: | kbBug kbConfig kbnofix kbServer kbsmsUtil KB235785 |
|---|
|