Condusiv Technologies's philosophy in regards to Customer Service is to service you
as near-instantly as possible. We also have one of the best-trained Support staffs in the business.
If possible, we like to get your questions answered on the spot. In the event that it is not,
we will ensure that you get your answers as quickly as we possibly can.
Request Support Now »
To provide you with more immediate assistance, we have provided commonly asked questions and
answers for online help, customer service and tech support.
Top 5 Questions from V-locity and Diskeeper Customers
V-locity I/O Reduction Software Put to the Test on 3500 VMs
Largest-Ever I/O Performance Study
V-locity 6.0 Solves Death by a Thousand Cuts in Virtual Environments
V-locity® VM consists of one component for both Microsoft® Hyper-V® platforms for VMware® ESX™/ESXi.™, in its present iteration. Citrix is not currently supported.
The V-locity VM Guest program is installed in all Windows® virtual machines hosted on Microsoft Hyper-V or VMware ESX/ESXi virtualization platforms.
V-locity 3 consists of two components for Microsoft Hyper-V platforms and two components for VMware ESX/ESXi.
The list of currently supported virtual platforms is: Microsoft Hyper-V, VMware ESX/ESXi 4.0 or later. It currently is not supported on Citrix XenServer.
The list of currently supported virtual platforms is: Microsoft Hyper-V, VMware ESX/ESXi 4.0 or later. V-locity 3 offers limited Citrix XenServer support. The V-locity 3 Guest can install with full functionality, but there is currently no Host Agent support. As a result, no automatic special virtual disk type detection is available, nor disk compaction features. Sparse disks or VMs employing any copy-on-write technologies should have Automatic Optimization disabled outside of scheduled maintenance windows where these features are temporarily disabled.
The V-locity VM Guest program will not install on the Hyper-V Host computer.
The V-locity 3 Host for Hyper-V will defragment the host NTFS file system, including any virtual hard disk files.
Yes, V-locity VM is designed to minimize impact on shadow copies.
Yes, you can run V-locity 3 on VSS-enabled drives. We recommend using the manual and the automatic VSS defragmentation operations that you can enable via the V-locity 3 configuration properties options.
Each V-locity VM program passively monitors I/O’s during its own local analysis as a basis for improving the performance of the system.
Each V-locity 3 Guest passively monitors resource usage during its own local optimization and determines when activity is impeded by other virtual machine activity on the same host or another host attached to the same storage. This invisible monitoring method requires no network resources or local resource overhead.
In ESXi 4.1 and 5.0, Storage vMotion will not automatically reclaim virtual disk space that has previously been zeroed out by V-locity. VMware is working on a resolution for this issue. There is a workaround which can be performed manually during a maintenance window:
Note: When you inflate the .vmdk, it converts the.vmdk provisioning from Thin to Thick. This is expected – after the Storage vMotion it converts it back to Thin.
This function was previously performed by the V-locity 3 Host program for Hyper-V and is no longer available in the V-locity VM program since there currently isn’t a host program.
The V-locity 3 Host for Hyper-V natively provides the ability to manually compact virtual disks. If you still wish to utilize manual disk compaction over VMware ESX, install the V-locity 2 Host Service for ESX (but not ESXi). V-locity 3 still fully supports the V-locity 2 Host Service for this purpose.
The V-locity VM program does not perform this function so the monitoring of a system for compaction purposes would need to be handled by the VM host platform’s management program.
The V-locity 3 Host Agent/Host for Hyper-V will indicate what degree of reclamation is available from associated virtual disks and whether compaction is recommended.
This function is no longer supported under V-locity.
You can only compact an ofﬂine Dynamic/Thin virtual hard disk using the V-locity 3 Host for Hyper-V/V-locity 2 Host Service. Dynamic/Thin drives are volumes where the space is allocated as needed.
No, I-FAAST® (Intelligent File Access Acceleration Sequencing Technology) is not available in the V-locity VM program.
No, I-FAAST and Directory Consolidation run only on the V-locity 3 Host for Hyper-V.
No, you cannot run V-locity VM from the command line on Windows systems.
Yes, you can run V-locity 3 from the command line on Windows systems.
The V-locity VM program for Hyper-V VM’s and for ESX/ESXi VMware Guest will improve performance in such a way that there is no need to detect Differencing Disks and Linked Clones in order to accelerate performance.
IntelliWrite is left on by default for these disk types as it is not recommended to manually or automatically defragment a Differencing Disks/Linked Clones.
The V-locity 3 Host for Hyper-V and V-locity 3 Host Agent for ESX/ESXi will automatically detect Differencing Disks and Linked Clones* and deliver this information to V-locity 3 Guests. V-locity 3 Guests configure settings to maximize performance and ensure no unwanted side effects occur. IntelliWrite® fragmentation prevention technology in V-locity 3 prevents up to 85% of fragmentation on the initial write and is fully compatible with these special virtual disk types.
IntelliWrite is left on by default if these disk types are detected. As it is not recommended to manually or automatically defragment a Differencing Disk/Linked Clone, Aut
The focus of the V-locity VM is the improve performance by evaluating the local system and accelerating performance in such a way that there is no longer a need for a host program or communication to it.
By default, port 8255 is used to communicate between the V-locity 3 Host for Hyper-V or V-locity 3 Host Agent (ESX/ESXi) and the V-locity 3 Guest Components. UDP is only used for the automatic Host Agent discovery. Once a connection is established, only TCP is used.
* A Differencing Disk (Hyper-V)/Linked Clone (ESX/ESXi) is a virtual hard disk that stores the changes or “differences” to an associated parent virtual hard disk for the purpose of keeping the parent intact. The Differencing Disk/Linked Clone is a separate file that is associated with the file of the parent disk. Changes continue to accumulate in these change disks until it is merged to the parent disk.
There is no longer a need to communicate to a Host Agent program or to the Host/vCenter console.
The Host Agent communicates with the ESX/ESXi Host or vCenter using HTTPS, by default using port 443. The port can be changed when configuring Host Agent connections to vCenter through the Host Agent UI, using the standard URL notation (:).
Automatic Discovery is no longer necessary because V-locity VM is self-contained and designed to work in such a way that performance is accelerated without the need to communicate with other components.
Automatic Discovery is the process by which individual V-locity 3 Guests discover either the V-locity 3 Host for Hyper-V or V-locity 3 Host Agent (ESX/ESXi).
There are three methods (in descending priority) by which a V-locity 3 Guest discovers the V-locity 3 Host within its local subnet:
Yes, group policy is fully supported in V-locity VM.
Microsoft group policy is not supported in V-locity 3; however, Diskeeper® Administrator can serve as a network administration tool to deploy and manage V-locity 3 installations.
In order to deploy V-locity and remotely control V-locity installs with Diskeeper Administrator, the computers running V-locity must be configured to allow Diskeeper Administrator to communicate via these ports:
Diskeeper Administrator will use these ports if the default ports are unavailable. Diskeeper Administrator.
SQL port: 1434 – Diskeeper Administrator uses this port if the SQL database is located on a remote computer.
2016 Condusiv Technologies Corporation. All Rights Reserved.