none
How to move WSUS to new drive on same server?

    Question

  • When I looked it up, I only found instructions on moving the content folder using wsusutil, but apparently this does not move the wsus database.

    We do not have SQL server, we are using the standard WSUS internal database that comes standard.

    What are the steps to move both the content and the database to a different drive on the same server?

    Can we just select all the folders, copy and paste them to a new drive and then reassign the old drive letter to the new drive?

    If so which services do we need to stop and restart during the file copy?

    Monday, October 28, 2013 3:30 PM

Answers

  • What are the steps to move both the content and the database to a different drive on the same server?

    The instructions for migrating the WSUS Database are documented in the WSUS Operations Guide.

    http://technet.microsoft.com/en-us/library/dd939918(v=ws.10).aspx

    The instructions apply regardless of the source and destination database edition, but the most common migration is from WID to a back-end SQL Server, so that's how they were written.

    In short, aside from the pedantic details of  how to connect Management Studio, the process is this:

    1. Stop the Update Services service.
    2. Detach the database.
    3. Move the database files.
    4. Attach the database.
    5. Start the Update Services service.


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

    • Marked as answer by MyGposts Tuesday, November 05, 2013 6:34 AM
    Friday, November 01, 2013 12:36 AM
    Moderator

All replies

  • I can't see why you couldn't use a drive letter switch (we've done with databases in the past) but I haven't tried that against the wsus content and I haven't seen anything documented to say it's "supported". To be safe, why not stick with wsusutil to move the content and treat the DB as any other Windows Internal Database: http://technet.microsoft.com/en-us/library/dd277864(v=office.12).aspx

    I hope this helps,
    Mark

    Monday, October 28, 2013 4:05 PM
  • That link is for SharePoint and describes shutting down the SharePoint services before moving the database.

    How do you disable the WSUS services?  I only see the windows update service on the WSUS server.

    Is there a separate service for WSUS server services?

    Monday, October 28, 2013 4:18 PM
  • Sorry, missed that part of the question. The article below mentions stopping the "IIS Admin Service" and "Update Services" before moving the database from Windows Internal Database to SQL Server: http://technet.microsoft.com/en-us/library/dd939918(v=ws.10).aspx If it's good enough for that I'd assume it's good enough for this process too.

    I hope this helps,
    Mark

    Monday, October 28, 2013 4:26 PM
  • This looks super complicated and requires piecing together instructions from different web sites.  Lots of opportunities for typos, failures and errors that will not apply to the SharePoint solution.

    I can't get connected to the database with SQLME because it asks for credentials and my domain admin credentials do not work and I don't know what credentials it is looking for.

    It also asks for server name and I put in the local server's name and it doesn't seem to work.  I tried the actual name and I tried localhost and neither works.  


    Monday, October 28, 2013 4:52 PM
  • You can use wsusutil export to export the database to a .xml.gz file, then switch the database by running postinstall. Finally, import the .xml.gz file into the new database using wsusutil import.

    Similarly, you can use wsusutil to move the content to a new location. Wsusutil will actually copy the content, but once it's done you can delete the content from its original location.

    Regards,
    Ben


    Monday, October 28, 2013 10:27 PM
    Moderator
  • What are the steps to move both the content and the database to a different drive on the same server?

    The instructions for migrating the WSUS Database are documented in the WSUS Operations Guide.

    http://technet.microsoft.com/en-us/library/dd939918(v=ws.10).aspx

    The instructions apply regardless of the source and destination database edition, but the most common migration is from WID to a back-end SQL Server, so that's how they were written.

    In short, aside from the pedantic details of  how to connect Management Studio, the process is this:

    1. Stop the Update Services service.
    2. Detach the database.
    3. Move the database files.
    4. Attach the database.
    5. Start the Update Services service.


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

    • Marked as answer by MyGposts Tuesday, November 05, 2013 6:34 AM
    Friday, November 01, 2013 12:36 AM
    Moderator
  • Having lots of problems.  I was able to unmount the wsus database, but now I need to remount it because I noticed the files that were copied to the new drive don't have the same permissions as they did on the original drive.

    I can't figure out the sqlcmd syntax to just reattach to the original database on the original drive that was just unattached.

    I only see instructions for  the command to detach the database.

    Monday, November 04, 2013 1:51 AM
  • Take a look at Step 4 "Reattach the databases and log files." in the link I sent you earlier: http://technet.microsoft.com/en-us/library/dd277864(v=office.12).aspx. I believe you could also manage this via Microsoft SQL Server Management Studio Express if you prefer a GUI: http://www.mssqltips.com/sqlservertip/1577/administering-your-windows-internal-database-microsoftssee-instance/

    I hope this helps,
    Mark

    Monday, November 04, 2013 12:45 PM
  • There were a couple extra things that had to be stopped besides just the Updates service.

    IIS Admin

    WSUS administration site also had to be stopped from the IIS Manager console or else the database fails to dismount.

    Tuesday, November 05, 2013 6:40 AM