Backup error

Hi all!
I take backup of a database every night using
"BACKUP DATABASE [Db1] TO DISK = N'\\server\e$\Backup\Databases\Db1\Db1.bak' WITH INIT , NOUNLOAD , NAME = N'Db1 backup', NOSKIP , STATS = 10, NOFORMAT"
But some nights a have recived the following error message when I view the job history.
"'\\server\e$\Backup\Db1\Db1\Db1.bak' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step fa
iled."
I have tried to delete the backup devices and created new ones. I am backing up close to twenty databases to the same folder every night. But I get error on a couple backup jobs every night, not the same ones every night. I have tride to run the jobs manu
ally daytime and sometimes they run ok and sometimes they fails.
I have read the MS KB 290787 but i'm not sure if it answers my question. Does anybody has any more info/help/hints it would be greatly appriciated.
Thansk
Fredrik
Sounds like you may have some disk issues. Have you checked the integrity
of that disk lately?
Andrew J. Kelly SQL MVP
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:46FACB20-2670-41DD-9452-CE9753680453@.microsoft.com...
> Hi all!
> I take backup of a database every night using
> "BACKUP DATABASE [Db1] TO DISK =
N'\\server\e$\Backup\Databases\Db1\Db1.bak' WITH INIT , NOUNLOAD , NAME =
N'Db1 backup', NOSKIP , STATS = 10, NOFORMAT"
> But some nights a have recived the following error message when I view the
job history.
> "'\\server\e$\Backup\Db1\Db1\Db1.bak' is incorrectly formatted. Backups
cannot be appended, but existing backup sets may still be usable. [SQLSTATE
42000] (Error 3266) BACKUP DATABASE is terminating abnormally. [SQLSTATE
42000] (Error 3013). The step failed."
> I have tried to delete the backup devices and created new ones. I am
backing up close to twenty databases to the same folder every night. But I
get error on a couple backup jobs every night, not the same ones every
night. I have tride to run the jobs manually daytime and sometimes they run
ok and sometimes they fails.
> I have read the MS KB 290787 but i'm not sure if it answers my question.
Does anybody has any more info/help/hints it would be greatly appriciated.
> Thansk
> Fredrik
|||Hi Fredrik
I have a similar problem and was able to fix it, quick and simple.
I renamed the backup and log file
and re ran my backup job, it obviously was unable to append as the file was not fould (due to name change), this created new file
and the backup job suceeded.
Note before all this I manually backed up DB (FULL) and Log file (for each db that I had the problem for) Just in case
For completness my exact error was
Executed as user: [USER NAME]. The backup data in '[DB NAME]' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (E
rror 3013). The step failed.
obviously i was able to delete all non required excess backup files after a few days as I was happy with my backups
Good Luck
Eoin B
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
sql

Backup DB to File WITH INIT?

