K# Developers X3

10Aug/154

10 good examples why you should try out atmfiler

I figured I might mention some examples for the application atmfiler, its quite neat in many circumstances.
It's mainly an application for power users, administrators and such.

  1. Update applications - you can automatically update applications with this, so your applications on several locations keeps updated.
  2. Automatically clear logfiles and such - after a specific timeframe you can move away less critical files to a long term storeage, ea log files, database backups for example.
  3. Make a failsafe folder - Like "My Documents", always keep a secondary folder as a mirror and save ALL changes to files with a version history.
  4. Sync multiple folders - It's easy to sync a folder aswell, just have the two folders as destination and source to each other and use the sync function on all folders.
  5. Sort your media - Move files from your possible already maxed out "Cloud Camera" Upload -folder to a local backup with in neat folders.
  6. Lightweight - No hidden bloat or anything, just straight out from the compiler.
  7. Compatible - If you manage to install .NET 2.0 or later you are good to go!
  8. Multiple services - If you have several configurations on the same computer and want to run them all in service mode, no problem!
  9. Move specific files - If you want to backup documents and pictures to different folders there is a setting for that aswell.
  10. To state the obvious - Move a file from folder A to folder B, C and D.

 

 

Would very much like to hear from you about your area of application for atmfiler.

Follow me on twitter:


 

Filed under: Note Leave a comment
Comments (4) Trackbacks (0)
  1. I am a support technician for a variety of stand-alone users, and have setup a filecopy process for them that uses xxcopy/Robocopy, or just xcopy, depending on their levels of ability, and how much their management require their system to be purely as supplied, or allow useful utilities.

    However my script, and the possibly somewhat better option of “File History” all suffer from a basic problem – fullname length limit.

    Can you detail if the atmfiler uses the API that does not suffer from the 250 character limit, and would consequently allow files with long names, in locations such as the desktop to have versions copied to a store, with their full source location retained, and a timestamp added.
    And, if atmfiler does not do this, is there a facility from any ‘recognisably safe’ supplier that does.

    I recognise that as a result of using the long-name capable API, the backups would have to be managed, and used for recovery using the app, but, to my thinking that is much safer than the “File History” process that allows users to just use explorer on the backups folder and delete stuff as they consider may be appropriate.

  2. I can confirm that atmfiler have a 250 character limit for file names, the limitations are in the NTFS file system.
    However, the 250 character limit is for the filename only, so you can have a file on the desktop (quite long filepath) and have the maxed out filename.
    atmfiler logs the timestamp, path and the complete filename.

    If you have a maxed out filename and use the “file history” option it will fail to copy due to renaming the copy to (0), (1) and so on.

    atmfiler does not have any management for restoring the file history, its quite manual. Even so, the users have to manually browse the backup folder as you mention. It should always be a file matching the source file in the backup, otherwise it will be backuped again if deleted by the user.

    • Thanks for the confirmation re the 250(approx.) char fullname limit for the filename within atmfiler.

      A slight correction – the is not a 250 char limit on fullnames within NTFS
      The limits (for recent versions of NTFS) are actually 32,767 Unicode characters with each path component (directory or filename) up to 255 characters long
      It’s the API generally used within Windows applications and utilities – e.g. (Windows Explorer/File Explorer) facilities that has the 255 char limit. there is an alternative API that conforms to the NTFS rather than the windows limits.

      I am hoping to find a backup facility that uses the NTFS related API – and will, presumably protect the files from inadvertent user deletion or modification by holding the backups in something like an ISO image – or a zip type store, with the app itself including an extraction routine.
      And – without even resorting to anything like a mountable ISO image, the facility could, using the NTFS API, have the highest level foldername as “atmfiller-store”, and the second level as a 253 character name, precluding the normal file explorer access to the files within that folder.
      OK, that would limit the atmfiler to holding the backup on a NTFS partition, but it seems to me that would be a relatively easy way to bypass the limits in the MS supplied “File History”, and many other Windows Apps/facilities for ‘file backup’ that are currently being marketed.

      Currently, the best option I have come across is to use a file-mode partition backup facility and create very frequent incremental backups – which causes problems for many backup facilities that cannot cope well, or at all with hundreds of incremental sets,
      or, alternatively –
      To put the files with a backup facility-assigned-name in a zip container with an associated index (text) file containing the file’s proper fullname, and version (date-timestamp).

      There are facilities such as Spideroak for small volume files – as in them that I typed the contents of)

  3. The application uses .NET Framework which is deeply embedded in Windows.
    I have not yet been limited by Windows file limitations.

    I use the application for shuffle xml-files from different locations that my services get all files they need. Its mainly EDI integrations between different companies. And its always good to make a backupfolder for reviewing errors. 🙂

    Anyway, thanks for showing intrest, its very informative to see other administrator and superusers needs for different tools.


Leave a comment

No trackbacks yet.