locked
Can I delete old WsusContent after doing a 'wsustuil movecontent' run? RRS feed

  • Question

  • I have WSUS running on a WS2008 R2 with WSUS3.x and it filled up drive C:. So I used "wsusutil movecontent e:\WSUS2 e:wsus2.log and it appears to have copied all the content from drive C: to drive D:. Log file shows everything ran successfully. However it did not delete the old WsusContent from old location so my drive C: is still full.

    I tried running the WSUS GUI Cleanup Wizard which ran quickly with no errors.

    Next I tried "wsusutil reset" but this seems to quit almost instantly with no errors. It had no impact on the size of content.

    So should I just manually delete the old WsusContent folder on drive C: since I did a movecontent to D:?

    Saturday, August 23, 2014 9:08 PM

Answers

  • Yes, you can delete the old WSUS content directory if it was successfully moved.
    • Marked as answer by Oregonbob Thursday, August 28, 2014 2:43 PM
    Tuesday, August 26, 2014 10:45 PM

All replies

  • 1. What does log say? Have the move finished yet?

    2. A good rule for used size on HDD is 15% free. Some operation needs free space. If you have not free space the operation(s) may fail. Try to delete temp and cached content in operating system and IE.

    3. Have you followed procedure (?)

    http://blogs.technet.com/b/sbs/archive/2009/09/23/how-to-move-wsus-content-and-database-files-to-a-different-partition.aspx

    Rgds

    Milos


    PS: Chances are that this may take some time as is the case with WSUS.
    Saturday, August 23, 2014 10:28 PM
  • The log for movecontent looks good:

    2014-08-23T17:49:37 Successfully stopped WsusService.
    2014-08-23T17:49:37 Beginning content file location change to e:\WSUS2
    2014-08-23T18:05:19 Successfully copied content files.
    2014-08-23T18:05:19 Successfully copied application files.
    2014-08-23T18:05:20 Successfully changed WUS configuration.
    2014-08-23T18:05:21 Successfully changed IIS virtual directory path.
    2014-08-23T18:05:21 Successfully removed existing local content network shares.
    2014-08-23T18:05:21 Successfully created local content network shares.
    2014-08-23T18:05:21 Successfully changed registry value for content store direct
    ory.
    2014-08-23T18:05:21 Successfully changed content file location.
    2014-08-23T18:05:24 Successfully started WsusService.
    2014-08-23T18:05:24 Content integrity check and repair...

    2014-08-23T18:05:24 Initiated content integrity check and repair.

    I noticed after this was finished it used a lot of CPU for about an hour running SQLserver. I waited until it was all done and system idle, then I reboot.

    I had onl;y 2GB free when I ran movecontent, but it appears to have gone OK. And now when I run WSUS Cleanip it runs OK with no errors. But still 'wusuutil reset' appears to do nothing quickly and finish.

    Yes I followed procedure. I manuall removed enough of the OLD Wsuscontent to get 20% free, but that didn';t matter.

    Saturday, August 23, 2014 10:43 PM
  • Yes, you can delete the old WSUS content directory if it was successfully moved.
    • Marked as answer by Oregonbob Thursday, August 28, 2014 2:43 PM
    Tuesday, August 26, 2014 10:45 PM
  • Hi,

    I’m writing to just check in to see if the suggestions were helpful. If you need further help, please feel free to reply this post directly so we will be notified to follow it up.

    Best Regards.



    Steven Lee

    TechNet Subscriber Support 
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
    Thursday, August 28, 2014 9:39 AM
  • I deleted the old WsusContent folder and all appears to be OK now. I'll keep an eye on it. I had been watching it for some time and running Cleanup wizard at least monthly.

    It appeared to me that the size of my WsusContent folder increased by around 18GB in the last 2 weeks of use. MS must have had a lot of updates. Microsoft should put a big warning in the WSUS install guide that one should allocate at least 100GB of space for running WSUS. My current size of that folder is 72GB.

    Thursday, August 28, 2014 2:48 PM
  • Microsoft should put a big warning in the WSUS install guide that one should allocate at least 100GB of space for running WSUS. My current size of that folder is 72GB.

    For most installations, the recommended storage allocation of 30GB is twice what a typical well-maintained server will require.

    Quite often disk consumption in excess of that 30GB recommended allocation is a suggestion that update administration (read: removing Approvals from superseded updates) is not being performed.

    Please refer to this article: Removing unneeded update approvals and see if that helps.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sunday, August 31, 2014 4:35 PM