Backup process failed with code 47

I’ve found a strange error. I have 3 backups scheduled. All set for ‘simple copy’, to a network drive. Their backup settings are all the same, apart from, obviously the source & destination locations. However, one of the backups sometimes fails with the error ‘Backup process failed with code 47’ - does anyone know what this means? What is wierd is that it doesn’t happen all the time…in fact, that job is running successfully at the moment, yet a few minutes ago refused to run, giving that error code.

Let me know if you need any more info from me…

Peter

Hi Peter,
I’m seeing this problem too, however, I am doing a simple file copy backup of a local drive to a local drive as opposed to local drive to a network drive. Apparently this problem isn’t network related?

What OS are you running on the client and backup machines?

I am running Windows Standard Server 2008 and am backing up files from my D drive to my F drive - neither of which are system drives nor contain system files - so it doesn’t seem to be a permissions or an open system file problem.

Another difference between what you are seeing and what I am is the fact that I can never get my scheduled job to run once it produces this error. I have to recreate the backup (which is a big pain).

Any help from someone is greatly appreciated.
-Steve

I have the same code 47 problem. Iam trying to back up files on C drive to an external drive on G. Hope some one can help 'cause this appears to be a good program.

Donn

Hi all

Can you please post the content of the log file?
You can enable logging in the settings tab
cypressguy: Are you using simple copy too?

Thanks

I’m using Windows 7 (32bit version) on the main machine, the network drive is on a NAS, copying from local drive to network drive. Annoying thing is that I had to recreate the jobs, they all worked fine for a while, now two of them have stopped working - and these are the two that were always working before…both with error code 47. The irritating thing is that the one that was giving the error, which I had to recreate, is working fine!

Here are the log files - as you can see, the first two fail:

Job 1:

25.11.2009 09:47:17 Running scheduled backup \GARFIELD\Backup\Backups\Web-Daily-Backup\
25.11.2009 09:47:17 Backup process failed with code 47

Job 2:

25.11.2009 09:48:28 Running scheduled backup \GARFIELD\Backup\Backups\Model-Railroad-Daily-Backup\
25.11.2009 09:48:28 Backup process failed with code 47

Job 3:

25.11.2009 09:48:57 Running scheduled backup \GARFIELD\Backup\Backups\Paliz-Design-Daily-Backup\
25.11.2009 09:48:57 Collecting Information…
25.11.2009 09:49:00 Starting Backup Process…
25.11.2009 09:49:00 Processing M:\Paliz Design\documents
25.11.2009 09:49:00 Processing M:\Paliz Design\documents\Business Link Articles
25.11.2009 09:49:00 Processing M:\Paliz Design\documents\Business Link Articles\Accessability.pdf
25.11.2009 09:49:01 Processing M:\Paliz Design\documents\Business Link Articles\Choosing a website developer.pdf
25.11.2009 09:49:01 Processing M:\Paliz Design\documents\Business Link Articles\Create a winning website.pdf
25.11.2009 09:49:01 Processing M:\Paliz Design\documents\Business Link Articles\E-commerce laws.pdf
25.11.2009 09:49:01 Processing M:\Paliz Design\documents\Business Link Articles\Make your website accessible.pdf
25.11.2009 09:49:02 Processing M:\Paliz Design\documents\Business Link Articles\Make your website Google friendly.pdf
25.11.2009 09:49:02 Processing M:\Paliz Design\documents\Business Link Articles\Online payments.pdf
25.11.2009 09:49:02 Processing M:\Paliz Design\documents\Business Link Articles\Website Strategy.pdf
25.11.2009 09:49:02 The backup process has been aborted by user.

Hi all

We were able to reproduce this issue.
It will be fixed in the next release.

To avoid this problem, recreate the schedule jobs that run with this error, but don’t edit them at all.

Thanks

Great, thanks! Any idea when the next release will be out?

I have almost the exact situation. I am running Windows XP Professional. Recreating the schedule jobs that run with this error, but not editing them did not work. I am still am getting the same error. Any other suggestions?

As Emanuel states, recreating the jobs fixes the error.