From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox Backup Server (beta)
Date: Fri, 10 Jul 2020 15:50:55 +0200 [thread overview]
Message-ID: <f09427ca-73ef-8cc7-9154-ba1c33caf39c@proxmox.com> (raw)
In-Reply-To: <a92c7f1d-f492-2d43-00b9-15bdb0e805ec@binovo.es>
Hi Eneko,
On 10.07.20 13:56, Eneko Lacunza wrote:
> El 10/7/20 a las 13:45, Dietmar Maurer escribió:
>>> Given we usually perform PVE backups to a NFS server (in a PVE cluster
>>> node or standalone NAS), do you think it would make sense to setup PBS
>>> in a VM, with storage on a NFS server?
>> I guess you can do that, but you may not get maximal performance this way.
>>
>> Especially if you put the data on NFS, you can end up sending
>> everything twice over the network ...
>>
> That's a good point to consider, although reusing existing infrastructure and/or not needing a fourth server could outweight it for small clusters, specially considering the bandwith savings due to incremental VM backups versus current PVE full backups.
>
Note that it also supports remote sync, and that backups can be
encrypted by the client, this opens a few possibilities.
One could be having local "hyper-converged" backup servers in each small
cluster, and one central (or depending on safety concerns, two) big server to
have a off-site copy of all the data in the case a cluster one fails. As data
can be encrypted by the client the backup server doesn't have to be fully
trusted. And as remote sync schedules are done efficiently (only the delta) one
could have a remote over the WAN.
This won't be the primary recommended setup, as a big (enough) local server as
primary backup is always faster and better than a hyper-converged one, but
should work for situations where one is limited by local available HW.
cheers,
Thomas
next prev parent reply other threads:[~2020-07-10 13:50 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 10:56 Martin Maurer
2020-07-10 11:42 ` Roland
2020-07-10 12:09 ` Dietmar Maurer
2020-07-10 12:24 ` Roland
2020-07-10 13:43 ` Thomas Lamprecht
2020-07-10 14:06 ` Roland
2020-07-10 14:15 ` Thomas Lamprecht
2020-07-10 14:46 ` Roland
2020-07-10 17:31 ` Roland
2020-07-10 13:44 ` Dietmar Maurer
[not found] ` <mailman.77.1594381090.12071.pve-user@lists.proxmox.com>
2020-07-10 11:45 ` Dietmar Maurer
[not found] ` <a92c7f1d-f492-2d43-00b9-15bdb0e805ec@binovo.es>
2020-07-10 13:50 ` Thomas Lamprecht [this message]
2020-07-10 12:03 ` Lindsay Mathieson
2020-07-10 12:13 ` Dietmar Maurer
2020-07-10 15:41 ` Dietmar Maurer
2020-07-11 11:03 ` mj
2020-07-11 11:38 ` Thomas Lamprecht
2020-07-11 13:34 ` mj
2020-07-11 13:47 ` Thomas Lamprecht
2020-07-11 14:40 ` Dietmar Maurer
2020-07-14 14:30 ` Alexandre DERUMIER
2020-07-14 15:52 ` Thomas Lamprecht
2020-07-14 21:17 ` Alexandre DERUMIER
2020-07-15 4:52 ` Thomas Lamprecht
[not found] ` <176392164.4390.1594849016963.JavaMail.zimbra@numberall.com>
2020-07-16 7:33 ` Thomas Lamprecht
[not found] ` <mailman.204.1594849027.12071.pve-user@lists.proxmox.com>
2020-07-16 10:17 ` Wolfgang Bumiller
2020-07-16 14:36 ` Mark Schouten
2020-07-16 17:04 ` Thomas Lamprecht
2020-07-16 13:03 ` Tom Weber
2020-07-17 7:31 ` Fabian Grünbichler
2020-07-17 13:23 ` Tom Weber
2020-07-17 17:43 ` Thomas Lamprecht
2020-07-18 14:59 ` Tom Weber
2020-07-18 18:07 ` Thomas Lamprecht
2020-07-10 12:45 ` Iztok Gregori
2020-07-10 13:41 ` Dietmar Maurer
2020-07-10 15:20 ` Iztok Gregori
2020-07-10 15:31 ` Dietmar Maurer
2020-07-10 16:29 ` Iztok Gregori
2020-07-10 16:46 ` Dietmar Maurer
[not found] ` <a1e5f8dd-efd5-f8e2-50c1-683d42b0f61b@truelite.it>
2020-07-10 14:23 ` Thomas Lamprecht
2020-07-10 15:59 ` Lindsay Mathieson
[not found] ` <mailman.86.1594396120.12071.pve-user@lists.proxmox.com>
2020-07-10 16:32 ` Dietmar Maurer
2020-10-06 13:12 ` Lee Lists
2020-10-08 8:21 ` Thomas Lamprecht
2020-10-09 9:27 ` Lee Lists
2020-10-09 12:10 Lee Lists
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f09427ca-73ef-8cc7-9154-ba1c33caf39c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=elacunza@binovo.es \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox