locked
Datastore Configuration RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    We have default Orchestrator DB and two custom DBs Orchestrator_runtime and Orchestrator_STAGING.

    We are planning to move all the three DB to new SQL servers. I went through blogs and collected information that 

    1.create a migration password, and to drop the master key

    2.Backup and Restore the DB to new server

    3. In New server, restore the master key, and drop the migration password

    After that in MS and RS, do the Datastore configuration. I want to know whether the datastore configuration should mapped to existing default ORCHESTRATOR DB or custom DBs. how can i find the datastore configured in my current server to check before move the DBs.

    1.Is there any specific procedure to follow the movement of above DBs to new SQL server?

    2. SCORCH 2016 to be installed after the movement of DBs or can be installed prior to the movement?

    3. Last time i did movement and installed the SCORCH 2016 by selecting existing DB and select Orchestrator. Installation went well and no errors but runbooks are not processing anything and no new users have been created in AD as part of provisioning runbook.

    Any help would be really appreciated.

    Regards,

    Vijay

    Thursday, December 14, 2017 4:41 PM

Answers

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    1. This is - in my opinion - the best guide to move an Orchestrator DB to another SQL instance: http://blogs.catapultsystems.com/mdowst/archive/2014/09/08/how-to-migrate-an-orchestrator-database/

    2. If I would move the Database, I would move the Database first an then install SQL 2016 with the option "Use existing Database" while installing SC 20106 Orchestrator.

    3. The problem was perhaps (!) that in the DB where the old Runbook Servers registered. So I would undeploy the Runbook Servers before starting the DB backup for movement.

    My other 2 cents:

    If you plan a to deploy a complete new environment I recommend to install it including all used Integration Packs. Make an Export of your Runbooks in the old environment selecting ALL "Global Settings" and "Global Configuration" and then import it to the new environment.

    This is best if you do not need the History Log of the old in the ne environment.

    If Update Rollup 4 for System Center 2016 Orchestrator make sure SQL Server Native Client is installed: http://sc-orchestrator.eu/update-rollup-4-for-system-center-2016-orchestrator-is-available/

    Regards,

    Stefan

    Visit go2azure.eu and my blog at www.sc-orchestrator.eu !

    Thursday, December 14, 2017 8:40 PM
    Answerer
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    How are things going? Please let us know if there is any progress.

    If the issue has been resolved, please mark it as "Answered".

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, December 27, 2017 8:17 AM