Table of contents

6.1 CPTec-Backup

6.1.1 Motivation

6.1.2 External Harddisk Drives

6.1.3 User Manual

6.1.3.1 Functional Principle

6.1.3.2 Installation

6.1.3.3 Configuration

6.1.4 Source Code Documentation

6.1.6 Download

6.1.7 Licenses

6.1.7.1 Job License

6.1.7.2 Source Code License

6.1.1 Backup Software for Hard Disk Media

For hard disk media? What does that mean? Of course, we mean to say that external, portable hard disks are used as a target medium instead of a tape.

Motivation or: Why use external hard disks as a backup medium?

Disadvantages of tape media

Today, the amount of data on file servers, database servers and e-mail servers that is caused by running projects and has to be archived by us on a regular basis is approx. 400 GBytes. In addition, another 1000 GBytes of data for completed projects are stored on our servers. 

All these data must be stored on external media on a regular basis - in the case of running projects every day. Until recently, we have used DDS2 DAT tapes (for incremental backups, Monday through Thursday) and SLR100 tapes (for the weekly backup on Friday) for this. The used backup software was Arcserve™ by Computer Associates[1] and later BackupExec™ by Veritas[2].

This solution did not cause substantial trouble, and due to rotating backup sets it was possible to reconstruct any data status of the last three months at any time. By the way, until today we never had the situation that data loss was caused by a hardware failure. Whenever our backup concept had to proof its operativeness, the data loss had been caused by users who deleted files by mistake.

On the other hand, the expenses and the effort for maintaining our backup concept during the last years were considerable:

• Expenses for backup media: approx. 120 DAT tapes, approx. 40 SLR 100 tapes (1 SLR 100 tape costs approx. 55 EUR today).
• A total of four repairs (two of them after the guarantee had expired) for two HP DDS2 streamers and a Tandberg SLR100 streamer. Yes, these components seem to break regularly if they are forced to do a lot of work.
• Approx. 2000 Euro for buying the backup software and approx. 4000 Euro for the hardware.
• High effort for changing the tapes during a backup run when using SLR100 media at the weekend.
• A lot of time required for double-checking if the backups can be restored properly.

For these reasons, we have always been looking around for alternatives to our existing backup concept. In particular, we had turned our attention to the use of external hard disks as backup media already one or two years ago. 

When both of our HP streamers started to write more and more garbage onto the tapes within several weeks, we finally decided to put the project "Use of external hard disks as backup media" into action.

Advantages of archiving to hard disks

The advantages of external hard disks with respect to tape media are obvious:

• Today, IDE hard disks are far superior to tapes with regard to capacity and purchase cost. One 200 GByte IDE disk with FireWire and USB interface in an external casing is much cheaper than four SLR100 media with 50 GByte native capacity each (140 EUR vs. 240 EUR).
• No additional hardware is required at all. An external hard disk can be connected to any modern PC via USB or FireWire. The stored data are available immediately. There are no expenses for streamers, cleaning tapes and repair work.
• There is no need anymore to change tapes during a backup run. A 200 GByte IDE disk contains four times the capacity of an SLR100 tape. In addition, we assume that the capacities of IDE disks will keep pace with our ever-growing amount of data to be stored regularly. We cannot expect a comparable trend for tape media. For these reasons, we decided to save the money that we had already set aside for buying an automatic tape changer.
• In the case of a "real disaster recovery", the archived data will be available much faster because there is no need for new acquisition and installation of streamers and streamer software.
• If the hard disks are formatted with Windows NTFS and the data are archived via Filecopy, the result of the backup process is transparent and checkable also for users who are not administrators. The data can be restored quickly and easily on any PC.

Possible problems when archiving to external hard disks

After we decided to put the project into action, we first had to remove some stumbling blocks along the path to an operative backup concept:

First of all, we had to take care of the fact that hard disks are more prone to error than tapes. In order to handle this problem, we simply decided to archive the data simultaneously to another internal hard disk.

It also became evident soon that commercially available backup software does not meet our special requirements. Professional software of well-known manufacturers is optimized for tape media. In addition, searching and restoring of archived data is cumbersome. There is only rudimentary support for archiving "via Filecopy".

