Have you tried the latest version?   ASM/VE has been renamed VSM, version 3.5 is available on the EQL support website. 
Hi all, Apologies if this has been asked already, but I've searched and come with nothing on this. The basic problem is that it does not appear to be possible to take quiesced virtual machine snapshots with the EqualLogic Host Integration Tools for VMware (HIT/VE) in an environment that is set up to NOT replicate "transient data" (virtual machine swap files and Windows paging files). In such an environment, a replication schedule configured in HIT/VE will run as specified, but not take VM level snapshots of the protected VMs, hence replicas aren't quiesced at the file system and application levels, and recovery is done from a replica which is, at best, crash consistent. I've been testing SRM 5.0 with Dell Equallogic firmware 5.2.5. In production I'll eventually be deploying SRM 5.1 and firmware to 6.0.1. From my reading it appears that I'll almost certainly face the same issues with these versions, as I believe the issue is a limitation of the EqualLogic VMware Host Integration Tools, which I am already using the latest version of (3.1.2). I want to avoid replicating the transient data to save bandwidth. The SRM 4.0 Administration guide included a comprehensive explanation of how to avoid replicating both vswp files and Windows paging files. The guide for SRM 5.1 only has the procedure for placing the vswp on a non-replicated datastore, and is qualified by the statement: "CAUTION Under normal circumstances, you should keep the swap files in the same datastore as the other virtual machine files. However, you might need to prevent replication of swap files to avoid excessive consumption of network bandwidth. Also, some storage vendors recommend that you do not replicate swap files. Only prevent replication of swap files if it is absolutely necessary." For HIT/VE to take a quiesced snapshot at the VM level in sync with the replication snapshot at the array level, the entire VM, including all of its transient data, must reside on one datastore. If the vswp file file resides on a different datastore, the HIT/VE "Create Smart Copy Replica" wizard throws up the warning "VM [virtual machine] is located on 2 datastores. VM snapshot will not be created". As I stated above, a smart copy replication schedule created in HIT/VE will run without any warnings, and simply not snapshot the VMs. It would appear that we are forced to choose between properly quiesced VM replicas, and saving bandwidth by excluding useless data from replication. Has anyone else encountered this situation? If so, what was your choice? Better chance of a smooth recovery at the expense of a higher RPO is presumably preferable. Is there a workaround?
Specifying a non-replicated datastore for transient data using array-based 
replication and VMware SRM