Issue:
SBS Operating System overhead is ballooning (e.g. over 400 GB). What maintenance tasks can be done to clean-up.
Solution:
Switch to Linux which auto rolls over logs and doesn't have WSUS gut, or remove WSUS.
Otherwise...
A: Turn off IIS logging for WSUS site.
1. Start --> Administrative Tools --> Internet Information Services (IIS) Manager
2. On the left, expand the server twistie (plus minus) and Sites folder twistie.
3. Click on WSUS Administration site
4. In the middle window, open the Logging icon (middle section under IIS heading)
5. Note where logging is located under the schedule area.
6. On the far right, under the Actions area, click the Disable option for logging.
B: Clear old IIS logs:
1. Open the c:\inetpub\logs\LogFiles folder
2. Open each of the funky coded folders. (There is one for each site and possibly others from old sites now gone.)
3. Clear all the old logs going back years to whatever date you feel comfortable. Leave the current log for today.
In our case, this cleared up 50 GB.
(It had been over a year since cleaned out.)
C: Clear out IIS 6 FTP logs:
1. Open up c:\windows\system32\LogFiles\ folder
2. Look for folders named like "MSFTPSVC1" and so on.
3. Open the folders and remove the older files.
In our case, this cleared up 1 GB.
D: Clear out old licensing debug logs:
1. Open the c:\windows\system32\winevt\Logs folder
2. Delete the older logs that start with:
Microsoft-Windows-Server Infrastructure Licensing%4Debug.etl.* (where * is a number. Leave the current/last dated file)
In our case, this cleaned up almost 1 GB.
E: Clean up WSUS:
1. Start --> Administrative Tools --> Microsoft Windows Server Update Services 3.0 SP1
(Yes, it starts with Microsoft so you know which WSUS, as if anyone else has one. Your SP version may be different.)
2. On the left, expand the server twistie (plus minus).
3. Click the "Options" option.
4. In the center window area, click the "Server Cleanup Wizard".
5. In the wizard dialog, leave selected the things to clean and click Next.
6. Wait. Wait. Wait and keep waiting. This will likely take hours.
In our case, we had not done this in over a year. Our WSUS folder was pretty huge. We just kicked it off and let it run.
(Note: as this agent ran, it actually used up more space as it cleaned. That's why we did the others first, to give this wizard room to use up more space to free up space.)
F: Clean up the SBS Management Console logs:
1. Open the c:\program files\Windows Small Business Server\Logs folder.
2. In this folder are the logs. (Expect at least a couple Gbs in this folder.)
3. Delete the older log files in the MonitoringServiceLogs folder used by the SBS Manager service.
4. The *.evtx log files are the steps of the migration/setup. If you are in production and your setup issues are OVER finally, it is supposedly safe to remove these.
As the other console logs each had unique names, we left them. We freed up 1.3 GB here without deleting anything but all but last few months of logs for #3 above.
G: Defrag
Now when WSUS's wizard is finally done.
1. Start --> All Programs --> Accessories --> System Tools --> Disk Defragmenter
H. Check out the SQL SharePoint Config site. You might find yours has even way surpassed WSUS.
Run this script:
(Complements of Microsoft :-) I don't know the KB number or I'd include it. )
 SharePointConfigDBPurge.rtf
Other options:
a. Delete the service pack files.
They are hidden. If you delete them, then the uninstalls won't work (like you'd revert anyway). The best way to remove them is to download the Windows Component Clean Tool (COMPCLN.exe) and use it to remove the Windows Server SP2 original files archive.
b. Check your SharePoint SQL server's transaction log size.
If it's pretty massive, look for KB 2000544 article on the MS support site.
c. There are "Move Data Wizards" to shuffle some features to other local disks. Search the MS TechNet site for "cc527581" and "cc766568".
previous page
|