...
The process of migrating from a single server to a flexible involves two steps.
Granting permission
Migrating data
Granting permission
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
Important The Single server instance from which data is migrated to Flexible Server, either this Single server must be kept running to allow rollback if required later.
It is suggested to take dump of Single server and preserve that dump to some secure location before terminating that Single server instance. This dump will be required to create a new single server with this dump imported in it when rollback of Kyvos is required to that last version of Kyvos which was supporting single server. |
...
Grant permission for data access from single server for migrating it to flexible server. To do this, open the single server for Kyvos and Kyvos Manager. Go to Connection Security and switch Allow access to Azure services to Yes.
Migrating Repository data from Single Server to Flexible Server
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
Important 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. |
...
