Can a currupt backup cause a hardrive failure?

I have a script that runs each time Windows 7 starts up that backs up an MS SQL database to a Synology NAS loaded with 12 Seagate ST4000NM002A-2HZ101 hard drives. Everyday at 3am the backed up database is "restored" to a MS SQL database running in a docker container running on the Synology NAS. In the last 6 months I've had 8 out of the 12 hard drives fail. All failures have happened early in the morning, just after the database restore script has executed (restored the last database backup to the MySQL database running in docker container). All of the failed drives have been from the original batch (no failures from the replaced drives). Have I received a dodgy batch of drives or could restoring a corrupt database backup to a docker container be causing the problem?

Ah...

In the last 6 months I've had 8 out of the 12 hard drives fail.

Ok, let's see...

12 Seagate ST4000NM002A-2HZ101 hard drives.

Classified as "Enterprise Drive for Bulk Data Applications"

I woudl be inclined to say that abusing them as performance databases may be not smart, otoh... "a 2 million hour MTBF rating and support workloads of 550TB per year" - that would require a SMART check, but those do not look like drives that should fail in 6 months to that degree.

If you bought them at the same time from the same shop, I would dare saying you likely hit a very bad batch. They come with significant warranty, so - there should be no problem replacing.

Yes, failure around a backup sounds normal - those are higher stress situations - but the statistics of 8 of 12 failing within 6 months is absolutely totally surreal high.