Windows tools also had to be ruled out for archiving our file servers. XCOPY is not designed for large amounts of data and a deep directory hierarchy. ROBOCOPY offers more features and runs stable, but the required transparency and the convenience of professional backup solutions cannot be achieved via scripting. "Windows Backup" archives into a single file only and lacks convenient operation if data are to be restored. These and similar solutions also do not offer methods to react to special events during the archiving process (e.g. if the hard disk is full). In addition, it is not possible to use a database in order to find archived data files.

Our Backup Software

In short: We have developed "CPTec Backup" - software that will do exactly what is important for us: 

• Simple command line tool that is controlled via a config file. Scheduling is possible via Windows Scheduler.
• Configuration file for backup control. Windows or web dialogs are not required.
• Incremental backups and full backups can be written to different hard disks. Each file can be written to any number of media. Each job may define several targets. This means that data can be mirrored without the need for special software or hardware.
• Creation of log entries into the Windows event log. Creation of backup logs which list every archived file. Creation of warning logs which list files that could not be archived. Creation of summary backup reports.
• Sending e-mails of log files and backup reports.
• Logging of the saved files and warnings in a database (MS SQL Server or MS Jet (MS Access)).
• Automatic deletion of full hard disk media if the need arises. This is a counterpart to the "Overwrite tape" option, but much smarter because only the oldest backup will be deleted if necessary and because different targets can also be written to alternatingly.

A detailed list of all features can hopefully :-) soon be found under "Backup Software Performance Features". A demo version (=> 6.1.6) is also available. You may, of course, also pay for it: You can buy our backup tool for 39 EUR (Job License (=> 6.1.7.1)) or 116 EUR (Source Code License (=> 6.1.7.2)). The software is for personal use only.

And now we tell you something about the required backup hardware (=> 6.1.2).

External links:

6.1.2 Used Backup Hardware

Casing

We have tested two different casings intended for holding external hard disks. 

No-name casing by Litec

Front view with operation LED	Rear view with on/off switch, power supply socket, USB 2.0 and Firewire

 
The casing attracts attention because it has a beautiful and sturdy design. It contains USB 2.0 and Firewire interfaces and was sold for 43.- EUR in April 2005. Unfortunately, there are several drawbacks:

• The thermal design is poor. The hard disk is mounted on rails which are not in good thermal contact with the fully closed casing. The heat is not carried off well because the casing is not equipped with a fan.
• The casing does not contain an acitivity LED.
• Mounting of the drive is cumbersome: When inserting the hard disk, you must make sure that the LED cable is not sequeezed at the front of the casing.
• We have not been able to find a homepage of the manufacturer. This means that there is no support and also no way to update the firmware.

ICY BOX 350

Front view with operation LED	Opened ICY BOX 350

 
The casing is available in several versions that differ with respect to the interfaces and the visual appearance (e.g. blue overall illumination). The advantages for our application are evident:

• Good concept for removal of heat: The hard disk is mounted directly on the aluminum base plate using two countersunk head screws. The perforated metal sheet enclosing the casing allows the air to circulate. 
• The casing contains separate operating and activity LEDs.
• Support by the manufacturer and firmware updates are available via the homepage.

A minor drawback of the ICY BOX 350 is the poor mechanical stability and the fact that the device easily slips on a smooth surface.

Hard disks

We have tested several 200GB disks from Maxtor, Western Digital and Samsung. The technical data of today's drives are fully sufficent for our backup purposes. The following points also seem to be worth mentioning:

• For the best value in GByte/EUR, select the second largest harddrive model of a manufacturer. The harddrive with the largest capacity often seems to be overly expensive.
• There should be at least three years of manufacturer guarantee. In addition, it should be possible to handle guarantee claims directly with the manufacturer. In general, this saves time and it also works smoothly with drives made by Maxtor and Western Digital.
• The current harddrives made by Samsung are especially quiet and they also stay rather cool during operation.

6.1.3 User Manual

1. Functional Principle (=> 6.1.3.1)
2. Installation (=> 6.1.3.2)
3. Configuration (=> 6.1.3.3)

6.1.3.1 Functional Principle

Basics

The software is used for automated archiving of data files on hard disks. Except for the initial setup and configuration, the programs do not require any user interaction. Log files and e-mail messages are used for communication with the user.

The process is controlled via configuration data in the XML format. There is no user interface.

