locked
Recoverying a site server using remote SQL cluster RRS feed

  • Question

  • This is a lab, so don´t wonder why I´m doing this :)

    Previously I had SCCM 2012 SP1 installation on W2008R2 and SQL2008 R2, SQL installation was local. I already tested the recovery scenario succsessfully, if SQL would be a local installation (W2012, SQL 2012).

    I moved my entire lab to a Hyper-V, and I have SQL Cluster 2012 installation. The point is to install all System Center products and make them use this SQL "centralized" cluster.

    Now I want to recover/reinstall my site server, using a DB which was saved during Backup Maintanance Task, but point it to a remote SQL (cluster).

    - Normal recovery process seems to require local SQL, because previous installation has a local SQL configuration which local hostname.
    - I was trying to think about, how to import my old database to a SQL cluster, but I have no idea how to do that. It seems to require other SQL server, where from to import, no chance to browsing files (I might be wrong about this).

    So is this even possible to accomplish?

    Friday, July 19, 2013 9:13 AM

Answers

  • I managed to solve this by setting on both end a SQL client settings to not require encryption, and to trust server certificate. This can be found behind SQL native client properties.
    Tuesday, July 30, 2013 5:41 AM

All replies

  • I´m now fallowing these instructions so far so good;

    http://www.systemcenterblog.nl/2012/06/01/moving-a-configmgr-2012-database-to-a-sql-cluster/

    I´ve backup database, moved to cluster and opened there okay. But when I´m doing the reconfiguration and entering new SQL server, during the configuration from ConfigMgrSetup.log I get these:

    SQL Server Native Client 11.0 SSL Provider: The Certificate chain was issued by the authority that is not trusted.
    SQL Connection Failed (SMS Access)

    Also in event viewer I see these:
    Event ID 36882: The Certificate received from the remote server was issued by untrusted certificate authority. Because of this, none of the data contained in certificate can be validated. The SSL connection request failed.


    No idea what to do here...
    Monday, July 29, 2013 1:08 PM
  • I managed to solve this by setting on both end a SQL client settings to not require encryption, and to trust server certificate. This can be found behind SQL native client properties.
    Tuesday, July 30, 2013 5:41 AM