Condusiv Help Center

V-locity FAQs

The new defragmentation engine that handles File FAL(File Attribute List) fragmentation is the only defragmenter that can safely defragment the FAL without making it grow. It also dynamically determines how often to process these effected files by the severity of the FAL fragmentation.

A new Free Space Consolidation engine has been added to handle volumes with extreme free space fragmentation and supports FAL(File Attribute List)-SAFE defragmentation.

Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2008 R2, Windows Server 2012 (or R2), Windows Server 2016, and Windows Server 2019

Microsoft Hyper-V, VMware ESX/ESXi
The V-locity will defragment the host NTFS file system, including any virtual hard disk files.

Yes, V-locity 3, 4 and VM supports vSphere™ 5.

V-locity 5,6 and 7 supports vSphere™ 5 and 6.

Yes, V-locity supports Citrix Xenserver. V-locity runs in the virtual machine(VM) and is agnostic to the hypervisor hosting the VMs.

In VMware, the V-locity receives this information from the separately installed V-locity and displays it. The V-locity gathers this data from the virtualization host or vCenter.™ A V-locity over Hyper-V will display the name of the host system that the Guest is communicating with.
Yes, you can run V-locity on VSS-enabled drives. We recommend using the manual and the automatic VSS defragmentation operations that you can enable via the V-locity configuration properties options.
V-locity 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.
V-locity contains an Automatic Space Reclamation Engine, which automatically zeroes out unused data blocks on virtual disks and makes virtual disk compaction easy. This allows the unused space to be reclaimed efficiently, without writing zeros to the disk. In some cases, this also permits the reclamation of zeroed out free space during storage migration on the virtual platform, such as Storage vMotion™ .
If SCSI UNMAP or ATA Trim is support or Zeroing out the free space is supported, then the Space Reclaimation feature can be used.

No, it is only as a feature that you can enable/disable to occur in the background.

The V-locity will indicate what degree of reclamation is available from associated virtual disks and whether compaction is recommended.
If SCSI UNMAP or ATA Trim is support or Zeroing out the free space is supported on the drives, then the Space Reclaimation feature can be used.
Yes, V-locity 7 supports large volumes.
Yes, you can run V-locity from the command line on Windows systems.

V-locity applies algorithms to improve performance in such a way as to minimize/eliminate potential growth of Dynamic/Thin disks.

Yes, movement of VMs from one host virtual system running the V-locity Guest to another virtual system running these is fully supported for V-locity 7.
Yes, these features/infrastructures are fully and natively supported and V-locity 7 is fully compatible. No special configurations are required.
There is no longer a need to communicate to a Host Agent program or to the Host/vCenter console.
Automatic Discovery is no longer necessary because V-locity is self-contained and designed to work in such a way that performance is accelerated without the need to communicate with other components.
Yes, group policy is fully supported in V-locity.

V-locity 6 and 7 have the option of a management console capable of deploying V-locity, licensing the installs and providing reporting.

In order to deploy V-locity 3 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 Push Install port: 31029 – Diskeeper Administrator uses this port to deploy V-locity to remote computers.
  • Diskeeper Administrator server port: 31037 – Diskeeper Administrator service receives data from remote V-locity computers via this port.
  • Diskeeper Administrator console port: 31036 – Diskeeper Administrator remote control console receives data from remote V-locity computers via this port.
  • Spare Diskeeper Administrator console ports: 31056, 31076, 31096, 31116, 31136, 31156, 31176, 31196, and 31216

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.

A reboot is required when you install the V-locity software version 6 or older, which occurs before you would run the Benefit Analyzer. It would another reboot would NOT be require before running the Benefit Analyzer.

The Benefit Analyzer uses the first day to measure system performance without any V-locity features. Then, V-locity features are turned on for day two so that cache gets filled up and the product learns what fragments may be affecting performance. On day three system performance is measured again with V-locity features fully functional. This is then compared to the performance from day one to provide an analysis of the performance benefits derived by running V-locity VM.
You can run it at any time but it is strongly recommended that you run the Benefit Analyzer in V-locity VM during regular production hours during the week. What the Benefit Analyzer needs to capture for best results is what the load is during peak workload hours.

No, it will not pick up where it left off at. If you restart the Benefit Analyzer in V-locity VM, it will initiate the 3 day processing all over again.

It was realized that I/O traffic was a major component in all aspects regarding performance on a system. In order to accelerate performance proactively, it is more effective to target I/O’s at the source if possible

The number of I/O’s stated in the report should be decreased after the V-locity VM Benefit Analyzer has run for 3 days, and the program has been running for a week or more.

If the system/VM is not on your domain, you have to install the V-locity program locally using the V-locity Standalone or VMCENSetup.exe programs.

Usually there is an Windows menu option for V-locity once installed. If you are unable to locate it, try opening up a browser IE (Internet Explorer) or Google Chrome. Then type ‘Localhost’ in the address bar.