The software is optimized for archiving of user data from a file server. The files are being copied using the mechanisms of the operating system including the access rights, if desired. A file will not be copied if access to the file is denied. This may e.g. happen in the case of database or system files.

FullBackup and IncrementalBackup

CPTec Backup comprises two programs for archiving of data:

• FullBackup is used for archiving of complete drives/paths/shared folders, e.g. for a complete backup created every week. It copies all files. It copies empty folders. It deletes the target folder (incl. DateFolder) if it is present already, e.g. if the backup is started several times on the same day.

• IncrementalBackup only archives data that have changed since the last backup, e.g. for a daily backup created in the evening. It creates folders which are required for the directory structure. It copies files into an already present target folder by overwriting. IncrementalBackup may also be started several times a day. In this case all changes that occur during the day will add up.

Application

Full backup (FullBackup.exe)

• All files and folders are being copied
• The archive bits for the source files are reset in general

Differential backup (IncrementalBackup.exe without reset of archive bit)

• Copies only files and folders whose archive bit is set
• The archive bits for the source files are not reset
• Regular creation of full backups is required additionally

Incremental backup (IncrementalBackup.exe with reset of archive bit)

• Copies only files and folders whose archive bit is set
• The archive bits for the source files are reset
• Regular creation of full backups is required additionally
• Requires less space than a differential backups, but the effort for restoring the data is higher

Terminology

The configuration file contains definitions for sources and for targets.

Source: A source for the backup. The drive/folder/shared folder that is to be copied. Every source is marked by a short and distinct name. As an example, a folder containing the personal data of all users may be called "PRIVATE" oder "USER".

Target: A target for the backup. The drive/folder/shared folder into which the data are to be copied.

SwitchTarget: A special target that will be selected from a list of defined targets. Depending on the contents of the listed "possible" targets, the one will be selected automatically that has not been a backup target for the longest period of time. The date of the last backup in such a target will be determined by checking the comprised DateFolders and not by checking the date and time stamps in the file system.

DateFolder: The date folder. A folder that will be created automatically on the target in order to arrange the individual backups according to the backup date. Using the format "YYMMDD", these folders will be named according to the backup date, e.g. "050907" for September 07, 2005. The date at the start of the backup is relevant for this. The <DayOffset Hours="n" /> command may be used to correct this date with respect to the real system time. The name of this folder will later on be used by the software to determine which DateFolder is to be deleted if the disk space on the target is getting short. When sorting in alphabetical order, this nomenclature makes sure that the backups on the target are also displayed in chronological order.

SourceFolder: The source folder. A folder that will be created on the target inside of the DateFolder for each copied source. The name of the related source is used as the name for this folder.

Backup sequence

Starting the backup

After CPTec Backup has been installed and the configuration for the backup job has been adjusted, you may execute the program (FullBackup or IncrementalBackup).

In general, the task scheduler is used to execute the program on a regular basis. However, if you want to run a quick test, you may also execute the program manually. For this purpose, open the "Command Prompt" window. Change to the installation directory and enter the program name. CPTec Backup starts and executes the steps described in the following.

SwitchTarget

If a target is defined as a SwitchTarget, the target to be used actually will be determined first. The target in the list that has not been a backup target for the longest period of time will be selected. In the case of FullBackup, the <ExistingDateFolder ReuseSwitchTarget="yes/no" /> command can be used to specify if an already used target from the SwitchTarget list may be used again for another run on the same day. In the case of IncrementalBackup, the oldest target is always selected.

DateFolder

A DateFolder is created for each target. If the backup is started for the second time on the same day, the DateFolder may exist already. In this case, FullBackup and IncrementalBackup will react differently:

• IncrementalBackup will copy all modified files into the existing DateFolder. This means that all changes that have been made during the day will add up.
• FullBackup may delete either the entire DateFolder or only the currently affected SourceFolder in the DateFolder before the data are copied again. This behavior can be controlled by means of the <ExistingDateFolder DeleteBySource="yes/no"> command.

SourceFolder

One after the other, all sources are copied into the DateFolder. To this end, a SourceFolder with the name of the source is created for each source, and the data will be copied to this folder. <ArchiveBit Ignore="yes/no" Reset="yes/no" /> can be used to specify if all files or only modified files are copied and if the archive bit of the source files is reset after copying. <Security Copy="yes/no" /> can be used to specify if the access rights for the folders and files have to be copied too.

