解决了

“ VMware Workstation”等效？

e
徽章 +1

大家好

最近，我们将我们的环境之一转换为ESX/vCenter的AHV/雅典卫城。

一切都很好，运行良好。

警告之一是，我们在“灾难”类型方案中使用了三级机器，使用该计算机，我们将使用备份解决方案来“备份” VM，并使用VMware Workstation运行。

据我了解，Nutanix没有提供“工作站”类型的解决方案，因此我希望获得有关“新”解决方案所需的反馈。

我可以构建一台小型PC并在上面运行社区版吗？

Communtiy Edition可以在说i9/32GB RAM/1TB SSD上运行，还是需要n+1才能功能？

这样，我可以将备份解决方案指向新的群集，或者让我的群集意识到NAS解决方案并根据需要在这些类型的情况下摄入AHV VM。

任何反馈都会帮助我努力！

图标

最好的答案mmsw_de2020年9月15日，14:14

If I understand the scenario correctly, this is about \u201cWhere do\u00a0we\u00a0run our\u00a0VMs when our only cluster is on fire?\u201d.\u00a0<\/p>

I\u2019m quite positive that you can\u2019t leverage any AOS or backup software feature to copy VMs to a CE cluster.<\/p>

I don\u2019t know the Veeam AHV solution and its features, but with Hycu, it\u2019s possible to export vdisk images to e.g. network shares, where they can be converted to vmdk files that can be attached to Vmware VMs. Please note that it is only vdisks that can be offloaded\u00a0this way, not complete VMs including their config. VMs will have to be prepared on the standby system.\u00a0<\/p>

Tested by exporting AHV vdisk file (RAW format) from Hycu to network\u00a0share, converting it to VMDK,\u00a0uploading it to ESXi 5.5 datastore and attaching it to a VM that was configured similar to\u00a0original\u00a0Ntx VM. ESXi VM needed another reboot to take care for newly discovered devices, but basically ran fine.<\/p>

Maybe any of this can be scripted for periodic vdisk exports.<\/p>

\u00a0<\/p>","className":"post__content__best_answer"}">

查看原件
Hi all<\/p>

\u00a0<\/p>

We recently converted one of our environments to AHV\/Acropolis from ESX\/VCenter.<\/p>

\u00a0<\/p>

All is well and runs just fine.<\/p>

\u00a0<\/p>

One of the caveats is, we have a tertiary machine we use in \u201cdisaster\u201d type scenarios and with this machine we would use our backup solution to \u201cbackup\u201d a VM to and run with VMWare Workstation.<\/p>

\u00a0<\/p>

As I understand it, Nutanix does not offer a \u201cWorkstation\u201d type solution, so I am reaching out to hopefully receive some feedback on what a \u201cnew\u201d solution would entail.<\/p>

\u00a0<\/p>

Could I build a small PC and run Community edition on it?<\/p>

\u00a0<\/p>

Can communtiy edition run on say an i9\/32gb RAM\/1TB ssd or does it need N+1 to function?<\/p>

\u00a0<\/p>

This way I could point my backup solution to the new cluster or have my cluster be aware of a NAS solution and ingest the AHV VM as needed in these type scenarios.<\/p>

\u00a0<\/p>

Any feedback will help me in the endeavor!<\/p>","quoteUsername":"EUSCADA","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

该主题已关闭以供评论

10个答复

阿罗纳
秩
UserLevel 6
徽章 +5

嗨，埃斯卡达，

您能以更具体的术语描述您的环境吗？您正在使用什么供应商来备份？

我的理解是正确的，因为您正在使用VMware工作站从备份中有效地恢复VM？

Nutanix在Commvault，Veeam，Veritas Netbackup和HYCU上有几个解决方案文档，您可以在门户网站上搜索这些文件。

Hi EUSCADA,<\/p>

\u00a0<\/p>

Are you able to describe your environment in more specific terms? What vendor are you using for the backups?<\/p>

Is my understanding correct in that you are effectively restoring a VM from a backup using VMWare Workstation?<\/p>

Nutanix has several solutions documents on Commvault, Veeam, Veritas NetBackup and HYCU you can search for those in the portal.<\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

e
徽章 +1

您好，感谢您的答复！

对不起，我的延迟。

我们有一个4个节点AHV群集运行雅典卫城。

我们曾经有一个3节点群集运行ESX / vCenter

我们将Veeam用作备份解决方案。

在我们的旧配置中，我们将VEEAM“ VM复制” VM到Workstation PC上，我们可以使用“在最坏的情况下”，在该PC上，我们将在Workstation中启动VM。

现在我们已经迁移到AHV，我们没有解决方案来“将VM从我们的群集中复制并在PC上运行”。

我希望这是有道理的！

我们正在寻找可以在旧服务器上安装的社区版本，看看是否可以解决我们的问题。

感谢您提供的任何其他输入。

Hello and thanks for the reply!<\/p>

\u00a0<\/p>

Sorry for my delay.<\/p>

\u00a0<\/p>

