Hi @alexiiii what is the K10 version that you are using?
did you change the DR Backup policy's frequency to OnDemand? this issue was fixed in version 6.5.1

we Fixed an issue where K10 Disaster Recovery failed when the k10-disaster-recovery-policy was edited to be on demand.




BR,
​​​​​​​Ahmed Hagag

Hello @Hagag,
I was using the version 7.0.1, but just before that I tried to perform the K10 Disaster Recovery, all my k10-disaster-recovery-policy were failling. But my backups policies were working.
So I tried to uninstall kasten and perform a DR and then this error happend.

My next question is : How much time I a kasten DR backup can be used ? 

Regards

Now my k10-disaster-recovery-policy always fail with this error :
 

{"message":"Failed to stream backup to remote kopia repository on Kopia API server","function":"kasten.io/k10/kio/kanister/function.moverBackupToServer","linenumber":243,"file":"kasten.io/k10/kio/kanister/function/mover_backup_to_server.go:243","cause":{"message":"Failed to exec command in pod: command terminated with exit code 1.\nstdout: Snapshotting k10-admin@ff66c2ab-b5a4-4a6d-83f6-b2fa4904e0b5.catalog-svc.catalog-pv-claim:/mnt/k10state ...\r\nCreated snapshot with root k285582721e50e67b3537d87a58f1f54f and ID dc0afb8f292e5ea7fea4a7c70895cd5d in 30s\nstderr: kando stream push \u003csource\u003e  flags]\r\nFlags:\r\n-d, --dirPath string Specify a root directory path for the data stream (required)\r\n-f, --filePath string Specify a file name or path for the data stream (required)\r\n-h, --help help for push\r\nGlobal Flags:\r\n-c, --config-file string Custom config file for object storage repository configuration\r\n-p, --password string Specify the password for object storage repository (required)\r\n-v, --verbosity string Log level (debug, info, warn, error, fatal, panic) (default \"warning\")\r\n{\"File\":\"kando/main.go\",\"Function\":\"main.main\",\"Line\":22,\"error\":\"Failed to create kopia snapshot: Get \\\"http://10.44.25.227:8000/v0/backup\\\": dial tcp 10.44.25.227:8000: i/o timeout\",\"hostname\":\"catalog

Hi,

I encountered the exact same problem on our test system today until I noticed that I was “helm installing” an old version of k10restore.

I did a “helm repo update” and after correctly installing k10restore 7.0.1 it worked :D

Best Regards,
Lukas Rath

Hi @alexiiii you can verify the pervious comment using the below command

 

helm search repo kasten

Thanks

Ahmed Hagag