Automatic FTP Backup Software

We are looking for software that can run transparently to the user, and run a scheduled backup of local documents to a remote server. The software needs to be able to run on Windows NT 4, 98, 2000, XP, and 2003. The software needs to be able to run on a computer for months without crashing, or interfering with anything. If a file scheduled to be backed up is in use the program needs to be able to detect that, and email an alert at the end of that scheduled backup. We do not need a good looking installer, or self extracting package, etc. A script to copy files will be fine because the program is to be installed by a technician. ---NOTE - I MODIFIED THE ATTACHED FILE TO REFLECT BETTER SMTP SPECIFICATIONS -------- ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). SPECIFICATIONS BEGIN HERE: FEATURE LIST 1. Transparent to the user (not even in system tray, maybe a shortcut to make the window visible) 2. Runs on all Windows operating systems from NT4 > Server 2003 3. Configured through a .ini file ??" not a gui 4. Error handling and logging 5. Mail notifications of successes and failures 6. Scheduler built in, configured through same .ini file 7. Zip capability for specified directories 8. FTP protocol to remote server TRANSPARENT TO THE USER It doesn’t matter how it’s done, preferably just a hidden window and system tray icon. All we need the main window to show is status. Here is a list of things to display in the gui. • List of files/directories to be backed up • Schedule of backup cycle • Success/failure logs from the previous backup attempts • Remote location of where files are going • “Help > About?? screen to show copyright, etc ERROR HANDLING & LOGGING We want the program to detect when there is a problem, at any step and log that problem. At the end the current backup process we want that error emailed to an email that is specified in the config file. There also needs to be confirmation emails when files were successfully backed up. Once the logfile reaches 1MB it needs to start a new file, and rename the old one to the current date. There needs to be emails with raw error logs going to an admin contact with the provider (me) and also the client. Same for confirmation emails, they need to be able to go to separate email addresses for a total of 4 email addresses. SCHEDULER This can be very primitive, maybe similar to the way you schedule something using crond in linux. We need to be able to run the backup on certain days, or weeks, or monthly, etc. ZIP We may want to specify that a directory on someone’s computer be zipped before uploading to remote server, it doesn’t matter if it uses Zip or .[login to view URL] technology, anything that compresses the files into a single file to be uploaded. FTP This program needs to be able to ftp successfully in ACTIVE mode and be very robust. We are planning on running this software on hundreds of machines, and potentially connecting to the same server with all of them at the same time. CONFIGURATION We want this to be very basic, one of the ways of keeping it that way is to make the program configured through an .ini file. The file should have variables for all features, in a simple syntax like: $RemoteServerAddress=??[login to view URL]? This way, once the program is installed by our technician, we can quickly fill in fields and save this file, and run the program. ## Platform As stated elsewhere, this program needs to run on all windows back through NT4 and windows 98.