> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/frequently-asked-questions/can-i-lock-preserve-instance-from-deletion.md).

# Can I Lock/Preserve Instance From Deletion?

## Problem

Is it possible to lock/preserve an instance from accidental deletion?

## Environment

* Platform9 Managed OpenStack - All Versions

## Answer

Yes, there is a way to prevent accidental deletion on instances performed by **non-admin** users by using the following command.

{% tabs %}
{% tab title="None" %}

```none
$ openstack server lock [server] [[server] ...]
```

{% endtab %}
{% endtabs %}

However, administrators can still perform several actions mentioned in [OpenStack documentation](https://docs.openstack.org/api-guide/compute/server_concepts.html), on the server even though the server is locked.

**Note:** By default, only owner or administrator can lock the sever, and administrator can overwrite owner's lock along with the *locked\_reason* if it is specified.

Unlock will unlock a server in locked state so additional operations can be performed on the server by non-admin users. By default, only owner or administrator can unlock the server.

## Additional Information

A soft delete functionality is work in progress in the pipeline and is currently targeted for a 4.6 release; which may allow one to retain the actual data despite accidental delete requests.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/frequently-asked-questions/can-i-lock-preserve-instance-from-deletion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.