Product documentation
Citrix Virtual Apps and Desktops
Service Current Release 2407 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR
View PDF

Migrating from cloud to cloud

December 5, 2024
Contributed by: 
C

Automated Configuration allows you to automate moving your cloud configuration to another cloud site or allowing you to restore your own cloud site.

Using Automated Configuration can solve many use cases:

  • Syncing your site from test or stage to production
  • Backing up and restoring your configuration
  • Reaching resource limits
  • Migrating from one region to another

In Studio on Citrix Cloud, see the Backup and Restore node for information about Automated Configuration and how it can be used to migrate your configuration from cloud to cloud.

migrate to cloud full config

Prerequisites for migrating your configuration

For backing up and restoring your configuration, you need:

  • Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) provisioned.
  • An active resource location with Connector installed.
  • Connectivity to sites accessing Citrix Cloud must be allowed and available. For more information, see System and Connectivity Requirements.

Note:

MCS cannot be backed up from the cloud using Automated Configuration.

Backing up your Citrix DaaS configuration

Important:

  • You must have your CustomerInfo.yml file with your customer ID, client ID, and the secret key information included. For more information on how to retrieve your customer ID, client ID and secret key, see Generating the customer ID, client ID, and secret key. For information on how to add this information to the CustomerInfo.yml file, see Populating customer info file.
  • When you run the backup commands, the CustomerInfo.yml must have the details of the source site customer from where you are taking the backup.
  • When you run the restore commands, the CustomerInfo.yml must have the details of the destination site customer to where you are restoring the configurations.
  • The ZoneMapping.yml file must include information that maps your resource locations in the cloud. For more information on how to map your zones, see Populating zone mapping file.
  • If you have host connections, you must input the corresponding info in the CvadAcSecurity.yml file.
  1. Install Automated Configuration.

    Note:

    For cloud-to-cloud migration, Automated Configuration can be installed on a machine having access to the internet that the administrator has direct access to.

  2. Double-click the Auto Config icon. A PowerShell window appears.

  3. Run the following command to do a backup.

    Backup-CvadAcToFile

After you run any cmdlet for the first time, an export folder with the .yml configuration files and logs is created. The folder is at %HOMEPATH%\Documents\Citrix\AutoConfig.

If you encounter any errors or exceptions, see the Fixups section in the log file.

Restoring your configuration to Citrix DaaS

  1. Double-click the Auto Config icon. A PowerShell window appears.

  2. Run the following command to do a restore.

    Restore-CvadAcToSite -RestoreFolder <folder path of the backup files>

Verify the expected state with the new current state.

After you run the cmdlet, an export folder with the .yml configuration files and logs is created. The folder is at %HOMEPATH%\Documents\Citrix\AutoConfig.

If you encounter any errors or exceptions, see the Fixups section in the log file.

The backup and restore process protects you from unintentional cloud site configuration changes or corruption. While Automated Configuration makes backups each time a change is made, this backup reflects the state of the cloud site configuration before the changes. Protecting yourself requires that you periodically back up your cloud site configuration and saving it in a safe place. If an undesirable change or corruption takes place, the backup can be used to fix the change or corruption at either a granular or full site configuration level.

Granular migration

Important:

For more information on component migration orders, see Component migration order.

Restoring entire components

Restoring one component involves selecting one or more component parameters.

To restore the entire delivery group and machine catalog components, follow this example:

Restore-CvadAcToSite -RestoreFolder %HOMEPATH%\Documents\Citrix\AutoConfig/Backup_yyyy_mm_dd_hh_mm_ss

Restoring component members

Restoring one or more component members makes use of the IncludeByName feature. The Restore cmdlet is invoked with the RestoreFolder parameter along with the selected single component and the inclusion list.

To restore two group policies from a backup, follow this example:

Restore-CvadAcToSite -RestoreFolder %HOMEPATH%\Documents\Citrix\AutoConfig/Backup_yyyy_mm_dd_hh_mm_ss

-GroupPolicies -IncludeByName Policy1,Policy2

-DeliveryGroups -MachineCatalogs

Restoring the entire cloud site configuration

Restoring the full cloud site configuration means selecting all components to restore.

To restore the entire cloud site configuration, follow this example:

Restore-CvadAcToSite -RestoreFolder %HOMEPATH%\Documents\Citrix\AutoConfig/Backup_yyyy_mm_dd_hh_mm_ss

Activating sites

Site activation allows you to control which site is active and controls your resources. For more information, see Activating sites.

Migrating from cloud to cloud
December 5, 2024
Contributed by: 
C
December 5, 2024
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.