08-26-2014 10:56 AM - edited 03-01-2019 09:10 AM
We just upgrade from 5.3 to Tidal 6.1. Whenever we lose connection to our VMWare adapter it takes over 6 hours to sync the inventory and start updating the jobs. Has anyone found a way to cut this time down? If we lose connection after 11 a.m. our jobs don't run because the sync takes it right up to the job starts
07-29-2015 03:05 PM
This discussion has been reposted from Additional Communities to the Tidal Enterprise Scheduler community.
09-10-2015 11:01 AM
To followup - The newest version of the adapter (2.0.1.580)will still take several hours to inventory (we have over 2000 VMWare servers)
But Tidal will now search the previous inventory for the server instead of waiting for the current inventory to complete.
Now if the VMWare admin decides to reboot their vCenter server at 5pm, we still have jobs successfully run immediately after.
My fingers are crossed that the VMWare adapter for Tidal 6.2SP2 will behave the same.
Michelle
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide