SBS 2008 Backup problem

[Rodopi]

I am totally new to microsoft server operating systems and have encountered a problem on our SBS 2008 server Backup.
Can anyone help please?

My backup is setup to secure my C: & D: volumes. The D: volume holding our user and application data.
As a backup device we are using a 60GB hard disc.
This was all working fine until our D: volume data population grew. We switched from full backup to incremental backup and this worked for a while then failed again.
there is only 15Gb of free space on the backup volume so we added another hard disc and reformatted using the Quick format utility.
We successfully added this to the sbsbackup service and rescheduled a backup.
This failed with:
"One of the backup files could not be created."
on inspecting the backup log we found the following:

+ System

- Provider

[ Name] Microsoft-Windows-Backup
[ Guid] {1db28f2e-8f80-4027-8c5a-a11f7f10f62d}

EventID 14

Version 0

Level 4

Task 0

Opcode 2

Keywords 0x4000000000000000

- TimeCreated

[ SystemTime] 2009-03-03T21:09:51.503Z

EventRecordID 149

Correlation

- Execution

[ ProcessID] 7248
[ ThreadID] 3176

Channel Microsoft-Windows-Backup

Computer ENW-EX02.enwltdprojects.local

- Security

[ UserID] S-1-5-18


- EventData

BackupTemplateID {DA1DB0A2-6FAE-442F-A35A-4A64EC6FEC8C}
HRESULT 2155348010
BackupState 12
BackupTarget Backup SBS2008 1st
NumOfVolumes 2
BackupTime 2009-03-03T21:00:02.306Z
HRESULT 2155348010
VolumesInfo <VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="14" HResult="0"
DetailedHResult="0" PreviousState="9" DataTransferred="27024097280" NumUnreadableBytes="0"

TotalSize="27024097280" Flags="2" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" SSBVhdSize="0"/>
<VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="12" HResult="-2139619286" DetailedHResult="-2147024784"
PreviousState="9" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" Flags="2" SSBTotalNoOfFiles="0"

SSBTotalSizeOnDisk="0" SSBVhdSize="0"/></VolumeInfo>
DetailedHRESULT 0
SourceSnapStartTime 2009-03-03T21:00:02.259Z
SourceSnapEndTime 2009-03-03T21:00:30.447Z
PrepareBackupStartTime <TimesList><Time Time="2009-03-03T21:04:44.452Z" /><Time Time="2009-03-03T21:09:43.956Z"
/></TimesList>
PrepareBackupEndTime <TimesList><Time Time="2009-03-03T21:04:48.343Z" /><Time Time="2009-03-03T21:09:43.987Z"
/></TimesList>
BackupWriteStartTime <TimesList><Time Time="2009-03-03T21:04:48.624Z" /><Time Time="2009-03-03T21:09:43.987Z"
/></TimesList>
BackupWriteEndTime <TimesList><Time Time="2009-03-03T21:09:43.956Z" /><Time Time="2009-03-03T21:09:44.003Z"
/></TimesList>
TargetSnapStartTime 1601-01-01T00:00:00.000Z
TargetSnapEndTime 1601-01-01T00:00:00.000Z
DVDFormatStartTime <TimesList></TimesList>
DVDFormatEndTime <TimesList></TimesList>
MediaVerifyStartTime <TimesList></TimesList>
MediaVerifyEndTime <TimesList></TimesList>
BackupPreviousState 9
ComponentStatus <ComponentStatus><ComponentStatusItem Name="250be69f-8739-4a92-900f-94bc4507cec3"
LogicalPath="Microsoft Exchange Server\Microsoft Information Store\ENW-EX02" AppId="Exchange" WriterId="{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}" ConsistencyCheckResult="0" ConsistencyCheckResultDetailed="0"/><ComponentStatusItem Name="65406f31-d2ba-4c7c-939c-f926bc4fb931" LogicalPath="Microsoft Exchange Server\Microsoft Information Store\ENW-EX02" AppId="Exchange" WriterId="{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}" ConsistencyCheckResult="0" ConsistencyCheckResultDetailed="0"/></ComponentStatus>
SSBEnumerateStartTime 1601-01-01T00:00:00.000Z
SSBEnumerateEndTime 1601-01-01T00:00:00.000Z
SSBVhdCreationStartTime 1601-01-01T00:00:00.000Z
SSBVhdCreationEndTime 1601-01-01T00:00:00.000Z
SSBBackupStartTime 1601-01-01T00:00:00.000Z
SSBBackupEndTime 1601-01-01T00:00:00.000Z
SystemStateBackup false

This means nothing to me and I have searched the internet using the failure codes present in log above.

I really don't know where to go from here, if anyone can point me in the right direction I would be eternally grateful.

Best Regards
Rodopi.

 

[markdmac]

Looks like you have a problem with the Exchange Writer interacting with VSS. (a common issue)

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then double-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. Double-click the Disable Exchange Writer value.
4. In the Value data text box, change the value from 1 to 0, and then click OK.
5. Quit Registry Editor.
6. Click Start, point to Administrative Tools, and then click Services.
7. Stop and then restart the Microsoft Exchange Information Store service.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Rodopi]

Thanks for your response Mark.
I'll give that a try

Regards
Rodopi

 

[ShackDaddy]

Mark, it doesn't seem like that would be the issue if it worked earlier with a different disk.

Rodopi, what you should know about native SBS 2008 backup is that by default it always and only does incrementals after an initial full. As far as I understand it, you can't set it up to do a full every night. How did you go about doing that?

If you use the native SBS 2008 backup, every time you add a new drive to the Backup Storage system, it first does a full backup to it and from then on it only does incrementals. If you remove that drive on a Friday and bring it back a week later, the next incremental covers a week's time, even if you had a second drive in place during the intervening week. And it automatically manages the number of snapshots on the drive for you, deleting the older ones as needed so that you wouldn't normally run out of room if your drive is 50% larger than the data you are protecting. You just wouldn't have as many restore points to go back to.

Once you've dedicated a disk to use for backup, you can't use that disk for anything else, and the system will format that disk for itself and the disk won't show up as a drive letter on your server anymore.

Have you tried unassociating the new disk from your backup system and then adding it in again fresh, allowing it to reinitialize the disk and see if the issue goes away. Or add a separate fresh disk to the system. There's no need to format any disk you add, since the system will always reformat it anyway when it gets added to the backup rotation.

And also, FYI, the "backup rotation" is arbitrary: you can feed the server disks in any order and it will still write a new incremental that goes off of the last incremental that was created on that disk. So if you took one disk away for a year, the next incremental would be VERY big when it was put back into rotation.

Hope that clarifies some things.

Dave Shackelford
ThirdTier.net