-
- Posts: 4
- Joined: Sat Aug 22, 2015 1:27 pm
Strange effect in Mirror copy
I am using Backup4All Mirror copy to backup my user's open PST files on a scheduled basis. Very simple job, uncompressed and unencrypted.. This evening for the first time the backup appeared to start and then stopped with no reported log entry or failure report. Restarting the backup manually got the same effect.
The log entry as far as it was entered was identical to prior log entries.
Since I had nothing to lose by trying I duplicated the job and manually started it and it is running fine.
I now plan to delete the original job since the copy is working.
What happened?
The log entry as far as it was entered was identical to prior log entries.
Since I had nothing to lose by trying I duplicated the job and manually started it and it is running fine.
I now plan to delete the original job since the copy is working.
What happened?
-
- Posts: 4
- Joined: Sat Aug 22, 2015 1:27 pm
Re: Strange effect in Mirror copy
Follow-up:
Apparently the "failed" backup was running although the process logging that you see when a job starts ended after very little being written to the log. When I checked the backup media I discovered two backups. The first "failed" backup was almost complete (I had cancelled it when it looked like it wasn't running) and the completed second backup.
Apparently the "failed" backup was running although the process logging that you see when a job starts ended after very little being written to the log. When I checked the backup media I discovered two backups. The first "failed" backup was almost complete (I had cancelled it when it looked like it wasn't running) and the completed second backup.