BackupAssist is a simple, affordable and useful backup utility for the servers of small and medium business.

BackupAssist makes business data protection painless and automatic in 5 ways: it schedules your backups (full, incremental or differential), implements media rotation, notifies you of backup results through email, sends you reminders to load/change media, and makes it easy to perform advanced tasks like custom scripting.

You can backup your files, Windows Servers, Exchange Servers and SQL Servers to a variety of different media including Tape, REV, Disk, NAS, DVD and other devices. BackupAssist provides business-class data protection and is a true alternative to products costing many times more.

Here are some key features of "BackupAssist":

· Open File backup
· Simple scheduling wizards
· Industry-standard tape / disk rotation schemes
· User-friendly setup and configuration interface
· Live Exchange Server backup
· Live SQL Server backup (optional add-on)
· Exchange Individual Mailbox backup (optional add-on)


Limitations:

· 30-day trial

What's New in This Release: [ read full changelog ]

· Enhanced: Installer now works properly on Vista and the other new OS's
· Enhanced: The Activation form now has a Manual button enabling users to choose this option directly if they don't have an Internet connection
· Enhanced: The ASR option is no longer available for users running Windows 2000 (where there is no ASR capability)
· Fixed: NTBackup advanced option Additional Command Line Parameters now working
· Fixed: Annoying domain handling when setting up the Backup User Identity
· Fixed: The SQL restore wizard won't complete if no databases have been selected
· Enhanced: schedules that allow selection of days of the week in a checkbox list now start with the culture-specific first day of the week
· Fixed: Multiple minor validation issues and other UI issues
· Fixed: When network authentication fails, the domain is now retained instead of being reset to the default
· Enhanced: If the console is started when the service isn't running, the user is asked if they want the service to be started
· Enhanced: ntbackup log file handling has been improved such that delays in the file showing up and temporary locks on the file (eg. antivirus software) don't prevent BackupAssist from being able to locate and read the log file
· NEW: All jobs may now be cancelled via the Monitor window during the main engine execution stage. The remaining steps of cancelled jobs are skipped, and the job list shows the job status as Cancelled
· Enhanced: The Exmerge and SQL engines now display more information during the backups via the Monitor window.
· Fixed: SQL backup filenames are no longer formatted using the local sql pseudonyms "." and "(local)", so that restores to the server don't have to be performed from the local server, but pre-existing filenames are still valid for SQL Restore
· Enhanced: If the Exmerge engine fails for a given period, it will no longer try to backup further periods
· NEW: The Exmerge engine offers a number of configurable options, including whether to delete original messages off the server during the export, whether to exclude specific directories from the export, whether or not to attempt to set mailbox rights before the backup, and how to handle setting the optional Domain parameter passed to Exmerge.
· Fixed: The scheduling conflict causing ntbackup jobs to fail if another job finishes during execution has been resolved by forcing ntbackup jobs to only run .one-at-a-time for the entirety of the job, and by executing jobs for other engine types without using DesktopRights.exe
· Fixed: The conventional file copy how uses an entirely new subdirectory of the user-specified working directory in order to avoid accidentally removing user files and/or backing up incidental user files.
· Fixed: NTBackup verify failure messages such as "Difference encountered in alternate file data." are now handled properly.
· Fixed: The should no longer fault when editing email addresses from the dropdown list.
· NEW: Now support sending emails via secure (SSL/TLS) smtp servers such as gmail (smtp.gmail.com) using a secondary mail component.
· Enhanced: Those experiencing issues with the default mail component may find that selecting to use the secondary mail component gives better results.
· Fixed: Configuration file saving has been improved, such that the rare issue where files are corrupted causing the service to fail should no longer occur.
· Fixed: The KnowledgeBase link for failure conditions is once again visible in emailed reports.
· Fixed: Network connections are how handled sensibly when running a job, such that the network path is tested before and after attempting to connect, thus avoiding failures from trying to connect to an already-available connection.
· Enhanced: Failures during RSM functions caused by system changes performed during installation of certain other backup software are now detected and reported specifically.
· NEW: Burning of discs can now be performed using an alternate burning component that can be used if the default component is not giving good results.
· Fixed: In rare cases the scheduler has been known to suddenly halt and hence fail to start scheduled jobs, while the remainder of the functionality was unaffected. The scheduler now includes code to detect this condition and recover silently.
· Fixed: Sometimes temporary files are left behind after a Destination Check. This problem has been fixed.
· Fixed: Out of range figures should no longer end up in the Media Usage Report.
· Fixed: System State only backups are now detected properly during the selection check.
· Fixed: The bug where the Destination Check could fail, but in some circumstances not show what the problem was, has now been fixed.
· Fixed: International characters now show up correctly in script logs.
· Fixed: Bug where large amounts of script output could cause the backup to hang.
· Fixed: System State-only jobs (with no other selections) now pass the selection check on the monitor screen (used to show Error)
· Enhanced: Added logging to assist with debugging errors with the RSM service
· Fixed: Bug where ordinals were showing up incorrectly in the monthly scheduling for maintenance notifications
· Script exit codes (using “exit ”) are now taken into account, zero is success, anything else failure
· The RSM service status check now assumes (hopes) unknown failures (like unauthorized access) won’t cause problems with detect