VMware Lab Manager、数据库和 Delta
我们刚刚开始安装 WMWare Lab Manager，但有一件事我无法弄清楚，那就是数据库和增量。
设想。我们创建 Database-1 的基本映像，然后将其克隆以供人们进行测试。我们将该数据库称为 Clone-1。现在，一位开发人员出现并决定他想要自己的 Clone-1 副本，这样他的工作就不会干扰团队的其他成员。开发人员从 Clone-1 创建一个克隆，我们将其称为 Personnel-Clone-1。现在，当团队的其他成员从 Clone-1 更新、插入和删除记录时，开发人员是否能看到 Personnel-Clone-1 中的这些更改？如果是这样，对 Clone-1 的更改似乎可能会使 Personnel-Clone-1 不稳定。另一方面，如果 Personnel-Clone-1 是 Clone-1 的完整副本，那么它似乎会占用大量磁盘空间。
We are just starting to install WMWare Lab Manager and there is one thing I cannot figure out and that is databases and deltas.
Scenario. We create a base image of Database-1 which is then cloned for people to do testing on. We will call that database Clone-1. Now a developer comes along and decides he would like his own copy of Clone-1 so that his work does not interfere with the rest of the team. The developer creates a clone from Clone-1 which we will call Personnel-Clone-1. Now when the rest of team updates, inserts, and deletes records from Clone-1 does the developer see those changes in Personnel-Clone-1? If so it would appear that changes to Clone-1 could make the Personnel-Clone-1 unstable. On the other side of the coin if Personnel-Clone-1 is a complete copy of Clone-1 that would seem like it would eat up a lot of disk space.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用克隆源的用户将永远不会看到对克隆所做的更改。 Lab Manager 在克隆模板或配置时会创建虚拟磁盘 (VMDK) 的链接克隆。链接克隆类似于快照，其中为克隆创建增量磁盘。增量磁盘很小，最初只有几兆字节。 Lab Manager 将引用源 VMDK + 增量磁盘。大多数块是从源磁盘读取的。但是，当数据开始写入克隆中并更改源磁盘中的内容时，Lab Manager 将执行写入时复制并将新数据记录在增量磁盘中。然后将从增量磁盘而不是克隆源读取新数据块。链接克隆可以由这些增量磁盘组成，也可以创建长树。如果您在 Lab Manager 中查看数据存储并查看上下文视图，Lab Manager 将向您显示链接克隆树的图形视图。
The user using the source of the clone will never see the changes made to the clone. Lab Manager creates linked clones of the virtual disks (VMDKs) when it makes a clone of a template or configuration. Linked clones similar to snapshots where a delta disk is created for the clone. The delta disk is small, initially only a few megabytes. Lab Manager will reference the source VMDK + the delta disk. Most blocks are read from the source disk. However when data starts to be written in the clone changing what it is in the source disk Lab Manager will do a copy-on-write and record the new data in the delta disk. The new data blocks will then be read from the delta disk instead of the of the source of the clone. Linked clones can be be made of these delta disks as well creating a long tree. If you look at your datastores in Lab Manager an view the context view, Lab Manager will show you a graphical view of the linked clone tree.