@olivierlambert now work fine, thank you
Posts made by robyt
-
RE: New xoa: unable to login
@robyt ok, i've drop and reinstall new XOA and work fine
-
New xoa: unable to login
Hi, ive deploy new xoa on my pool but i can't login.
I've use the default password, i've use the xo-server-recover-account with 2 email but nothing, i've invalid credentials
whats'up doc? -
RE: two separate process for backup?
@CJ said in two separate process for backup?:
@robyt said in two separate process for backup?:
@CJ said in two separate process for backup?:
@DustinB What are you using for cloud sync?
is not a cloud sync, is a copy to a qnap connected via gigabit ethernet
You'll note that that was a reply to @DustinB who is using cloud sync, not you.
@robyt said in two separate process for backup?:
@CJ said in two separate process for backup?:
@robyt When you say 10/12 NBD, are you referring to the setting of NBD connections per disk? Or connexion as the UI says. How are you checking that NBD is being used?
Connexion in UI
What happens if you reduce the number? From my understanding your Qnap isn't all that powerful, so it sounds like you're overwhelming the poor thing. I'm using 1 per disk and seeing over 1Gbps speeds. My main limitation is the 2.5G connection to XO.
However, I will say that I'm not sure if I'm actually using NBD or not. I don't see anything in the UI to indicate whether it's being taken advantage of. I also have my backup concurrency set to 1 to avoid running multiple transfers through XO as the switching can eat into the overall bandwidth.
when i've incremented connexion i see a lot of http timeout.
In UI if i open the detail of a backup job i see "Transfer data using NBD"
I know that qnap is not a wonderful and very fast nas but i want buy another (and more expensive) hardware without more test
Some vm is very very slow (the transfer of mailserver's snapshot is.. slooooooowwww) but the configuration is the same (network, part of disk in SSD and part in mechanical HD etc) -
RE: two separate process for backup?
@CJ said in two separate process for backup?:
@robyt When you say 10/12 NBD, are you referring to the setting of NBD connections per disk? Or connexion as the UI says. How are you checking that NBD is being used?
Connexion in UI
-
RE: two separate process for backup?
@CJ said in two separate process for backup?:
@DustinB What are you using for cloud sync?
is not a cloud sync, is a copy to a qnap connected via gigabit ethernet
-
RE: two separate process for backup?
@DustinB
with 10/12 NDB i've a lot of http timeouttransfer Start: Feb 3, 2024, 06:03:22 AM End: Feb 3, 2024, 05:04:54 PM Duration: 11 hours Error: HTTP connection has timed out
and next delta become a full...
The speed is very very low for some backuptransfer Start: Feb 6, 2024, 11:39:45 AM End: Feb 6, 2024, 12:12:32 PM Duration: 33 minutes Size: 686.66 MiB Speed: 357.42 KiB/s
i
-
RE: two separate process for backup?
@CJ said in two separate process for backup?:
@robyt Yes, that's exactly what I had talked about. With separate concurrency settings all of your snapshots would have finished before your first transfer did.
Also, you should look into the new backup SR. I assume that your slow transfer is due to internet speeds, so you could do backups locally and then use the backup SR to do the transfer offsite.
Hi, i've a little nas (qnap 419 with extension TR-004) connected with a gibait ethernet (bonded but not in parallel, only one at once)
now i'm trying an update/rebbot of the nas and update xen orchestra ;-( -
RE: two separate process for backup?
@CJ said in two separate process for backup?:
@olivierlambert This is related to the concurrency settings I was asking for previously. That way @robyt could set snapshot concurrency fairly high and transfer concurrency low.
Hi, but this is in the same backup's session
If i start another session but the previous was in transfer the new backup job aborted.
Job start
snapshot_1
transfer -->another backup job start: xoa create the snapshot_2 but don't transfer anything
End of transfer of snapshot_1, start transfer snapshot_2 -
two separate process for backup?
Hi, is there a mode to separate snapshot and transfer?
My problem is the slow transfer and when the transfer want days i've days without backup.
But if the process is not linked.. i may have one snapshot every six hours, if the previous transfer is ended ok, otherwise XOA wait and when previous transfer was finished start the new transfer and so on.
(excuse for the english!) -
RE: In delta backup force the full backup task in a specific day
@olivierlambert said in In delta backup force the full backup task in a specific day:
Block mode with NBD enabled? That sounds too slow, especially for a first backup (which will be full and won't require any merge)
is locked to 37%... ho i can stop the backup job without damage old backups? -
RE: In delta backup force the full backup task in a specific day
@olivierlambert said in In delta backup force the full backup task in a specific day:
Block mode with NBD enabled? That sounds too slow, especially for a first backup (which will be full and won't require any merge)
yes, i've tried with and without block mode and nbd is enabled; the network is on NDB nic in pool
-
RE: In delta backup force the full backup task in a specific day
@olivierlambert said in In delta backup force the full backup task in a specific day:
A quick computation: ext4 by default will be able to handle 4 billion files.
Since we store 2MiB blocks, it means up 8 billions MiB stored max. Which is roughly equal to 7PiB worth of data.
If you need to store more than this, then you need to go for XFS or ZFS.
it's too slow.
I've enable the block mode, i start a backup and the write speed computed by nas is 6/7 mB/sec
but if i mount (when the backup process is active) the nas on a linux server and transfer a 1GB block i see 18,3 mB/sec on linux, the nas compute `24 mB/Sec
When the linux transfer end the speed go down to 6/7 mB/Sec
i'm confused..
How i can interrupt the backup process?
I need to restart XOA vm? -
RE: In delta backup force the full backup task in a specific day
@olivierlambert said in In delta backup force the full backup task in a specific day:
A quick computation: ext4 by default will be able to handle 4 billion files.
Since we store 2MiB blocks, it means up 8 billions MiB stored max. Which is roughly equal to 7PiB worth of data.
If you need to store more than this, then you need to for XFS or ZFS.
ok, i tried with a small VM in separated backup job
-
RE: In delta backup force the full backup task in a specific day
@florent said in In delta backup force the full backup task in a specific day:
@robyt said in In delta backup force the full backup task in a specific day:
@florent said in In delta backup force the full backup task in a specific day:
@robyt I think I misunderstood, you want to decrease the concurrency ?
the settings is not exposed in the UX or in the config file, but it can be changed in the code if you're ready to test ( if this is an XOA, please open a ticket I will patch for you)the file is in <xo server directory>/node_modules/@xen-orchestra/backups/_runners/VmsXapi.mjs and you can put 1 in diskPerVmConcurrency: 0 It will limit the number of disk transferred in parallel per VM
that way, by limiting VM concurrency, and the disk per vm , you will limit the numbe of thread writing to the NAS
Hi, in UI i've "Number of NBD connexion per disk": i've 4 for disk, for last backup i've decreased the value to 1 for 3 backup job and 2 for the big backup job
at this moment remain only the big, the other was finished
after the copy to the vm i see a lot of nfs daemon and the load of nas goes high (over 30)
of course i've a lot of DW nfs daemon in nasafter the backup there is the merge process, that will colaesce/merge the older backups. This one is very expensive.
If your NAS allow it, you can switch the remote to block based storage, in the bottom of the remote settings : "Store backup as multiple data blocks instead of a whole VHD file. (creates 500-1000 files per backed up GB but allows faster merge)"Please note that the next backup after enabling/disabling it will be a full for all VM.
Hi, i've tried some months ago but is very very slow
For the big VM i've over 2 tb of data, may ext4 manage two million files ? -
RE: In delta backup force the full backup task in a specific day
@florent said in In delta backup force the full backup task in a specific day:
@robyt I think I misunderstood, you want to decrease the concurrency ?
the settings is not exposed in the UX or in the config file, but it can be changed in the code if you're ready to test ( if this is an XOA, please open a ticket I will patch for you)the file is in <xo server directory>/node_modules/@xen-orchestra/backups/_runners/VmsXapi.mjs and you can put 1 in diskPerVmConcurrency: 0 It will limit the number of disk transferred in parallel per VM
that way, by limiting VM concurrency, and the disk per vm , you will limit the numbe of thread writing to the NAS
Hi, in UI i've "Number of NBD connexion per disk": i've 4 for disk, for last backup i've decreased the value to 1 for 3 backup job and 2 for the big backup job
at this moment remain only the big, the other was finished
after the copy to the vm i see a lot of nfs daemon and the load of nas goes high (over 30)
of course i've a lot of DW nfs daemon in nas -
RE: In delta backup force the full backup task in a specific day
@robyt said in In delta backup force the full backup task in a specific day:
@florent said in In delta backup force the full backup task in a specific day:
@robyt hi, I tested with up to 16 NBD connection per disk . If the xapi don't accept the connection, it will continue the backup with the open one
It should be faster, though. What are the latencies between XOA and the host, and XOA and the NAS ?
Are you using a block based storage ? The merging of such backups may be very expensive either way
Hi, disk is a single sr?
Some server has 7(8 sr for a single VM, the nas (a small QNAP) goes under a high load.
I try to lower NBD to 2 for disk and check the status of nasaddenda:
the nas is shared with nfs connection (1 gigabit)
The transfer is good, but when the transfer ended and start the other operation the load on nas goes over 30 and slow down all transfer -
RE: In delta backup force the full backup task in a specific day
@florent said in In delta backup force the full backup task in a specific day:
@robyt hi, I tested with up to 16 NBD connection per disk . If the xapi don't accept the connection, it will continue the backup with the open one
It should be faster, though. What are the latencies between XOA and the host, and XOA and the NAS ?
Are you using a block based storage ? The merging of such backups may be very expensive either way
Hi, disk is a single sr?
Some server has 7(8 sr for a single VM, the nas (a small QNAP) goes under a high load.
I try to lower NBD to 2 for disk and check the status of nas -
RE: In delta backup force the full backup task in a specific day
@CJ said in In delta backup force the full backup task in a specific day:
@robyt You may want to change your concurrency to 1 instead of the default 2. That way you won't have multiple backups trying to copy to the NAS at the same time.
Also, remember that the backups relay through XO so you could be network constrained depending on the host and SR networking.
the huge vserver is a single vm.
how many NBD connection i can use?
the nas is on gigabit lan, the problem is not the transfer (i see "nothing" in tasks but the work after the transfer