Flexible servers in different Resource Groups and Kyvos resources in different Resource Groups are not supported.
The DNS zone of the Flexible servers must be in the same Resource Group.
Creation of a Flexible Server instance
Anchor
creation
creation
...
Panel
panelIconId
atlassian-info
panelIcon
:info:
bgColor
#FFFAE6
Important
Before initiating the migration process, ensure all applications connecting to the production server are stopped. Refer to Microsoft documentation for further details.
When upgrade operation is started and reaches to a stage where services of BI Server is stopped then start migration of Single server data to the Flexible server. Perform this step in an overlapping manner with the Kyvos upgrade to save the time and thus minimize the downtime window as in this particular upgrade additional activities (like data migration to Flexible server from single server as well as switching the system from single server to flexible server) are also required which if not done in an overlapping manner then it can increase downtime window.
Panel
panelIconId
atlassian-note
panelIcon
:note:
bgColor
#DEEBFF
Note
The steps to migrate data from the Single Server Repository to the Flexible Server remain the same for Kyvos and Kyvos Manager.
To migrate from Single Server to Flexible Server, you need to perform the following steps for Kyvos Manager and Kyvos separately using their corresponding instances.
