...
Creation of Flexible Server instance
Data migration
Configuration
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
|
Note |
Creation of a Flexible Server instance
...
Download the FlexibleServerKyvosManagerRepository.json templates from here to create a Flexible PostgreSQL Server.
Deploy the template and while providing parameters, ensure that you keep the repository’s password and username the same as currently in use on the single server.
...
Download the FlexibleServerKyvosRepository.json templates from here to create a Flexible PostgreSQL Server.
Deploy the template and while providing parameters, ensure that you keep the repository’s password and username the same as currently in use on the single server.
...
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 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.
|
...
Login into Kyvos Manager, navigate to Utilities then refer to the https://kyvosdocumentation.atlassian.net/wiki/spaces/KD20235/pages/29922859/Manage + Kyvos +Repository#KyvosMigrationRepository section.
After completing the upgrade process and configuring Flexible server, you must start Kyvos services.
...