We have a 4 node AHV cluster running Acropolis.<\/p>

\u00a0<\/p>

We used to have a 3 node cluster running ESX \/ vCenter<\/p>

\u00a0<\/p>

We are using Veeam as a backup solution.<\/p>

\u00a0<\/p>

In our old config, we had Veeam \u201cVM Copy\u201d a VM to a Workstation PC that we could use \u201cin worst case scenarios\u201d and on that PC we would launch the VM within workstation.<\/p>

\u00a0<\/p>

Now that we have migrated to AHV, we don\u2019t have a solution to \u201cCopy a VM off our cluster and run it on a PC\u201d.<\/p>

\u00a0<\/p>

I hope this makes sense!<\/p>

\u00a0<\/p>

We are looking at Community Edition to install on an old server and see if this will solve our issue.<\/p>

\u00a0<\/p>

Thanks for any additional input.<\/p>","quoteUsername":"EUSCADA","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

阿罗纳
秩
UserLevel 6
徽章 +5

谢谢您的解释。我觉得您可以选择本地快照，并从快照中恢复VM。您无需进行现场还原，因此可以拥有VM的副本，然后如果您不再需要它，则可以bin。

因此，数据保护>创建保护域（在列表中添加感兴趣的VM）>配置时间表（仅本地），设置要保留的快照数。

要恢复VM，请使用该快照可以恢复的选项（PD>选择PD的PD>本地快照）。您无需恢复所有VM，并且它们会以电源关闭状态恢复，因此您有机会根据需要编辑网络设置。

让我知道这是否有帮助。

Thank you for explaining. I feel like you could go with local snapshots and recover a VM from a snapshot. You don\u2019t have to do in-place restore so you can have a copy of the VM and then bin it if you no longer need it.<\/p>

So Data Protection> Create Protection Domain (add VMs of interest to the list)>configure schedule (local only), set number of snapshots to keep.<\/p>

To recover a VM there is an option against the snapshot to recover (PD>select PD of interest> local snapshots). You don\u2019t have to recover all VMs and they are recovered in a powered off state so you have a chance to edit networking settings if you need to.<\/p>

Let me know if that helps.<\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

m
UserLevel 2
徽章 +5

如果我正确理解场景，这是关于“我们唯一的群集着火时我们在哪里运行VM？”。

我很肯定您无法利用任何AOS或备份软件功能将VM复制到CE群集。

我不知道Veeam AHV解决方案及其功能，但是使用HYCU，可以将VDisk图像导出到例如网络共享，可以将它们转换为可以连接到VMware VM的VMDK文件。请注意，只有VDisks可以通过这种方式卸载，而不是完成包括其配置在内的VM。VM必须在待机系统上准备。

通过将AHV VDISK文件（RAW格式）导出从HYCU到网络共享，将其转换为VMDK，将其上传到ESXI 5.5数据存储，然后将其连接到与原始NTX VM相似的配置的VM。ESXI VM需要再次重新启动来照顾新发现的设备，但基本上运行良好。

也许可以将其中的任何一个用于定期VDISK出口。

If I understand the scenario correctly, this is about \u201cWhere do\u00a0we\u00a0run our\u00a0VMs when our only cluster is on fire?\u201d.\u00a0<\/p>

I\u2019m quite positive that you can\u2019t leverage any AOS or backup software feature to copy VMs to a CE cluster.<\/p>

I don\u2019t know the Veeam AHV solution and its features, but with Hycu, it\u2019s possible to export vdisk images to e.g. network shares, where they can be converted to vmdk files that can be attached to Vmware VMs. Please note that it is only vdisks that can be offloaded\u00a0this way, not complete VMs including their config. VMs will have to be prepared on the standby system.\u00a0<\/p>

Tested by exporting AHV vdisk file (RAW format) from Hycu to network\u00a0share, converting it to VMDK,\u00a0uploading it to ESXi 5.5 datastore and attaching it to a VM that was configured similar to\u00a0original\u00a0Ntx VM. ESXi VM needed another reboot to take care for newly discovered devices, but basically ran fine.<\/p>

Maybe any of this can be scripted for periodic vdisk exports.<\/p>

\u00a0<\/p>","quoteUsername":"MMSW_DE","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

e
徽章 +1

你好 @mmsw_de并感谢您的答复。

因此，将CE群集作为“远程群集”和指向其指向其备份解决方案的想法不起作用吗？

不幸的是，我们以前的ESX和Veeam“将整个VM复制”到独立的PC的解决方案效果很好……

老实说，我们忘记了这篇文章，直到我们与AHV“全部”。

哦！哈

我将考虑导出VDisk图像，并查看情况如何，尽管我没有那个作品的经验，尽管听起来很直截了当。

还有一个问题，一个人如何将VDisk转换为VMDK？与AHV移动？

非常感谢您的答复

Hi\u00a0@MMSW_DE<\/user-mention>\u00a0and thanks for the reply.<\/p>

\u00a0<\/p>

So the idea of running a CE cluster as a \u201cRemote cluster\u201d and having a backup solution pointing to it wont work?<\/p>

