XO Backup [NOBAK] for full backups
-
I think it's coming this release, isn't it @julien-f ?
-
@normanghenderson Yep, it should be coming at the end of the month
-
-
@julien-f Excellent, thank you!
-
Has this been implemented yet?
I've tried the [NOBAK] method, and the disk still gets cycled into the weekly VM backup. -
Running the latest xen orchestra. Just finished our latest weekly backup. It still backed up the 1TB disk I had labeled as [NOBAK].
-
@mrbaz I don't think its been implemented yet. Its coming from what I've read though.
-
It should be for this release, this time
@julien-f is working on it! -
@olivierlambert Has there been any progress on the VDI.snapshot? Read somewhere that there could be another branch for testing, but I did not find any.
-
@johnarvid ah yes let me ping @julien-f about this, I don't remember exactly where are we on the VDI.snapshot front
-
@olivierlambert Is there an Update to this? We would also like to use the [NOBAK] with the Full Backup feature of XO.
-
Ping @julien-f
-
Hey everyone,
[NOBAK]should work for all types of backup: Rolling Snaphost, Disaster Recovery, Continuous Replication, Full Backup and Delta Backup.Unfortunately, due to the way the snapshot process is implemented in XCP-ng, ignored VDIs will still be snapshotted before being deleted, which takes time and space unnecessarily, but we have discussed with the XCP-ng team and they are working on improving this
In the meantime, XO tries to work around this by temporary detaching these VDIs from the VM during the snapshot, but this only work when the VM is halted (see offline backup in the advanced settings of a backup job).
-
Hi does the Backup job still create the Snapshot (and therefore required time and space) when not doing an offline backup or has this been improved by now ?
-
@julien-f said in XO Backup [NOBAK] for full backups:
Hey everyone,
[NOBAK]should work for all types of backup: Rolling Snaphost, Disaster Recovery, Continuous Replication, Full Backup and Delta Backup.Unfortunately, due to the way the snapshot process is implemented in XCP-ng, ignored VDIs will still be snapshotted before being deleted, which takes time and space unnecessarily, but we have discussed with the XCP-ng team and they are working on improving this
In the meantime, XO tries to work around this by temporary detaching these VDIs from the VM during the snapshot, but this only work when the VM is halted (see offline backup in the advanced settings of a backup job).
Ironically enough in my case, the VM I have that has a passthrough disk attached to it (a VDI I would like to [NOBAK]) is the VM that is setup as the remote for the backup job in XOA. So shutting it down wouldn't exactly work
.That being said I'm sure I could implement a workaround, but is there a feature request or tracking ticket URL somewhere where I can track XCP-ng team's work on this issue?
-
I don't remember the status about this. I'm adding @marcungeschikts so he can tell us where it is in the backlog, when he's back from holidays
-
Done in XO Release 5.71 delivered in May, this year.Internal Ref. only NOBAK support for all backup modes with snapshots
-
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
-
@marcungeschikts I understand that this issue has been solved by halting a VM before taking the snapshot. Per this comment by @julien-f , "[...] but we have discussed with the XCP-ng team and they are working on improving this", is there an issue or feature request or ticket to track XCP-ng's work to improve the implementation so that halting a VM is no longer required?
-
Not sure to understand. The potential XAPI side improvement is to allow a
VM.snapshotcommand to add extra parameters, excluding some disks.You don't need to halt a VM to make a snapshot, it's completely unrelated. Maybe I'm missing something?
-
Hi @bnerickson ,
The xcp-ng part to Exclude VDI from snapshot has been done on XAPI project and can be seen in github https://github.com/xapi-project/xen-api/issues/4551 , but will be only embedded in xcp-ng 8.3 planned around 6 month (+/- 3).
For the XO part, [Backup] Use ignore_vdis param when snapshotting, I will see with the XO Team and Olivier to synchronize the delivery
