Skip to main content
  • EN

We are testing out Kasten to do a Export/Import to migrate an application from one AKS cluster to another.  The export is working fine and we are able to export to Azure blobstorage. Verified that the files and directories were also created successfully. However, when we do an import we are running into the following problem:

cause:
  cause:
    cause:
      cause:
        - cause:
            Code: 1
            Err: {}
          file: kasten.io/k10/kio/kopia/repository.go:441
          function: kasten.io/k10/kio/kopia.CreateKopiaRepository
          linenumber: 441
          message: Failed to create the backup repository
        - cause:
            Code: 1
            Err: {}
          file: kasten.io/k10/kio/kopia/repository.go:528
          function: kasten.io/k10/kio/kopia.ConnectToKopiaRepository
          linenumber: 528
          message: "Failed to connect to the backup repository: repository not found"
      file: kasten.io/k10/kio/kopiaapiserver/api_server.go:200
      function: kasten.io/k10/kio/kopiaapiserver.SetupAPIServer
      linenumber: 200
      message: Failed to initialize Kopia API server
    file: kasten.io/k10/kio/exec/phases/phase/migrate.go:626
    function: kasten.io/k10/kio/exec/phases/phase.importDataFromKopiaCollection
    linenumber: 626
    message: Failed to prepare Kopia API server for migration
  file: kasten.io/k10/kio/exec/phases/phase/migrate.go:495
  function: kasten.io/k10/kio/exec/phases/phase.importUsingKopia
  linenumber: 495
  message: Failed to import collection from kopia repository
message: Job failed to be executed
fields: ]
 

Any tips on what might be the problem?

Hello Anthony,

 

Could you please gather your debug logs, and please look through the logging-svc to narrow down the cause? This could be related to multiple things, and looking for the “cause” in the logs should help narrow down the issue’s.

You can now simply access the debug logs from within the support page in K10 UI.

 

Thanks

Emmanuel

Emmanuel - thanks for picking this up.  So turns out one of my colleagues uninstall and reinstalled k10 (same aks cluster, same storage acct, and same everything with 1 exception - this time she had added an ingress route vs doing port forwarding for the UI) and now it is magically working.  The downside is i lost the logs. We’ll continue our testing and see if we can repro the problem.

Hello Anthony,

 

That's great to hear. Doesn't sound like you would need the logs at this point.

 

Thanks

Emmanuel

Comment


Terms & Conditions