none
Bare-metal Restore FailedDC & Remote SQL Instance RRS feed

  • Question

  • Hi,

    in my client environment, we have DPM 2010 server with remote SQL 2008 instance with 1 DC. We already backup the DC with system protection (baremetal & system state) in DPM disk pool. The problem occur when we try to do baremetal restore the DC to network share folder (with DC already down). the DPM console immediately crash with a notification that tells dpm connection with remote sql is disconnected.

    ============================================================

    The following information was included with the event:

    Unable to connect to the database because of a fatal database error. It is unlikely that the database itself has been damaged.  Review the event log and take appropriate action. Make sure that SQL Server is running.

    Problem Details:
    <FatalServiceError><__System><ID>19</ID><Seq>0</Seq><TimeCreated>1/9/2012 3:10:28 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>SqlException</ExceptionType><ExceptionMessage>A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)</ExceptionMessage><ExceptionDetails>System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlContext.Open()
       at Microsoft.Internal.EnterpriseStorage.Dls.Utils.GlobalSetting.GetGlobalProperty(String propertyName)
       at Microsoft.Internal.EnterpriseStorage.Dls.Utils.ApplicationSettings.GetDatabaseVersion()
       at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CServiceModule.DoStartupValidation(CServiceModule* )
       at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CServiceModule.Initialize(CServiceModule* )
       at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CServiceModule.InitializeSecurity(CServiceModule* )</ExceptionDetails></FatalServiceError>

    ================================================================

    So, what the best practise for restoring the failed DC with DPM 2010 + remote SQL?

    Thank you :)



    Tuesday, January 10, 2012 4:02 AM

All replies

  • Hi

    Is this the configuration you have?

    Server 1 - DPM 2010

    Server 2 - DC

    Server 3 - SQL Server 2008 (hosting DPMDB)


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, January 10, 2012 5:09 AM
  • Hi Wilson,

     

    yup, that is my server configuration. So we cannot use DPM unless the DC is up, right?

    if this only one DC corrupt, down or stolen (?) we cant recover the files inside dpm at all?

     

    What if, we already recover the baremetal files to destination shared folder (from recovery process) before the DC down.

    Can we access that shared folder (after the DC down) from target recovery physical machine?

     

    im still a bit confused about BMR DC :(

     

    Thx.

     

    Tuesday, January 10, 2012 6:57 AM
  • If DC is down and there is no other DC then the restore will be done outside DPM.

    Like mounting the desided Recovery Point (mountvol) and sharing it.


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, January 10, 2012 8:49 AM
  • Thanks for the reply.

    Another solution is add additional DC right, so the SQL services still can authenticating through remaining DC?

     

     

    Thursday, January 12, 2012 3:23 AM
  • Yes,

    Always asure that you can have a working DC if everything else goes south(bad)....


    Thanks, Wilson Souza - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, January 12, 2012 3:27 AM