Getting MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled) with XenServer 7.1

olivierlambert

On the technical side, upgrading to XS 7.1 to XCP-ng 8.2 will cost you exactly the same effort than upgrading from 7.1 to XS 8.2

nikade

@marcom said in Getting MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled) with XenServer 7.1:

@olivierlambert Yes I know, I'm evaluating several solution, also the Xen 8.2 and yours.

I still don't have clear idea, I have to read more about your xcp-ng

Thanks for the support

BR
Marco

Do you currently pay for XenServer or are you using the free version?
XenServer and XCP-NG is pretty much the same and XCP-NG offers both a free version AND a paid version which includes support, XCP-NG also offers more features than XenServer and the migration would be rather easy since you are already using XenServer.

marcom

@nikade Sorry for the late answer. At the moment running the free version, but I would like to switch to supported one, because we are a company and we want the systems and the support really reliable.

There is something interesting that attract me in the project. Maybe I will ask a demo to @olivierlambert to go deep in some aspects.

BR
Marco

nikade

@marcom said in Getting MESSAGE_METHOD_UNKNOWN(VDI.get_cbt_enabled) with XenServer 7.1:

@nikade Sorry for the late answer. At the moment running the free version, but I would like to switch to supported one, because we are a company and we want the systems and the support really reliable.

There is something interesting that attract me in the project. Maybe I will ask a demo to @olivierlambert to go deep in some aspects.

BR
Marco

I understand, I think you are correct about asking Vates for a presentation or a demo of some kind if you want to buy their supported product.

Remember that you can always setup a lab with the free/opensource version of XCP-NG 8.2.1 (8.3 will be released soon as well) and try stuff out.
The XCP-NG product is very much a like the XenServer product, but at the same time it is very different because of the enhancements made by Vates and the community.

marcom

@nikade yes I will do.
Easy question. With Xen actually I use also the Windows APP Xen center to manage the pool.
With XCP-ng if I undestood correctly will be used Orchestra as management tool, right?

In that case would be better to have Orchestra as physical server outside the Hypervisor environment? or?

BR
Marco

olivierlambert

Everything is possible, you can run XO on the production pool or anywhere else. It's up to you. Both solutions work fine.

nikade

I can only speak for myself, but we have always run it as a VM in the pool.
The VM itself will be migrated to a different host during maintenance, updates and so on as long as you have shared storage (iSCSI or NFS).

marcom

mmm ok. Let's take an example. Full disaster recovery. I have my backups on the NAS but I lost everything and I have to install everything from scratch.
What are the steps I need to do? What I imagine is:

reinstall the XCP-ng
reinstall the Orchestra on it
reconfigure the NAS on it

After that I can restore the metadata and backups, and also the shared storage will be reconfigured automatcally?

Are more or less those the steps?

BR
Marco

nick.lloyd

@marcom The only thing that I would add (and I'm guessing you knew, adding this just in case) is to restore the backup of XO(A) and the pool metadata.

nikade

Exactly what @nick-lloyd said, it is important to backup XO configuration AND the pool metadata as well to be able to recovery completely.