This is my first post, so please be gentle!
This is also my first (and second) attempt at building a system. Let me explain!
I bought a new ASUS Prime Z690-P WIFI D4 motherboard to replace my aging HP Envy system. Along with the motherboard, I also bought an i7-12700 processor, 32GB of Corsair Vengeance DDR4 3600MHz memory, two 500GB WD Black SN850 NVMe SSD's, a Corsair CX650 80 Plus Gold power supply and a Corsair case to put everything into. Also bought a copy of Windows 10 Pro.
I use this machine primarily for photo editing. I don't do gaming, so the only overclocking enable on this machine is the XMP.
Now the problem. I run a backup program (Veeam) every night to back up this machine to a TrueNAS server I put together a number of years ago. The backup is supposed to start at 04:00am daily, but (and here is the issue) it never seems to start on time. In fact it starts anywhere from just a minute to up to 20 or even 30 minutes late. From my further testing, it appears that if I do not use the computer for a day, the start of the backup can be quite late (20 minutes), but if I've used the computer late into the night, then the backup may start only a few minutes late.
It's seems that the machine loses time when it sleeps and when I'm not using the machine, I always put it to sleep. Never shut it down.
I contacted ASUS explaining my problem and they wanted me to send the motherboard back. However it would cost me more to send the board back than to buy another motherboard.
So, I then bought a Gigabyte AORUS Z690 Elite AX DDR4 motherboard and replaced the ASUS with this new board, but retained all previous parts.
The very first thing when I had finished building the new machine, was to try and test my backup again. Lo and behold, the backup on this new machine acted exactly the same as the old machine. Backup starts really late if machine is not used much and closed to the correct time is machine used late into the night.
Now I'm thinking that the problem must be some BIOS setting that I haven't set correctly. But try as i might, I could find no setting that would resolve this problem. In fact, both the ASUS and Gigabyte boards supported a feature that has the BIOS wake the machine and on both machines I could never get this function to work. That left me with the feeling that the problem might lie in the Z690 chipset but I could find nothing anywhere on the Internet dealing with this issue.
My last step was to now purchase a i5-13500 CPU, 64GB of Corsair Vengeance DDR4 32MHz memory and two 1TB WD Black SN770 NVMe drives and another Corsair 650 power supply, put it all in the Gigabyte motherboard and retry my testing all with the same results as above.
I now give up and come begging for someone to help me!
One last thing that I did do was to create a Windows task scheduler job to wake the machine one half hour before the backup was scheduled to run and by doing this I now have my backup running only a couple of seconds late each night. By the way, I did this on both new machines (as I now have two!) and while not fixing the problem, it does alleviate it!
Any and all help or suggestions would be appreciated. Thanks.
Greg
This is also my first (and second) attempt at building a system. Let me explain!
I bought a new ASUS Prime Z690-P WIFI D4 motherboard to replace my aging HP Envy system. Along with the motherboard, I also bought an i7-12700 processor, 32GB of Corsair Vengeance DDR4 3600MHz memory, two 500GB WD Black SN850 NVMe SSD's, a Corsair CX650 80 Plus Gold power supply and a Corsair case to put everything into. Also bought a copy of Windows 10 Pro.
I use this machine primarily for photo editing. I don't do gaming, so the only overclocking enable on this machine is the XMP.
Now the problem. I run a backup program (Veeam) every night to back up this machine to a TrueNAS server I put together a number of years ago. The backup is supposed to start at 04:00am daily, but (and here is the issue) it never seems to start on time. In fact it starts anywhere from just a minute to up to 20 or even 30 minutes late. From my further testing, it appears that if I do not use the computer for a day, the start of the backup can be quite late (20 minutes), but if I've used the computer late into the night, then the backup may start only a few minutes late.
It's seems that the machine loses time when it sleeps and when I'm not using the machine, I always put it to sleep. Never shut it down.
I contacted ASUS explaining my problem and they wanted me to send the motherboard back. However it would cost me more to send the board back than to buy another motherboard.
So, I then bought a Gigabyte AORUS Z690 Elite AX DDR4 motherboard and replaced the ASUS with this new board, but retained all previous parts.
The very first thing when I had finished building the new machine, was to try and test my backup again. Lo and behold, the backup on this new machine acted exactly the same as the old machine. Backup starts really late if machine is not used much and closed to the correct time is machine used late into the night.
Now I'm thinking that the problem must be some BIOS setting that I haven't set correctly. But try as i might, I could find no setting that would resolve this problem. In fact, both the ASUS and Gigabyte boards supported a feature that has the BIOS wake the machine and on both machines I could never get this function to work. That left me with the feeling that the problem might lie in the Z690 chipset but I could find nothing anywhere on the Internet dealing with this issue.
My last step was to now purchase a i5-13500 CPU, 64GB of Corsair Vengeance DDR4 32MHz memory and two 1TB WD Black SN770 NVMe drives and another Corsair 650 power supply, put it all in the Gigabyte motherboard and retry my testing all with the same results as above.
I now give up and come begging for someone to help me!
One last thing that I did do was to create a Windows task scheduler job to wake the machine one half hour before the backup was scheduled to run and by doing this I now have my backup running only a couple of seconds late each night. By the way, I did this on both new machines (as I now have two!) and while not fixing the problem, it does alleviate it!
Any and all help or suggestions would be appreciated. Thanks.
Greg
Facebook
Twitter
Instagram