@andrewreid Yes, I can't wait to share it with everybody.
florent
@florent
Best posts made by florent
-
RE: Backblaze B2 as a backup remote
-
RE: Externalised backup LTO
@b-dietrich said in Externalised backup LTO:
Hi everyone,
I would like to know if it's possible to externalised backup on library tape with XOA ?
Is it in the roadmap for 2024 ?
I will let @olivierlambert on the backlog point. It is still planned, but there is a lot of ground work before :
- since tape can't be easily seek , so you'll have to write the backup at once no turning back to update a previously written block/metadata
- you'll have to build a catalog of tape<->backup to know which tape you'll have to use to restore, or rewrite. This is a huge change since XO don't use any database , the backup repositories are self contained : you can mount a backup repository to a new XO, and the backup will be listed . With tapes, you'll have to keep (and backup) the backup catalog. Yep , we'll need to backup the backups and ensure it's recoverable
That being said, the mirror backup feature as been built to pave the way to tape backup
For now the easiest way to do tape backup is to use full backup to a backup repository only used for this, and to mirror it to tapes. At our scale, priorities can also change if there is a big enough sponsor, that is ready to take a part of the financial load of this feature and gives us access to real world hardware and processes.
-
RE: VMware migration tool: we need your feedback!
the test with @dumarjo showed that there is still a bug during the import. I am still investigating it and will keep you informed, hopefully today or tomorrow
-
RE: VMware migration tool: we need your feedback!
@ismo-conguairta said in VMware migration tool: we need your feedback!:
I have two different behaviour on two different XO instances. Each XO instance refers to a different pool (different hosts, same xcp-ng version). In both the instances I try to connect to the same Private Virtual Datacenter based on VMware/vSphere at OVH.
In the first one I get the following error message by using the web UI: "invalid parameters" (take a look at this logfile 2023-02-28T19_25_21.933Z - XO.txt )
In the second one, I get the following error message by using the web UI "404 Not Found https://<vsphere-ip>/folder/<vm-name>/<vm-name>.vmx?dsName=<datastore-name>"
By using the xo-cli I get the "404 Not Found" on both the instances.
Regarding the "404 Not Found", I want to point out that at OVH I have a VMware datacenter (with 2 hosts) and in order to access to the storage I need to specify the parameter
dcPath=<datacenter-name>
So the right URL should be https://<vsphere-ip>/folder/<vm-name>/<vm-name>.vmx?dcPath=<datacenter-name>&dsName=<datastore-name>
Simply adding (in a static way) the dcPath specification on line :54 of esxi.mjs file makes it work.
I thought it was constant. I will look into the api to get it, and if not possible expose it in the UI
@Seclusion : noted I will look into theis error message, this one is a first for me
-
RE: VMware migration tool: we need your feedback!
@brezlord mac address and uefi should works now
-
RE: Xen-Orchestra Terraform provider and Windows
@rochemike patch done this morning
-
RE: Xen-Orchestra Terraform provider and Windows
@rochemike great, that will be even easier
can you open a support ticket and open a support tunnel ? I will connect and patch your installation
-
RE: Import from VMware fails after upgrade to XOA 5.91
@acomav you're up to date on your XOA
I pushed a new commit , fixing an async condition on the fix_xva_import_thin branch . Feel free to test on your XO from source.
-
RE: Continuous Replication job fails "TypeError: Cannot read properties of undefined (reading 'uuid')" at #isAlreadyOnHealthCheckSr
@techjeff thanks for your effort, I found the problem
can you test this branch : fix_cr_healthcheck ? (
git checkout fix_cr_healthcheck
from xen-orchestra folder) it will be merged soon
Latest posts made by florent
-
RE: CBT: the thread to centralize your feedback
@rtjdamen it's still fresh, but on the other hand, the worse that can happen is falling back to a full backup. So for now I would not use it on the bigger VM ( multi terabytes )
We are sure that it will be a game changer on thick provisioning ( because snapshot cost the full virtual size) or on fast changing VM , where coalescing an older snapshot is a major hurdleIf everything goes well it will be on stable by the end of july, and we'll probably enable it by default on new backup in the near future
-
RE: CBT: the thread to centralize your feedback
dataDestroy will be enable-able (not sure if it's really a word) today, in he meantime, the
Please note that the metadata snapshot won't be visible in the UI since it's not a VM Snapshot, but only the metadata of the vdi snapshots
latest commits in the fix_cbt branch add an additionnal check on dom0 connect, more error handling
-
RE: CBT: the thread to centralize your feedback
Hello everybody,
thanks for your feedback, Here is a work branch with CBT enabled : https://github.com/vatesfr/xen-orchestra/pull/7792 . The branch name isfix_cbt
It fixes :
-
snapshot retention with full backups
-
off by one error for retention length
-
parent locator error
-
can't destructure undefined error
-
it don't leak vdi attached in the dom0 in our lab
-
progress is back on the export task
Please test it if you can , and don't hesitate to provide feedback
Regards,
Florent
-
-
RE: Stuck VDI Exports After Latest Upgrade
@Delgado said in Stuck VDI Exports After Latest Upgrade:
This issue seems to be fixed. Tasks are finishing and disappearing. I am seeing the below errors but I believe that is being discussed in another thread possibly somewhere.
Hi,
can you upload the full log of this error ? I am still not reproducing it in our lab
regards
-
RE: Snapshots not being removed after successful backup
@Dude417 thanks for your report it helped me detect a mishandling for full backup
I will keep you informed a soon as the fix is testable/merged -
RE: Continuous Replication fails with XO update (June-20)
@Andrew said in Continuous Replication fails with XO update (June-20):
Here's part of the log....
"message": "transfer", "start": 1718906431567, "status": "failure",
HI Andrew,
can you try this branch https://github.com/vatesfr/xen-orchestra/pull/7763 ?
regards
-
RE: backups started failing: Error: VDI must be free or attached to exactly one VM
@Anonabhar because this is an immediate error for something thta was under the radarn and was (mostly ) recovering by itself
But when it fails, it's not great ( no VDI coalesce for moth to work with) .
We'll try to find a good equilibrium point between enuring backup are running correctly and detecting problems early by the end of the month
-
RE: backups started failing: Error: VDI must be free or attached to exactly one VM
@manilx Hi, manlix
after a working backup, do you have any disk attached to dom0 ? (dashboard => health )
-
RE: VMware migration tool: we need your feedback!
@Riven said in VMware migration tool: we need your feedback!:
@olivierlambert - Yes, so when we do a V2V there is only 1 VIF listed to put the migrated VIFs in to, even if the VM has 5 VIFs
Is it possible to query each vmx and allow us to select a 'network' for each VIF that it has?
not for now
-
RE: Compressed backups
@CJ said in Compressed backups:
@olivierlambert Are you referring to the compression ratio when you mention performance? I turned it on for my remote and it tanked my transfer speeds compared to the standard sequential backup.
Since I'm using zfs for my remote, is there a way to turn off compression for the delta backups?
you can turn compression off by setting vhd compression to none instead of brotly in your configuration file ,
[backups] # Mode to use for newly created backup directories vhdDirectoryCompression = 'brotli
writing vhd blocks is often slower than sequential, and compression should not have a lot of impact , but the merging is faster. So the best solution depends on the limiting factor on your infrastructure
(also this storage mode have been made for s3 which do not like modifying the files )