How to cause vault to pre-load when server rebooted

[Mordachai]

When we first connect to Vault after the server has rebooted for any reason, that connect takes upwards of 3 mins to complete.

Is there a simple way to force the OS to load whatever is needed when it boots, instead of wasting my users time by delaying until they actually need to connect?

[Beth]

There's no way around needing to reconnect, but your connection speed could be faster.

Try having your users turn off "Request Database Delta on Repository Cache Miss" found in the Vault Tools - Options - Network Settings.

[Mordachai]

Beth - I'm not sure if I'm communicating clearly.

It is only the first time I connect (or any person connects) after a reboot of the server.

Once I have connected once, after a reboot of the server, then all future connections are very fast (for myself and for all other users). It doesn't matter who is the first to attempt the connection - whomever it is suffers a LONG DELAY.

So I assume that there must be some extra work that happens only for that first connection... say, vault server is launching / loading whatever it needs to on the server, in order to process a user connecting to it.

This is what is so abysmally slow.

Does that make sense?

[Beth]

A server reboot will clear out the server side cache.

Had you tried changing "Request Database Delta on Repository Cache Miss?" What were your results?

[Beth]

Try bringing up the Vault tree in the web client. The URL is http://<your Vault server>/vaultservice/vaultweb. That will force Vault to load the tree into the server side memory.

[Mordachai]

Intriguing. Not sure how I can get that to happen automatically by the server when the server is reset - no logged in account...

Any ideas?

[Beth]

You could use the command-line client and have it perform a Show History on $/ for just the latest version or something small. That can then be made into a script that automatically runs on start up.