Skip to main content
  • EN

Hello Team,

 

When creating a backup policy with export to external storage, a migration token is being created in form of a kubernetes secret in `kasten-io` namespace. The token can be then used in import policy, to migrate the data between two clusters.

key values redacted for brevity.

When we were trying to define the secret and token by ourselves, we received the following errors:

It seems like the secret, apart from being base64 encoded is encrypted (perhaps using Kasten’s master key?), therefore, when it tries to decipher a custom secret, the result is an empty string.

Is it possible to define custom migration token in backup policies? This would be helpful as we are deploying Kasten’s blueprints, policies, bindings etc. using Kustomize and instead of providing the plain receive string to the import policy, we would like to patch the receiveString using the custom token value from the secret as a target.

Thanks in advance.

@jaiganeshjk 

@peterturnip , Thanks for opening this topic.

This migrationToken/receiveString is a encoded string that policy controller in k10 creates and adds to the policy. 
This basically has the metadata about the export location, connection parameters etc. You cannot specify a custom migration string to use it for import.

It must be created by k10 based on few variables in your location profile and the policy that you are creating. 

 

Comment


Terms & Conditions