introduction: history: minor rewording and fixup
Some minor spelling and grammar fixes. Rewording of some sentences. Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
This commit is contained in:
parent
61c6eafc08
commit
6cd8496008
|
@ -179,29 +179,28 @@ along with this program. If not, see AGPL3_.
|
||||||
History
|
History
|
||||||
-------
|
-------
|
||||||
|
|
||||||
Backup is, and always was, as central aspect of IT administration.
|
Backup is, and always has been, a central aspect of IT administration.
|
||||||
The need to recover from data loss is fundamental and increases with
|
The need to recover from data loss is fundamental and only increases with
|
||||||
virtualization.
|
virtualization.
|
||||||
|
|
||||||
Not surprisingly, we shipped a backup tool with Proxmox VE from the
|
For this reason, we've been shipping a backup tool with Proxmox VE, from the
|
||||||
beginning. The tool is called ``vzdump`` and is able to make
|
beginning. This tool is called ``vzdump`` and is able to make
|
||||||
consistent snapshots of running LXC containers and KVM virtual
|
consistent snapshots of running LXC containers and KVM virtual
|
||||||
machines.
|
machines.
|
||||||
|
|
||||||
But ``vzdump`` only allowed for full backups. While this is perfect
|
However, ``vzdump`` only allows for full backups. While this is fine
|
||||||
for small backups, it becomes a burden for users with large VMs. Both
|
for small backups, it becomes a burden for users with large VMs. Both
|
||||||
backup time and space usage was too large for this case, specially
|
backup duration and storage usage are too high for this case, especially
|
||||||
when Users want to keep many backups of the same VMs. We need
|
for users who want to keep many backups of the same VMs. To solve these
|
||||||
deduplication and incremental backups to solve those problems.
|
problems, we needed to offer deduplication and incremental backups.
|
||||||
|
|
||||||
Back in October 2018 development started. We had been looking into
|
Back in October 2018, development started. We investigated
|
||||||
several technologies and frameworks and finally decided to use
|
several technologies and frameworks and finally decided to use
|
||||||
:term:`Rust` as implementation language to provide high speed and
|
:term:`Rust` as the implementation language, in order to provide high speed and
|
||||||
memory efficiency. The 2018-edition of Rust seemed to be promising and
|
memory efficiency. The 2018-edition of Rust seemed promising for our
|
||||||
useful for our requirements.
|
requirements.
|
||||||
|
|
||||||
In July 2020 we released the first beta version of Proxmox Backup
|
In July 2020, we released the first beta version of Proxmox Backup
|
||||||
Server, followed by a first stable version in November 2020. With the
|
Server, followed by the first stable version in November 2020. With support for
|
||||||
support of incremental, fully deduplicated backups, Proxmox Backup
|
incremental, fully deduplicated backups, Proxmox Backup significantly reduces
|
||||||
significantly reduces the network load and saves valuable storage
|
network load and saves valuable storage space.
|
||||||
space.
|
|
||||||
|
|
Loading…
Reference in New Issue