Forum Discussion

Calli-TK's avatar
Calli-TK
Level 2
10 years ago

Bad performance - Transvault with Enterprise Vault

Hi all, currently we are migrating from Lotus Notes to Microsoft Exchange. We also have to migrate our existing EV Archive Domino to EV Archive Exchange. We are using the Transvault software for m...
Best Practice
Configuring
Enterprise Vault
Error messages
Information Governance
Monitoring
Performance
Recovering
Troubleshooting
Windows Server (2003-2008)
  • Paul_Honey's avatar
    Paul_Honey
    10 years ago

    Torsten,

    As we have discussed offline and with Support, this delay actually looks to be one that we have seen previously with various partner migration solutions that use the Content Management API. Whilst the root cause of such a slow bind to a Global Catalog should be diagnosed and resolved in the environment where it occurs as it seems unusually laboured, we have also refactored some code to include additional caching to significantly reduce the volume of calls to the GC to offset the impact of slow binding. This change was officially released in Enterprise Vault 11.0.0 CHF1, and referenced in the readme as follows:

    Ingestion using the Content Management API was slow in environments with many Exchange servers [3415538]

    Ingestion using the Enterprise Vault Content Management API was slow in environments with many Exchange servers.

    This has been fixed.

    Don't be put off by the reference to 'many Exchange servers' as whilst the original environment to report the issue observed delays due to volume of servers in the environment, the issue can similarly be observed with few servers but very slow GC lookups as per your scenario, with both situations being addressed by the same caching fix.

    Let us know how you go

    Paul

     

Paul_Honey's avatar
Paul_Honey
Level 5
10 years ago

Torsten,

As we have discussed offline and with Support, this delay actually looks to be one that we have seen previously with various partner migration solutions that use the Content Management API. Whilst the root cause of such a slow bind to a Global Catalog should be diagnosed and resolved in the environment where it occurs as it seems unusually laboured, we have also refactored some code to include additional caching to significantly reduce the volume of calls to the GC to offset the impact of slow binding. This change was officially released in Enterprise Vault 11.0.0 CHF1, and referenced in the readme as follows:

Ingestion using the Content Management API was slow in environments with many Exchange servers [3415538]

Ingestion using the Enterprise Vault Content Management API was slow in environments with many Exchange servers.

This has been fixed.

Don't be put off by the reference to 'many Exchange servers' as whilst the original environment to report the issue observed delays due to volume of servers in the environment, the issue can similarly be observed with few servers but very slow GC lookups as per your scenario, with both situations being addressed by the same caching fix.

Let us know how you go

Paul