Moving Folders With FSRM

Nick 1

My team has been asked to set up an automated system to "archive" project directories on our Server 2019 share. In reality they want certain directories to be moved to another location automatically based on a flag file saved within the directory that needs to be move, this flag file would be something like flag.abcd. I know FSRM can screen for file extension, I'm able to see the events created when saving a file like this to the share, but I can't seem to find a way to have FSRM do something with that directory. Is there an automated way to have FSRM do something with the directory it sees a file in that gets hit by the file extension screen? I figure there may be some way to run a script for every file found but I don't know if FSRM would pass that file path off to the script step, if that makes any sense.

Nick 1

To follow up on my own post, I figured I could just do this using PowerShell and Task Scheduler, below is a script I'm working on to do what I described.

$log = Get-EventLog -LogName Application -Message "*flag.wxyz*" -After (Get-Date).AddDays(-1) | select Message -ExpandProperty Message

$paths = @()

foreach ($event in $log) {
    $event -match "attempted to save (?<content>.*) to D:\\"
    $paths += ($Matches['content']).Substring(0,31)
    }

foreach ($path in $paths) {
    Move-Item $path -Destination C:\test
    }

Rich Matheisen 46,636 Reputation points

2020-08-26T21:33:23.143+00:00

I'd be careful of that regex. The "." matches both nothing (zero characters) and everything (a string of infinite length bounded at the end by an anchor -- probably a CrLf character pair). It might be better to swap the "" for a "+". Even then it's pretty inefficient. Either the * or + will immediately match to the end of the string and then have to backtrack , fail, backtrack again (to get to the " t") and then continue the search from there.

So, I'd suggest changing the ".*" to ".+?" to match do a minimal match and then continue the search for the " to D:\".
Rich Matheisen 46,636 Reputation points

2020-08-26T21:37:26.207+00:00

Also (because there's a stinking 1000 character limit on replies so I couldn't put this in the last reply!), try wrapping the Move-Item in a Try\Catch block (adding "-ErrorAction Stop" to the Move-Item). Ignore the "file not found" errors, but log any other errors for someone's attention.

And, try using Get-WinEvent instead of Get-EventLog. It's a lot faster and has access to event logs that Get-EventLog doesn't.
Rich Matheisen 46,636 Reputation points

2020-08-26T21:39:14.36+00:00

And . . . because you're going back one day, you're going to try to move files twice, resulting in errors. Thus, my previous post about using Try\Catch!

1 answer

Ian Xue 36,661 Reputation points Microsoft Vendor

2020-08-27T06:51:35.753+00:00

Hi,
I don't suppose FSRM is the best way to monitor file creation. The System.IO.FileSystemWatcher class could be helpful.
https://learn.microsoft.com/en-us/dotnet/api/system.io.filesystemwatcher?view=netcore-3.1

Best Regards,
Ian

----------

Please remember to "Accept Answer" and upvote if the reply is helpful.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Moving Folders With FSRM

1 answer

Your answer