Hi,

I have a customer box - SBS2003. The overnight backup is just failing, 
the logs say nothing. A manual backup works fine. The entry in the log 
is below:

"11/02/2010 23:30
-------------------------------
Date: 11/02/2010
Time: 23:30
User: SYSTEM
-------------------------------

Backup Runner started.
Launching NTBackup: ntbackup.exe backup "@C:\Program Files\Microsoft 
Windows Small Business Server\Backup\Small Business Backup Script.bks" 
/d "SBS Backup created on 11/02/2010 at 23:30" /v:yes /r:no /rs:no 
/hc:off /m normal /j "Small Business Server Backup Job" /l:s /f 
"F:\Backup Files\Small Business Server Backup (02).bkf" /UM
NTBackup finished the backup with errors.

For more information about failed backups, see the article on 
troubleshooting your backup at the following Web page: 
http://go.microsoft.com/fwlink/?LinkId=18414

Backup ended at 11 February 2010 23:30
Backup Runner finished.
"

In event log there are just wo entries, one the backup started followed by:

eent id 5634:
One or more components of Small Business Server Backup failed. For more 
information, click Backup in Server Management, and view the log files.


This is all that's written.

Any ideas, the logs give nothing to go on.

Thanks

Simon

Hmmmm.....

Nothing in the report, and nothing in the logs.  Running the SBS Backup script 
manually works correctly but the same job scheduled does not work.

What is the destination of the backup job?  We mostly see this issue with 
backups to tape drives.

If tape, look for articles in this list or archived, or in MS KB that discuss 
the concept of "sleep" and reseting rsm.exe so it knows the tape has changed.

Here is one from an older post... sorry I don't know who to give credit:

<snip>
I've had a similar problem and after reading the thread it really sounds
like if you don't have any hidden devices in the RSM database, maybe you
need to take another look at 'this page'

