Backup and Restore Application for Cloud Storage

This application will consist of a backup application as well as backup service that will utilize Microsoft Volume Shadow Copy Service (VSS) to backup local and network files as well as database files including Microsoft Exchange version 2003 and up as well as SQL DB's. It will need to follow a logical backup sequence, such as incremental, full backups and restores with scheduling functionality. Application must work with the following versions of windows: XP, Vista, Windows 7, Server 2003 and Server 2008 in 32 bit and 64 bit versions for all. The application at runtime should automatically detect and use the correct target for VSS. There should be two applications built, a user interface (UI) as a Windows Presentation Foundation (WPF) application, and a component dll (referred to Service from now on) that does the work of the backup/restore based on a set of instructions from the UI. The UI would also initially query the Service and present options to a user based on what may be available to backup on the system that the application is running on. The target storage will be API based Cloud storage and we will provide a listing of all the different application provides we will need to have the application integrated with, such as Amazon S3, Rackspace, etc. Restore functionality will need to access the cloud storage target and retrieve the files. ## Deliverables **A COMPLETE PROJECT SPEC WILL BE PROVIDED TO FINAL ROUND OF BIDDERS.. **Must be written in C# (.NET version 3.5 or 4.0) with exception of parts that may require C++. If C++ is required, it must be managed C++. The finished work must be provided as one or more Visual Studio Solutions in VS 2008. Release and Debug versions are required and must be able to run debug version in Visual Studio for testing. The Service should be designed to work within a Windows service. The Service and UI should communicate using Windows Communications Foundation (WCF), probably using .NET Remoting, but that decision can be made at a later time. The UI should be able to manage a Service by connecting to a machine that has a Service running. Authentication is required and can be done through Active directory. All request needed to populate the UI should go to the Service and not directly to the local system since the local system would not have the correct information for a Service on a remote system.