@florent hi, i've adjusted the retention parameters and i'm waiting for some days of backup/mirror for checking

Hi, i've this situation in Task

What's this task?
Now i've ~50 of this call..

@olivierlambert now work fine, thank you

Hi @florent, i've clean backup data, add the correct retention and now
it's fine

i'm lowering nbd connection (from 4 to 1), the speed of "test backup con mirror" is too low

@florent hi, i've adjusted the retention parameters and i'm waiting for some days of backup/mirror for checking

@acebmxer of course, this is only a test.
the problem is not the schedulng but why incremental send every time all data.

@acebmxer [excuse for the poor english!]
i've now this situation:
1 backup job with two disables schedules, one full and one delta, to a nas
1 mirror full backup to wasabi (S3)
1 mirror incremental backup

i've insert two sequences:
one starting at sunday for full backup (the sequence is full backup and then full mirror)
one every 3 hours with delta backup and then mirror incremental

the job start at the correct hour but the mirror incremental send every time the same data size..
backup to nas:

dns_interno1 (ctx1.tosnet.it)
Transfer data using NBD
    Clean VM directory
    cleanVm: incorrect backup size in metadata
    Start: 2025-06-24 16:00
    End: 2025-06-24 16:00
    Snapshot
    Start: 2025-06-24 16:00
    End: 2025-06-24 16:00
    Backup XEN OLD
        transfer
        Start: 2025-06-24 16:00
        End: 2025-06-24 16:01
        Duration: a few seconds
        Size: 132 MiB
        Speed: 11.86 MiB/s
    Start: 2025-06-24 16:00
    End: 2025-06-24 16:01
    Duration: a minute

Start: 2025-06-24 16:00
End: 2025-06-24 16:01
Duration: a minute
Type: delta

 dns_interno1 (ctx1.tosnet.it)
    Wasabi
        transfer
        Start: 2025-06-24 16:02
        End: 2025-06-24 16:15
        Duration: 13 minutes
        Size: 25.03 GiB
        Speed: 34.14 MiB/s
        transfer
        Start: 2025-06-24 16:15
        End: 2025-06-24 16:15
        Duration: a few seconds
        Size: 394 MiB
        Speed: 22.49 MiB/s
    Start: 2025-06-24 16:02
    End: 2025-06-24 16:17
    Duration: 15 minutes
    Wasabi
    Start: 2025-06-24 16:15
    End: 2025-06-24 16:17
    Duration: 2 minutes

Start: 2025-06-24 16:02
End: 2025-06-24 16:17
Duration: 15 minutes

the job send every time 25gb to wasabi, not the incremental data.

Good morning, sequence work fine but i've a long list of task closed but at 50% (?)
raw log is correct

{
  "id": "0mca491c8",
  "properties": {
    "name": "Schedule sequence",
    "userId": "c5ce5e50-29d9-4c00-84e8-402e1063a5c7",
    "type": "xo:schedule:sequence",
    "progress": 50
  },
  "start": 1750744800007,
  "status": "success",
  "updatedAt": 1750746259107,
  "end": 1750746259107
}

It's only a ui problem?

@acebmxer ok, i don't use (for full + delta) the old schedulng (one job but two scheduling, one full and one delta), but i must separate the two jobs?

Good morning, i'v some VM (~30) in four logical group.
for every group i create the backup (one full weekly and 40 incremental) and i want mirror to wasabi S3 storage.
How i can start mirroring when one of the full/incremental backup end?
I don't want to start mirror when a backup is not finished!
thank you

@olivierlambert ops.. why the best topology?

@olivierlambert live migration, the vm is very important (today, in christmas holyday, i've received some phone calls for 7 minutes of freeze..)

@olivierlambert hi, today i've upgraded my host..
The big VM frozen for ~7 minutes, is a big vm (96 gbram and 32 cpu) but 7 minutes is a very long time (for customer!)
i've setting 96/06 in dynamic: is a normal time?