> 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-back-up-a-server.md).

# How to Back Up a Server

A backup stores an image of the disk at a specific moment so it can be recovered later.

In addition to the automatic backups that already run by default, you can launch a **manual** when you want, for example just before an important change. In this tutorial you create that one-off backup.

> #### 👍 What you get
>
> A backup launched on demand and, once it finishes processing, a new restore point available for that disk.

### When to launch a manual backup

Automatic backups cover day-to-day needs. The manual one makes sense when you don’t want to wait for the next scheduled backup: before an update, a migration, or any change for which you want a recent rollback point.

| Mechanism        | Purpose                                                             |
| ---------------- | ------------------------------------------------------------------- |
| Automatic backup | Continuous protection, without intervention                         |
| Manual backup    | An on-demand restore point, before a change                         |
| Snapshot         | Quick, temporary rollback of the VM; it does not replace the backup |

### Before you begin

* Log in to the Plenit platform.
* Have a subscription to **Servers** or **Remote Desktop** enabled.

### Step 1. Access the Backup settings

1. Enter the subscription of **Servers** from its card.
2. Open the subsection **Backup** from the left side menu.

{/\* 📸 SCREENSHOT 1 · left sidebar menu with the Backup subsection \*/}

![Access to the subscription's Backup subsection](https://REEMPLAZA-URL/servidores-howto-backup-manual-01.png)

### Step 2. Create the manual backup

In **Backup** you will see the section **Schedules**, with the periodic backups, their retention, and their schedules. Click **New Schedule** and fill in the window:

1. **Server**: the server to act on.
2. **Disk**: the disk to copy from.
3. **Frequency**: choose **Manual** for a one-off backup.
4. **Name**: a name to identify it.

Click **Accept**. The backup is processed and, when it finishes, it appears in the tab **Restore Points**.

{/\* 📸 SCREENSHOT 2 · New schedule window with Server, Disk, Frequency Manual and Name \*/}

![Manual backup configuration with Manual frequency](https://REEMPLAZA-URL/servidores-howto-backup-manual-02.png)

> #### 📘 The same screen is used for recurring backups
>
> If instead of **Manual** you choose a weekly or monthly frequency, you set up recurring backups from this same window.

> #### 📘 For data with a database, ensure consistency
>
> A backup taken while the database is writing may be incomplete. If possible, stop the service just before and start it again afterward.
>
> In Windows, from PowerShell:
>
> ```powershell
> Stop-Service -Name "MSSQLSERVER"
> ```
>
> On Linux:
>
> ```bash
> sudo systemctl stop <service>
> ```

### Verify the backup

The backup takes a little while to process. When it finishes, open it in **Restore Points**: if it appears there with its name, it is ready to be used in a restore.

### If something does not match

| Symptom                        | Likely cause                                    | What to do                                        |
| ------------------------------ | ----------------------------------------------- | ------------------------------------------------- |
| The backup does not appear yet | It is still being processed                     | Wait a few minutes and refresh **Restore Points** |
| Concerns about data integrity  | It was copied while the application was writing | Repeat the backup with the service stopped        |

### Conclusion

With this, you generate an on-demand restore point, without waiting for the next scheduled backup, ideal as a safety net just before a change.

The backup only serves its purpose if you can recover it: when you need it, restore it by following [How to restore a disk backup.](/docs-en/productos/servers/how-to/how-to-restore-a-disk-backup.md)


---

# 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-back-up-a-server.md?ask=<question>&goal=<endgoal>
```

`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.