Winscp script to download files newer than timestamp

When destination directory contains old files

When your destination directory already contains all the previously transferred files, synchronize source directory to destination directory, instead of simple transfer.

Basically use instead of and instead of .

With WinSCP .NET assembly that means, use , with argument set to or instead of or respectively.

When destination directory does not contain old files

When the old files are removed from the destination directory, you can instead select the new files based on timestamp.

Relative time constraint

For that you can use file mask with time constraint. For example, to transfer only files created/modified since yesterday, use mask (means all files modified in the last 24 hours).

In scripting, apply the mask using switch of or commands.

For example:

put-filemask="*>=1D" *

In WinSCP .NET assembly, use . PowerShell example:

$transferOptions = New-Object rushbrookrathbone.co.ukerOptions $rushbrookrathbone.co.uksk = "*>=1D"   $rushbrookrathbone.co.ukes("d:\toupload\*", "/home/user/", $False, $transferOptions)

Absolute time constraint

If you need to select file specifically created/modified today (not simply in the last 24 hours), you can use keyword (or other time specifications).

In scripting:

put-filemask="*>=today" *

In WinSCP .NET assembly:

$transferOptions = New-Object rushbrookrathbone.co.ukerOptions $rushbrookrathbone.co.uksk = "*>=today"   $rushbrookrathbone.co.ukes("d:\toupload\*", "/home/user/", $False, $transferOptions)

Remembering the last timestamp

In some cases you cannot rely on some artificially determined timestamp. E.g. because the files are being added continuously and your code needs to continuously (or very frequently) fetch them. In such case, you can remember the last run time, or even better the timestamp of the latest file processed in the last run, and use that timestamp as the threshold for the consecutive run.

The following snippet shows, how to implement a continuously running PowerShell script that fetches new files:

$sourcePath = "/remote/path/*" $destPath = "C:\local\path\" $lastTimestamp = $Null   while($True)&#; $transferOptions = New-Object rushbrookrathbone.co.ukerOptions   if($lastTimestamp -ne $Null)&#;Write-Host"Downloading files modified after $lastTimestamp" $rushbrookrathbone.co.uksk = ("*>" + $rushbrookrathbone.co.ukng("yyyy-MM-dd HH:mm:ss"))&#;else&#;Write-Host"Downloading all files"&#;   $transferResult = $rushbrookrathbone.co.ukes($sourcePath, $destPath, $False, $transferOptions) $rushbrookrathbone.co.uk()   # Find the latest downloaded file $latestTransfer = $rushbrookrathbone.co.ukers | Sort-Object -Property @&#; Expression = &#;(Get-Item $_.Destination).LastWriteTime &#;&#; ` -Descending | Select-Object -First 1   if($latestTransfer -eq $Null)&#;Write-Host"No files found."&#;else&#; $lastTimestamp = (Get-Item $rushbrookrathbone.co.ukation).LastWriteTime Write-Host("Downloaded $($rushbrookrathbone.co.uk) files, " + "latest being $($rushbrookrathbone.co.ukme) with timestamp $lastTimestamp.")&#;   Write-Host"Waiting"Start-Sleep -Seconds 5&#;

Though, your code may run in separate scheduled runs, rather than continuously. Then you have to persist the last timestamp between the runs, for example like this:

# Read last timestamp of previous run, if any $timestampFile = "rushbrookrathbone.co.uk"if(Test-Path $timestampFile)&#; $lastTimestamp = [DateTime]::ParseExact((Get-Content $timestampFile), 'O', $Null)&#;else&#; $lastTimestamp = $Null &#;   # The inner code from loop of the above code snippet   # Persist timestamp for the next runSet-Content -Path $timestampFile -Value $rushbrookrathbone.co.ukng("O")

Remembering already transferred files

See example Remember already downloaded files so they are not downloaded again.