From: Lindsay Mathieson <lindsay.mathieson@gmail.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Revisited: External disk backup using PBS - Requesting Criticism/Advice?
Date: Sat, 10 Apr 2021 23:28:50 +1000 [thread overview]
Message-ID: <e92b8b56-e89f-928d-a3c8-7b423e334cf5@gmail.com> (raw)
In-Reply-To: <mailman.235.1618038675.359.pve-user@lists.proxmox.com>
On 10/04/2021 5:10 pm, Arjen via pve-user wrote:
> Don't expect to be able to backup the PBS container with 4TB to a 2TB external drive.
I only passed 2TB through and the actual backup data comes to 1.3TB
> The Datastore of a PSB does not compress much further and Proxmox VE Backup will only backup virtual disks and not mountpoints or storages passed from host, if I understand correctly.
I wondered that. Will be testing.
> I suggest adding a virtual disk of 2TB to the PBS container (and format it with ext4) which can be backed up by the Proxmox VE Backup.
Certainly a possibility.
I also wondered if it was practical to attach an external disk to PBS as
a Datastore, then detach it. A bit more manual, but doable.
> I would also run the PBS container (with virtual disk) on the cluster instead on separate hardware which is a single point of failure. The local PBS would be then just as reliable as your cluster.
I want to keep the storage separate from the cluster, in that regard the
local storage is a single point of failure, hence the need for offsite
storage as well :)
>
> Regarding safeness: I suggest doing a automated disaster recovery every week to make sure it works as expected. Or at least partially, like restoring the PBS from an external drive.
I'll definitely be testing restore options to check that it works.
> Regarding practicality: I would have a remote PBS sync with your local PBS instead of moving physical disks (but you mentioned before that that was not really possible).
Alas :(
Perhaps I could do a backup on site, then physically move it offsite and
attach it to a offsite PBS server and then sync it remotely -
incremental backups over the net would be doable.
nb. Our NAS died, hence my increased investigation of this :) Definitely
want to go with a more open and targeted solution this time, the NAS was
a good appliance, but inflexible.
Thanks!
--
Lindsay
next prev parent reply other threads:[~2021-04-10 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 3:22 Lindsay Mathieson
[not found] ` <mailman.235.1618038675.359.pve-user@lists.proxmox.com>
2021-04-10 13:28 ` Lindsay Mathieson [this message]
2021-04-12 1:57 ` Lindsay Mathieson
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=e92b8b56-e89f-928d-a3c8-7b423e334cf5@gmail.com \
--to=lindsay.mathieson@gmail.com \
--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