(http://support.microsoft.com/?kbid=267574) 

already referenced 'here'

(http://tinyurl.com/2nqndz). 

My experience is with ntbackup but apparently any backup software using
RSM will be affected. When you change a tape without ejecting via
software (ie by just pressing eject on the drive) the next automatic
backup will fail. Backups run interactively will work because RSM
inventories the drive when the backup is run interactively.

My preferred solution with ntbackup is to refresh RSM before the backup
command, and eject the tape afterward to ensure RSM knows the tape has
changed. Here's an simple ntbackup batch file example:

REM Refresh removable storage manager so it knows the tape has
changed:

rsm.exe refresh /lf"Hewlett Packard DDS4 USB Drive"
C:\Bat\sleep.exe 30

REM Next, run the backup:
C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and
Settings\Administrator\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data\Daily Backup.bks" /d "Daily
Backup" /v:no /r:no /rs:no /hc:on /snap:on /m normal /j "Daily Backup"
/l:s /p "4mm DDS" /um

REM Eject tape cartridge:
REM rsm eject /lf"Hewlett Packard DDS4 USB drive" /astart

As long as the tapes are initialized as part of the drive's pool in
RSM, this works pretty consistently. Hope this helps.
<end snip>

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> Hi,
> 
> I have a customer box - SBS2003. The overnight backup is just failing,
> the logs say nothing. A manual backup works fine. The entry in the log
> is below:
> 
> "11/02/2010 23:30
> -------------------------------
> Date: 11/02/2010
> Time: 23:30
> User: SYSTEM
> -------------------------------
> Backup Runner started.
> Launching NTBackup: ntbackup.exe backup "@C:\Program Files\Microsoft
> Windows Small Business Server\Backup\Small Business Backup Script.bks"
> /d "SBS Backup created on 11/02/2010 at 23:30" /v:yes /r:no /rs:no
> /hc:off /m normal /j "Small Business Server Backup Job" /l:s /f
> "F:\Backup Files\Small Business Server Backup (02).bkf" /UM
> NTBackup finished the backup with errors.
> For more information about failed backups, see the article on
> troubleshooting your backup at the following Web page:
> http://go.microsoft.com/fwlink/?LinkId=18414
> 
> Backup ended at 11 February 2010 23:30
> Backup Runner finished.
> "
> In event log there are just wo entries, one the backup started
> followed by:
> 
> eent id 5634:
> One or more components of Small Business Server Backup failed. For
> more
> information, click Backup in Server Management, and view the log
> files.
> This is all that's written.
> 
> Any ideas, the logs give nothing to go on.
> 
> Thanks
> 
> Simon
> 

Hi Larry,

thanks for the reply, this server is backing up to an external usb drive .
Thanks
Simon

Larry Struckmeyer[SBS-MVP] wrote:
> Hmmmm.....
> 
> Nothing in the report, and nothing in the logs.  Running the SBS Backup 
> script manually works correctly but the same job scheduled does not work.
> 
> What is the destination of the backup job?  We mostly see this issue 
> with backups to tape drives.
> 
> If tape, look for articles in this list or archived, or in MS KB that 
> discuss the concept of "sleep" and reseting rsm.exe so it knows the tape 
> has changed.
> 
> Here is one from an older post... sorry I don't know who to give credit:
> 
> <snip>
> I've had a similar problem and after reading the thread it really sounds
> like if you don't have any hidden devices in the RSM database, maybe you
> need to take another look at 'this page'
> 
> (http://support.microsoft.com/?kbid=267574)
> already referenced 'here'
> 
> (http://tinyurl.com/2nqndz).
> My experience is with ntbackup but apparently any backup software using
> RSM will be affected. When you change a tape without ejecting via
> software (ie by just pressing eject on the drive) the next automatic
> backup will fail. Backups run interactively will work because RSM
> inventories the drive when the backup is run interactively.
> 
> My preferred solution with ntbackup is to refresh RSM before the backup
> command, and eject the tape afterward to ensure RSM knows the tape has
> changed. Here's an simple ntbackup batch file example:
> 
> REM Refresh removable storage manager so it knows the tape has
> changed:
> 
> rsm.exe refresh /lf"Hewlett Packard DDS4 USB Drive"
> C:\Bat\sleep.exe 30
> 
> REM Next, run the backup:
> C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and
> Settings\Administrator\Local Settings\Application
> Data\Microsoft\Windows NT\NTBackup\data\Daily Backup.bks" /d "Daily
> Backup" /v:no /r:no /rs:no /hc:on /snap:on /m normal /j "Daily Backup"
> /l:s /p "4mm DDS" /um
> 
> REM Eject tape cartridge:
> REM rsm eject /lf"Hewlett Packard DDS4 USB drive" /astart
> 
> As long as the tapes are initialized as part of the drive's pool in
> RSM, this works pretty consistently. Hope this helps.
> <end snip>
> 
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
> 
> 
>> Hi,
>>
>> I have a customer box - SBS2003. The overnight backup is just failing,
>> the logs say nothing. A manual backup works fine. The entry in the log
>> is below:
>>
>> "11/02/2010 23:30
>> -------------------------------
>> Date: 11/02/2010
>> Time: 23:30
>> User: SYSTEM
>> -------------------------------
>> Backup Runner started.
>> Launching NTBackup: ntbackup.exe backup "@C:\Program Files\Microsoft
>> Windows Small Business Server\Backup\Small Business Backup Script.bks"
>> /d "SBS Backup created on 11/02/2010 at 23:30" /v:yes /r:no /rs:no
>> /hc:off /m normal /j "Small Business Server Backup Job" /l:s /f
>> "F:\Backup Files\Small Business Server Backup (02).bkf" /UM
>> NTBackup finished the backup with errors.
>> For more information about failed backups, see the article on
>> troubleshooting your backup at the following Web page:
>> http://go.microsoft.com/fwlink/?LinkId=18414
>>
>> Backup ended at 11 February 2010 23:30
>> Backup Runner finished.
>> "
>> In event log there are just wo entries, one the backup started
>> followed by:
>>
>> eent id 5634:
>> One or more components of Small Business Server Backup failed. For
>> more
>> information, click Backup in Server Management, and view the log
>> files.
>> This is all that's written.
>>
>> Any ideas, the logs give nothing to go on.
>>
>> Thanks
>>
>> Simon
>>
> 
>