SMS: Shared SQL Server Backup Can Corrupt Backup Files (235195)
The information in this article applies to:
- Microsoft Systems Management Server 2.0
This article was previously published under Q235195 SYMPTOMS
When you attempt to restore the SQL database for a Microsoft Systems Management Server (SMS) site, the restore process may not be successfully completed.
CAUSE
This behavior can occur if the primary site's SQL database is on a shared Microsoft SQL Server computer also used by other primary sites. The SMS backup process begins by getting a directory list of *.tmp files in the root folder of the system where the SQL Server computer is installed. It then generates a unique file name for temporary files used during backup. There is a delay between the generation of this unique file name and the actual creation of the temporary file in the SQL Server root folder. Meanwhile, another site server, which is also using that same SQL Server computer, is running the same process. It also generates the same temporary file name for use during its site database backup because the other site process has not yet created the new *.tmp file. One of these temporary files overwrites the other, corrupting the backup for the other site server.
WORKAROUND
To work around this issue, be sure to stagger the backup of SMS sites that share a common SQL Server computer.
STATUS
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.MORE INFORMATION
By staggering the SMS site backups, you also have the advantage of spreading the SQL database dump load on the SQL Server computer.
| Modification Type: | Minor | Last Reviewed: | 6/14/2005 |
|---|
| Keywords: | kbBug kbConfig kbDatabase kbinterop kbServer kbsmsUtil KB235195 |
|---|
|