PHPackages                             idct/php-proxmox-backups - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. idct/php-proxmox-backups

AbandonedArchivedProject[Utility & Helpers](/categories/utility)

idct/php-proxmox-backups
========================

Simple PHP executable tool for making backups with Proxmox 5 env easier.

51PHP

Since Aug 18Pushed 6y ago1 watchersCompare

[ Source](https://github.com/bpacholek/php-proxmox-backups)[ Packagist](https://packagist.org/packages/idct/php-proxmox-backups)[ RSS](/packages/idct-php-proxmox-backups/feed)WikiDiscussions master Synced today

READMEChangelogDependenciesVersions (1)Used By (0)

PHP Proxmox Backups
===================

[](#php-proxmox-backups)

Simple tool for easing the execution of VMs and CTs backups with Proxmox 5 environment (provided by OVH).

Apart from starting backups of defined machines allows to send notification emails (SMTP required) or Telegram messages using a Telegram Bot.

FEATURES
========

[](#features)

- init of backups building using internal proxmox tools
- storing on FTPs and keeping a backlog on N backups
- sending notification emails
- sending Telegram notifs

TODOs
=====

[](#todos)

- schedule of backups
- different rules for backlog: to keep weekly, monthly and not only daily entries
- provide better readme
- different FTPs for different machines
- master logging

Installation
============

[](#installation)

Download
========

[](#download)

Download ZIP package or clone using git:

```
git clone git@github.com:ideaconnect/php-proxmox-backups.git
```

or install using Composer:

```
composer require idct/php-proxmox-backups
```

Install
=======

[](#install)

Install using Composer:

```
composer install
```

This will create the `vendors` folder with all required libraries.

Create **config.json** file (check **configuration** section below and **config\_sample.json**).

Execute the tool:

```
cd bin/
./dobackups
```

In case of errors try to execute using php directly:

```
cd bin/
php dobackups
```

You can also add this to cron - for example to execute at 23:00 each day:

```
0 23 * * * cd [path to your application]/bin && php dobackups > /var/log/proxmox-backups.log 2>&1

```

Configuration
=============

[](#configuration)

Create **config.json** file with two objects: **global**, **machines** (array).

For example:

```
{
    "global": {},
    "machines: []
}
```

If you want FTP upload support define `ftp` object in the `global` section - for example:

```
{
    "global": {
        "ftp": {
            "login": "sample-username",
            "pass": "your-password",
            "dir": "/backups/",
            "host": "ftpbackups.some.host.net"
        }
    },
    "machines: []
}
```

Machine must have `ftp.backlog` value defined to use the `ftp` feature.

If you want to use email notifications feature then please add `smtp` object into the `global` section - for instance:

```
{
    "global": {
        "smtp": {
            "host": "smtp.your.host.net",
            "username": "smtp_username",
            "password": "smtp_password",
            "port": 25,
            "from_mail": "backups@yourname.pl",
            "from_name": "My Best Backups"
        },
        "ftp": {
            "login": "sample-username",
            "pass": "your-password",
            "dir": "/backups/",
            "host": "ftpbackups.some.host.net"
        }
    },
    "machines: []
}
```

The most important part is to provide information about VMs or CTs which are meant to be included in the process. Sample block:

```
        {
            "id": 101,
            "storage": "backups",
            "email": "you@youremail.com",
            "ftp.backlog": 3,
            "telegram": {
                "bot": "",
                "channel": ""
            }
        }
```

- id -> identifier of the VM or CT from Proxmox
- storage -> identifier of the storage from Proxmox to which the particular VM (or CT) can perform backups
- email -> optional, if set then email notifications about the process will be sent (if SMTP is provided)
- telegram -> optional, allows sending simple notifications using a Telegram Bot.

You can provide more than one machine (VM or CT).

Contribution
============

[](#contribution)

I more than appreciate any contribution: please provide it using pull requests or issues reporting. Be sure to follow PSR rules when contributing any code!

###  Health Score

18

—

LowBetter than 8% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community4

Small or concentrated contributor base

Maturity36

Early-stage or recently created project

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/b76a5fac115d24d698d09cc939a6922bf309732ae61d0f2f215ae9e7397658ea?d=identicon)[ideaconnect](/maintainers/ideaconnect)

### Embed Badge

![Health badge](/badges/idct-php-proxmox-backups/health.svg)

```
[![Health](https://phpackages.com/badges/idct-php-proxmox-backups/health.svg)](https://phpackages.com/packages/idct-php-proxmox-backups)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)