just to #brag

Deploy of worker is okay (one big rocky linux with default settings 6vcpu, 6Gb RAM, 100Gb vdi)

first backup is fine, with decent speed ! (to a xcp hosted S3 minio)

will keep testing

Hey all,

We are proud of our new setup, full XCPng hosting solution we racked in a datacenter today.
This is the production node, tomorrow i'll post the replica node !

XCPng 8.3, HPE hardware obviously, and we are preparing full automation of clients by API (from switch vlans to firewall public IP, and automatic VM deployment).

This needs a sticker "Vates Inside" #vent

@sluflyer06 and I wish HPE would be added too

I did stick to version: 1 in my working configuration

Had to rename my "Ethernet 2" nic name to Ethernet2 without the space

You have to put the exact template nic name for this to work.

Could we have a way to know wich backup is part of LTR ?
In veeam B&R, when doing LTR/GFS, there is a letter like W(weekly) M(monthly) Y(yearly)to signal the fact in the UI

That's pure cosmectics indeed, but practical.

@Forza I didn't try, as my default Graylog Input was UDP and worked with the hosts...

But guys, that was it. In TCP mode, it's working. Rapidly set up a TCP input, and voila.

@MK.ultra don't think so

it's working without for me.

@tmk hi !
Many thanks, your modified python file did the trick, my static IP address is now working as intented.

I can confirm this is working on Windows 2025 Server as well.

@Bastien-Nollet ha yeah, sequences are a set of schedules... so I have to put the two schedules in two sequences.

my fear is that it is still not clear if the two separated sequences of schedules will behave as two schedules in one job. see what I mean ? (chain continuity of two schedules attached to one job)

I dont want to get a new full with the standalone sequence/schedule that is healthcheck configured.

i'll need to try and report back here.

and I noticed a "bug?" with mirror copy job ?

Even if I only manually select one VM out of the 7 that are on the remote, they are "checked" by the job, but excluded by the job filter

on the remote, all 7 VMs folders are created, but only the copied VM contains data

the copy is OK for the selected VM, but why check and create the other VMs/folders ?

@Bastien-Nollet here comes the test :

Same job, A_testhealth, delta backup
Two schedules, healthcheck is ON only wenesday

I manually started it today, it will take a full
tomorrow, will be a delta
after tomorrow should be a delta+healthcheck
after after tomorrow should be a simple delta

all in one backup chain. time will tell ! c ya in 4 days for the results

@Bastien-Nollet I'm not a big fan of the way it is implemented right now : when you make a mirror copy, it first duplicate all the points then prune to the desired retention

but if you keep this way of handling mirror copies, it has the advantage of not needing to handle incomplete chains ?

@Bastien-Nollet nice !

@Bastien-Nollet ha yeah, sequences are a set of schedules... so I have to put the two schedules in two sequences.

my fear is that it is still not clear if the two separated sequences of schedules will behave as two schedules in one job. see what I mean ? (chain continuity of two schedules attached to one job)

I dont want to get a new full with the standalone sequence/schedule that is healthcheck configured.

i'll need to try and report back here.

@francis-chiew hey, seems very nice. need some screenshots of the dashboards

and I noticed a "bug?" with mirror copy job ?

Even if I only manually select one VM out of the 7 that are on the remote, they are "checked" by the job, but excluded by the job filter

on the remote, all 7 VMs folders are created, but only the copied VM contains data

the copy is OK for the selected VM, but why check and create the other VMs/folders ?

Hi,

I'm trying to get together homogeneous backup copies for client VMs that have backup copy option on our side.

First of all, there is no LTR options possible in MIRROR COPY jobs. the only way to have more points in the backup copy is to get a longer retention in mirror copy job schedule than the source job schedule.
Could we get LTR options also in mirror copy job ?

Second point, mirror copy job is either all VMs from remote, or manually selected VMs, no possibility of "SMART" selection by tags.
I'd like to be able to TAG VMs with client_name/backupcopy_option to autoselect the concerned VMs

If you could get these demands in future dev, would be great

Thanks in advance.

@Bastien-Nollet @florent

Could we have a way to know wich backup is part of LTR ?
In veeam B&R, when doing LTR/GFS, there is a letter like W(weekly) M(monthly) Y(yearly)to signal the fact in the UI

That's pure cosmectics indeed, but practical.

Hi,

I tend to manage all my backups with SEQUENCES, working great, as expected.
Say I have this sequence :

I'd like to proceed with health check on BCK-HVA, only on sundays.

How would one configure the schedule on the job ?
If i simply tick the Health Chek yes, it will be done everyday.
Current schedule on BCK-HVA :

Should I add another schedule specific for sundays with HealthCheck, and exclude HealthCheck for other days in the week ?

Will the Sequence take into account the two schedules parameters in the job ? didnt find answers anywhere about this corner case...

@florent what if we use XO Proxies ?