I beleive this is the problem for the server(s) but it only happens to the Sql 2000 & the distributer Sql 2005 server which I think it is interesting and I would like to share this and hopefully an expert can solve this problem for me.
I have 3 servers,
A: Win2003, SQL Server 2005 Distributor/Publicator/published by this server
B: Win2003, SQL Server 2005 Subscription
C: Win2003, SQL Server 2000 Subscription
The replication works but after a week, the two servers: A & C are heavily reducing disk spaces. I did the disk clean up, disk defragment for the server itself. Then, I go to the SQL Server, Shrink the database (the article), Master, Model using the wizard, then I manually do the following on Master, the article's db and the model,
backup Log <database name> with truncate_only
dbcc shrinkfile (<database name>_log,1000)
Usually, the manual shrinking scripts should work and reduce the disk space(s), however, it doesn't work for me.
I would like to know did I do something on the replication? If it is an error, the replication shouldn't work, right? But I check the Error Log & the Server Agent's Log, I seen it is working. The only errors I have is when I am doing the backup, I always received the following,
Backup Failed: C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32\ReporterSvc.log
Error e0010013: Operation skipped on file
Backup Failed: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
Error e0010013: Operation skipped on file
Backup Failed: C:\WINDOWS\system32\dhcp\DhcpSrvLog-Thu.log
Error e0010010: Client file is busy, retry
Backup Failed: C:\WINDOWS\system32\wbem\Logs\wbemcore.log
Error e0010010: Client file is busy, retry
Backup Failed: C:\WINDOWS\system32\wbem\Logs\wbemprox.log
Error e0010010: Client file is busy, retry
Fatal: there was a nonsense bundletag and size:
I am really frustrated. Should I stop the replication or what else I can do?
Thanks.
I have 3 servers,
A: Win2003, SQL Server 2005 Distributor/Publicator/published by this server
B: Win2003, SQL Server 2005 Subscription
C: Win2003, SQL Server 2000 Subscription
The replication works but after a week, the two servers: A & C are heavily reducing disk spaces. I did the disk clean up, disk defragment for the server itself. Then, I go to the SQL Server, Shrink the database (the article), Master, Model using the wizard, then I manually do the following on Master, the article's db and the model,
backup Log <database name> with truncate_only
dbcc shrinkfile (<database name>_log,1000)
Usually, the manual shrinking scripts should work and reduce the disk space(s), however, it doesn't work for me.
I would like to know did I do something on the replication? If it is an error, the replication shouldn't work, right? But I check the Error Log & the Server Agent's Log, I seen it is working. The only errors I have is when I am doing the backup, I always received the following,
Backup Failed: C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32\ReporterSvc.log
Error e0010013: Operation skipped on file
Backup Failed: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
Error e0010013: Operation skipped on file
Backup Failed: C:\WINDOWS\system32\dhcp\DhcpSrvLog-Thu.log
Error e0010010: Client file is busy, retry
Backup Failed: C:\WINDOWS\system32\wbem\Logs\wbemcore.log
Error e0010010: Client file is busy, retry
Backup Failed: C:\WINDOWS\system32\wbem\Logs\wbemprox.log
Error e0010010: Client file is busy, retry
Fatal: there was a nonsense bundletag and size:
I am really frustrated. Should I stop the replication or what else I can do?
Thanks.