I am using:
BACKUP DATABASE XXX TO DISK = @.MyFile
-- If @.MyFile exists, i want to overwrite it. The help file says "Use
the INIT clause to overwrite the backup media, and write the backup as
the first file ... ". This sounds like it will clean-up my entire D-
Drive and then do the backup. It should simply overwrite the specific
file @.MyFile if it exists. I just want to be a 100% sure before I run
this command.
Thanks,
Jay
WITH INIT = delete all the backups in your backup device, which is the .BAK
file you specified. This means, everytime you backup, you only have the
backup from the last time the backup command executed.
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183609141.844241.152410@.d30g2000prg.googlegr oups.com...
> I am using:
> BACKUP DATABASE XXX TO DISK = @.MyFile
> -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> the INIT clause to overwrite the backup media, and write the backup as
> the first file ... ". This sounds like it will clean-up my entire D-
> Drive and then do the backup. It should simply overwrite the specific
> file @.MyFile if it exists. I just want to be a 100% sure before I run
> this command.
> Thanks,
> Jay
>
|||Jay
It will NOT clean your entire drive. Think about it, as if you backup
database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
BOL says
INIT
Specifies that all backup sets should be overwritten, but preserves the
media header. If INIT is specified, any existing backup set data on that
device is overwritten.
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183609141.844241.152410@.d30g2000prg.googlegr oups.com...
> I am using:
> BACKUP DATABASE XXX TO DISK = @.MyFile
> -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> the INIT clause to overwrite the backup media, and write the backup as
> the first file ... ". This sounds like it will clean-up my entire D-
> Drive and then do the backup. It should simply overwrite the specific
> file @.MyFile if it exists. I just want to be a 100% sure before I run
> this command.
> Thanks,
> Jay
>
|||OK, does this mean that if I have older backup files like
(MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Jay
> It will NOT clean your entire drive. Think about it, as if you backup
> database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
> BOL says
> INIT
> Specifies that all backup sets should be overwritten, but preserves the
> media header. If INIT is specified, any existing backup set data on that
> device is overwritten.
> "Jay" <jay6...@.hotmail.com> wrote in message
> news:1183609141.844241.152410@.d30g2000prg.googlegr oups.com...
>
>
>
>
> - Show quoted text -
|||Jay
if MYDB_20061231.bak contains more than one file and you issue BACKUP
DATABASE db to disk='c:\MYDB_20061231.bak' WITH INIT so YES it will be
overwritten
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183614106.316025.235930@.j4g2000prf.googlegro ups.com...
> OK, does this mean that if I have older backup files like
> (MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
>
> On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>
|||OK - thanks. I got it. I didn't know a backup file can contain more
than one backups.
On Jul 5, 10:58 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Jay
> if MYDB_20061231.bak contains more than one file and you issue BACKUP
> DATABASE db to disk='c:\MYDB_20061231.bak' WITH INIT so YES it will be
> overwritten
> "Jay" <jay6...@.hotmail.com> wrote in message
> news:1183614106.316025.235930@.j4g2000prf.googlegro ups.com...
>
>
>
>
>
>
> - Show quoted text -

Backup DB to File WITH INIT?

I am using:
BACKUP DATABASE XXX TO DISK = @.MyFile
-- If @.MyFile exists, i want to overwrite it. The help file says "Use
the INIT clause to overwrite the backup media, and write the backup as
the first file ... ". This sounds like it will clean-up my entire D-
Drive and then do the backup. It should simply overwrite the specific
file @.MyFile if it exists. I just want to be a 100% sure before I run
this command.
Thanks,
JayWITH INIT = delete all the backups in your backup device, which is the .BAK
file you specified. This means, everytime you backup, you only have the
backup from the last time the backup command executed.
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
> I am using:
> BACKUP DATABASE XXX TO DISK = @.MyFile
> -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> the INIT clause to overwrite the backup media, and write the backup as
> the first file ... ". This sounds like it will clean-up my entire D-
> Drive and then do the backup. It should simply overwrite the specific
> file @.MyFile if it exists. I just want to be a 100% sure before I run
> this command.
> Thanks,
> Jay
>|||Jay
It will NOT clean your entire drive. Think about it, as if you backup
database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
BOL says
INIT
Specifies that all backup sets should be overwritten, but preserves the
media header. If INIT is specified, any existing backup set data on that
device is overwritten.
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
> I am using:
> BACKUP DATABASE XXX TO DISK = @.MyFile
> -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> the INIT clause to overwrite the backup media, and write the backup as
> the first file ... ". This sounds like it will clean-up my entire D-
> Drive and then do the backup. It should simply overwrite the specific
> file @.MyFile if it exists. I just want to be a 100% sure before I run
> this command.
> Thanks,
> Jay
>|||OK, does this mean that if I have older backup files like
(MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Jay
> It will NOT clean your entire drive. Think about it, as if you backup
> database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
> BOL says
> INIT
> Specifies that all backup sets should be overwritten, but preserves the
> media header. If INIT is specified, any existing backup set data on that
> device is overwritten.
> "Jay" <jay6...@.hotmail.com> wrote in message
> news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
>
>
> > I am using:
> > BACKUP DATABASE XXX TO DISK = @.MyFile
> > -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> > the INIT clause to overwrite the backup media, and write the backup as
> > the first file ... ". This sounds like it will clean-up my entire D-
> > Drive and then do the backup. It should simply overwrite the specific
> > file @.MyFile if it exists. I just want to be a 100% sure before I run
> > this command.
> > Thanks,
> > Jay- Hide quoted text -
> - Show quoted text -|||Jay
if MYDB_20061231.bak contains more than one file and you issue BACKUP
DATABASE db to disk='c:\MYDB_20061231.bak' WITH INIT so YES it will be
overwritten
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183614106.316025.235930@.j4g2000prf.googlegroups.com...
> OK, does this mean that if I have older backup files like
> (MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
>
> On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> Jay
>> It will NOT clean your entire drive. Think about it, as if you backup
>> database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
>> BOL says
>> INIT
>> Specifies that all backup sets should be overwritten, but preserves the
>> media header. If INIT is specified, any existing backup set data on that
>> device is overwritten.
>> "Jay" <jay6...@.hotmail.com> wrote in message
>> news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
>>
>>
>> > I am using:
>> > BACKUP DATABASE XXX TO DISK = @.MyFile
>> > -- If @.MyFile exists, i want to overwrite it. The help file says "Use
>> > the INIT clause to overwrite the backup media, and write the backup as
>> > the first file ... ". This sounds like it will clean-up my entire D-
>> > Drive and then do the backup. It should simply overwrite the specific
>> > file @.MyFile if it exists. I just want to be a 100% sure before I run
>> > this command.
>> > Thanks,
>> > Jay- Hide quoted text -
>> - Show quoted text -
>|||OK - thanks. I got it. I didn't know a backup file can contain more
than one backups.
On Jul 5, 10:58 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Jay
> if MYDB_20061231.bak contains more than one file and you issue BACKUP
> DATABASE db to disk='c:\MYDB_20061231.bak' WITH INIT so YES it will be
> overwritten
> "Jay" <jay6...@.hotmail.com> wrote in message
> news:1183614106.316025.235930@.j4g2000prf.googlegroups.com...
>
> > OK, does this mean that if I have older backup files like
> > (MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
> > On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> >> Jay
> >> It will NOT clean your entire drive. Think about it, as if you backup
> >> database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
> >> BOL says
> >> INIT
> >> Specifies that all backup sets should be overwritten, but preserves the
> >> media header. If INIT is specified, any existing backup set data on that
> >> device is overwritten.
> >> "Jay" <jay6...@.hotmail.com> wrote in message
> >>news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
> >> > I am using:
> >> > BACKUP DATABASE XXX TO DISK = @.MyFile
> >> > -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> >> > the INIT clause to overwrite the backup media, and write the backup as
> >> > the first file ... ". This sounds like it will clean-up my entire D-
> >> > Drive and then do the backup. It should simply overwrite the specific
> >> > file @.MyFile if it exists. I just want to be a 100% sure before I run
> >> > this command.
> >> > Thanks,
> >> > Jay- Hide quoted text -
> >> - Show quoted text -- Hide quoted text -
> - Show quoted text -

Backup DB to File WITH INIT?

I am using:
BACKUP DATABASE XXX TO DISK = @.MyFile
-- If @.MyFile exists, i want to overwrite it. The help file says "Use
the INIT clause to overwrite the backup media, and write the backup as
the first file ... ". This sounds like it will clean-up my entire D-
Drive and then do the backup. It should simply overwrite the specific
file @.MyFile if it exists. I just want to be a 100% sure before I run
this command.
Thanks,
JayWITH INIT = delete all the backups in your backup device, which is the .BAK
file you specified. This means, everytime you backup, you only have the
backup from the last time the backup command executed.
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
> I am using:
> BACKUP DATABASE XXX TO DISK = @.MyFile
> -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> the INIT clause to overwrite the backup media, and write the backup as
> the first file ... ". This sounds like it will clean-up my entire D-
> Drive and then do the backup. It should simply overwrite the specific
> file @.MyFile if it exists. I just want to be a 100% sure before I run
> this command.
> Thanks,
> Jay
>|||Jay
It will NOT clean your entire drive. Think about it, as if you backup
database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
BOL says
INIT
Specifies that all backup sets should be overwritten, but preserves the
media header. If INIT is specified, any existing backup set data on that
device is overwritten.
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
> I am using:
> BACKUP DATABASE XXX TO DISK = @.MyFile
> -- If @.MyFile exists, i want to overwrite it. The help file says "Use
> the INIT clause to overwrite the backup media, and write the backup as
> the first file ... ". This sounds like it will clean-up my entire D-
> Drive and then do the backup. It should simply overwrite the specific
> file @.MyFile if it exists. I just want to be a 100% sure before I run
> this command.
> Thanks,
> Jay
>|||OK, does this mean that if I have older backup files like
(MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Jay
> It will NOT clean your entire drive. Think about it, as if you backup
> database on C:\ drive BACKUP DATABASE commnad would destroy the OS ?
> BOL says
> INIT
> Specifies that all backup sets should be overwritten, but preserves the
> media header. If INIT is specified, any existing backup set data on that
> device is overwritten.
> "Jay" <jay6...@.hotmail.com> wrote in message
> news:1183609141.844241.152410@.d30g2000prg.googlegroups.com...
>
>
>
>
>
>
> - Show quoted text -|||Jay
if MYDB_20061231.bak contains more than one file and you issue BACKUP
DATABASE db to disk='c:\MYDB_20061231.bak' WITH INIT so YES it will be
overwritten
"Jay" <jay6447@.hotmail.com> wrote in message
news:1183614106.316025.235930@.j4g2000prf.googlegroups.com...
> OK, does this mean that if I have older backup files like
> (MYDB_20061231.bak, MYDB_20070101.bak....) they all will be deleted?
>
> On Jul 5, 10:18 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>|||OK - thanks. I got it. I didn't know a backup file can contain more
than one backups.
On Jul 5, 10:58 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Jay
> if MYDB_20061231.bak contains more than one file and you issue BACKUP
> DATABASE db to disk='c:\MYDB_20061231.bak' WITH INIT so YES it will be
> overwritten
> "Jay" <jay6...@.hotmail.com> wrote in message
> news:1183614106.316025.235930@.j4g2000prf.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -sql

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

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_log
shipping_init.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
PaulMy 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_log
shipping_init.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_log
shipping_init.bak' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> When it gets around 10% through, the system blue screens. Even if we do th
is
> 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_log
shipping_init.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

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_init.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
PaulMy 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_init.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_init.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_init.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

Backup ?

I do this to backup the database on our production server
BACKUP DATABASE [DP2] TO DISK = N'D:\mssql\data\MSSQL\BACKUP\DailyDbBackup'
WITH INIT , NOUNLOAD , NAME = N'DP2 Backup Job', NOSKIP , STATS = 10,
NOFORMAT DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='DP2'and
type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset
where database_name='DP2')
RESTORE VERIFYONLY FROM DISK = N'D:\mssql\data\MSSQL\BACKUP\DailyDbBackup'
WITH FILE = @.i
It works fine. However if I change to a mapped drive it gives me the
following error. I had agent running under the system account with failures
so thought I would change to my account, it also fails. I have full control
of that directory from this machine in windows. What gives?
Executed as user: DP2SQL02\jcantley. Cannot open backup device
'V:\DailyDbBackup'. Device error or device off-line. See the SQL Server error
log for more details. [SQLSTATE 42000] (Error 3201) BACKUP DATABASE is
terminating abnormally. [SQLSTATE 42000] (Error 3013) Associated statement
is not prepared [SQLSTATE HY007] (Error 0) Cannot open backup device
'V:\DailyDbBackup'. Device error or device off-line. See the SQL Server error
log for more details. [SQLSTATE 42000] (Error 3201) VERIFY DATABASE is
terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Hi
Mapped drives are not supported. You have to use UNC paths.
Regards
Mike
"jcantley" wrote:

> I do this to backup the database on our production server
> BACKUP DATABASE [DP2] TO DISK = N'D:\mssql\data\MSSQL\BACKUP\DailyDbBackup'
> WITH INIT , NOUNLOAD , NAME = N'DP2 Backup Job', NOSKIP , STATS = 10,
> NOFORMAT DECLARE @.i INT
> select @.i = position from msdb..backupset where database_name='DP2'and
> type!='F' and backup_set_id=(select max(backup_set_id) from msdb..backupset
> where database_name='DP2')
> RESTORE VERIFYONLY FROM DISK = N'D:\mssql\data\MSSQL\BACKUP\DailyDbBackup'
> WITH FILE = @.i
> It works fine. However if I change to a mapped drive it gives me the
> following error. I had agent running under the system account with failures
> so thought I would change to my account, it also fails. I have full control
> of that directory from this machine in windows. What gives?
> Executed as user: DP2SQL02\jcantley. Cannot open backup device
> 'V:\DailyDbBackup'. Device error or device off-line. See the SQL Server error
> log for more details. [SQLSTATE 42000] (Error 3201) BACKUP DATABASE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013) Associated statement
> is not prepared [SQLSTATE HY007] (Error 0) Cannot open backup device
> 'V:\DailyDbBackup'. Device error or device off-line. See the SQL Server error
> log for more details. [SQLSTATE 42000] (Error 3201) VERIFY DATABASE is
> terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
|||Mike,
Here is what I get when i use UNC. We are running active dir could that be
an issue? I am running this under my account but would like to just run it
under system, but what ever works.
Executed as user: DP2SQL02\jcantley. Cannot open backup device
'\\Dp2sql01\BACKUP\DailyDbBackup'. Device error or device off-line. See the
SQL Server error log for more details. [SQLSTATE 42000] (Error 3201) BACKUP
DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013) Associated
statement is not prepared [SQLSTATE HY007] (Error 0) Cannot open backup
device '\\Dp2sql01\BACKUP\DailyDbBackup'. Device error or device off-line.
See the SQL Server error log for more details. [SQLSTATE 42000] (Error 3201)
VERIFY DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013).
The step failed.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Mapped drives are not supported. You have to use UNC paths.
> Regards
> Mike
> "jcantley" wrote:
|||Hi
Have you verified, that when you log on to the server as the account that
runs SQL server and Agent Service, then the folder is available and you have
write access to the folder?
What about the syntax for the TO DISK = ... is that correct? You specify TO
DISK = \\dp2sql01\BACKUP\DailyBackup - could it be that SQL reads this as a
folder rather than as a file? What if you try with ...TO DISK =
'\\dp2sql01\BACKUP\DailyBackup.bak' ?
Regards
Steen
StiderGuy wrote:[vbcol=seagreen]
> Mike,
> Here is what I get when i use UNC. We are running active dir could
> that be an issue? I am running this under my account but would like
> to just run it under system, but what ever works.
> Executed as user: DP2SQL02\jcantley. Cannot open backup device
> '\\Dp2sql01\BACKUP\DailyDbBackup'. Device error or device off-line.
> See the SQL Server error log for more details. [SQLSTATE 42000]
> (Error 3201) BACKUP DATABASE is terminating abnormally. [SQLSTATE
> 42000] (Error 3013) Associated statement is not prepared [SQLSTATE
> HY007] (Error 0) Cannot open backup device
> '\\Dp2sql01\BACKUP\DailyDbBackup'. Device error or device off-line.
> See the SQL Server error log for more details. [SQLSTATE 42000]
> (Error 3201) VERIFY DATABASE is terminating abnormally. [SQLSTATE
> 42000] (Error 3013). The step failed.
> "Mike Epprecht (SQL MVP)" wrote: