From: Lorne Guse via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"m.carrara@proxmox.com" <m.carrara@proxmox.com>,
Morgan Littlewood <morgan@truenas.com>
Cc: Lorne Guse <boomshankerx@hotmail.com>
Subject: [pve-devel] TrueNAS over iSCSI: Snapshot Management
Date: Sat, 27 Sep 2025 16:45:12 +0000 [thread overview]
Message-ID: <mailman.455.1758991554.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 10997 bytes --]
From: Lorne Guse <boomshankerx@hotmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, "m.carrara@proxmox.com" <m.carrara@proxmox.com>, Morgan Littlewood <morgan@truenas.com>
Subject: TrueNAS over iSCSI: Snapshot Management
Date: Sat, 27 Sep 2025 16:45:12 +0000
Message-ID: <DM6PR17MB34662F5ABDA587979C0FFDA2D019A@DM6PR17MB3466.namprd17.prod.outlook.com>
I'd like to get some input on snapshot management relating to TrueNAS. Currently, Proxmox does not allow for multigeneration rollback of snapshots.
TASK ERROR: can't rollback, 'preupgrade' is not most recent snapshot on 'nas:vm-803-disk-0'
I was wondering if there is a way for Proxmox to allow for the use of TrueNAS periodic snapshots without breaking Proxmox snapshots.
Is there a way to import TrueNAS snapshots into Proxmox via the API?
Could multi-generation rollback work because TrueNAS supports it?
--
Lorne Guse
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-09-27 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.455.1758991554.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=boomshankerx@hotmail.com \
--cc=m.carrara@proxmox.com \
--cc=morgan@truenas.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