Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: synchronization of new files only with filemask

Did you try -filemask="export_*>3D"?
Guy2

Re: synchronization of new files only with filemask

martin wrote:

You are not doing anything wrong. The file mask would only prevent download of older files. I assume there are no not-synchronized files older than 3 days.

WinSCP still needs to list the directories to tell what the file time is.

Possibly you want to exclude some export_<date> folders completely.



Thanks Martin.
Excluding old folders would be ideal.. but how can i achieve this using normal script. the <date> is dynamic (every day a new date :))
martin

Re: synchronization of new files only with filemask

You are not doing anything wrong. The file mask would only prevent download of older files. I assume there are no not-synchronized files older than 3 days.

WinSCP still needs to list the directories to tell what the file time is.

Possibly you want to exclude some export_<date> folders completely.
Guy2

synchronization of new files only with filemask

Hi,

Situation:
The remote location has following structure:
root\export_<date>\subfolders

Every hour thousands of files are added to the subfolders. The server keeps all files for about 8 days... resulting in over 500k files.

Now i have a synchronization job running to download these files (to process them lateron). Due to the high number of files, the synchronization process is too slow to be comfortable. So i've tried to change the filemask to filter as such that i get only files that are newer than 3 days

The filemask looks like this:
synchronize local -filemask="A*.gz>3D" D:\DROPZONE\

This doesnt seem to work. The synchronization process still reads all folders and files available on the server...

Am i doing something wrong?

Thanks,
Guy