Before posting, and to avoid disappointment, please read the following:

  • This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
  • If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.

Mirror now warning that 100% of destination files are about to be deleted

For technical support visit https://support.2brightsparks.com/
Post Reply
Kopy Katt
Newbie
Newbie
Posts: 2
Joined: Tue Aug 29, 2023 2:14 am

Mirror now warning that 100% of destination files are about to be deleted

Post by Kopy Katt »

SyncBack Touch (Android SD card) Mirror to NAS using SyncBack V10. Without having made any changes to the weekly mirror profile that I run, I now get this message: "Warning: 100.0% of your files (xx,xxx of xx,xxx) are about to be deleted. Are you sure you want to continue? Yes/No?"

When I start the profile it begins scanning the destination, and before it scans the source, the message appears.

The source files appear to be available because I can review the files on the source when modifying the profile. I have another Android phone and ran it's similar Mirror profile without this problem.

I abort the profile because I don't want to delete all the destination files which took many, many hours to copy the first time!

Any ideas about what may be triggering this warning message? Thanks in advance for your contributions!
Kopy Katt
Newbie
Newbie
Posts: 2
Joined: Tue Aug 29, 2023 2:14 am

Re: Mirror now warning that 100% of destination files are about to be deleted

Post by Kopy Katt »

I upgraded to the latest SE V11 and the profile will run now without giving the warning.
I suppose whatever glitch in V10 that caused this was fixed. Oh, well...
Post Reply