From: Rodney Wild <rdwild@azcs.ca>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [pbs-devel] Proxmox Backup Server Cloud Backup
Date: Tue, 10 Oct 2023 08:04:23 -0600 [thread overview]
Message-ID: <4E996E09-BFED-49E0-8DFE-96A854688766@azcs.ca> (raw)
In-Reply-To: <b4a7f428-5fd9-400d-bb2e-0c4b64abdbaf@proxmox.com>
We have plans for a s3 plugin as well after renterd plugin is complete.
Sent from my iPhone
> On Oct 10, 2023, at 3:19 AM, Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
>
> Am 07/10/2023 um 05:31 schrieb Rodney Wild:
>> Sorry about the delay, I have a research grant (from the Sia Foundation) to research the possibility of developing a method of backing up proxmox to the cloud. The idea would be to develop a module similar to the tape module and add plugin capability to allow for different cloud platforms. I should be releasing our findings that it is possible to develop such a module and plugin addons. The first plugin will be be to allow backups in the Sia Storage network. This will be open source project and if approved I would like to contribute the source back to the proxmox backup project and would like to know the liklyhood of that being entertained so I can add it to my report. Thank-you for your time.
>>
>
> In generally we plan to add support for S3 off-site syncs, i.e., a
> slightly specialized version of sync jobs (a bit closer to tape ones) so
> that admins can configure off-site copies to any S3 capable storage.
>
> S3 is widely poplar and while surely it has some shortcomings, like any
> tech has, it is proven to work and there are many open source
> implementations for server and client, like e.g., a Ceph setup can be
> used as S3 target. Iow., S3 is established and won't go away anytime
> soon, if Sia Storage network has a bridge for S3 it would then be
> already set.
>
> If you have general contributions for improving/fixing things in one of
> our repos feel free to send, but please ensure to follow our developer
> documentation's rules and guidelines:
>
> https://pbs.proxmox.com/wiki/index.php/Developer_Documentation#Example
>
> But please note that we cannot give you an upfront guarantee of accepting
> any code, as an initial implementation is only a small fraction of the
> work, continuous maintenance (which we only can bet on us doing, external
> devs often tend to vanish after their changes got in) is much more work.
>
> regards
> Thomas
>
prev parent reply other threads:[~2023-10-10 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 21:45 Rodney Wild
2023-08-09 6:23 ` Dietmar Maurer
[not found] ` <d01892b5-64a8-b280-fc9a-1d4ee932d2d4@azcs.ca>
2023-10-07 3:31 ` Rodney Wild
2023-10-10 9:18 ` Thomas Lamprecht
2023-10-10 14:04 ` Rodney Wild [this message]
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=4E996E09-BFED-49E0-8DFE-96A854688766@azcs.ca \
--to=rdwild@azcs.ca \
--cc=dietmar@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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