TFTP Server: move timestamped Cisco config backups into a folder per device

There's nothing built in for this yet, so for now it would need an external file watcher. But it fits something we've been thinking about, so let me run the idea past you.

We'd add an optional "after upload" hook: you point the server at a script of your own, and it runs once per completed upload with the file it just received, the device's IP and the full path of the timestamped file it renamed out of the way. That last one is the bit you need. Your script would get D:\TFTPboot\SW01-confg.20260918-090512 directly, take the device name from it and move it wherever you like, in two or three lines and with nothing else running.

Would that cover it? If there's anything else you'd want passed to the script, now is a good time to say, while the design is still open.

It's built in now, so you won't need a script or a file watcher after all. Instead of the hook I described, the server reads a rules file and does the work itself. It's in TFTP Server 26.10, on the TFTP Server page.

Open Settings, go to the Transfers page and click Post-processing rules. That opens TFTPRules.ini, which sits beside your TFTPServer.ini. It's fully commented, and the server re-reads it every time you save, so nothing needs restarting.

For your setup, add this:

[Rule.0]
Event = upload-complete
MatchType = regex
Match = ^(.+)-confg$
Action = move
Source = previous
Target = D:\TFTPold\{1}\{file}

Source = previous is the line that matters: the rule acts on the timestamped copy the server renamed out of the way, not on the new upload. Match is still tested against the uploaded name, so the brackets capture everything before -confg and {1} becomes SW01. {file} is the renamed file's own name, so SW01-confg.20260918-090512 ends up at D:\TFTPold\SW01\SW01-confg.20260918-090512, and any folders that don't exist yet are created for you.

Leave When file already exists on Rename with timestamp suffix as you have it now, since that's what produces the file the rule moves.

The label next to the button shows how many rules were loaded and, if one has a mistake in it, the line number to look at. Everything the rules do goes into the server log as well.

Thanks for letting me know, good to hear it works :)

You described a real setup precisely enough that there was something definite to build against, which is rarer than you'd think. The rules are part of the public release now, TFTP Server 26.10, so there's no need to stay on the preliminary build.