MASK error, not detecting file

English Support for Syncovery on Windows.
Post Reply
Contractor5Prepays9
Posts: 18
Joined: Wed Sep 23, 2020 10:38 pm

MASK error, not detecting file

Post by Contractor5Prepays9 »

dear support
bizarre behavior

copying from left to right - only the .FTMB files extension, in the mask
I run in attended mode, yoiu see the file is in existence, but syncovery does not show it, in previowe.
next slide, i changed the file NAME to add a "B" before the .FTMB extension, then ran syncovery in attended mode, aid it DOES see the file.
THEN, I changed it BACK and removed the "B", and syncovery did NOT see the file.

any feedback appreciated
thanks
nick
Attachments
598.jpg
598.jpg (270.01 KiB) Viewed 1887 times
596.jpg
596.jpg (243.49 KiB) Viewed 1887 times

tobias
Posts: 482
Joined: Tue Mar 31, 2020 7:37 pm

Re: MASK error, not detecting file

Post by tobias »

Syncovery only shows files that need to be copied. Probably the file already exists on the right-hand side.

To prove that something is wrong, you would need to choose "Show: All" in the top left corner of the Sync Preview, and then scroll to the location where the file should be (alphabetically). Then you can check if it's there and compare the file details for the two sides. If it's identical, Syncovery will not copy it. If the file is different but newer on the destination, it will only copy it in Exact Mirror mode.

Contractor5Prepays9
Posts: 18
Joined: Wed Sep 23, 2020 10:38 pm

Re: MASK error, not detecting file

Post by Contractor5Prepays9 »

i did do a "show all". nothing showed up.
it is as if it did not detect that file as .FTMB, until i added the "B" at end fo file name.
if it happens again, i wil check both sides (I had not checked the folder on right),
thanks
nick

tobias
Posts: 482
Joined: Tue Mar 31, 2020 7:37 pm

Re: MASK error, not detecting file

Post by tobias »

Hello,
I think you would need to post the log file and/or send to support@syncovery.com. There are sometimes some left-over settings in the job that can cause such things.

Contractor5Prepays9
Posts: 18
Joined: Wed Sep 23, 2020 10:38 pm

Re: MASK error, not detecting file

Post by Contractor5Prepays9 »

here is log file, it copied the "B".ftmb file



Syncovery v9.23, build 117 (64-bit)


System Info: Microsoft Windows 10 Pro Build 19041
Using Backup Privilege

Log for profile FAMILY_TREE_MAKER 11_H18-CURRENT-to-BACKUP, started at 08:45:08 AM on 01/10/2021

LEFT: \\HOME18\Data_CURRRENT-c\FamilyTree_Data
RIGHT: \\HOME18\Data_BACKUP_c\FamilyTree

The profile is run in attended mode.

Previous run was at 01/10/2021 08:35:51 AM: 1 copied (19.1MB), 1 deleted, Binary Comparisons: 1, Successful: 1

Left Side Volume Name: Windows
Right Side Volume Name: Windows

Copying Direction : Left To Right

Not checking network connections again (already done).
Scanning Folders Started At 01/10/2021 08:45:08 AM

Free Space on left side : 71 GB, needed: 0 Bytes
Free Space on right side: 71 GB, needed: 19,517 kB

Using Internal Copying Function
08:45:43 AM Compared \\HOME18\Data_CURRRENT-c\FamilyTree_Data\2_McMonagle_McCabe_2021-01-06b.ftmb with \\HOME18\Data_BACKUP_c\FamilyTree\2_McMonagle_McCabe_2021-01-06b.ftmb (19985795 Bytes): IDENTICAL
DELETE L \\HOME18\Data_CURRRENT-c\FamilyTree_Data\2_McMonagle_McCabe_2021-01-06b.ftmb
MOVE \\HOME18\Data_CURRRENT-c\FamilyTree_Data\2_McMonagle_McCabe_2021-01-06b.ftmb (19.1MB)


SUMMARY
------------------------------------------------------------------
Short Results: 1 copied (19.1MB), 1 deleted, Binary Comparisons: 1, Successful: 1
Operation completed at 08:45:43 AM on 01/10/2021
Total duration: 00:00:34

Copied To Right Side: 1 (19.1MB)
Deleted On Left Side: 1 (19.1MB)

Overall average transfer rate : 1.3 MB/s
Average copying time per file : 14.1 s
Copying time for fastest file : 14.1 s
Copying time for slowest file : 14.1 s

Average transfer rate per file : 1387.0 kB/sec
Transfer rate for slowest file : 1387.0 kB/sec
Transfer rate for fastest file : 1387.0 kB/sec
For the fastest/slowest rates, only files at least 1 kilobyte in size were counted.


Local time zone offset: -5.0 hours.
Time used for free space checks on left side: 0.0162 seconds for 2 space checks.
Time used for free space checks on right side: 0.1858 seconds for 3 space checks.

------------------------------------------------------------------

Profile Settings From C:\Users\user01\PortApps2\Syncovery-x64\00aa_Syncovery_DATA\Syncovery_ALL.ini

[General]
Name=FAMILY_TREE_MAKER 11_H18-CURRENT-to-BACKUP
LastModified=01/10/2021 08:42:56 AM
LeftPath=\\HOME18\Data_CURRRENT-c\FamilyTree_Data
RightPath=\\HOME18\Data_BACKUP_c\FamilyTree
LeftToRight=Yes
UseSubfolderSelection=Yes
MoveFilesMode=mmOverwriteDest
MoveByCopying=Yes
SubfolderSelections=\FamilyTree_Data/

[Comparison]
BinaryCompMode=bcmNone
SizeConflictAction=scaCopy

[Files]
VerifyAfterCopy=Yes
MaxParallelCopiers=1
PreventZeroByteReplacements=No

[Job]
Connection2=\\HOME18\Data_CURRRENT-c\FamilyTree_Data@user01:/NN

[Inclusion Masks]
FileMasks=*.ftmb

[Safety->Attended]
WarnMoving=No

[Safety->Unattended]
UnattendedDeleteMaxPercent=10
UnattendedSpecialWarnings=Yes

[Special]
ApplyPermissionsToCompressedFiles=Yes
PutPermissionsIntoCompressedFiles=No
ApplyADSToCompressedFiles=Yes
PutADSIntoCompressedFiles=No


------------------------------------------------------------------


System Info: Microsoft Windows 10 Pro Build 19041
Codepage/Country/Locale: 1252/1/0409
Windows Timezone Offset: -300
OS Architecture: 64-bit
OS Language: 1033
System Device: \Device\HarddiskVolume5
System Directory: C:\WINDOWS\system32
Windows Directory: C:\WINDOWS
Default System Codepage: 1252

------------------------------------------------------------------


Email Notification Settings:
Email Notification is OFF.


------------------------------------------------------------------

tobias
Posts: 482
Joined: Tue Mar 31, 2020 7:37 pm

Re: MASK error, not detecting file

Post by tobias »

Hello,
OK that is strange. What we need to analyze further is:
a) please update to the latest version
b) choose "File List Building Details" on the Program Settings dialog, tab sheet Logs.

Then run the job once more, with the file that it doesn't see, so we have a log where the issue occurred.

Then the reason should be in the log, which will be much more detailed.

Post Reply