Click here to Skip to main content
13,050,606 members (85,392 online)
Click here to Skip to main content
Add your own
alternative version


57 bookmarked
Posted 16 May 2009

Backup of Data files - Full and Incremental

, 16 May 2009
Rate this:
Please Sign up or sign in to vote.
Full and incremental backup of files.

main programcscreen


We were backing up all of the files in a directory for an application. However, not all of the files get changed all of the time. Some of them are very large. Occasionally, only a couple of small files get changed. We were backing up the entire data folder every time, and needed to reduce the time and storage capacity for a backup. What this article goes to show is that a full backup and then an incremental will cut down the backup time substantially. The additional cost is the restore time, which is done only when needed.

Using the Code

To start, I needed a zip compression routine to zip the files up and restore them. This was the first problem I encountered. I was able to find the routines, and an article on how to use them. Thanks to VB Rocks and his article Zip Files Easy! This at least got me to understand how to zip the files. I found that there are issues with this methodology. I found the zip routines also include a file that is used to show what is in the compressed file. I also found these routines will only uncompress the files that were created with these routines but not all of the zip files that Windows creates. For my purpose, that was fine since I was only using this program as a proof of concept. In the final version, we probably will use GZip and not Zip.

The normal backup methodology is to do a full backup first and then do the incremental ones (differences from the full) which are done every time after. In my case, I was going to schedule the Full on Sunday, and then the incremental ones for Monday through Friday. The process then starts all over. To do a restore, you restore the full backup and then each incremental (in order) until the entire incremental backup set is finished. To test this, the program would take a source directory and a directory to place the zip file into. The resulting filename is a combination of the type of backup (Full, Incremental) and what sequence it is. To store the sequences of the full and increment, I use an XML file to save the settings. A good article Quick and Dirty Settings Persistence with XML by circumpunct describes a quick and easy way to save settings in an XML file, which I used. Each time a backup is done, the program updates the setting so the next time they use different file names. How I distinguish the sequences is a full backup has a name like BackupFull-(Full backup sequence#).zip. Each time a full backup is done, the sequence number is incremented. The incremental file name is BackupInc-(Full backup sequence#)-(Incremental sequence#).zip. The following screenshot shows several backups to illustrate this technique.

examples of filenames

This routine allows a restore to pick a sequence number, get the full backup, and then get all the incremental versions that have the full backup number, then restore each one in proper order. This is very similar to a tape backup system.

This sample program does a compress and an FTP backup. I did both since they were fairly easy to implement and showed the concept. On the restore, I wanted to only do the uncompress since the FTP restore would be more time consuming to write and would not show much more of the concept. The code below shows how to do the compress depending on if it is a full backup or not. How I handled the incremental is to check the archive bit for each file. If it is set, then we do not backup the file since the last backup. Once the file(s) are backed up, the archive bit is cleared so we do not back it up again the next time, unless it is actually changed.

/// <summary>
/// Zip the files up depending on if this is a full or incremental. 
/// </summary>
/// <param name="zipPath">The directory that will contain the zip file when done</param>
/// <param name="sourceDirectory">The directory that contains the source files to zip</param>
/// <param name="bcktyp">The type of backup</param>
public void ZipFiles(string zipPath, string sourceDirectory, BackupType bcktyp)
    DirectoryInfo di = new DirectoryInfo(sourceDirectory);
    FileInfo[] filess = di.GetFiles();
    FileAttributes fileAttributes;

    // Open the zip file if it exists, else create a new one 
    Package zip = ZipPackage.Open(zipPath, FileMode.OpenOrCreate, FileAccess.ReadWrite);

    //Add as many files as you like
    for (int ii = 0; ii < filess.Length; ii++)
        if (bcktyp == BackupType.Incremental)
            // get the attibutes
            fileAttributes = File.GetAttributes(filess[ii].FullName);

            // check whether a file has archive attribute
            bool isArchive = ((File.GetAttributes(filess[ii].FullName) & 
                 FileAttributes.Archive) == FileAttributes.Archive);

            // if the archive bit is set then clear it
            if (isArchive)
                // add to the archive file
                AddToArchive(zip, filess[ii].FullName);
            // add to the archive file
            AddToArchive(zip, filess[ii].FullName);

        // clear the bit we archived it 
        File.SetAttributes(filess[ii].FullName, FileAttributes.Normal);
    // Close the zip file
/// <summary>
/// Add the file to the zpi package
/// </summary>
/// <param name="zip">The package to add the fiel to </param>
/// <param name="fileToAdd">The fielname to add</param>
private void AddToArchive(Package zip, string fileToAdd)
    // Replace spaces with an underscore (_) 
    string uriFileName = fileToAdd.Replace(" ", "_");

    // A Uri always starts with a forward slash "/" 
    string zipUri = string.Concat("/", Path.GetFileName(uriFileName));

    Uri partUri = new Uri(zipUri, UriKind.Relative);
    string contentType = MediaTypeNames.Application.Zip;

    // The PackagePart contains the information: 
    // Where to extract the file when it's extracted (partUri) 
    // The type of content stream (MIME type):  (contentType) 
    // The type of compression:  (CompressionOption.Normal)   
    PackagePart pkgPart = zip.CreatePart(partUri, contentType, CompressionOption.Normal);

    // Read all of the bytes from the file to add to the zip file 
    Byte[] bites = File.ReadAllBytes(fileToAdd);

    // Compress and write the bytes to the zip file 
    pkgPart.GetStream().Write(bites, 0, bites.Length);

/// <summary>
/// Unzip the files
/// </summary>
/// <param name="zipPath">The file to unzip</param>
/// <param name="destinationDirecory">The destination directory</param>
public void UnZipFiles(string zipPath, string destinationDirecory)
    PackagePartCollection ppc;
    // Open the zip file if it exists, else create a new one 
    Package zip = ZipPackage.Open(zipPath, FileMode.Open, FileAccess.Read);

    ppc = zip.GetParts();

    foreach (PackagePart pp in ppc)
        // Gets the complete path without the leading "/"
        string fileName = pp.Uri.OriginalString.Substring(1);

        Stream stream = pp.GetStream();

        // Read all of the bytes from the file to add to the zip file
        int il = (int)stream.Length - 1;
        Byte[] bites = new Byte[il] ;

        stream.Read(bites, 0, bites.Length);

        fileName = fileName.Replace("_", " ");  // replace underscore with space
        File.WriteAllBytes(String.Concat(destinationDirecory, "\\", fileName), bites);
    // Close the zip file

This following is the code that I use to save and get the backup sequence number and the increment number:

private void GetSettings()
    Settings settings;
    fullbacknum = 1;
    Incnumber = 1;

    settings = new Settings();

    fullbacknum = settings.GetSetting("BackupNumber", fullbacknum);
    Incnumber = settings.GetSetting("Incnumber", Incnumber);

private void SaveSettings()
    Settings settings;

    settings = new Settings();

    settings.PutSetting("BackupNumber", fullbacknum);
    settings.PutSetting("Incnumber", Incnumber);

private void btnCompress_Click(object sender, EventArgs e)
    string strsourcedir = "";    // the directory we want to compress
    string strzipdir = "";      // where the zip file is to be created
    string strfilename ="";     // the final filename we want to create
    HCompress   hc;
    BackupType bt = BackupType.Full;


    if (txtSourceDir.Text.Length == 0)
        errorProvider1.SetError(txtDestinationDir, "Enter Source dir");
    if (txtZipDir.Text.Length == 0)
        errorProvider1.SetError(txtZipFile, "Enter zip dir");

    // Get the directory locations
    strsourcedir = txtSourceDir.Text;
    strzipdir = txtZipDir.Text;

    // check what radio button is enabled
    if (rdobtnFull.Checked)
        bt = BackupType.Full;
        strfilename = string.Format("BackupFull-{0}.zip", fullbacknum);
        Incnumber = 0;  // On a full backup reset the increment number
    if (rdobtnInc.Checked)
        bt = BackupType.Incremental;
        strfilename = string.Format("BackupInc-{0}-{1}.zip", fullbacknum, Incnumber);
    strfilename = strzipdir + "\\" + strfilename;
    txtFilename.Text = strfilename;

    hc = new HCompress();
    hc.ZipFiles(strfilename, strsourcedir, bt);


The following chart tries to show the amount of space we will be saving. I used 1000 files as an example of the total number of files there might be and what percentage of the total are in each size category to calculate the total amount of disk storage that would be used. This shows that a typical backup is 7.3 Gig every night using a full backup methodology. The second set of numbers shows what percentage of each file size category might change every night. You can change the percentages to explore the various sizes, but I used this as an example. The incremental is only 1.6 Gig, which is a sizable amount of disk storage saved, not to mention the time to process this much data. If we were to see what doing a full backup every night would cost, it is a total of 36.5 Gig compared to doing a full and incremental which is 14 Gig. These are very good numbers. Now, you can see why tape backup companies have always used these methodologies.

% of files# Files in data folderSize (Meg)Tot Size (Meg)Meg
1000101001100Full Backup7300
3030051500Incremental backup1680
% changeTot Size (Meg)Change Size (Meg)
301500450Restore Full7300
202500500Restore Inc14020

Points of Interest

I have not found an example that works for the zip file compression routines. Of all the articles I have read, there are two compression libraries that I will be looking at. The first is SharpZipLib and the second is DotNetZip. Both have many very good comments about them, and they are free to use.


  • 16 May 2009 - Initial release.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Web Developer
United States United States
I am a Director of Engineering, have an MBA and work in C# forms, Asp.Net and I have been writing Windows program since windows 3.0. I am currently working in the Healthcare industry.

I enjoy reading, music (most types), and learning new technology. I am involved in opensource projects at codeplex.

My linkedin link is

You may also be interested in...

Comments and Discussions

GeneralConsider use of NTFS change journal Pin
pquirk10-Aug-09 9:39
memberpquirk10-Aug-09 9:39 
The NTFS change journal, first introduced in Windows 2000, can provide your backup up with a near real-time feed of information about changed files and the reason for changes. Implementing a service which processes the change journal to minimize the number of files you need to look at can dramatically reduce the effort in creating a backup file.

See for the initial implementation.
GeneralImportant solution Pin
Matt Sollars29-May-09 4:10
memberMatt Sollars29-May-09 4:10 
GeneralNice.... Pin
Shivprasad koirala26-May-09 12:59
memberShivprasad koirala26-May-09 12:59 
GeneralRe: Nice.... Pin
Donsw27-May-09 1:22
memberDonsw27-May-09 1:22 
GeneralDifferential backup would be a nice addition Pin
PedroMC20-May-09 0:02
memberPedroMC20-May-09 0:02 
GeneralRe: Differential backup would be a nice addition Pin
Donsw26-May-09 11:43
memberDonsw26-May-09 11:43 
GeneralRe: Differential backup would be a nice addition Pin
Matt Sollars29-May-09 4:23
memberMatt Sollars29-May-09 4:23 
GeneralRe: Differential backup would be a nice addition Pin
PedroMC30-May-09 0:49
memberPedroMC30-May-09 0:49 
GeneralRe: Differential backup would be a nice addition Pin
Matt Sollars30-May-09 9:23
memberMatt Sollars30-May-09 9:23 
GeneralRe: Differential backup would be a nice addition Pin
VJSWAMI4U8-Jun-09 3:59
memberVJSWAMI4U8-Jun-09 3:59 
GeneralRe: Differential backup would be a nice addition Pin
Donsw8-Jun-09 15:59
memberDonsw8-Jun-09 15:59 
GeneralRe: Differential backup would be a nice addition Pin
Matt Sollars29-May-09 4:12
memberMatt Sollars29-May-09 4:12 
GeneralRe: Differential backup would be a nice addition Pin
Donsw30-May-09 4:44
memberDonsw30-May-09 4:44 
GeneralExisting sw Pin
Mi.Chal.16-May-09 8:18
memberMi.Chal.16-May-09 8:18 
GeneralRe: Existing sw Pin
Donsw16-May-09 8:24
memberDonsw16-May-09 8:24 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.170713.1 | Last Updated 16 May 2009
Article Copyright 2009 by Donsw
Everything else Copyright © CodeProject, 1999-2017
Layout: fixed | fluid