> For the complete documentation index, see [llms.txt](https://docs.cloud.olakrutrim.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud.olakrutrim.com/basics/core-infrastructure/storage/block-storage/backups.md).
# Backups
### What is a Backup?
A **Backup** is a durable, zone-resilient copy of a volume, optimized for disaster recovery. Unlike snapshots (which are stored locally), backups are replicated across availability zones or regions and are designed for long-term retention and restoration of your data.
Our backups are priced at **Rs 1.83 per GB Per Month.**
* Backup storage can be incremental or instant.
* Use backups to recover from accidental deletion, failures, or corruption.
* Can be created:
* **Manually**
* **Automatically via Backup Policies**
***
### Creating a Backup (Manual or Policy)
**Manual Backup:**
1. Go to **Volumes** → three-dot menu → **Create Instant Backup**.
2. Enter:
* **Name**
* **Description**
* **Tags**
3. Click **Create**.
Or
1. Go to Backup
2. Click on “Create Instant Backup”
3. Select the volume or VM for which you want to create a Backup
4. Enter:
* **Name**
* **Description**
* **Tags**
5. Click **Create**.
**Policy-Based Backup:**
* You can create policy-based backup in two ways;
* Approach 1;
* Go to Backup
* Click on "Create Backup policies"
* Select either a VM Backup to create a backup for a VM or a Volume Backup for a volume
* Select the VM or volume
* Select the maximum number of backups that you want to create for the respective volume or VM
* Enter the policy name
* Enter the description
* Select appropriate values for the scheduler
* Click on "Create Policy"
* This will create a Backup for the scheduler you have created
* Approach 2;
* While you create your volume, you can add the backup policies, which will create a backup for the volume
***
### Backup Creation Logic
* The first backup or any instant backups = **Primary (#1)**.
* Additional backups follow: `#2`, `#3`, ..., up to policy-defined limit for both Instant and Incremental backups
* In case of Incremental backups `#2`, `#3` will become Delta backups.
* When the limit is hit:
* The oldest non-primary backup is overwritten in case of Incremental backups, and the oldest backup will be overwritten in case of non-incremental backups
* \#2 will become the newest backup in case of Incremental backups, and #1 will become the newest backup in case of non-incremental backups.
***
### Restoring a Backup
1. Go to **Backups**.
2. Click on the three dots
3. Click **Restore Backup**.
4. A **new volume** will be created:
* With the primary + delta changes
* Restored to the exact point in time
***
### Deleting a Backup
1. Navigate to **Backups**.
2. Click **Delete**.
3. Primary backup cannot be deleted unless a new one is marked as Primary.
***
### Billing and Pricing
Our volumes are priced at **Rs 1.83 per GB Per Month**, one of the cheapest prices in the world.
Even though it’s priced at a Monthly rate, the billing happens every hour at a rate of Rs 0.003 per GB per hour. You will be charged for the total storage you have used in the hour across all your backups. For example, if you have used 100 GB across all your backups during the hour, you will be charged 100\*0.003 = Rs 0.30.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cloud.olakrutrim.com/basics/core-infrastructure/storage/block-storage/backups.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.