none
DPM sharepoint backup agent configuration problem RRS feed

  • Question

  • Hi,

    I have o problem with DPM 2010 sharepoint backup. Here is a brief description of the problem.

    Active Directory with 2 (or more trees)
        Company.xyz  
            -sharepoint 2010 services (srv1.company.xyz)+Agent
        Company.abc  
            -SQL Server with inscance in1 (sql.company.abc\in1)+Agent
            -DPM 2010 Server
       
    Sharepoint configuration has FQDN names for SQL (sql.company.abc\in1)
    Configuresharepoint.exe have been run.
    Agents installed

    Problem:
    When trying to create sharepoint protection from DPM-manager I get an error that sql.company.xyz (???) is not having Agents. Agent log file gives this information

    0FAC 0D50 08/18 06:46:23.773 03 machinename.cpp(282) [0000000002F7E2D0]  WARNING Failed: Hr: = [0x80005008] : d: lVal : pds->GetColumn(hSearch, c_aszAttributes[0], &ascADsPath)
    0FAC 0D50 08/18 06:46:23.773 03 localmachinename.cpp(135)   WARNING GetDnsDomainSuffix failed. wszDnsDomainName = company.abc
    0FAC 0D50 08/18 06:46:23.773 31 vssbaserequestor.cpp(1528)   NORMAL DependencyLogicalPath SQL\SQL\in1 refers to a Component with LogicalPath SQL\in1 on LocalMachine SQL.company.abc

    DMP Manager gives error ID:s 956 and 32008

    It seems to me thar somehow agent is reading wrong DB-path, but in DPM manager the path under sharepoint folder is showing the right db path to configuration db.

    Any Ideas?:)
       

    Wednesday, August 18, 2010 6:58 AM

All replies

  • Hi,

    I have o problem with DPM 2010 sharepoint backup. Here is a brief description of the problem.

    Active Directory with 2 (or more trees)
        Company.xyz  
            -sharepoint 2010 services (srv1.company.xyz)+Agent
        Company.abc  
            -SQL Server with inscance in1 (sql.company.abc\in1)+Agent
            -DPM 2010 Server
       
    Sharepoint configuration has FQDN names for SQL (sql.company.abc\in1)
    Configuresharepoint.exe have been run.
    Agents installed

    Problem:
    When trying to create sharepoint protection from DPM-manager I get an error that sql.company.xyz (???) is not having Agents. Agent log file gives this information

    0FAC 0D50 08/18 06:46:23.773 03 machinename.cpp(282) [0000000002F7E2D0]  WARNING Failed: Hr: = [0x80005008] : d: lVal : pds->GetColumn(hSearch, c_aszAttributes[0], &ascADsPath)
    0FAC 0D50 08/18 06:46:23.773 03 localmachinename.cpp(135)   WARNING GetDnsDomainSuffix failed. wszDnsDomainName = company.abc
    0FAC 0D50 08/18 06:46:23.773 31 vssbaserequestor.cpp(1528)   NORMAL DependencyLogicalPath SQL\SQL\in1 refers to a Component with LogicalPath SQL\in1 on LocalMachine SQL.company.abc

    DMP Manager gives error ID:s 956 and 32008

    It seems to me thar somehow agent is reading wrong DB-path, but in DPM manager the path under sharepoint folder is showing the right db path to configuration db.

    Any Ideas?:)
       


    Sorry, made on typing error when replasing names from log:)

    0FAC 0D50 08/18 06:46:23.773 03 machinename.cpp(282) [0000000002F7E2D0]  WARNING Failed: Hr: = [0x80005008] : d: lVal : pds->GetColumn(hSearch, c_aszAttributes[0], &ascADsPath)
    0FAC 0D50 08/18 06:46:23.773 03 localmachinename.cpp(135)   WARNING GetDnsDomainSuffix failed. wszDnsDomainName = company.xyz
    0FAC 0D50 08/18 06:46:23.773 31 vssbaserequestor.cpp(1528)   NORMAL DependencyLogicalPath SQL\SQL\in1 refers to a Component with LogicalPath SQL\in1 on LocalMachine SQL.company.xyz

    Wednesday, August 18, 2010 7:01 AM
  • Mika,

    There is issue with the SharePoint writer to report the correct domain name when WFE and SQL Servers are in different domain. You can try the following:

    1. Install SQL Client Connectivity Components on WFE.

    2.On the WFE, Add TCP/IP SQL alias using SQL Server Configuration Manager under SQL Native Client Configuration. Details -  Alias Name = sql,  Server Name = sql.company.abc, port = port number of sql.company.abc\in1 . ensure the connEction to sql.company.abc\in1 is fine from WFE using SQL alias "sql".

    You would be able to protect the farm after adding this alias correctly.

     

    Tuesday, September 14, 2010 7:16 AM