Importing restore point back into the same cluster from S3 if retired

As stated in the https://docs.kasten.io/latest/usage/migration.html#importing-applications  "Import policies are only supported for importing applications into a cluster that is different from the one where the application was captured." Therefore, to bring a retired restore point back to the same cluster, you must use DR restore, provided your DR backup included the restore point before it was retired. We also tested the immutable S3 scenario as you described, and the statement remains valid. Thanks

Thanks @michaelxue . Would it be possible to put in a feature request to prevent manually retiring restore points if they are on immutable storage? I am thinking to something similar to what Veeam does in relation to immutable backups? When I worked at a service provider often customers would ask me to test the immutability of the backups by going in and trying to delete them. 

cheers

Hi @Geoff Burke 

Sure, it's a valid request, and I can ask for this feature. Currently, the only option is to use DR restore as Michael said.

BR,
Ahmed Hagag

Thanks Guys, I appreciate the quick responses. By the way I love the new DR restore in the UI! 

​@Hagag Do you think they might implement something. I tested again today and same situation as last year. I can manually delete from the Kasten UI immutable backups. The are not deleted from the S3 bucket. I can do a Full DR to another cluster and I get back all the restore points. I can then restore. I can’t seem to get the restore points to be visible back in the Kasten dashboard in the original cluster.

Ideally, when someone attempts to remove the restore point from the UI and it is marked with the green lock immutable, an error should be displayed and the action disallowed

Hi ​@Geoff Burke 
 

Thanks again for raising this and for sharing your detailed testing scenarios. I wanted to let you know that I am actively tracking a feature request on this.

The acceptance criteria we’re tracking are:

• When a user attempts to retire a restore point, the system must check if it is part of an immutable storage policy.

• If the restore point is immutable, the manual retirement action should be prevented.

• The UI should display a clear and user-friendly error message, such as: “This restore point cannot be retired as it is protected by an immutable storage policy.”

• The action button (e.g., Retire Restore Point) should either be grayed out or include a tooltip explaining why the action is disabled for immutable backups.

I’ll keep monitoring progress on this request and will notify you as soon as I have any updates from our side.

P.S. could you please provide the the k10 version you have test with.

Best regards,
Ahmed Hagag

Thanks ​@Hagag much appreciated.

cheers

Geoff

sorry ​@Hagag forgot to mention versions. So in one instance the latest version. In another through the Harverster marketplace which is a few version behind, 8.0.1?