From: mj <lists@merit.unu.edu>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] PBS backup/restore issue
Date: Wed, 24 Feb 2021 10:44:33 +0100 [thread overview]
Message-ID: <ac4b4f9e-259c-cea9-92dd-602bdff2e90e@merit.unu.edu> (raw)
In-Reply-To: <mailman.28.1614066435.365.pve-user@lists.proxmox.com>
Hi Eneko,
Just to say: that sounds scary! Do you have any update on this..?
MJ
next prev parent reply other threads:[~2021-02-24 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.28.1614066435.365.pve-user@lists.proxmox.com>
2021-02-23 8:06 ` Dietmar Maurer
2021-02-24 9:44 ` mj [this message]
[not found] ` <mailman.44.1614161184.365.pve-user@lists.proxmox.com>
2021-06-13 18:36 ` proxmox
[not found] <c390959d-e5b5-9a95-770c-ff6853357cbe@binovo.es>
2021-02-24 10:34 ` Stefan Reiter
[not found] ` <6120d3f8-67c8-873f-164c-1913c2016a54@binovo.es>
2021-02-24 19:03 ` Thomas Lamprecht
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=ac4b4f9e-259c-cea9-92dd-602bdff2e90e@merit.unu.edu \
--to=lists@merit.unu.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.