> 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/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** from 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 recovered to the state of a restore point, as a new disk or replacing an existing one, whichever suits you best.
### The two types of backup
| Type | Frequency and retention |
| ------------------- | ----------------------------------------------------------------------------------------------- |
| Default (automatic) | Every hour (last 5 h), every day at 00:10 (14 days), and every week, Sundays at 00:15 (8 weeks) |
| Manual (optional) | Weekly backups launched manually, retained for up to 30 weeks |
> #### ๐ Backup is not the same as snapshot
>
> Backup is your ongoing protection, with retention measured in weeks. A snapshot is a one-time rollback before a change.
>
> If you were looking for the latter, see [How to take a server snapshot and restore it](/docs-en/productos/servers/how-to/how-to-snapshot-and-restore-a-server.md).
### Before you begin
* Log in to the Plenit platform.
* Have a subscription to **Servers** or **Remote Desktop** with a deployed server and at least one disk.
* Have at least one restore point available for that disk.
### Step 1. Access the restore points
1. Enter the subscription of **Servers** from its card.
2. Open the subsection **Backup** from the side menu. By default you will see **Schedules**, with the frequency, retention, and schedules.
3. Open **Restore Points**.
{/\* ๐ธ SCREENSHOT 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 for 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 the server's own disk |
Choose the option, click **Accept** and confirm. The restore takes a few minutes and we will notify you when it is done.
{/\* ๐ธ SCREENSHOT 2 ยท restore dialog with the options and the Accept button \*/}
> #### ๐ Replacing 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 stays there in case you need to go back to it, so the operation is reversible.
### Verify the restored disk
If you restored it as a new disk, attached it to another server, or replaced it, it is a good idea to check 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 appear 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 match
| 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 |
| There are no restore points | None has been generated yet for that disk | 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.
With the restore process understood, your backups become real protection.
---
# 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/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.