您如何组织 VMware Workstation 映像? [英] How do you organize VMware Workstation images?

问题描述

我目前使用 VMware 工作站为我工作的各种客户端创建单独的工作区.因此，对于给定的客户端，我只安装特定工作所需的软件，而不必担心客户端 #1 的软件 A 为客户端 #2 搞砸软件 B.

I currently use VMware workstation to create separate workspaces for various clients that I do work for. So for a given client I only install software needed for a specific job, and don't have to worry about software A for client #1 mucking up software B for client #2.

如果有足够大的硬盘，这运行良好，但我不确定我是否充分利用了 VMware.我在准备一份新工作时经历的步骤是:

With an adequate sized hard drive this works well but I am not sure I am using VMware to its best advantage. The steps I go through when setting up for a new job are:

1. 对我保存的基础 VMware 映像执行 Windows 更新.
2. 制作基本映像的完整克隆并为新作业重命名
3. 启动新映像并根据需要进行配置/安装.

这样做一段时间后，我现在有一组 VMware 映像，这些映像都处于不同的更新级别，除非我手动进入每个映像并开始更新周期.如果我想要在我的所有图像中使用一些新工具，我也必须四处走动并进行多次手动安装.但是我知道每个图像都是独立的(尽管一次命中需要 10+Gb)，并且如果单个图像发生任何问题，那么问题就不会传播到任何其他图像，我对此感到很放心.(请注意，我会定期备份所有图片)

After doing this for a while I now have a collection of VMware images sitting around that are all at different levels of updates unless I manually go into each image and kick off an update cycle. And if there is some new tool that I want in all of my images I have to also go around and do multiple manual installs. But I feel secure in knowing that each image is self contained (albeit taking 10+Gb at a hit) and that if anything happens to a single image then an issue cannot propagate into any other image. (Note that I do do regular backups of all my images)

所以我的问题是我这样做是最好的方式，还是应该考虑链接克隆，以便我只需要在我的基本系统上执行 Windows 更新或通用应用程序安装?每种组织方式的优缺点是什么?

So my question is am I doing this the best way, or should I consider linked clones so that I only have to do a windows update or common application install on my base system? What are the pro's and con's of each way of organizing things?

此外，尽管我尽量不将数据文件保存在 Image 的本地磁盘中，但我发现与 Images 文件系统相比，共享到本地硬盘驱动器的速度似乎非常慢，因此我倾向于将工作留在图像中.我应该强迫自己不要在图像中留下数据吗?或者换句话说，在映像文件系统中的任何单个文件变得无法访问之前，VMware 映像会损坏多少?

In addition, although I try not to keep data files inside the Image's local disks I find that the share to my local hard drive seems very slow compared to the Images file system, hence I tend to leave work inside the image. Should I force myself to not leave data inside the image? Or put another way, how much corruption can a VMware image take before any single file in the images filesystem becomes inaccessible?

编辑

自从发布这个问题后我的一些想法

Some thoughts I have had since posting this question

• 通过完整克隆，我可以将旧作品存档并从主硬盘中删除
• 链接克隆比完整克隆占用的空间少得多，但我担心将链接克隆归档到其他地方.
• 制作完整克隆所需的时间并不算太长(5-10 分钟)，而且我通常每周进行一次.
• 不过，我也倾向于做很多让我们看看全新安装会发生什么"，尤其是在我记录如何为客户端安装应用程序时.
• 我发现我的 VMware 映像会在我的硬盘驱动器上造成大量碎片，因此在使用 VMware 之前，我还进行了更多的碎片整理.我不确定使用链接克隆是否会减少这种情况.

推荐答案

我会坚持使用您当前的系统.在这种情况下，拥有隔离图像可为您提供更大的灵活性.更新和安装可能会花费您更多时间，但这是值得的.这主要是你在做其他事情时可以在后台进行的事情，所以如果你很好地管理你的时间，那么花在这上面的时间应该可以忽略不计.

I'd stick with your current system. In this situation, having isolated images gives you a lot more flexibility. It might cost you some more time doing updates and installs, but it will be worth it. And that's mostly stuff that you can have going in the background while you do other things, so if you manage your time well the time spent on that should be negligible.

此外，将图像保存在自己的磁盘上或至少保存在自己的分区上可能是个好主意.如果您这样做，它应该不会对系统其余部分的碎片产生任何影响.

Also, it's probably a good idea to keep your images on their own disk or at least on their own partition. If you do that it shouldn't have any effect on fragmentation on the rest of your system.

这篇关于您如何组织 VMware Workstation 映像?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！