Automatic cleanup

If the free space on the target falls below the "FreeGB" value during the copy process, the software determines the oldest DateFolder on the target and deletes this folder. Afterwards the copying process is continued. If it is not possible to free enough disk space this way the backup is aborted.

Logging and messaging

During the copy process, two log files will be written into the folder specified with <LogFiles Path="Ordner" />: A "progress log" containing all files that have been copied and a "warning log" containing all files that could not be copied. The names of these log files start with the name of the DateFolder. The current state of the log files is copied into the DateFolder of each completed target.

Configuration errors are displayed in the console and in the event log. All other errors will be reported in the event log and via e-mail, if configured. Start and stop of the backup are also logged in the event log.

If configured, an e-mail containing statistical data and a copy of the warning log will be sent after the backup process has been completed.

Tips for efficient archiving

In general, sources are shared folders. In order to optimize efficiency, CPTec Backup performs the backup process in two steps: First, all sources are copied to the first target. Afterwards, the files are being copied from this target to all the other targets.

The benefits of this method become apparent if a local drive is selected for the first target. In this case, copying to the other targets offers the following advantages:

• Higher copying speed
• Reduced network load
• Reduced load on the source drives or servers
• Data on the different targets will be consistent

Version 1.0

6.1.3.2 Installation

Prerequisites

The following operation systems are supported:

• Windows 2000 with .Net Framework 1.1
• Windows XP with .Net Framework 1.1
• Windows Server 2003

For Windows 2000 and Windows XP, you also need .Net Framework. This software may e.g. be downloaded and installed via "Windows Update" from the Microsoft website. Windows Server 2003 already contains the framework.

If you want to use database logging, you need either Microsoft SQL Server or e.g. Microsoft Access for processing of a Jet database.

Copy the files

In order to install the software, simply copy the "IncrementalBackup" and "FullBackup" folders to the backup server. You may also copy the two versions to different servers because they operate fully independent of each other. The folders contain all the required DLLs.

Configure

After copying, the supplied XML configuration files "IncrementalBackup.conf" and "FullBackup.conf" must be adjusted to suit your specific application. Read the separate chapter "Configuration" for this.

Copy the license

When you acquire a license, you will receive a file named "license.lic". Copy this file into the folders which contain the executable files. You may also run the software without a license file for a limited period of time in order to evaluate the software.

Configure a database (optional)

You may use a database for logging a list of the archived files and also of any problems that may have occurred. This option is currently supported for Microsoft SQL Server and Microsoft Jet (Access).

Data that have been copied may be deleted or overwritten in a subsequent backup run. In this case, the related entries in the database will also be deleted. Nevertheless, the database may grow large. It is recommended that you always keep an eye on the required space.

You do not need separate databases for IncrementalBackup and FullBackup. A database field is used to distinguish between the respective entries.

Microsoft SQL Server

Use Enterprise-Manager to create a new database. You may choose any name, e.g. "backuplog". For this database, execute the supplied SQL script named "backuplog.sql", e.g. by means of Query Analyzer. In the current database, the script will generate a table named "backuplog" with the required indices. You may modify the script if you wish to name the table differently.

For a higher level of security, you may create a separate user account for the backup software on the SQL server. The user requires access rights for the UPDATE and INSERT tables.

The name of the database and of the table as well as the login and the password for the user must be specified in the XML configuration files. Read the separate chapter "Configuration" for this.

Jet

A Jet database is being supplied with the file named "backuplog.mdb". If you want to use it, copy the file onto your server and specify the path in the XML configuration files. Read the separate chapter "Configuration" for this. This database can be processed directly e.g. with Microsoft Access.

Scheduler

After the configuration has proved successful in tests, it is advisable to automate the backup jobs by means of the Task Scheduler. For more information on the Task Scheduler, please refer to the instruction manual for your operating system.

Version 1.0

6.1.3.3 Configuration

The configuration data for FullBackup and IncrementalBackup are stored in two separate XML files: FullBackup.conf and IncrementalBackup.conf. The two configuration files are very similar in design. If a parameter is not valid for both files, it will be pointed out clearly in the following description.

Targets

<Targets>

    <Target Path="I:\" FreeGB="1" />

    <Target Path=" VolumePrefix[Weekly]\backup" Optional="yes" />

    <Target>

        <Switch Path="J:\" FreeGB="5" />

        <Switch Path="K:\" FreeGB="5" />

    </Target>

