1. Since my incremental backup sizes are way too small compared to the overall size of my outlook.pst file, I am assuming that SP must be treating the outlook.pst file as a special case and somehow only backing up the new emails that have occured since last backup instead of backing up the entire changed file each time?

 2. If I use the monthly template with full backups scheduled on the 1st and 15th of the month at 1am and incremental backups every day of the week also at 1am, then on the 1st or the 15th will the 1am full backup keep the 1am incremental of the same day from also running?

 3. When Hard Drive #1 has 3 partitions C:, D:, and E: and I create a backup of only the C: partition, besides the data from C:, does this backup file also contain the complete partitioning structure for Hard Drive #1 or only information about the C: partition structure? 

4. Testing my Recovery CD, I am able to access local hard drives including external USB drives, and I am able to see my Buffalo TeraStation NAS on the network, but all of the User and Admin Log-in ID's and Passwords for the TeraStation NAS are rejected.  The Buffalo TeraStation does not require any special drivers to be accessed from Windows so what could the problem be?

Thanks in advance for your assistance.

 Chris  

SP uses a sector-based, rather than file-based, backup. If you have incremental backups, then SP will track and backup only the sectors that have changed since the last backup.

I believe the Full Backup will take precedence over any incremental backup scheduled to occur at the same time.

If you backup Partition C, then the backup will only contain partition C. If you restore that backup to a blank disk you will only restore that partition. If the partition you back up is a system volume (i.e. a bootable partition containing WinXP etc.) then the registry of that system volume will contain references to the other partitions. However, that will have little or no impact on the operation of the restored partition. If the C Partition is not only a system partition, but also the main boot partition, then it will also contain the bootloaders (ntldr/boot.ini for WinXP, BCD for Vista). If you have a mult-boot PC, then you will also have entries in the boot.ini/BCD that will refer to the other bootable partitions. Again, this shouldn't affect the operation of any restored C partition.

Chris,

 1. Since my incremental backup sizes are way too small compared to the overall size of my outlook.pst file, I am assuming that SP must be treating the outlook.pst file as a special case and somehow only backing up the new emails that have occured since last backup instead of backing up the entire changed file each time?

Actually, ShadowProtect does not look at individual files or emails at all.  It watches for changes to disk sectors and then backs up those sectors that have been changed.  But you've got the right idea.  :)

  2. If I use the monthly template with full backups scheduled on the 1st and 15th of the month at 1am and incremental backups every day of the week also at 1am, then on the 1st or the 15th will the 1am full backup keep the 1am incremental of the same day from also running?

Yes, it would prevent the incremental backup from running, and would run the full backup instead.  So if you want to have an incremental backup on the same days that the full backups run, you should schedule them for a different time.

  3. When Hard Drive #1 has 3 partitions C:, D:, and E: and I create a backup of only the C: partition, besides the data from C:, does this backup file also contain the complete partitioning structure for Hard Drive #1 or only information about the C: partition structure?

It contains only information about the C: partition.  All of our backups are of individual volumes, so even if you selected all three partitions, it would create three separate backup image files, one for each volume.

 4. Testing my Recovery CD, I am able to access local hard drives including external USB drives, and I am able to see my Buffalo TeraStation NAS on the network, but all of the User and Admin Log-in ID's and Passwords for the TeraStation NAS are rejected.  The Buffalo TeraStation does not require any special drivers to be accessed from Windows so what could the problem be?

These kinds of problems usually turn out to be either a permissions issue, or the user credentials are not being entered properly.  First, make sure you are entering everything just right.  You can hover your mouse over the path and username text boxes to see examples of how these should be entered.  You might also try using the IP address of the NAS instead of its name. I suppose it could also be some kind of security issue, like a firewall, if you have anything like that in place.