Before migrating to XCP-NG I was a VMWare user with Veeam as my backup solution, it works but it's 3rd party and somewhat bloated. I think one of the big things xcp-ng has to offer is the native backup. I honestly wouldn't even consider Veeam unless there is some niche use for it that native can't do.
Best posts made by sluflyer06
-
RE: Veeam and XCP-ng
-
RE: Just performed server update and stats page is blank in XO now.
@olivierlambert oh cool, i did poke around the xo forum but not the 8.3 thread, awesome no problem then, thanks!
-
RE: Want to compare insecure_nbd but doesn't seem to work (secure does)
@olivierlambert I'm willing to dig in and provide any data. right now it's 10 VM's all with 1 disk each, i'm currently running a backup without NBD using my flash array as a NFS destination, it's a handful of fast samsung SAS 12 SSD's that are striped (they're 3.2TB each). When that finishes I'll flip NBD back up and re-run so at least I think that will take storage out of the equation I believe.
-
RE: Cannot export OVAs
@Andrew Exporting all my large VM's worked on that branch.
-
RE: Backup jobs started to fail after last XOA update
@Forza Wow, I just tried that out and backup speed increased by 48%.
Latest posts made by sluflyer06
-
RE: Veeam and XCP-ng
Before migrating to XCP-NG I was a VMWare user with Veeam as my backup solution, it works but it's 3rd party and somewhat bloated. I think one of the big things xcp-ng has to offer is the native backup. I honestly wouldn't even consider Veeam unless there is some niche use for it that native can't do.
-
RE: Just performed server update and stats page is blank in XO now.
@olivierlambert oh cool, i did poke around the xo forum but not the 8.3 thread, awesome no problem then, thanks!
-
Just performed server update and stats page is blank in XO now.
Hi,
I"m on 757a8 in XO and yesterday I let XO apply pending patches to my single host machine and then rebooted the host and now all my stat pages for VM's and the host itself all say 'no stats'.
Not sure where to look or where I go from here. Thanks!
-
RE: OIDC not redirecting back to XO
@maxcerny maybe post the config you are using? I use OIDC with Google for XO and it worked right out of the gate.
-
RE: Google Sign-in stopped working "internal server error" (log attached)
@HeMaN this may have actually worked...
In etc/network/interfacesThe primary network interface
allow-hotplug eth0
iface eth0 inet dhcpThis is an autoconfigured IPv6 interface
iface eth0 inet6 auto
post-up route add default via 10.10.10.1 dev eth0auto eth1
iface eth1 inet static
address 10.10.5.188
post-up route del default dev eth1 -
RE: Google Sign-in stopped working "internal server error" (log attached)
@olivierlambert well I still can't have 2 networks in that VM, literally all I need to do is be able to set 10.10.10.1 in eth0 as the default gateway and I can find no way to do that. Debian is defaulting to eth1 with the backup network as default. I can find no persistent way to set a default gateway of my choosing.
-
RE: Google Sign-in stopped working "internal server error" (log attached)
@olivierlambert there no XO problem. I thought I figured out how to have a 2nd network on the debian XO VM but I'm at a loss. I spent half the night trying to figure out how to make a persistent default gateway in debian and nothing seems to work. Either the VM has no access on my first subnet or ONLY has access to the 2nd subnet if I did a defined route in interfaces file. This seems like such a simple thing but I've tried everything from every forum I can find.
-
RE: Want to compare insecure_nbd but doesn't seem to work (secure does)
@florent like Oliver was telling me, to compare secure to secure, it is faster than https,.still curious if anyway to try insecure.
Also. Is there a way to update XO (from sources) without losing the config.yaml or just a minor inconvenience until NBD is fully rolled into XO? (I assume we'll get told when we don't have to run custom config for NBD whenever it's ready?)
-
RE: Google Sign-in stopped working "internal server error" (log attached)
Shows my lack of Linux fu, the solution was flushing the default route in debian and then setting it to eth0.
Edit(2 hours later): ended up being so much more digging to make that a persistent change, but appears to be working after reboot now.