I just installed the latest version on my wife's computer and I am getting an
error anytime a mirrored backup runs and something needs to be deleted. It
says, "Recycle Bin is not available for the following paths! Files will be
deleted permanently instead:
\\thenetworklocationofmybackupdestination\
Press "Switch" to open freefilesync GUI mode."
I never had this issue (that i know of) with the 3.16 I run on my machine, and
I noticed that the recycle bin error is something tweaked in version 3.19, so
is there something I need to do different?
Thanks
error with new version?
- Posts: 2
- Joined: 25 Apr 2011
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
This is a new error message only, no difference in behavior. Old versions
simply deleted instead of moving to recycler if latter is not available for a
particular path. Since such behavior cannot be expected by the user, the new
version makes this situation transparent. It's a warning only, so you may
ignore it.
simply deleted instead of moving to recycler if latter is not available for a
particular path. Since such behavior cannot be expected by the user, the new
version makes this situation transparent. It's a warning only, so you may
ignore it.
- Posts: 2
- Joined: 25 Apr 2011
OK, thank you, that makes sense.
But I am curious why this would be an issue. I can click on a file on the
network drive an delete it, so why wouldn't filesync be able to move it to the
recycle bin?
But I am curious why this would be an issue. I can click on a file on the
network drive an delete it, so why wouldn't filesync be able to move it to the
recycle bin?
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
In the sync settings the user can specify "recycle bin" as a means to handle
to be deleted files. This is a safety guarantuee by FFS that in case it is
required an accidental deletion may be undone manually. The tool must honor
this request and in case it cannot be followed due to technical reasons (as
there usually is no recycle bin on Windows network shares), it must clearly
state this situation. It would be an unpleasant surprise if a user that is not
informed about these technical restrictions needs to recover an important file
and finds FFS has simply deleted it instead of doing what it was expected to.
to be deleted files. This is a safety guarantuee by FFS that in case it is
required an accidental deletion may be undone manually. The tool must honor
this request and in case it cannot be followed due to technical reasons (as
there usually is no recycle bin on Windows network shares), it must clearly
state this situation. It would be an unpleasant surprise if a user that is not
informed about these technical restrictions needs to recover an important file
and finds FFS has simply deleted it instead of doing what it was expected to.
- Posts: 6
- Joined: 18 Jul 2012
I'm having a similar problem. This is what the log of a batch job shows.
Warning: Recycle Bin is not available for the following paths! Files will be
deleted permanently instead:
N:\Documents\
Error: Synchronisation aborted!
This is a folder on my NAS drive that I'm syncing with the one on my computer
(C:\Users\Mark\Documents), but apparently it is trying to delete the folder on
the NAS altogether.
Both document folders are identical, apart of the subfolder on my computer
which is meant to store these very batch logs. The NAS folder did not contain
this folder yet so that is what it is trying to sync. Any idea what could
cause this behavior?
Warning: Recycle Bin is not available for the following paths! Files will be
deleted permanently instead:
N:\Documents\
Error: Synchronisation aborted!
This is a folder on my NAS drive that I'm syncing with the one on my computer
(C:\Users\Mark\Documents), but apparently it is trying to delete the folder on
the NAS altogether.
Both document folders are identical, apart of the subfolder on my computer
which is meant to store these very batch logs. The NAS folder did not contain
this folder yet so that is what it is trying to sync. Any idea what could
cause this behavior?
- Posts: 6
- Joined: 18 Jul 2012
First of all, notice how I create a syncloop by including the logfiles into
the folder that is to be synced.
Hand -> Face.
Second, the reason why it failed is supposedly this: both folders contain the
batchfile for the job, but I modified the one on my computer after the first
few successful testruns. It seems that this caused the failure cause when I
manually copied it to the NAS it ran fine again.
the folder that is to be synced.
Hand -> Face.
Second, the reason why it failed is supposedly this: both folders contain the
batchfile for the job, but I modified the one on my computer after the first
few successful testruns. It seems that this caused the failure cause when I
manually copied it to the NAS it ran fine again.
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
> Warning: Recycle Bin is not available for the following paths! Files will be
deleted permanently instead:
This warning comes up when at least one file is scheduled for update or
deletion on a volume that does not have a recycle bin. To avoid this warning
in the future, change "deletion handling" to "delete permanently" or
"versioning".
deleted permanently instead:
This warning comes up when at least one file is scheduled for update or
deletion on a volume that does not have a recycle bin. To avoid this warning
in the future, change "deletion handling" to "delete permanently" or
"versioning".