Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 855
  • Last Modified:

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

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
Senior IT System Engineer
Asked:
Senior IT System Engineer
  • 4
  • 3
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
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
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
for all 50 VMs is 2GB ?

2GB is nothing, that's small?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Senior IT System EngineerIT ProfessionalAuthor Commented:
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
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
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
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
It's the only suggested way in Citrix xenDesktop environment.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now