...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Note You need to manually create nodes for Kyvos Manager from the terminal. |
Prerequisites
Create a new node for Kyvos Manager, and ensure the following:
This node should have the same set of permissions in terms of roles, tags (UsedBy / CreatedBy, CLUSTER_ID, ROLE : KM, LAYER : KM_Service), network access rules and permissions (VirtaulNetwork, Subnet, Security Group, Resource Group), credentials, size and instance type, disk organization (mount point, disks, directories where Kyvos Manager and Kyvos installed) as that of the original Kyvos Manager node which doesn’t exist anymore.
For access purposes, you need to either add the same security group or the security group added must have the same set of access rules and permissions.
If Secrets Manager/Key Vault is in use, then ensure that the roles assigned to the new Kyvos Manager node have access to the Secrets Manager/Key Vault.
Ensure that roles assigned to the new Kyvos Manager node have access to the S3 bucket/ABFS account.
If the Kyvos Manager node is created by attaching a disk image of any old Kyvos Manager node, then ensure the below in mentioned sequence:
Agent service is stopped on that node.
Agent cron entry deleted from crontab.
Kyvos Manager Agent and Kyvos folders were deleted from it.
The OS commands must be present in the path of a non-interactive login session for the user account used to log in to the nodes.
To restore Kyvos Manager on the new node, download a script file named disaster-recovery-kyvosmanager.sh from the DFS at path <engine_work>/setup/scripts/ and execute that script. This will restore the Kyvos Manager server and the Kyvos Manager service will start automatically.
...