</Targets>

Specifies the target drives for the backup.

Path

Specifies the target folder/drive. If the drive letter is unknown, you may also use "VolumePrefix[name]". In this case, the first drive whose name starts with "name" will be used. This way it is e.g. possible to access external hard disks whose assigned drive letter is not yet known when configuring the backup. Useful names for the drives are e.g. "Weekly1", "Weekly2" etc. In this case, "VolumePrefix[Weekly]" will access one of these drives (the one that is actually connected).

NOTE: Target folders are not created automatically. They must already be present on the related target drives before starting the backup.

FreeGB

The backup job will keep open the specified amount of disk space. If the disk space falls short of this value, old backup files will be deleted automatically in order to free up disk space. Default: FreeGB="1".

Optional

The Optional="yes" statement is used to specify an optional target. Optional targets are checked for availability. This is especially important for external drives. When a backup is started, all optional targets are checked and missing targets are reported via e-mail and warning log. Immediately before copying to an optional target, this check is performed again. If a target is missing, this event will be logged. The backup process continues. Default: Optional="no".

Switch

A "target" node can also be specified without attributes, but with "switch" child nodes instead. In this case, the "switch" nodes can have the same attributes as a single "target" attribute. When writing to these "switch" targets, the one will be used that has not been a backup target for the longest period of time. The names of the "date folders" located in potential target paths are used for selecting the actual target path. Date and time stamps in the file system are not relevant for this.

Sources

<Sources>

    <Source Path="D:\userdata" Name="DATA"/>

    <Source Path="F:\" Name="DriveF" />

</Sources>

It is possible to specify any number of sources for the backup.

Path

Specifies the folders or shared folders to be archived.

Name

A directory with this name will be created in the DateFolder on the target drive. The folders or shared folders which have been specified using "Path" will then be archived in this directory.

LogFiles

<LogFiles Path="f:\" />

Path

Two log files will be stored under this path: [DATE]_progress.log and [DATE]_warning.log. The date is inserted in the "YYMMDD" format which means that a chronological order will be obtained when sorting alphabetically. The progress of the backup run is stored in the progress log file. Information on sources and target drives is written and all copied files are listed. A block with statistical data is inserted at the end of each source. Files that could not be copied are listed in the warning log.

The contents of the warning log and statistical information are being sent to the e-mail address specified under SmtpMail. Error messages, e.g. if the backup is aborted, are stored in the event log and are also sent to the SmtpMail, if possible.

NOTE: The folder for the log files is not created automatically. It must already be present on the related drive before starting the backup.

ArchiveBit

<ArchiveBit Ignore="yes" Reset="no" />

Specifies how to handle the archive bit of the source files.

Ignore

If Ignore="yes" is selected, IncrementalBackup will copy all files. If Ignore="no" is selected, only files whose archive bit is set will be copied. FullBackup will always copy all files. (For IncrementalBackup only.)

Reset

If Reset="yes" is selected, the archive bit of the source file will be reset after copying successfully. If Reset="no" is selected, the previous state will be kept.

DayOffset

<DayOffset Hours="8" />

Hours

Specifies how a backup runs is assigned to a day. In order to determine the date for the backup, the specified number of hours will be subtracted from the current time. If Hours="8" is selected, a backup that is started before 8 o'clock a.m. will be written to a folder with the date of the previous day. The log file will also be stored using the modified date. The date at the beginning of the backup run will be used for the entire run.

Security

<Security Copy="yes" />

Copy

Specifies how to handle the security settings at the target. If Copy="yes" is selected, the security settings (access rights) for the copied files will also be copied.

Priority

<Priority Value="Normal" />

Value

Specifies the priority of the backup task. Value is the task priority: Normal, Low, Lowest.

Sleep

<Sleep Milliseconds="0" />

Milliseconds

Specifies the idle time after copying a file. After each copied file, the process will "sleep" for the specified number of milliseconds.

ExistingDateFolder (FullBackup only)

<ExistingDateFolder DeleteBySource="no" ReuseSwitchTarget="yes" />

Specifies the behavior of the software if folders to be copied/created are already present on the target. (For FullBackup only.) 

DeleteBySource

DeleteBySource="no": If the target already contains a folder for the current date, the contens of the folder will be deleted completely.

