Skip to main content

How to backup and restore WSUS



WSUS is a key technology in maintaining any Windows network. From servers to clients to major Microsoft software packages, WSUS will make life easier on you. The following instructions were taken from http://technet.microsoft.com/en-us/library/cc708546(WS.10).aspx.

To back up the update file storage folder

1. On your WSUS server, click Start, and then click Run.

2. In the Open box, type %systemdrive%\%windir%\system32\ntbackup.exe and then click OK.

3. In the Backup or Restore Wizard, click Next.

4. Verify that Back up files and settings is selected, and then click Next.

5. Click Let me choose what to back up, and then click Next.

6. Select the WSUSContent folder (under %systemdrive%\WSUS\), and then click Next.

7. Use the Browse button to choose a place to save your backup, type a name for the backup, and then click Next.

8. If you want to set additional specifications for your backup, including whether it will be an incremental backup, whether you want to verify the backup, set a recurring schedule for the backup, or other options, click Advanced, and then follow the instructions in the wizard.

9. When the wizard is finished, click Finish.

10. When the message appears that informs you that the backup is complete, click Close.

To back up the WSUS database

1. On your WSUS server, click Start, and then click Run.

2. In the Open box, type %systemdrive%\%windir%\system32\ntbackup.exe and then click OK.

3. In the Backup or Restore Wizard, click Next.

4. Verify that Back up files and settings is selected, and then click Next.

5. Click Let me choose what to back up, and then click Next.

6. Under %systemdrive%\WSUS\MSSQL$WSUS\, select the Data and LOG folders, and then click Next.

7. Use the Browse button to choose a place to save your backup, type a name for the backup, and then click Next.

8. If you want to set additional specifications for your backup, including whether it will be an incremental backup, whether you want to verify the backup, set a recurring schedule for the backup, or other options, click Advanced, and then follow the prompts that appear in the wizard.

9. When the wizard is finished, click Finish.

10. When the message appears that informs you that the backup is complete, click Close.

To restore the update file storage folder

1. On your WSUS server, click Start, and then click Run.

2. In the Open box, type %systemdrive%\%windir%\system32\ntbackup.exe and then click OK.

3. In the Backup or Restore Wizard, click Next.

4. Click Restore files and settings, and then click Next.

5. In the What to restore dialog box, under Items to restore, expand the file that contains the WSUSContent folder (under%systemdrive%\WSUS\), and then click Next.

Alternatively, you can select a subset of the %systemdrive%\WSUS\WSUSContent folder to restore. Within the%systemdrive%\WSUS\WSUSContent folder, you can restore one, all, or a combination of its subfolders and files.

6. If you want to set additional specifications for your restore, including whether you want to restore the files or folders to a different location, replace existing files, restore security settings, or specify other options, click Advanced, and then follow the instructions in the wizard.

7. When the wizard is finished, click Finish.

8. When the message appears that informs you that restoring is complete, click Close.

To restore the WSUS database

1. On your WSUS server, click Start, and then click Run.

2. In the Open box, type %systemdrive%\%windir%\system32\ntbackup.exe and then click OK.

3. In the Backup or Restore Wizard, click Next.

4. Click Restore files and settings, and then click Next.

5. In the What to restore dialog box, under Items to restore, expand the file that contains the Data and LOG folders (under%systemdrive%\WSUS\MSQL$WSUS), and then click Next.

Alternatively, you can select a subset of the %systemdrive%\WSUS\MSQL$WSUS\Data or%systemdrive%\WSUS\MSQL$WSUS\LOG folders to restore. Within the %systemdrive%\WSUS\MSQL$WSUS\Data and%systemdrive%\WSUS\MSQL$WSUS\LOG folders, you can restore one, all, or a combination of their subfolders and files.

6. If you want to set additional specifications for your restore, including whether you want to restore the files or folders to a different location, replace existing files, restore security settings, or specify other options, click Advanced, and then follow the instructions in the wizard.

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...