New
#21
Hi Everyone – Afraid my problem is not yet fixed.On Saturday I scheduled backups of my C: (OS) and M: (Data) drives to run at 02:00 and 03:00 respectively this (Monday) morning and to run again on Wednesday and Friday mornings.The first should have taken about 30 mins and the second about 15 mins to run.When I came to my PC today there was no sign of my backup drive D: Label – Backups of System and Data Ptns in Windows Explorer and I had to re-boot the system in order to see it.Then when I clicked on folder Op System backups I could see that a new (fifth) file - My Backup W7 OS4-00-00.mrimg – had been created at 02:00 but the size was shown as 0 KB.I then looked in folder Data Partn backups only to find that no new file had been created (expected to have been at 03:00).When I reverted to folder Op System backups to my surprise the size had updated to 2,478,080 KB, which was very much smaller than previous successfully created files of about 19,378,586 KB.
Clicking on the new file resulted in a message stating the file was corrupt, whereas clicking on the larger earlier files had enabled one to mount the image, choose a drive letter and view the contents. Looking at the Scheduler History entries the first task started on time (Triggered on Scheduler) at 02:00 but appeared to have completed at 03:32:47 which meant it had taken about 1 hour longer than previously to run, and moreover would have overlapped with the due start of the second task at 03:00. The second task was Triggered on Scheduler at 03:32:37 – 10 seconds before the previous task had completed – but at 03:32:39 showed "Task triggered by user", which in the details below showed as: - Event ID 110“Task Scheduler launched "{ca90848a-f1f8-4c11-8b22-8a37f887ad2e}"instance of task "\My Backup Data xml"for user "Peter"” but I can assure posters that I was then safely in bed and asleep! At exactly the same time, Event 322 showed “Task Scheduler did not launch task "\My Backup Data xml"because instance "{ee48dd94-ae94-4276-9a15-fc15b380cae6}"of the same task is already running.” and Event 101 “Task Scheduler failed to start "\My Backup Data xml" task for user "Peter-PC\Peter". Additional Data: Error Value: 2147750687.” Then at 03:33:19 Event 201”Action completed” and Event 102 “Task completed” – total task duration of 42 seconds. With the exception of Event 110 all the above events showed the same Correlation Id, as quoted above between { }
I am quite new to Macrium Reflect and only realised today that the program writes logs of what has happened when it is run. Looking at the logs of the most recent runs shows the C: backup ended with an error message “Backup aborted! - Write operation failed - The system cannot find the file specified.” and the M: backupshows a start time of 03:33:13 with error message “Backup aborted! – None of the specified backup locations could be written to” The logs showed similar errors for previous failures, but there were also logs of successful runs.
Researching what might have caused these errors I came across a page in the Macrium Knowledge Base – http://kb.macrium.com/KnowledgebaseArticle50010.aspx and scrollingdown to “Make sure that the VSS Service isn’t disabled” it advises changing the startup type to “Automatic”. My own setting was “Manual” so I changed it to “Automatic” in the hope that it would do no harm but perhaps some good, but I have not yet attempted to re-run the Scheduled backups until I get some advice from the experts on this Forum as to what is wrong and a suggested cure. I am particularly puzzled as to why I had to re-boot in order to see the D: drive
Quote