DeleteBySource="yes": If the target already contains a folder for the current date and the current source (specified in <Source Name=…>), only this source directory will be deleted.

This function allows you to archive different sources, one after the other, into a common target directory without any mutual effects.

ReuseSwitchTarget

ReuseSwitchTarget="no": The switch logic strictly adheres to the date of the last backup: If the backup is started twice in succession, you end up with two switch targets containing a directory with the current date. 

ReuseSwitchTarget="yes": If one of the switch targets already contains a directory with the current date, this one will be used again.

DatabaseLogging (optional)

Microsoft SQL Server

<DatabaseLogging>

    <Type Name="MSSql" />

    <Connection Name="server=(local);uid=sa;pwd=secret;database=backuplog;" />

    <Table Name="backuplog" />

</DatabaseLogging>

Jet (Access)

<DatabaseLogging>

    <Type Name="Jet" />

    <Connection Name="Provider=Microsoft.Jet.OLEDB.4.0;data source=C:\Backup\Jet\backuplog.mdb" />

    <Table Name="backuplog" />

</DatabaseLogging>

Specifies a database. The log will also be written to this database.

Type Name 

Type of the used database. Allowed settings are: MSSql, Odbc, OleDb and Jet.

Connection Name

Connection string for the database. Syntax depends on the used database type.

Table Name

Table within the database.

NOTE: These parameters are optional. If a database is not available or if you do not wish to write the logs to a database, delete all related entries from the configuration file.

SmtpMail

<SmtpMail>

    <Server Name="smtp.provider.de" />

    <To Name="bdmin@company.de" />

    <From Name="backupserver@company.de" />

</SmtpMail>

Specifies the SMTP server and adresses for the e-mail status report.

Server Name

Name of the SMTP server.

To Name

Recipient of the e-mail.

From Name

Sender of the e-mail (many SMTP server request an existing e-mail address for the sender).

NOTE: These parameters are optional. If an SMTP server is not available or if you do not wish to send the status reports via e-mail, delete all related entries from the configuration file.

Configuration Examples

In order to illustrate the concept and the use of the individual options, you find our own configuration and the ideas behind it in the following. For clarity, we have added comments to the XML file in italic lettering.

Fullbackup.conf

<?xml version="1.0" encoding="utf-8"?>

<Configuration>

    <Targets>

        <Target>

            <Switch Path="g:\" FreeGB="1" />

            <Switch Path="h:\" FreeGB="1" />

        </Target>

        <Target Path="VolumePrefix[WeeklyExt]" FreeGB="1" Optional="yes" />

    </Targets>

<!--

Backups are being written to the internal drives "g:\" and "h:\" by turns. In addition, a backup is always written to an external hard disk whose volume name starts with "WeeklyExt". We currently use 5 external hard disks labeled "WeeklyExt1" through "WeeklyExt5" which are used consecutively. The external drives are normally stored outside of the office in order to cover the risk of fire and the like. The additional copies on the internal disks give us more redundancy, and we can restore the data faster during normal operation. In case that no external drive has been connected by mistake, the Optional="yes" statement makes sure that the backup will still be performed for the internal drives.

-->

    <Sources>

        <Source Path="\\server3\exchangefiles" Name="exchange" />

        <Source Path="\\server3\systemstates" Name="systemstate" />

        <Source Path="\\server3\publicfiles" Name="pub" />

        <Source Path="\\server3\privatefiles" Name="priv" />

    </Sources>

<!--

These are the data to be saved. Special data that cannot be saved as files during operation are "exported" automatically in our system and placed in special shared folders. In the above example, this applies to the sources named "exchangefiles" and "systemstates" which contain backups of the system states for all workplace PCs and for one exchange server.

-->

    <LogFiles Path="c:\Backup\Full\Log" />

<!--

This is the path for the log files.

-->

    <ArchiveBit Reset="yes" />

<!--

The archive bit of the original files will be reset after copying. This way, the next run of the daily IncrementalBackup will only copy files that have been modified since the last weekly FullBackup.

-->

    <DayOffset Hours="10" />

<!--

If the backup run should have failed for some reason, it may be repeated until 10:00am on the following day. In this case, the date of the previous day will still be used for storing the backup.

-->

    <Security Copy="yes" />

<!--

The security settings for the files are also being copied.

