4 replies to this topic

[axoid]

The add-in will be made up of two components: The WHS UI and the Windows service.

The UI will allow the user to configure file management jobs on the settings panel. Each job will have the options: task (copy/move/delete), in which folder, file filter (Defaults to *.*), and how often (Daily,Hourly,Every # of minutes). Deletes will have the additional option of defining how old the file is before it is deleted.
Displayed on the add-in main console screen will be a history list of the last 300 files that have been managed. There won’t be any real-time interaction between the UI and the service in the first version.

The service will perform the file management based of the setting saved from the UI. New setting changes may take up to an hour before they become active. The service will not copy, move or delete a file if it is being used by another application.

Feel free to discuss and offer suggestions.

[HSS-Dave]

Sounds like the start of a good Add-In. Is it possible to monitor a share or drive letter on the server and copy it's contents to another share or drive letter? Without any further interaction? Say I copy a photo to a folder I would like it automatically copied to wherever I designated via the UI.

What's the underlying engine for file manipulation? Robocopy?

[axoid]

Sounds like the start of a good Add-In. Is it possible to monitor a share or drive letter on the server and copy it's contents to another share or drive letter? Without any further interaction? Say I copy a photo to a folder I would like it automatically copied to wherever I designated via the UI.

What's the underlying engine for file manipulation? Robocopy?

The add-in will monitor any specified folder that is viewable from the server OS. That includes the shares, system drive or any other drive or part of the file system. It will be able to do the photo copy that example that you described.
One thing I’m wondering about is would people want the file recopied every time the action job was executed, or only copied the first time it finds the file or have it monitor the file for the last modified date to change and then copy it again? Do you want the copy to overwrite the file if it is already there or make that configurable?

There wont be an underlying engine. C# has a file management API to handle copy, move and delete. The rest is just adding logic and control around it.

[jmwills]

Is this for Vail for Version 1? There is a similar option withing Server 2008R2 that will age files and allow you to delete,move, etc given a defined set of date parameters.

[axoid]

This will be for V1 for now. I'm not sure I'm going to go to Vail, though I have the beta to install.