> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers-1/how-to/how-to-restore-a-disk-backup.md).
# How to Restore a Disk Backup
A backup is a copy of your data that lets you recover it if you lose it. In this tutorial you restore a disk from **Servers** or **Remote Desktop** one of its restore points.
The process is the same for the two types of backup offered by the service.
> #### ๐ What you get
>
> A disk restored to the state of a restore point, as a new disk or replacing an existing one, whichever suits you.
### The two types of backup
| Type | Frequency and retention |
| ------------------- | -------------------------------------------------------------------------------------------------- |
| Default (automatic) | Every hour (last 5 hours), every day at 00:10 (14 days) and every week, Sundays at 00:15 (8 weeks) |
| Manual (optional) | Manually launched weekly backups, with retention of up to 30 weeks |
> #### ๐ Backup is not the same as a snapshot
>
> Backup is your ongoing protection, with weeks of retention. A snapshot is a one-off rollback before a change.
>
> If you were looking for the latter, see [How to take a snapshot of a server and restore it](/docs-en/productos/servers/how-to/how-to-snapshot-and-restore-a-server.md).
### Before you start
* Log in to the Plenit platform.
* Have a **Servers** or **Remote Desktop** with a deployed server and at least one disk.
* That there is at least one restore point available for that disk.
### Step 1. Access restore points
1. Go to the subscription of **Servers** from its card.
2. Open the subsection **Backup** in the side menu. By default you will see **Schedules**, with the frequency, retention, and times.
3. Open **Restore Points**.
{/\* ๐ธ CAPTURE 1 ยท side menu Backup with the Restore Points subsection \*/}
### Step 2. Restore the disk
Expand the disk you want to restore to see its available backups. In the context menu of the chosen restore point, select **Restore**. You have three ways to do it:
| Option | What it does | When it fits |
| ---------------------------------------- | ------------------------------------------------------------------------------ | ----------------------------------------------- |
| New disk on the same server | Creates a disk with the restored content and attaches it to the current server | Recover data without touching the disk in use |
| New disk on another server or unattached | Creates the disk and connects it to another server, or leaves it unattached | Move data or have it available to connect later |
| Replace an existing disk | Creates the restored disk, connects it, and disconnects the previous one | Roll back a server's own disk |
Choose the option, click **Accept** and confirm. Restoration takes a few minutes and we'll notify you when it's done.
{/\* ๐ธ CAPTURE 2 ยท restore dialog with the options and the Accept button \*/}
> #### ๐ Replace does not delete the previous disk
>
> If you choose replace, we disconnect the current disk from the server, but we do not delete it. It remains there in case you need to go back to it, so the operation is reversible.
### Verify the restored disk
If you restored as a new disk, attached it to another server, or replaced it, it is worth checking from inside that the system sees it and that the data is accessible. A newly connected disk may appear **offline** or unmounted.
In Windows, from PowerShell:
```powershell
Get-Disk # a restored disk may show up Offline
Set-Disk -Number -IsOffline $false # bring it online if needed
Get-Volume # check the drive letter and status
```
On Linux:
```bash
lsblk # identify the disk and its partition
sudo mount /dev/sdX1 /mnt/restore # mount it to access the data
df -h
```
### If something does not fit
| Symptom | Likely cause | What to do |
| ----------------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------ |
| The restored disk does not appear in the system | It is offline after connecting it | Bring it online (`Set-Disk` in Windows) or check `lsblk` in Linux |
| You cannot see the restored data | The volume is not mounted | Mount it (`mount` in Linux) or assign it a drive letter in Windows |
| No restore points | None has been generated for that disk yet | Wait until at least one exists |
### Conclusion
With this, you recover a disk to the state of any of its restore points, as a new disk or replacing an existing one, and always without losing the original.
The key is not just knowing how to restore, but having done it before you need it: a backup you have never tested restoring is not a safety net, it is an assumption.
Once restoration is internalized, your copies become real backup.
---
# 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.plenit.com/docs-en/productos/servers-1/how-to/how-to-restore-a-disk-backup.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.