-->

    <Priority Value="Low" />

<!--

The backup process is started with a low priority. As a result, compression is performed while copying in cases where compression is activated for a target drive. This setting is important because the maximum disk capacity cannot be utilized otherwise.

-->

    <Sleep Milliseconds="0" />

<!--

No other jobs are running on our backup server. For this reason, it is not necessary to reduce the load.

-->

    <ExistingDateFolder DeleteBySource="yes" ReuseSwitchTarget="yes" />

<!--

The "ReuseSwitchTarget" option makes sure that the data will be written to the same target drive/directory. The "DeleteBySource" option makes sure that each source will be deleted individually before copying, and not the entire target directory. This may save time because sources which have been copied successfully will be preserved.

-->

    <DatabaseLogging>

        <Type Name="MSSql" />

        <Connection Name="server=(local);
        uid=user;pwd=topsecret;database=backuplog;" />

        <Table Name="backuplog" />

    </DatabaseLogging>

<!--

Information on the archived data are also written to an MS SQL database.

-->

    <SmtpMail>

        <Server Name="smtp.cptec.org" />

        <To Name="name1@cptec.org;name2@cptec.org;name3@cptec.org" />

        <From Name="backup_server2@cptec.org" />

    </SmtpMail>

<!--

Reports on the backup run are being sent to the e-mail recipients specified here.

-->

</Configuration>

In the following, only parts that are different from Fullbackup.conf will be commented.

IncrementalBackup.conf

<?xml version="1.0" encoding="utf-8"?>

<Configuration>

    <Targets>

        <Target>

            <Switch Path="g:\" FreeGB="1" />

            <Switch Path="h:\" FreeGB="1" />

        </Target>

        <Target Path="VolumePrefix[DailyExt]" FreeGB="1" Optional="yes" />

    </Targets>

<!--

Backups are being written to the internal drives "e:\" and "f:\" by turns. In addition, a backup is always written to an external hard disk whose volume name starts with "DailyExt". We currently use 2 external hard disks labeled "DailyExt1" and "DailyExt2" which are used consecutively. The external drives are normally stored outside of the office in order to cover the risk of fire and the like. The additional copies on the internal disks give us more redundancy, and we can restore the data faster during normal operation. In case that no external drive has been connected by mistake, the Optional="yes" statement makes sure that the backup will still be performed for the internal drives.

-->

    <Sources>

        <Source Path="\\server3\exchangefiles" Name="exchange" />

        <Source Path="\\server3\publicfiles" Name="pub" />

        <Source Path="\\server3\privatefiles" Name="priv" />

    </Sources>

    <LogFiles Path="c:\Backup\Incremental\Log" />

    <ArchiveBit Ignore="no" Reset="yes" />

<!--

Only modified files (archive bit set) will be copied. After copying a file, its archive bit will be reset.

-->

    <DayOffset Hours="10" />

<!--

If the backup run should have failed for some reason, it may be repeated until 10:00am on the following day. The data will be written to the same target drive/directory. Files which have been modified in the meantime will be copied. This will overwrite the archived version of the previous day. Files which habe already been copied and have not been modified since then will not be copied again. They are already present on the target drive.

-->

    <Security Copy="yes" />

    <Priority Value="Low" />

    <Sleep Milliseconds="0" />

    <DatabaseLogging>

        <Type Name="MSSql" />

        <Connection Name="server=(local);
        uid=user;pwd=topsecret;database=backuplog;" />

        <Table Name="backuplog" />

    </DatabaseLogging>

    <SmtpMail>

        <Server Name="smtp.cptec.org" />

        <To Name="name1@cptec.org;name2@cptec.org;name3@cptec.org" />

        <From Name="backup_server2@cptec.org" />

    </SmtpMail>

</Configuration>

Testing the Configuration

The command line parameter "test" may be used to test the configuration.

The following tests will be performed:

• Does the configuration file contain valid XML code?
• Are all specified paths available?
• Can a connection to the database be established?
• Does sending of e-mails work properly?

No data will be saved or logged during the test. Errors are displayed directly at the command line and they will also be reported via e-mail, if possible.

Version 1.0

6.1.4 CPTec Backup Source Code Documentation

• Class library (HTML)[1]
• Class library (CHM file, 400 kb)[2]

External links:

6.1.6 Backup Demo Version

