Wednesday, February 1, 2017

Database migration in XenApp 7.6 and XenDesktop 7.6 /7.8/7.11

Recently I have migrated the XenDesktop/XenApp 7.6 Citrix platform database to a new SQL server.


Steps followed:


1. Closed all consoles on first Delivery controller
2. Stopped DB logging and monitoring
     Stop the Configuration Logging Service
  1. Start Windows PowerShell as an Administrator and run:
    asnp Citrix*
  1. Before moving the database, stop configuration Logging. In PowerShell, run:
    Set-LogSite -State "Disabled"

  2.  Stop Monitoring
    In PowerShell, run:
    Set-MonitorConfiguration -DataCollectionEnabled $False

3. Took the full back up on SQL server and restored to new SQL server with all roles and permissions.
4. Migrate first controller to database
    1. Remove the existing Database connections
        Open Power shell in administrator mode and Run below power shell commands
               ## ## First unregister the Delivery Controllers from the current database:
               ## Note: AdminDBConnection must be the last command.
               Set-ConfigDBConnection -DBConnection $null
               Set-AcctDBConnection -DBConnection $null
               Set-AnalyticsDBConnection -DBConnection $null             #  7.6 and newer
               Set-AppLibDBConnection -DBConnection $null                  # 7.8 and newer
               Set-OrchDBConnection -DBConnection $null                    #  7.11 and newer
                Set-TrustDBConnection -DBConnection $null                    #  7.11 and newer

                Set-HypDBConnection -DBConnection $null
                Set-ProvDBConnection -DBConnection $null
                Set-BrokerDBConnection -DBConnection $null
                Set-EnvTestDBConnection -DBConnection $null
                Set-SfDBConnection -DBConnection $null
                Set-MonitorDBConnection -DataStore Monitor -DBConnection $null
                Set-MonitorDBConnection -DBConnection $null
                Set-LogDBConnection -DataStore Logging -DBConnection $null
                Set-LogDBConnection -DBConnection $null
                Set-AdminDBConnection -DBConnection $null -force
5. If you see the following error, you must restart all the Citrix services:



After restarting all the Citrix services, you must restart the server:
Get-Service Citrix* | Stop-Service -Force
​Get-Service Citrix* | Start-Service



6. Redirected the Controller to the new database
     Run below commands from Power shell in admin mode

         ## Replace with the New SQL server, and instance if present
         ## Replace with the name of your restored Database
         ## Note: AdminDBConnection should be first

        $ServerName=""
        $SiteDBName = ""
        $LogDBName = ""
        $MonitorDBName = ""
        $cs="Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True"
        $csLogging= "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True"
        $csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True"

       Set-AdminDBConnection -DBConnection $cs
       Set-ConfigDBConnection -DBConnection $cs
      Set-AcctDBConnection -DBConnection $cs
      Set-AnalyticsDBConnection -DBConnection $cs               # 7.6 and newer
      Set-HypDBConnection -DBConnection $cs             
      Set-ProvDBConnection -DBConnection $cs
      Set-AppLibDBConnection –DBConnection $cs                 #  7.8 and newer
      Set-OrchDBConnection –DBConnection $cs                    # 7.11 and newer
      Set-TrustDBConnection –DBConnection $cs                  #  7.11 and newer
      Set-PvsVmDBConnection -DBConnection $cs
     Set-BrokerDBConnection -DBConnection $cs
     Set-EnvTestDBConnection -DBConnection $cs
     Set-SfDBConnection -DBConnection $cs
     Set-LogDBConnection -DBConnection $cs
     Set-LogDBConnection -DataStore Logging -DBConnection $null
     Set-LogDBConnection -DBConnection $null
     Set-LogDBConnection -DBConnection $cs
     Set-LogDBConnection -DataStore Logging -DBConnection $csLogging
     Set-MonitorDBConnection -DBConnection $cs
     Set-MonitorDBConnection -DataStore Monitor -DBConnection $null
     Set-MonitorDBConnection -DBConnection $null
     Set-MonitorDBConnection -DBConnection $cs
     Set-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring

7.  After moving the Delivery Controllers, on each of them enabled Monitoring and Logging:
            ##Enable Monitoring
             Set-MonitorConfiguration -DataCollectionEnabled $true
           
          ##Enable Configuration Logging
             Set-LogSite -State "Enabled"
           
8. Restarted the Citrix Studio.
9. From each Controller, I have tested the database connection services to the new database:

          Get-AcctServiceStatus
          Get-AdminServiceStatus
          Get-AnalyticsServiceStatus                # 7.6 and newer
          Get-AppLibServiceStatus                   # 7.8 and newer
          Get-BrokerServiceStatus
          Get-ConfigServiceStatus
          Get-EnvTestServiceStatus
          Get-HypServiceStatus
         Get-LogServiceStatus
         Get-MonitorServiceStatus
         Get-OrchServiceStatus                   #  7.11 and newer
         Get-TrustServiceStatus                  #  7.11 and newer
        Get-ProvServiceStatus
        Get-SfServiceStatus

The Citrix article on DB migration is https://support.citrix.com/article/CTX140319 .

5 comments:

  1. hello did you do this guide on each controller individually ?for example i have 2 delivery controller on the same network and 1 on a different network, so i must do this guide for each one of them?

    ReplyDelete
    Replies
    1. Techie: Database Migration In Xenapp 7.6 And Xendesktop 7.6 /7.8/7.11 >>>>> Download Now

      >>>>> Download Full

      Techie: Database Migration In Xenapp 7.6 And Xendesktop 7.6 /7.8/7.11 >>>>> Download LINK

      >>>>> Download Now

      Techie: Database Migration In Xenapp 7.6 And Xendesktop 7.6 /7.8/7.11 >>>>> Download Full

      >>>>> Download LINK JS

      Delete
  2. Did you need to run the commands on both controllers? I am about to do this myself...

    ReplyDelete
  3. The data migration processisa complex process, because it involves not only data, but also the people and departments that own and manage that data. The data migration plan should address these people and departments. It should also address any data governance, such as data security and data ownership. One reason it's so important to plan for data governance is that if you don't plan for it, you might find that your data migration will fail.

    ReplyDelete
  4. Amazon Web migration Services is the market leader in cloud computing services, so you know that moving your applications there is a good idea. But how do you get your data there? The answer depends on your data. If your data is largely static, you can move it using an FTP client or a tool like RoboMover.

    ReplyDelete