Sql Server Database Backup Utility

Source code checked in, #76924

Project Collection Service Accounts — Mon, 01 Oct 2012 21:29:18 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #76923

Project Collection Service Accounts — Mon, 01 Oct 2012 21:23:54 GMT

Checked in by server upgrade

Project License Changed

Wed, 14 Mar 2012 13:23:52 GMT

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and 2. You must cause any modified files to carry prominent notices stating that You changed the files; and 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

Source code checked in, #72926

obastemur — Wed, 07 Mar 2012 03:16:40 GMT

Closed Issue: Feature Request: Improve error handling [7005]

obastemur — Wed, 07 Mar 2012 03:04:04 GMT

I would like to request that error handling be improved.

For example, on a failed backup the console output still displays "Backup process completed successfully".

SqlDatabaseBackup process started
HOSTNAME\SqlExpress 9.0.5000
Starting the backup process...
Backing up database master to C:\Users\username\Downloads\SqlDatabaseBackup_1.0.0.0\backups\master_20110805 115504.bak...Error backing up database, Backup failed for Server 'HOSTNAME\SqlExpress'.
Backing up database model to C:\Users\username\Downloads\SqlDatabaseBackup_1.0.0.0\backups\model_20110805 115504.bak...Error backing up database, Backup failed for Server 'HOSTNAME\SqlExpress'.
Backup process completed successfully

Starting the archive process...
Archive process completed successfully

SqlDatabaseBackup process complete
Comments:

Implemented + Mail Feature

Closed Issue: Feature Request: Automatically create the backup destination directory if it does not exist. [7004]

obastemur — Wed, 07 Mar 2012 03:03:16 GMT

Hi.

Thank you for Sql Server Database Backup Utility v1.0.0.0.

I would like to request that the backup destination directory is automatically created if it does not exist.

Currently, I get the following exception:

SqlDatabaseBackup process started
HOSTNAME\SqlExpress 9.0.5000
Starting the backup process...
Backing up database master to C:\work\Sql Backups\master_20110805 114734.bak...Error backing up database, Backup failed for Server 'HOSTNAME\SqlExpress'.

Backing up database model to C:\work\Sql Backups\model_20110805 114735.bak...Error backing up database, Backup failed for Server 'HOSTNAME\SqlExpress'.
Backup process completed successfully

Starting the archive process...
Error archiving files, Could not find a part of the path 'C:\work\Sql Backups\SqlBackup_20110805_114735.zip'.

Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\work\Sql Backups\SqlBackup_20110805_114735.zip'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at ICSharpCode.SharpZipLib.Zip.ZipFile.Create(String fileName)
at SqlDatabaseBackup.ArchiveManager.ArchiveFiles(String archivePath, ArrayList filesToArchive) in D:\work\SqlBackup\SqlDatabaseBackup\ArchiveManager.cs:line 25
at SqlDatabaseBackup.Program.ArchiveFiles() in D:\work\SqlBackup\SqlDatabaseBackup\Program.cs:line 248
at SqlDatabaseBackup.Program.Main(String[] args) in D:\work\SqlBackup\SqlDatabaseBackup\Program.cs:line 55

Thank you.
Comments:

Implemented

Source code checked in, #72925

obastemur — Wed, 07 Mar 2012 03:01:33 GMT

Release Version 1.01 - Solution file is updated to Visual Studio 2010 - .NET Framework version is to 3.5 - Improvement: Console Messages, Error Handling - Feature: Application asks for Admin Rights in order to work (TIP: start Visual Studio with Admin Rights) - Feature: Creates backup folder if its not exist (createNotExist key inside config file) (App.config -> Backup) - Feature: Send HTML formatted Email (All the console output) (App.config -> Email) - Feature: Delete Files Older Than X Days (App.config -> Archive)

Closed Issue: Feature Request: Upgrade sln to Visual Studio 2010 [7006]

obastemur — Wed, 07 Mar 2012 00:33:33 GMT

I would like to request the sln be upgraded to Visual Studio 2010.

It is currently a Visual Studio 2005 sln.

Thank you.
Comments:

Solution is updated to VS2010

New Post: what's the advantage against using sqlserver scheduels?

damzzz — Thu, 19 Jan 2012 17:43:08 GMT

Maybe because there is no jobs with SQL Express ?

Reviewed: Sql Database Backup v1.0 (Oct 12, 2011)

danieltharris — Wed, 12 Oct 2011 08:33:33 GMT

Rated 5 Stars (out of 5) - This is great, easy to use and quick to setup. I have extended this so that it emails me when a backup completes and also added the option to upload via FTP to another server. As soon as I get a chance i'll post the source if anybody is interested in these small extensions.

New Post: what's the advantage against using sqlserver scheduels?

yhtonline — Sat, 13 Aug 2011 08:25:50 GMT

for sqlserver 2008, we use sqlserver jobs/schedules for automatically backup, not quite understand what's this utilities advantages?

New Post: Project Description is a little misleading

icnocop — Sat, 06 Aug 2011 21:03:01 GMT

Hi.

The Project Description, "This application is designed to help automate the backup of Sql Server Databases to the local file system." is a little misleading because the backup path is actually relative to the sql server.

You can use a unc path, but that is not really a "local file system" because it is actually relative to the sql server.

For example, if I have a sql server running on a remote machine, I cannot back up a database on that server and expect the backup file to be placed on my local C:\ without using a unc path for example.

Thank you.

Created Issue: Feature Request: support sql authentication [7010]

icnocop — Sat, 06 Aug 2011 20:16:13 GMT

I would like to request the ability to use sql authentication instead of only windows authentication.

Thank you.

Created Issue: Feature Request: create a library with the core logic that can be refrenced in other applications [7008]

icnocop — Sat, 06 Aug 2011 07:17:52 GMT

I would like to request a library be created with the core logic that can be reference in other applications.

The console project should reference the new library and pass the configuration settings to it so as to not duplicate code.

In this way, another application can programmatically use the library without having to execute an exe.

Thank you.

Created Issue: Feature Request: ability to pass command line parameters (instead of only relying on the configuration file) [7007]

icnocop — Sat, 06 Aug 2011 07:12:25 GMT

I would like to request the ability to pass command line parameters to SqlDatabaseBackup.exe instead of only relying on the configuration file.

For example:
SqlDatabaseBackup.exe "master"+"model" "C:\backup" /server=.\SqlExpress /archive="SqlBackup_{0}.zip"

Here is a great library for parsing command line arguments:
http://code.google.com/p/nconsoler/

Thank you.

Created Issue: Feature Request: Upgrade sln to Visual Studio 2010 [7006]

icnocop — Sat, 06 Aug 2011 07:03:15 GMT

I would like to request the sln be upgraded to Visual Studio 2010.

It is currently a Visual Studio 2005 sln.

Thank you.

Created Issue: Feature Request: Improve error handling [7005]

icnocop — Sat, 06 Aug 2011 06:59:43 GMT

Created Issue: Feature Request: Automatically create the backup destination directory if it does not exist. [7004]

icnocop — Sat, 06 Aug 2011 06:53:52 GMT

Updated Release: Sql Database Backup v1.0 (Dec 23, 2008)

aaudette — Thu, 26 May 2011 12:59:01 GMT

Works with SQL Server 2005, 2008 & 2008 R2. Also works with SQL Express.

The configuration file holds the name of the server, and a list of databases to include in the backup. When the utility is run, all the databases included in the list will be backup up to the configured directory. You can also to have all backup files compressed into a single .zip archive file for ease of backup management.

Released: Sql Database Backup v1.0 (Dec 23, 2008)

Thu, 26 May 2011 12:59:01 GMT