Solved

Maintain control of VMware VM snapshot over the Citrix Non-persistent VM deployed by MCS ?

Posted on 2014-04-22
7
838 Views
Last Modified: 2014-06-03
Hi All,

By using Citrix XenDesktop 7.5 and VMware vSphere 5.1u1 using MCS delivery method.

I have successfully deployed 50x Windows 7 desktop VM and also Windows Server 2008 Std. R2 (for XenApp) in my VMFS data store.

However, the VM is growing bigger overtime even after user log off from the session. To make things even worse, the VM was reported to have huge snapshot that cannot be closed / committed from vSphere console.

So how can I make sure that the VM snapshot is always at the manageable level to avoid datastore crash ?

Thanks.
0
Comment
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 121
ID: 40014613
How large is the snapshot?

At deployment is a snapshot used with the VM?

Can you create a new golden image without the snapshot, e.g. new clone parent vmdk?
0
 
LVL 8

Author Comment

by:Senior IT System Engineer
ID: 40014623
Hi Andrew,

The Snapshot size (based on the redo log) is 2 GB for all of the 50x VM so it is quite large.

The VM was deployed by Citrix from one single golden image and then snapshot as the linked clone to create non-persistent VM which will clear up the changes after the VM is rebooted from the Citrix Studio console.

Going to the vSphere console snapshot manager shows nothing about the snapshot, but yet VCenter keeps on reporting the snapshot is growing larger everyday.

I don't know how can we manage the VDI VM deployed by Citrix to prevent data store crash.
0
 
LVL 121
ID: 40014637
for all 50 VMs is 2GB ?

2GB is nothing, that's small?
0
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

 
LVL 8

Author Comment

by:Senior IT System Engineer
ID: 40014674
well that is growing bigger, because it is just the redo log. The base image is 40 GB
and each VM that is deployed from this base VM image got differential disk 16 MB and 2 GB redo log.
0
 
LVL 121
ID: 40014691
Yes, okay so the snapshot for each VM is 2GB, and over the course of deployment how large does it grow.

Using Linked Clones reduces the overall space, that is required for deployment, if you deployed standard VMs, that would be:-

40GB x 50VMs, rather than 40GB + 50 VMs * Snapshot size.
0
 
LVL 8

Accepted Solution

by:
Senior IT System Engineer earned 0 total points
ID: 40024612
it seems that the only way to reduce it is by resetting / rebooting the VM automatically from the XenDesktop policy.

Rebooting from vSphere client still not clearing the snapshot file size.
0
 
LVL 8

Author Closing Comment

by:Senior IT System Engineer
ID: 40108048
It's the only suggested way in Citrix xenDesktop environment.
0

Featured Post

Automating Your MSP Business

The road to profitability.
Delivering superior services is key to ensuring customer satisfaction and the consequent long-term relationships that enable MSPs to lock in predictable, recurring revenue. What's the best way to deliver superior service? One word: automation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question