\u00a0<\/p>

Semi unfortunate as our previous solution with ESX and Veeam \u201ccopying the entire VM\u201d to a stand alone PC worked just fine\u2026<\/p>

\u00a0<\/p>

We honestly forgot about this piece until we were \u201call in\u201d with AHV.<\/p>

\u00a0<\/p>

Ooops! HA<\/p>

\u00a0<\/p>

I will look into exporting the vdisk images and see how that goes, although I don\u2019t have experience with that piece, although sounds straight forward.<\/p>

\u00a0<\/p>

One more question, how does one convert a a vdisk to vmdk? With AHV Move?<\/p>

\u00a0<\/p>

Thanks much for your reply<\/p>","quoteUsername":"EUSCADA","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

m
UserLevel 2
徽章 +5

有一个称为QEMU-IMG的命令行工具，可让您在各种方向上处理VDISK图像。

即使有第二个集群以适合您的DR（当然是对我们来说），您也会很快获得对AHV群集的稳定性的信心。如Alona所建议的那样，设置本地快照，以涵盖大多数短期VM问题，并确保将Veeam备份置于您假定的灾难范围之外。

无论如何，对于VMware WS（或CE）来说，一个四个节点群集和您可以在其上运行的工作负载的数量/大小听起来像是很多。

There is a commandline tool called\u00a0qemu-img that lets you process vdisk\u00a0images in all sorts of directions.<\/p>

Even if\u00a0having a second cluster for proper DR is out of reach for you (as it certainly\u00a0is for us), you will quickly gain confidence in the stability of your AHV cluster. Set up local snapshots as suggested by Alona to cover the majority of short-term VM issues and be sure to have your Veeam backups out of range of your assumed disaster.<\/p>

A four\u00a0node cluster and the number\/size of workloads you can run on it sounds like a lot to chew on for VMware WS (or CE) anyway.<\/p>","quoteUsername":"MMSW_DE","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

e
徽章 +1

再次感谢您的答复，感谢它。

我们的环境是独一无二的，在所有现实中，我们只需要1 VM即可运行整个过程。（我们将复制到第三级机器）…

我们的Veeam备份发送到2倍位置，一个位于服务器机架外。

我们一直在集思广益，让所有群集互相交谈（我们有3个群集，尽管这是第一个从VMware握把中脱颖而出并转换为AHV的努力），但是在其他2个群集转换后，这将必须发生到AHV。

非常感谢您的答复

Thanks again for the reply, appreciate it.<\/p>

\u00a0<\/p>

Our environment is unique, in all reality we only need 1 VM to run our entire process. (The one we would copy off to a tertiary machine)\u2026<\/p>

\u00a0<\/p>

Our Veeam backups are sent to 2x\u00a0locations and one is outside of the server rack.<\/p>

\u00a0<\/p>

We have been brainstorming having\u00a0all of our clusters talk to each other (we have 3 although this one is the first endeavor of getting out from the VMWare grip and converted to AHV), but that will have to happen after the other 2 clusters are converted to AHV.<\/p>

\u00a0<\/p>

Thanks much for your replies<\/p>","quoteUsername":"EUSCADA","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

e
徽章 +1

你好，我们又见面了 @mmsw_de

只是好奇，在HYCU软件界面中，“工作”是什么来伸入Nutanix存储并导出VDisk图像的东西？

更好的是，有没有办法（NCLI驱动？）可以抓住VDisk并将其从Nutanix存储中复制出来？

目前，它似乎不是Veeam软件中的功能。

Hi again @MMSW_DE<\/user-mention>\u00a0<\/p>

\u00a0<\/p>

Just curious, in the HYCU software interface, what is the \u201cjob\u201d called to reach into the Nutanix storage and export the vdisk images?<\/p>

\u00a0<\/p>

Better yet, is there a way (ncli driven?) that I can grab the vdisk and copy it out of the Nutanix storage?<\/p>

\u00a0<\/p>

It does not appear to be a feature in the Veeam software at this time.<\/p>","quoteUsername":"EUSCADA","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

e
徽章 +1

啊，实际上只是找到了这个

https://next.nutanix.com/how-it-works-22/ahv-vdisk-part-part-part-1-wher-wher-wher-are-they-sthey-stored-33618


m
UserLevel 2
徽章 +5

在HYCU软件界面中，什么“工作”是什么来访问Nutanix存储并导出VDisk图像？

当您使用HYCU恢复VM时，将磁盘图像导出到网络共享是一个选择。它使用自己的备份进行导出，这是有道理的，因为从运行VM下载实时VDISK文件可能不明智。

\t

in the HYCU software interface, what is the \u201cjob\u201d called to reach into the Nutanix storage and export the vdisk images?<\/p>\t<\/content-quote>

Exporting disk images to a network share is an option when you restore a VM with Hycu. It uses its own backups for export, which makes sense because it may not be wise to download a live vdisk file from a running VM.<\/p>","quoteUsername":"MMSW_DE","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

Baidu