Condusiv Help Center
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.
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
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.
How do V-Aware™ and CogniSAN™ technologies detect resource usage across the virtual platform/storage infrastructure?
No, it is only as a feature that you can enable/disable to occur in the background.
V-locity applies algorithms to improve performance in such a way as to minimize/eliminate potential growth of Dynamic/Thin disks.
Which port do the V-locity program on Hyper-V/V-locity program on (ESX/ESXi) and V-locity Guests communicate through?
If I am using Diskeeper Administrator to manage V-locity installations, what ports are needed to communicate?
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.
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.
In reviewing the Benefit Analysis report, outside of the percentages, how else can I determine if there is a significant improvement?
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.