none
Protecting WSUS DB (WID) with DPM 2012 SP1 RRS feed

  • Question

  • Hi,

    trying to configure protection of our WSUS server that is built on Windows Server 2012, were using WID as back-end for this particular installation and for some reason I'm unable to set up protection from DPM 2012 SP1 - database simply does not appear on the list of objects available for backup only network shares and system state are listed. So far we've reinstalled DPM agent, installed UR5 for DPM 2012 SP1 and updates all agents, added NTAuthority\System to the Sysadmin group but still no joy.

    Any ideas?

    Cheers

    Michal


    MB


    • Edited by MichalB_SDS Monday, February 24, 2014 12:56 PM
    Monday, February 24, 2014 12:55 PM

Answers

  • HI,

    OK - If the SQL Writer is not involved, then DPM cannot protect it natively, however if there is a mechanism to dump the DB or back it up to a folder using WSUS, then we could invoke DPM pre-backup script to run the manual backup, then protect the destination folder.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Tuesday, February 25, 2014 3:56 PM
    Moderator

All replies

  • Hi,

    Check to make sure the SQL Server VSS writer is started.

    On the problematic SQL Server run the following from an administrative command prompt:

    C:\Windows\system32>diskshadow.exe /l c:\temp\writers.txt
    Microsoft DiskShadow version 1.0
    Copyright (C) 2007 Microsoft Corporation
    On computer:  Computer_Name,  

    DISKSHADOW> list writers

    DISKSHADOW> EXIT

    Now open the output file writers.txt using notepad - then search for "SqlServerWriter" - see if the DB is listed there under that section.

     

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, February 24, 2014 11:15 PM
    Moderator
  • Hi Mike,

    when running commands suggested by you SqlServerWriter is not listed at all, just "WIDWriter" with SUSDB as one of its components.

    Just to clarify, this WSUS (running off Windows Server 2012) installation takes advantage of Windows Internal Database rather than dedicated SQL instance, we have only SQL Management Studio installed locally, it appears that with Windows Server 2012, string used for connecting to DB has changed from \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query used in previous versions to \\.\pipe\MICROSOFT##WID\tsql\query - we were suspecting that this change had something to do with DPM not supporting it initially, but now after both products being mature we expected it to start working.


    MB

    Tuesday, February 25, 2014 10:01 AM
  • HI,

    OK - If the SQL Writer is not involved, then DPM cannot protect it natively, however if there is a mechanism to dump the DB or back it up to a folder using WSUS, then we could invoke DPM pre-backup script to run the manual backup, then protect the destination folder.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Tuesday, February 25, 2014 3:56 PM
    Moderator