Verify a connection
Click Verify on the connection screen to run a connection check through your local DeltaVault Agent. The agent runs inside your network, so DeltaVault never connects to your database directly.
Before you verify
Section titled “Before you verify”Verification requires an online agent. If none is connected, the connection screen shows “No DeltaVault Agent is online” with a link to Manage agents. See the local agent setup guide for installation steps.
Running a check
Section titled “Running a check”Click Verify on the connection screen. While the check is running the button shows Verifying. When it completes:
- Success: the connection is stamped Verified and shows the host name of the agent that ran the check.
- Failure: an error message appears. For network-shaped failures, DeltaVault shows a Local Agent remediation card to help you diagnose the problem.
Live status while verifying
Section titled “Live status while verifying”While a verify is in progress, the connection status strip shows the current phase and how long it has been running:
- Queued means the job is waiting for an agent to pick it up.
- Running on
<host>means an agent is actively running the check, identified by its host name.
A live elapsed timer counts up so you can see how long the check has taken.
If the check runs longer than usual, the strip shows a note that the verify is taking longer than expected. This is informational and does not mean the check has failed.
A verify that cannot complete within about 90 seconds is reported as a timeout. The strip shows Verification timed out and offers a Verify again action. A timeout is different from a connection error: it means no agent picked up the job, or the agent stopped responding mid-check. The Local Agent remediation card does not appear for a timeout because the problem is agent availability, not the connection itself. To resolve a timeout, confirm that an agent is online and then verify again.
Troubleshooting
Section titled “Troubleshooting”“Login failed for user.” This is a credentials problem, not a network one. No agent change will help. Check the username and password. For Microsoft Entra service principals, also verify the tenant identifier and client identifier.
The server cannot be reached, or the connection is refused. The agent could not reach the database host. Confirm that an agent is online on a machine inside the network that has a route to the database server, then verify again. The Local Agent remediation card on the failed-verify screen guides you through this.
No agent is online. The connection screen shows “No DeltaVault Agent is online”. Install or restart an agent inside the network that can reach your database server. See the local agent setup guide.