Re: Backup job fails to complete and SQLServer hangs
- From: "Claus" <cjobes@xxxxxxxxxxxxx>
- Date: Wed, 6 Feb 2008 21:53:44 -0500
Are you sure you excluded all of them? Did you check under the SQL program
files on the C drive?
--
Claus
"countryboy75" <countryboy75@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:99F23DC6-41ED-47A5-B1A2-722DF4A75DAC@xxxxxxxxxxxxxxxx
Hi Claus
I already do exclude the SQL data files. This is the Backup job that runs:
C:\
D:\
D:\MSSQL\ /Exclude
JET OFFICESERVER\Microsoft Information Store\First Storage Group\
Cheers
"Claus" wrote:
I always discourage people to even try running backups that include
active
SQL DBs. Exclude those folders from your general backup and run the SQL
backups from within the SQL Enterprise Manager or Studio (depending on
your
version). You will be much happier and the backups will be actually
useable
for restores.
The build in SBS backup is great and very reliable but it has it's
limitations.
--
Claus
"countryboy75" <countryboy75@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:18800014-2464-49BF-8BA5-12948BD5E14B@xxxxxxxxxxxxxxxx
Hi
I have a Widnows SBS 2003 server running SQL. Every night I run two
backups
- the first backups up everything but the SystemsState, the second
backs
up
the SystemState alone.
Every second night or so the first NTBackup fails to finish (the
process
is
still running in the morning), the second backup attempts to start but
fails
with the following log:
Volume shadow copy creation: Attempt 1.
Timeout before function completed
Error returned while creating the volume shadow copy:0xffffffff.
Error returned while creating the volume shadow copy:ffffffff
Aborting Backup.
----------------------
The operation did not successfully complete.
The problem is that SqlServer stops responding at some stage during or
before the backup and can only be rectified by rebooting the server.
The SqlServer error log has the following lines at the end:
2008-02-07 00:30:23.43 spid53 Database master: IO is frozen for
snapshot
2008-02-07 00:30:23.52 spid54 Database model: IO is frozen for
snapshot
2008-02-07 00:30:23.61 spid55 Database msdb: IO is frozen for
snapshot
2008-02-07 00:30:23.69 spid56 Database pubs: IO is frozen for
snapshot
2008-02-07 00:30:23.79 spid59 Database Northwind: IO is frozen for
snapshot
2008-02-07 00:30:23.88 spid58 Database WRAP_Temp: IO is frozen for
snapshot
2008-02-07 00:30:23.96 spid61 Database wrap_devel: IO is frozen for
snapshot
2008-02-07 00:30:24.04 spid57 Database ClientTracker: IO is frozen
for
snapshot
2008-02-07 00:30:24.21 spid60 Database wrap: IO is frozen for
snapshot
2008-02-07 00:30:24.38 spid62 Database Archive: IO is frozen for
snapshot
2008-02-07 08:11:15.50 server SQL Server terminating because of
system
shutdown.
2008-02-07 08:11:15.50 server LogEvent: Failed to report the current
event. Operating system error = 31(A device attached to the system is
not
functioning.).
The stuff at 08:11 am is me rebooting the server. So to me it seems
that
the
backup job is locking the files but then not releasing them? Does that
sounds
right?
Any help would be great.
.
- References:
- Backup job fails to complete and SQLServer hangs
- From: countryboy75
- Re: Backup job fails to complete and SQLServer hangs
- From: Claus
- Re: Backup job fails to complete and SQLServer hangs
- From: countryboy75
- Backup job fails to complete and SQLServer hangs
- Prev by Date: Re: Permission Settings for Shares
- Next by Date: Re: Failed intranet/sharepoint installation
- Previous by thread: Re: Backup job fails to complete and SQLServer hangs
- Next by thread: Re: Backup job fails to complete and SQLServer hangs
- Index(es):
Relevant Pages
|