Operating systems

Please check the list of supported operating systems before downloading the file:

• Windows 2000 with .Net Framework 1.1
• Windows XP with .Net Framework 1.1
• Windows Server 2003

.Net Framework 1.1 may for example be installed via Windows Update.

Time limit

We will release a new demo version every second month. Each new demo version will run for the next 4 months. This will give you at least 2 months of time for testing.
The backup software allows automatic deletion of outdated backup files. This function is also limited to the 4 months mentioned above. Backup files created outside of this time limit will be ignored.

Removing the time limit

If you would like to continue using our backup software after the trial period, you may purchase a license at any time. In this case, you will receive a license file via e-mail. Simply copy this file into the directory which contains the backup software. This will remove the time limit.

Job License

For only 39 EUR incl. 19% sales tax, you will receive a license without any time limit: Purchase (=> 6.1.7.1)

Source Code License

For only 116 EUR incl. 19% sales tax, you will receive a license without any time limit, and also the complete and fully commented source code: Purchase (=> 6.1.7.2)

Installing

There is no need to install the backup software. All files that are required for operation are stored in a Zip file.
Simply unpack the downloaded Zip file into a local directory. Then read the enclosed "readme.txt" file for further steps required to configure the software.

External links:

6.1.7 CPTec Backup Licenses

Job License

One Job License is 39 EUR incl. 19% sales tax.

The software consists of a full backup component ("FullBackup") and an incremental backup component ("IncrementalBackup"). Both components can be configured individually. Any number of source directories may be specified. The backup jobs may be started as often as necessary (no limit) and they may run on different computers.
However, only one configuration for the full backup and one configuration for the incremental backup is allowed at a time for each license. This means, only one FullBackup job and one IncrementalBackup job. more... (=> 6.1.7.1)

Source Code License

One Source Code License is 116 EUR incl. 19% sales tax.

Contains one Job License. In addition, you receive the complete and fully commented source code. You may modify and recompile the source code as you like. more... (=> 6.1.7.2)

6.1.7.1 Backup Job License

Order[1]

Your order will be processed over a secure connection.

Price

One Job License is 39 EUR incl. 19% sales tax.

Scope

The software consists of a full backup component ("FullBackup") and an incremental backup component ("IncrementalBackup"). Both components can be configured individually. Any number of source directories may be specified. The backup jobs may be started as often as necessary (no limit) and they may run on different computers.
However, only one configuration for the full backup and one configuration for the incremental backup is allowed at a time for each license. This means, only one FullBackup job and one IncrementalBackup job.

Support

We provide free support in our forum[2].

Updates

The license is valid for all 1.x versions of the software. All updates are available as free downloads. Information on planned new features can be found here.

How to proceed

You may download the latest demo version (=> 6.1.6). If you purchase a Job License, you will receive a license file via e-mail. Simply copy the license file into the directory which contains the backup software. This will remove the time limit.

External links:

6.1.7.2 CPTec Backup Source Code License

Order[1]

Your order will be processed over a secure connection.

Price

One Source Code License is 116 EUR incl. 19% sales tax.

Scope

Contains one Job License:
The software consists of a full backup component ("FullBackup") and an incremental backup component ("IncrementalBackup"). Both components can be configured individually. Any number of source directories may be specified. The backup jobs may be started as often as necessary (no limit) and they may run on different computers.
However, only one configuration for the full backup and one configuration for the incremental backup is allowed at a time for each license. This means, only one FullBackup job and one IncrementalBackup job.

In addition, you receive the complete and fully commented source code. You may modify and recompile the source code as you like.
The backup software has been implemented as a .Net 1.1 application using Microsoft Visual Studio 2003 in C#. You receive the complete project data files which can be opened and compiled right away. There are no external dependences.

However, this is not an unlimited license. If the software is used for more than one job, additional Job Licenses (=> 6.1.7.1) must be purchased.

Support

We provide free support in our forum[2].

Updates

The license is valid for all 1.x versions of the software. All updates are available as free downloads. New versions of the source code will be distributed via e-mail. Information on planned new features can be found here.

How to proceed

You may download the latest demo version (=> 6.1.6). If you purchase a Source Code License, you will receive a license file and a Zip file with the source code via e-mail. Simply copy the license file into the directory which contains the backup software. This will remove the time limit.

External links: