Migrating Orchestrator Packages From Azure Or S3 To External Storage

News Knowledge Base
1

How can Orchestrator packages be migrated from Azure or S3 storage to external storage after a version upgrade to 22.10.x?

Those who have been using Azure or S3 storage for Orchestrator packages prior to the 22.10 update and then switch to external storage may find that packages are not automatically migrated to the new storage location. This requires manual intervention to copy the packages using the Azcopy utility.


Resolution:

  1. Confirm Orchestrator Library Storage:
  • Confirm values of current Orchestrator library storage in blob matches:
    • container name = orchestrator-host
  1. Confirm Orchestrator Packages Storage:
  • Confirm values of current Orchestrator packages storage in blob matches:
    • container name = orchestrator-xxxxxxxxxxxxxx (the specific ID value needs to be obtained here)
  1. (a) Use Azcopy to Migrate Packages:
  • # Command template
azcopy sync "/" "//folder/folder/" --recursive=true

    # Example command (substitute placeholders with your specific details)
    
    azcopy sync '“https://.blob.core.windows.net/<orchestrator-???>” “https://.blob.core.windows.net/uipathstore-UiPath-as-orchestrator-prod/orchestrator/<Orchestrator-???>/” --recursive=true

  1. (b) Use Azcopy to Migrate Libraries:
  • # Command template
azcopy sync "/" "//folder/folder/" --recursive=true

    # Example command (substitute placeholders with your specific details)
    
​​​​​​​    azcopy sync '“https://.blob.core.windows.net/orchestrator-host” “https://.blob.core.windows.net/uipathstore-UiPath-as-orchestrator-prod/orchestrator/Orchestrator-Host/” --recursive=true