I have the WD EX4100 with Volume 1 (2X4TB Raid 1) and Volume 2 (2X4TB Raid 1) with the last firmware 2.30.165.
I created a job for internal backup of the Volume 1 (some folders from here) to the Volume 2 (to a folder here). The Backup type that I had choose is “Synchronize” and I set the Recurrence to “ON” for daily backup at 02:00. So far so good.
My problem is that from the three days that this job is on the two had fail, and the problem is that I do not know why. Is there any Log file that has created with the error, so to understand the problem?
The strange think is that when I am starting the job manually everything goes well and I have my backup. Why the scheduled job at 02:00 failing and the same job by running it manual it succeeds?
Thank you very much for your quick responce.
I have all ready setup an internal BackUp and i can run it manually without any problem. The problem begins when this scheduled backup must start at the time that i had set it at 02:00.Next day I see the message (At internal backup page) that the backup failed but I do not know WHY. There is no log file or message about the reason that the backup failed. In the Notification area there is no error message. If i will take a log file with the procedure that you said to me, i can not find any entry about the internal backup and why it failed.
The photos are some screenshots. The one that failed is from the scheduled one. As you can see there are no alerts. And the other one is when i manually started the backup. As you can see everything went well without any problem.
Thanks again for your help, i will try to open a case at WD Support.
I think that i have found what causes the problem. The last 5 days i had change the time that i had schedule the backup from 02:00 to another one (try 22:00, 05:00 etc) and the result was a complete buckup with out any problem. So my conclusion is that at the same time “02:00:” it was steel active another backup from my Server to the Nas Drive (WDEX4100) and was a conflict between them.
The only problem is that there was not any failure log file with the problem so i must guess what the problem was.