Howdy folks, just curiosity I have staging environments for Production Public VMs I like to test upgrades and changes on staging environments, is it possible to copy a existing Disk to use on another staging Virtual Machine without messing with the existing VM?

Regards

@waveguide This makes sense. Windows will treat it as changing hardware due to the Boot environment and BIOS.

It is no different to doing a motherboard swap on a Server or PC.

Windows should reactivate though once connected to the Internet.

@olivierlambert I am open to building stuff into XCP-ng if my knowledge was there to do it.

@olivierlambert Thanks for your reply. I will have a play over the weekend. Have a few days as it’s bank holiday so I can get something’s done. Are you going to implement the UPS API you did for me? I’ve chooses to go with PowerChute in the end over NUT. I will post some documentation once I have implemented it and tested if that’s okay.

Regards.

@olivierlambert Hope you have a great time away sir Would it be possible if you could add dark mode to the next version of XO 5.9.4 ? I know you mentioned about it being in version 6. Anyways have a good weekend

@olivierlambert That's great, hope something great comes out of it. Good luck

@olivierlambert said in Dell cancels VMWare contract after Broadcom purchase:

Time to make a phone call to Dell

Yes sir do it. I hopefully a contract between you / Vates and Dell is on the horizen. Really hope XCP-ng comes as the standard for Virtualization just like ESXi once was.

@olivierlambert That's great, any luck with partnership with Dell?

@tc-atwork that’s not entirely true. I’ve had a few clients that has had issues with Veeam where backups get stuck and never finish until you restart Veeam. When having problems like this, this in my opinion is not good enough for backups.

My previous job had 8 Hypervisors in a Cluster which also used Veeam and backups was getting stuck.

@jasonnix there is having something faster and there is something that’s going to be reliable. I’d rather compromise on faster backup speed and have the designed backup system.

I’m not saying that Veeam isn’t going to be reliable but what I am going to say is that you are at more risk of backups not being reliable and you are going to have to consult Veeam if you need help resolving a issue, where with XO you are not going to have any problems as it’s designed to work.

Not only that you need to think about extra licensing too.

If this is a Production environment I would go with the XCP-ng and XO because if something goes wrong you are going to be a laughing stock to the company it will be embarrassing. If it’s a homelab then it doesn’t really matter if it breaks.

@nikade that is one of the downfalls. Limit on backup, I have a 10Gbp iSCSI backbone with 10Gbp core network but maximum I am able to achieve is 80mbps maximum turns outs it’s a known problem according to Olivier Citrix Hypervisor also has the same problem.

@Andrew Meh if you say so, i mean it is up to you but it will only end in tears.

Making something work for backups which is so crucial is a bad thing.

@aurora-chase why would you want to use a 3rd party solution? XO has it all built in. Question is what feature is it your wanting and what doesn’t XO have built in which veeam have? Personally my opinion is that XO has all features that Veeam has and using Veeam means an extra VM and more resources.

@jasonnix better to use XO for backups tbh. But it would work.

@jasonnix Yes XCP-ng has vSAN look here https://xcp-ng.org/docs/storage.html#storage-types it is called XOSAN.

XCP-ng will work fine with EMC & QNAP. I am using two EMC iSCSI SANs with my 3 node Cluster.

@jasonnix Depends what the requirement are, extras like vSAN will require licensing but Type 1 Hypervisors are all like this tbh. Personally when it comes to shared to storage I would either recommend using iSCSI or NFS than vSAN only because you would require high speed networking. Performance. In my testing between ESXi and XCP-ng there aren’t many differences but then again it all depends on the hardware that is being used. I’ve tested on R710s, R620s, R630s and all performed quite well.

Security. That is all down to the Technician that has deployed it, I wouldn’t expose it to the Public for sure.

@nikade no management VLAN looks a mess. Don’t moan when you get compromised and you wonder why data breaches happen

@nikade that is wrong. Bond0 never has a IP. It is one of the weaknesses with TCP-IP and 802.3ad. When I did my CCNA/CCNP it was well documented.

@nikade correct. But I strongly recommend putting Management in a management VLAN. Do away with Native VLANs. Bond0 should never have a IP on it. Build Bond0 then VLANs on top I.e MGMT VLAN, Servers that are going to be exposed in an isolated VLAN. It is good practice to not use Native VLAN 1 and working in a Data Center like myself VLAN everything.

@OskarNTT you select the both which will automatically assign it to management just like in XCP-ng Center. I’ve done it like this on 3 nodes in a cluster.