Configure time is Veeam Backup and replication

[hari]

the backup job is configured to run at 3AM but starts at around 1Pm. But in shows started at 3AM in running jobs section of veeam. Why is there a time difference in System time to Veeam. How to rectify this.

Support Case ID: #04782330

(My first time in forms, so if done any mistake let me know )

[Egor Yakovlev]

Hi Hari

Veeam Backup Service(one that triggers jobs to start) works under Backup Server's local system time. Let's see what support digs out.
Note that if you are connected over remote console, timestamps will be your remote system's local format.

p.s. Just checked your case, there are no backup logs attached. Please do upload them to the case using this KB.

/Thanks!

[hari]

Thank you Egor Yakovlev for reply. I am not using remote console. I am doing RDP to Veeam Machine.
I don't have logs currently. Will ask the customer to upload them.

[Egor Yakovlev]

Perfect, that takes remote console out of equation.
Please do upload logs to the support case.

[hari]

I have uploaded the logs.

[Egor Yakovlev]

Some clear time shift happens on your VBR server between 15 April and 26 April. Your server is jumping between UTC offset +5.50 and -7.00. Once again, on April 28 Backup Service was started with UTC offset -7.00 hours. Maybe its a virtual machine that is time-syned with two different source? Like VMware Tools pushing ESXi time to the Guest OS, and Guest OS is also synced with domain time?

[wishr]

Check what time sources your VBR server uses and if your NTP server (if present) is functioning properly.

[hari]

I will connect with customer and check his time sources. So I am assuming this might be also the problem for not able to do any operations in Veeam Explorer for Microsoft SQL as it gives me "Connection Timeout Expire" Error message when I try to do Instant recovery or Restore database operations.

[hari]

Screenshot of the error message,
https://s3.ap-southeast-2.amazonaws.com ... 78ec1107e0

[Egor Yakovlev]

Let's fix the time jumps first and see if backup mounting timeouts are gone with it.

[hari]

Problems have been fixed, Thanks to you all.

While installing veeam (physical server), the timezone in system was different. And customer changed it after few days to the correct time zone(Asia/Kolkata). So, when I found out this, I closed veeam console and made sure any veeam application is not opened and restarted veeam services. And time issues was solved. Now backup jobs run at correct time.

And this also solved the problem when I try to restore a database, where it gives "Connection timeout expired" error earlier.

(Not related to this but just wanted to share)
While trying to restore database using Instant recovery option to same machine, I was getting new errors like, "A connection was successfully established with server, but then an error occured during pre-login handsake". Then later found out the issue was with the user permissions(I am not sure but thats what I came to conclusion), So choose "Instant recovery to another server" option (but restoring to same server) and now I get to enter sql username and password and windows username and password which worked.

[Egor Yakovlev]

Wonderful, thanks for update!
Glad it worked well.