Backup craches server when using WITH INIT on SQL 2000

Hi
When creating the log ship maintenance plan, the first thing it does is
initiate a backup using:-
BACKUP DATABASE [ActiveBank] TO DISK =
N'\\Uatsql01\LogShipSend1\ActiveBank_logshipping_i nit.bak' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
When it gets around 10% through, the system blue screens. Even if we do this
manually, the same thing happens. Now if we try
BACKUP DATABASE [ActiveBank] TO DISK =
N'G:\LogShipSend\ActiveBank230507.bak' WITH NOINIT , NOUNLOAD , NAME =
N'ActiveBank backup', NOSKIP , STATS = 10, NOFORMAT
The backup works.
Thanks for any help in advance
Paul
My first guess is that you have a network driver that is behaving badly.
This could be due to either a driver flaw or hardware problem. See if you
can find an updated NIC driver. If that doesn't address the issue, replace
the network card.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul T" <PaulT@.discussions.microsoft.com> wrote in message
news:50AAC645-E017-4E7C-9DC7-AC505D11216F@.microsoft.com...
> Hi
> When creating the log ship maintenance plan, the first thing it does is
> initiate a backup using:-
> BACKUP DATABASE [ActiveBank] TO DISK =
> N'\\Uatsql01\LogShipSend1\ActiveBank_logshipping_i nit.bak' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> When it gets around 10% through, the system blue screens. Even if we do
> this
> manually, the same thing happens. Now if we try
> BACKUP DATABASE [ActiveBank] TO DISK =
> N'G:\LogShipSend\ActiveBank230507.bak' WITH NOINIT , NOUNLOAD , NAME =
> N'ActiveBank backup', NOSKIP , STATS = 10, NOFORMAT
> The backup works.
> Thanks for any help in advance
> Paul
|||Hi Paul
"Paul T" wrote:

> Hi
> When creating the log ship maintenance plan, the first thing it does is
> initiate a backup using:-
> BACKUP DATABASE [ActiveBank] TO DISK =
> N'\\Uatsql01\LogShipSend1\ActiveBank_logshipping_i nit.bak' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> When it gets around 10% through, the system blue screens. Even if we do this
> manually, the same thing happens. Now if we try
> BACKUP DATABASE [ActiveBank] TO DISK =
> N'G:\LogShipSend\ActiveBank230507.bak' WITH NOINIT , NOUNLOAD , NAME =
> N'ActiveBank backup', NOSKIP , STATS = 10, NOFORMAT
> The backup works.
> Thanks for any help in advance
> Paul
To add to Dan's suggestion, a dedicated LAN between the two machines would
be benificial and also check that there isn't any virus checker software on
the remote machine that could be forcing this error. Check the Windows Event
Logs on both machines as well as the SQL Server Error log for messages which
may relate to this. You could try backing up to a UNC on a different server
as well.
John
|||Maybe it is simply a bug and you should get MS involved?
As Guzman says, definitely update all drivers along the chain. Also, what
about directory/permissions of the sqlagent service login? Just reaching
with that one though.
TheSQLGuru
President
Indicium Resources, Inc.
"Paul T" <PaulT@.discussions.microsoft.com> wrote in message
news:50AAC645-E017-4E7C-9DC7-AC505D11216F@.microsoft.com...
> Hi
> When creating the log ship maintenance plan, the first thing it does is
> initiate a backup using:-
> BACKUP DATABASE [ActiveBank] TO DISK =
> N'\\Uatsql01\LogShipSend1\ActiveBank_logshipping_i nit.bak' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> When it gets around 10% through, the system blue screens. Even if we do
> this
> manually, the same thing happens. Now if we try
> BACKUP DATABASE [ActiveBank] TO DISK =
> N'G:\LogShipSend\ActiveBank230507.bak' WITH NOINIT , NOUNLOAD , NAME =
> N'ActiveBank backup', NOSKIP , STATS = 10, NOFORMAT
> The backup works.
> Thanks for any help in advance
> Paul