Iniciar sesión
 
InicioBibliotecaAprendizajeDescargaSoporteComunidadForos
Recursos para Profesionales de TI >
> 
> 
DPM 2010 and Sharepoint 2010

Unanswered DPM 2010 and Sharepoint 2010

  • jueves, 26 de enero de 2012 10:17
     
     
    Inicie sesión para votar
    0

    Hi, I trying to backup Sharepoint 2010 with DPM 2010.  On our testenvironment, I can add Sharepoint backup in DPM, but on prod-environment I can´t find Sharepoint. 

    I have run the same commands on both setups. The different is that production got two servers, (one frontend and one index). 

    Same DB-server for both test and production. 

    I have followed this guide: http://scug.be/blogs/scdpm/archive/2010/03/11/sharepoint-2010-protection-in-dpm-2010-part-1.aspx

     

    Thanks for tips to troubleshooting this, Magnus

     

    Magnus
     

Todas las respuestas

  • jueves, 26 de enero de 2012 12:27
     
     
    Inicie sesión para votar
    0

    When you expand your WFE when creating protection do you see the SharePoint icon?

    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
     
  • jueves, 26 de enero de 2012 13:11
     
     
    Inicie sesión para votar
    0

    When you expand your WFE when creating protection do you see the SharePoint icon?

    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights

    Nope, only "All Shares, All volumes and System Protection". On test, I got "Sharepoint". 

     

    Thanks, Magnus

    Magnus
     
  • jueves, 26 de enero de 2012 13:12
     
     
    Inicie sesión para votar
    0

    Do you get any errors when you run ConfigureSharePoint -enablesharepointprotection on your WFE?

    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
     
  • jueves, 26 de enero de 2012 14:12
     
     
    Inicie sesión para votar
    0

    Do you get any errors when you run ConfigureSharePoint -enablesharepointprotection on your WFE?

    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Nope, no error. 
    Magnus
     
  • jueves, 26 de enero de 2012 14:13
     
     
    Inicie sesión para votar
    0
    Does the sharepoint writer shows up when you run VSSADMIN LIST WRITERS on the server that you ran configuresharepoint?
    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
     
  • jueves, 26 de enero de 2012 15:21
     
     
    Inicie sesión para votar
    0
    Does the sharepoint writer shows up when you run VSSADMIN LIST WRITERS on the server that you ran configuresharepoint?
    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Seems ok out?
    C:\Windows\system32>VSSADMIN LIST WRITERS
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    Writer name: 'SharePoint Services Writer'
       Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
       Writer Instance Id: {8db2458f-0b6f-470b-8920-7d93099e3341}
       State: [1] Stable
       Last error: No error
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {2e9473bf-25a5-47c6-88dc-0b26ba809b78}
       State: [1] Stable
       Last error: No error
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {3dc15fbd-ca16-4c4f-a305-d73630efd117}
       State: [1] Stable
       Last error: No error
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {c423a115-4e2c-40f9-8704-b66161d7a437}
       State: [1] Stable
       Last error: No error
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {b4a4db82-bec3-4152-8a08-6d6be93c9fb1}
       State: [1] Stable
       Last error: No error
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {2beeead5-f6e9-4320-ac42-f84db0f4012a}
       State: [1] Stable
       Last error: No error
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {7da1430a-0508-4c09-a507-83a0e4d4d31b}
       State: [1] Stable
       Last error: No error
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {c7b202b9-2113-490a-b1f0-ca2411fb06c8}
       State: [1] Stable
       Last error: No error
    Writer name: 'OSearch14 VSS Writer'
       Writer Id: {0ff1ce14-0201-0000-0000-000000000000}
       Writer Instance Id: {04be78b3-ddfc-4967-92c7-6e7d9961e4ee}
       State: [1] Stable
       Last error: No error
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {2a098d5c-0b77-4a3a-9e6a-696574de7280}
       State: [1] Stable
       Last error: No error
    C:\Windows\system32>
    Magnus
     
  • jueves, 26 de enero de 2012 21:27
     
     
    Inicie sesión para votar
    0

    Hello,

    The WSS Writer enumerates the configuration database and all content databases that are part of the farm. It also enumerates the SQL instances and the version of the SQL writer for each of these databases.  If not configured properly then we will not see the contents. If you go to the WFE and open up the DCOM config and go to the WSSCmdletsWrapper properties, then to the Identity tab. What credentials do you have there? The configuresharepoint.exe "should" have configured this for you if done correctly.  Do the credentials there differ from what you specified when you ran configuresharepoint.exe.?

     

    Thanks,
    Shane


     

     
  • viernes, 27 de enero de 2012 8:35
     
     
    Inicie sesión para votar
    0

    Hello,

    The WSS Writer enumerates the configuration database and all content databases that are part of the farm. It also enumerates the SQL instances and the version of the SQL writer for each of these databases.  If not configured properly then we will not see the contents. If you go to the WFE and open up the DCOM config and go to the WSSCmdletsWrapper properties, then to the Identity tab. What credentials do you have there? The configuresharepoint.exe "should" have configured this for you if done correctly.  Do the credentials there differ from what you specified when you ran configuresharepoint.exe.?

     

    Thanks,
    Shane


     

    Yes, it same account, it´s farm admin. 

     

    Magnus
     
  • viernes, 27 de enero de 2012 18:43
     
     
    Inicie sesión para votar
    0
    Hello Magnus,

    What version of DPM 2010 is this? In the DPM gui click on the "i" in the right hand corner. 
    Is it 7707 or earlier?


    Thanks,
    Shane
     
  • miércoles, 28 de marzo de 2012 12:32
     
     
    Inicie sesión para votar
    0

    Hi, sorry, missed your last question. 

    I got 3.0.7707.0.

    Thanks, Magnus

    Magnus

     
  • lunes, 16 de abril de 2012 17:50
     
     
    Inicie sesión para votar
    0

    Hello,

    If the DPM agent is installed on the WFE and the Backend SQL server, from this point we'd want to look at the MSDPMCurr.errlog on the DPM side, the DPMR log on the WFE and the backend SQL and the WSSCmdletswrapper.logs to see what datasources get enumerated.
    Unfortunately the logs are not that intuitive and not exactly something that can be easily done via DPM forum post.

    If you are still having this issue can you gather those logs from:
    Client Side Activity        %Program Files%\Microsoft Data Protection Manager\DPM\Temp
    DPM Server Activity       %Program Files%\Microsoft DPM\DPM\Temp

    I'd reproduce the issue, try to enumerate the SP farm via DPM as before, then gather those logs.  Search then from the bottom up for the Sharepoint Farm name.

    Thanks
    Shane

    Regards, Shane. 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. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • viernes, 27 de abril de 2012 11:05
     
     
    Inicie sesión para votar
    0

    Hi again, could I email logfiles to you? I have all files now, but can´t figure it out what is wrong. 

    I have also updated to DPM2012 with no luck. 

    Thanks, Magnus

    Magnus

     
  • viernes, 27 de abril de 2012 16:40
     
     
    Inicie sesión para votar
    0

    Hello,

    Updating to DPM 2012 changes things a bit.  After placing the DPM 2012 agent on all the servers in play (WFE and backend SQL server), are you sure you ran the configuresharepiont.exe?  http://technet.microsoft.com/en-us/library/hh758126.aspx

    Thanks
    Shane

    Regards, Shane. 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. This posting is provided "AS IS" with no warranties, and confers no rights.

     
  • viernes, 27 de abril de 2012 17:51
     
     
    Inicie sesión para votar
    0

    Yes, I ran “Stsadm –o unregisterwsswriter" first, and ConfigureSharePoint -EnableSharePointProtection.

    I have added a ticket to MS Support now, see what they say, added the logfiles that you requested earlier. 

    Thanks, Magnus

    Magnus