@olivierlambert now work fine, thank you
Best posts made by robyt
Latest 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