Computer Clock Is Not Synchronized (code 3000)
Running a new format image backup to Wasabi on a computer that has been backing up this way for quite a while. Running version
Computer failed the backup due to:
The Computer clock is not synchronized (code: 3000)
The computer clock is 0 d 0 h 19 min 48 sec slow
I logged on to the server. The clock appears to be correct within 1 minute of the correct date/time. Time zone is correct. Computer receives inputs from an ntp server.
Checked the Microsoft Server 2016 event logs. Found this recent entry:
The time provider NtpClient is currently receiving valid time data from 10.0.0.1,0x8 (ntp.m|0x8|0.0.0.0:123->10.0.0.1:123).
Does anyone know why this error would have popped up?
This error is caused by the difference between local system time and backup storage time. The acceptable difference is up to 15 minutes, if I'm not mistaken (it depends on the storage provider). You can check if the system time on your computer matches the actual time in your time zone at
I'd reach out to Wasabi tech support if the time is accurate and you still have the problem.
Here is the
link to the KB article
Thanks. We will check with the cloud storage provider.
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
Quick Support Client Bug - Screen Sharing is paused by Remote Computer
How to transfer a file from remote computer to my local computer.
Adding 2nd remote computer to host computer
Adding additional remote desktop computer to access the host computer
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2022 MSP360 Forum