I have setup a backup device that backs up a databases daily but i want to
overwrite the data weekly right now its has two months of data in the device.
How do i set it to overwrite
Use the INIT option of the BACKUP command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"lyle" <lyle@.discussions.microsoft.com> wrote in message
news:683AAFF2-4F8C-44F3-A195-F85A9881C047@.microsoft.com...
> I have setup a backup device that backs up a databases daily but i want to
> overwrite the data weekly right now its has two months of data in the device.
> How do i set it to overwrite
Showing posts with label backs. Show all posts
Showing posts with label backs. Show all posts
Tuesday, March 27, 2012
Thursday, February 16, 2012
BACKUP LOG failed - no reason given
Hello,
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN '}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.T RN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN ' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.
Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN '}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.T RN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
> N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN ' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>
|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN '}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.T RN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN ' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.
Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN '}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.T RN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
> N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN ' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>
|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim
BACKUP LOG failed - no reason given
Hello,
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN'}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.TRN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK = N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN'}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.TRN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK => N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN'}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
{'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.TRN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK = N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_200501211015.TRN'}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> {'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_200501211015.TRN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK => N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501211015.TRN' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim
BACKUP LOG failed - no reason given
Hello,
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_20
0501211015.TRN'}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
& #123;'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_
200501211015.TRN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501
211015.TRN' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> & #123;'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_20
0501211015.TRN'}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> & #123;'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_
200501211015.TRN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
> N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501
211015.TRN' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim
I have an agent job that backs up transaction logs of several databases,
referring a maintenance plan.
Recently, one of the backups began to fail sometimes - the one of the
largest database. The messages in the log are:
...
Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1, device
information: (FILE=1, TYPE=DISK:
& #123;'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_20
0501211015.TRN'}).
Log backed up: Database: RGRSQL, creation date(time): 2004/01/08(10:20:44),
first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
device information: (FILE=1, TYPE=DISK:
& #123;'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_
200501211015.TRN'}).
BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501
211015.TRN' WITH INIT , NOUNLOAD ,
NOSKIP , STATS = 10, NOFORMAT
MSKB article says to examine the previous errors in the log, but there are
none, neither in sql server log, nor in any event log of the machine.
And then on the next scheduled time, it succeeds. Then again fails. No
pattern.
Pretty much same thing is happening with the full database backup - same
database.
"CHECKDB found 0 allocation errors and 0 consistency errors in database
'VMFG'."
How to troubleshoot it? is there a way to make it to tell _why_ it failed?
thanks,
Vadim Rapp
Polyscience, Inc.Is someone else trying to put your backup device onto tape while your trying
to write to it?
"Vadim Rapp" <vrapp@.nospam.polyscience.com> wrote in message
news:#6Hq$J#$EHA.2316@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have an agent job that backs up transaction logs of several databases,
> referring a maintenance plan.
> Recently, one of the backups began to fail sometimes - the one of the
> largest database. The messages in the log are:
> ...
> Log backed up: Database: OLAP, creation date(time): 2004/01/21(11:42:56),
> first LSN: 4615:16:1, last LSN: 4617:16:1, number of dump devices: 1,
device
> information: (FILE=1, TYPE=DISK:
> & #123;'D:\MSSQL\MSSQL\BACKUP\OLAP_tlog_20
0501211015.TRN'}).
> Log backed up: Database: RGRSQL, creation date(time):
2004/01/08(10:20:44),
> first LSN: 50593:45:1, last LSN: 50614:57:1, number of dump devices: 1,
> device information: (FILE=1, TYPE=DISK:
> & #123;'D:\MSSQL\MSSQL\BACKUP\RGRSQL_tlog_
200501211015.TRN'}).
> BACKUP failed to complete the command BACKUP LOG [VMFG] TO DISK =
> N'D:\MSSQL\MSSQL\BACKUP\VMFG_tlog_200501
211015.TRN' WITH INIT , NOUNLOAD
,
> NOSKIP , STATS = 10, NOFORMAT
> MSKB article says to examine the previous errors in the log, but there are
> none, neither in sql server log, nor in any event log of the machine.
> And then on the next scheduled time, it succeeds. Then again fails. No
> pattern.
> Pretty much same thing is happening with the full database backup - same
> database.
> "CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'VMFG'."
> How to troubleshoot it? is there a way to make it to tell _why_ it failed?
>
> thanks,
> Vadim Rapp
> Polyscience, Inc.
>
>|||Hello Chris:
You wrote on Fri, 21 Jan 2005 11:09:20 -0800:
C> Is someone else trying to put your backup device onto tape while your
C> trying to write to it?
No.
Vadim
Monday, February 13, 2012
backup job sometimes fails
Hi
In which account is the job running and does the account has backup operator privilege to those failed db's?
We have a nightly job on a production server which backs up all databases
(about 90 on the server)
Sometimes it'll only backup some of them, yet it reports success.
Our proc to manage the process is below:
Any ideas on what we need to do to make it reliable ?
--
DECLARE @.DB_Name varchar(32)
DECLARE @.Backup_Path varchar(255)
DECLARE @.Backup_Name varchar(255)
DECLARE DB_Cursor CURSOR FOR SELECT NAME FROM sysdatabases
OPEN DB_Cursor
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
WHILE @.@.FETCH_STATUS = 0
BEGIN
IF @.DB_Name <> 'tempdb' AND @.DB_Name <> 'model'
BEGIN
print '--<< ' + @.db_name + '
>>--'
SET @.Backup_Path = N'd:\sql2005backups\nightly\' + @.DB_Name + 'Daily' +
'.bak'
SET @.Backup_Name = @.DB_Name + N' backup'
BACKUP DATABASE @.DB_Name TO DISK = @.Backup_Path WITH INIT
print ''
END
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
END
Print "Finished backing up the databases"
CLOSE DB_cursor
DEALLOCATE DB_cursor
My suggestion is to look into a 3rd party package for reliable backups of business critical data....SQL 2005 just isn't there yet in this area.
Jeff
|||create a job with the above script and keep the script in step1 of the job and then in the advanced options set an output file so that the output will be written to a text file, which will be used for troubleshooting purposes..............in the step2 you can have the mail step......and see whats the output after the backup completes.......is this box with sql 2005 sp1? if yes better go to SP2 as there are few bugs which are fixed in sp2.........also try to go with maintenance plan and see whats the result if the above option fails....|||Hi
Thanks for this
We already write the output to a file - it doesn't contain any errors or anything unusual - most strange...
The box is running SQL 2005 sp2.
I could go and buy something like Red-gate backup - but I don't see why I should have to ! Most frustrating..
thanks
Bruce
|||You don't need a third party solution - SQL native backups were fine and have for years. Third party solutions are the ones that tend to be a bit more problematic. The only problem I can think of that Jeff would have been referring to is maintenance plans. The problem is with maintenance plans, not SQL Server backups.
I'm curious - you are using both single quotes as well as double quotes for print statements? Is that the actual script you are using? What is in the output file? Does it have the name of the database that are skipped or not? What is in the error log? Have you tried running a server side trace during the times you run the backups to see what is actually being executed?
-Sue
|||Hi Sue
Thanks for replying..
The line with the double-quotes we ended up commenting out.
I also put the backup statement in a 'try catch' as follows below and there was no error logged
No - it doesn't have the name of the databases that are skipped - it just seems to exit without logging any errors - and it's not consistent - some nights it gets to the end.
There is nothing logged in the error logs.... No I haven't tried running a server side trace..
thanks, Bruce.
DECLARE @.DB_Name varchar(32)
DECLARE @.Backup_Path varchar(255)
DECLARE @.Backup_Name varchar(255)
DECLARE DB_Cursor CURSOR FOR SELECT NAME FROM sysdatabases order by name
OPEN DB_Cursor
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
WHILE @.@.FETCH_STATUS = 0
BEGIN
IF @.DB_Name <> 'tempdb' AND @.DB_Name <> 'model'
BEGIN
print '--<< ' + @.db_name + ' >>--'
SET @.Backup_Path = N'd:\sql2005backups\nightly\' + @.DB_Name + 'Daily' + '.bak'
SET @.Backup_Name = @.DB_Name + N' backup'
BEGIN TRY
BACKUP DATABASE @.DB_Name TO DISK = @.Backup_Path WITH INIT ;
END TRY
BEGIN CATCH
Print 'Error -- ' + ERROR_MESSAGE();
END CATCH;
print ''
END
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
END
CLOSE DB_cursor
DEALLOCATE DB_cursor
print 'Finished backing up'
|||So you need to run a trace during the backups (and for a time prior to them starting) to see more of what is going on. You'll also want to look at the logs prior to and during the backups.
-Sue
|||Bruce,
I too have something like this. I noticed that this happens when you have many databases needs to be backed up.
What we did here is to split this backup jobs into multiple steps. Each Job will backup few databases may be 50.
Try this and let me know.
Thanks
Shilpi
|||Can you check whether the existing backup file is in use? If possible alter the script to append date at the end of backup filename. Since we are backingup nearly 88 databases but didnt find any issues.In which account is the job running and does the account has backup operator privilege to those failed db's?
backup job sometimes fails
Hi
In which account is the job running and does the account has backup operator privilege to those failed db's?
We have a nightly job on a production server which backs up all databases
(about 90 on the server)
Sometimes it'll only backup some of them, yet it reports success.
Our proc to manage the process is below:
Any ideas on what we need to do to make it reliable ?
--
DECLARE @.DB_Name varchar(32)
DECLARE @.Backup_Path varchar(255)
DECLARE @.Backup_Name varchar(255)
DECLARE DB_Cursor CURSOR FOR SELECT NAME FROM sysdatabases
OPEN DB_Cursor
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
WHILE @.@.FETCH_STATUS = 0
BEGIN
IF @.DB_Name <> 'tempdb' AND @.DB_Name <> 'model'
BEGIN
print '--<< ' + @.db_name + '
>>--'
SET @.Backup_Path = N'd:\sql2005backups\nightly\' + @.DB_Name + 'Daily' +
'.bak'
SET @.Backup_Name = @.DB_Name + N' backup'
BACKUP DATABASE @.DB_Name TO DISK = @.Backup_Path WITH INIT
print ''
END
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
END
Print "Finished backing up the databases"
CLOSE DB_cursor
DEALLOCATE DB_cursor
My suggestion is to look into a 3rd party package for reliable backups of business critical data....SQL 2005 just isn't there yet in this area.
Jeff
|||create a job with the above script and keep the script in step1 of the job and then in the advanced options set an output file so that the output will be written to a text file, which will be used for troubleshooting purposes..............in the step2 you can have the mail step......and see whats the output after the backup completes.......is this box with sql 2005 sp1? if yes better go to SP2 as there are few bugs which are fixed in sp2.........also try to go with maintenance plan and see whats the result if the above option fails....|||Hi
Thanks for this
We already write the output to a file - it doesn't contain any errors or anything unusual - most strange...
The box is running SQL 2005 sp2.
I could go and buy something like Red-gate backup - but I don't see why I should have to ! Most frustrating..
thanks
Bruce
|||You don't need a third party solution - SQL native backups were fine and have for years. Third party solutions are the ones that tend to be a bit more problematic. The only problem I can think of that Jeff would have been referring to is maintenance plans. The problem is with maintenance plans, not SQL Server backups.
I'm curious - you are using both single quotes as well as double quotes for print statements? Is that the actual script you are using? What is in the output file? Does it have the name of the database that are skipped or not? What is in the error log? Have you tried running a server side trace during the times you run the backups to see what is actually being executed?
-Sue
|||Hi Sue
Thanks for replying..
The line with the double-quotes we ended up commenting out.
I also put the backup statement in a 'try catch' as follows below and there was no error logged
No - it doesn't have the name of the databases that are skipped - it just seems to exit without logging any errors - and it's not consistent - some nights it gets to the end.
There is nothing logged in the error logs.... No I haven't tried running a server side trace..
thanks, Bruce.
DECLARE @.DB_Name varchar(32)
DECLARE @.Backup_Path varchar(255)
DECLARE @.Backup_Name varchar(255)
DECLARE DB_Cursor CURSOR FOR SELECT NAME FROM sysdatabases order by name
OPEN DB_Cursor
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
WHILE @.@.FETCH_STATUS = 0
BEGIN
IF @.DB_Name <> 'tempdb' AND @.DB_Name <> 'model'
BEGIN
print '--<< ' + @.db_name + ' >>--'
SET @.Backup_Path = N'd:\sql2005backups\nightly\' + @.DB_Name + 'Daily' + '.bak'
SET @.Backup_Name = @.DB_Name + N' backup'
BEGIN TRY
BACKUP DATABASE @.DB_Name TO DISK = @.Backup_Path WITH INIT ;
END TRY
BEGIN CATCH
Print 'Error -- ' + ERROR_MESSAGE();
END CATCH;
print ''
END
FETCH NEXT FROM DB_Cursor INTO @.DB_Name
END
CLOSE DB_cursor
DEALLOCATE DB_cursor
print 'Finished backing up'
|||So you need to run a trace during the backups (and for a time prior to them starting) to see more of what is going on. You'll also want to look at the logs prior to and during the backups.
-Sue
|||Bruce,
I too have something like this. I noticed that this happens when you have many databases needs to be backed up.
What we did here is to split this backup jobs into multiple steps. Each Job will backup few databases may be 50.
Try this and let me know.
Thanks
Shilpi
|||Can you check whether the existing backup file is in use? If possible alter the script to append date at the end of backup filename. Since we are backingup nearly 88 databases but didnt find any issues.In which account is the job running and does the account has backup operator privilege to those failed db's?
Backup Job Failing
I have an SSIS package that does one simple thing: perform a FULL backup of a database.
I executed this package yesterday at 2:00. The package backs up to four individual files on a network share. The network share is accessible from the SQL Server. THe database in question is 245GB in size.
The package was running fine when I left for the day. When I got in today, there was an error in the SQL Server log:
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE ServicingODS. Check the backup application log for detailed messages.
Where is this infamous backup application log?!? The Event Viewer says the same thing. Needless to say, the error message is a bit vague.
There were no "issus" overnight (power outages, network issues, etc.)
Anyone have any ideas?
Thanks!
Hi A.M
If you check the SQL server error log, there should be another line of error above the message that you have posted.
Could you please check and post a few lines from above and below the message you have already posted.
Jag
Backup job failed-SVP2
I have a job that has run fine for quite a while now. It backs up db and
trans logs file and then deletes bak and log files older than 2 days. I
noticed that since 4/23/07, it hadn't deleted the bak files nor the trans
log files either. I also remembered putting SVP2 on it about that time.
I'm running SS2005 on Server 2003. The job has 4 'nodes' Back Up Databse
(full)/ Back Up Databse Trans log/databse cleanup/trans log cleanup. I
noticed that the backup jobs connection says, "Target Server Connection" but
the "maintenance" jobs (the ones that delete the old bak and trans log files
that is bombing) was run as "SACONNECT". Does anyone know why that would
have changed with SVP2? Honestly, I'm not sure what it was prior to SVP2
going in.
What IS the difference between "Target server connection", "SACONNECT", and
"Local server connection"? I just want the one that has the ability to
delete older files in the backup folders.
You didn't mention if there are any errors or what's in the
history for the maintenance plan but this could be related
to some known issues with SP2. The issues are related to the
clean up tasks.
You should still check for logs for errors when the
maintenance plan runs. And then you should try to figure out
what version of SP2 you are running on the server as well as
your client side and see if you are affected by the issues
with SP2. See the following article:
Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup
tasks run at different intervals than intended
http://support.microsoft.com/kb/933508
-Sue
On Mon, 7 May 2007 10:06:40 -0400, "Peter Lux"
<pete.lux@.theheritagegrp.com> wrote:
>I have a job that has run fine for quite a while now. It backs up db and
>trans logs file and then deletes bak and log files older than 2 days. I
>noticed that since 4/23/07, it hadn't deleted the bak files nor the trans
>log files either. I also remembered putting SVP2 on it about that time.
>I'm running SS2005 on Server 2003. The job has 4 'nodes' Back Up Databse
>(full)/ Back Up Databse Trans log/databse cleanup/trans log cleanup. I
>noticed that the backup jobs connection says, "Target Server Connection" but
>the "maintenance" jobs (the ones that delete the old bak and trans log files
>that is bombing) was run as "SACONNECT". Does anyone know why that would
>have changed with SVP2? Honestly, I'm not sure what it was prior to SVP2
>going in.
>What IS the difference between "Target server connection", "SACONNECT", and
>"Local server connection"? I just want the one that has the ability to
>delete older files in the backup folders.
>
|||Hi Peter,
Could you please mail me (changliw_at_microsoft_dot_com) the SQL error logs
for further research?
By default, the error logs were in the folder: %ProgramFiles%\Microsoft SQL
Server\MSSQL\LOG.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:vvlQF1RkHHA.1144@.TK2MSFTNGHUB02.phx.gbl...
> Hi Peter,
> Could you please mail me (changliw_at_microsoft_dot_com) the SQL error
> logs
> for further research?
Charles.. I sent it.
|||Hi Pete,
Thanks for your email response.
After looked through the error logs, I found that your database back files
were stored separately in the subdirectories of MSSQLBackups. I am afraid
that that is the trick.Maintenance tasks in SQL Server 2005 cannot delete
subdirectories. I recommend that you create a separate Maintenance cleanup
for each database.
For more information, please refer to:
Back up Database Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms189647.aspx
( refer to the section Create a sub-directory for each database).
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||SP1 fixed the subfolder delete issue. After applying SP1,
there is a checkbox on the Maintenance Cleanup Task called
"Include first-level subfolders". You select that to delete
files in subfolders. However, You can't configure it using
the wizard. You have to create the Maintenance Plan and then
go back and modify the Maintenance Cleanup Task afterward.
-Sue
On Wed, 09 May 2007 07:19:38 GMT,
changliw@.online.microsoft.com (Charles Wang[MSFT]) wrote:
>Hi Pete,
>Thanks for your email response.
>After looked through the error logs, I found that your database back files
>were stored separately in the subdirectories of MSSQLBackups. I am afraid
>that that is the trick.Maintenance tasks in SQL Server 2005 cannot delete
>subdirectories. I recommend that you create a separate Maintenance cleanup
>for each database.
>For more information, please refer to:
>Back up Database Task (Maintenance Plan)
>http://msdn2.microsoft.com/en-us/library/ms189647.aspx
>( refer to the section Create a sub-directory for each database).
>If you have any other questions or concerns, please feel free to let me
>know. It is my pleasure to be of assistance.
>Best regards,
>Charles Wang
>Microsoft Online Community Support
>================================================= ====
>Get notification to my posts through email? Please refer to:
>http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>ications
>If you are using Outlook Express, please make sure you clear the check box
>"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
>Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
>where an initial response from the community or a Microsoft Support
>Engineer within 1 business day is acceptable. Please note that each follow
>up response may take approximately 2 business days as the support
>professional working with you may need further investigation to reach the
>most efficient resolution. The offering is not appropriate for situations
>that require urgent, real-time or phone-based interactions or complex
>project analysis and dump analysis issues. Issues of this nature are best
>handled working with a dedicated Microsoft Support Engineer by contacting
>Microsoft Customer Support Services (CSS) at
>http://msdn.microsoft.com/subscriptions/support/default.aspx.
>================================================= =====
>When responding to posts, please "Reply to Group" via
>your newsreader so that others may learn and benefit
>from this issue.
>================================================= =====
>This posting is provided "AS IS" with no warranties, and confers no rights.
>================================================= =====
>
|||Hi Sue,
Thanks for your pointing out. I am sorry that I missed that since I checked
a SQL Server 2005 instance with no SP1.
Pete, could you please check the content of the File Extention? The correct
conent should be like ".trn;.bak". Please check if the dot was missed.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
trans logs file and then deletes bak and log files older than 2 days. I
noticed that since 4/23/07, it hadn't deleted the bak files nor the trans
log files either. I also remembered putting SVP2 on it about that time.
I'm running SS2005 on Server 2003. The job has 4 'nodes' Back Up Databse
(full)/ Back Up Databse Trans log/databse cleanup/trans log cleanup. I
noticed that the backup jobs connection says, "Target Server Connection" but
the "maintenance" jobs (the ones that delete the old bak and trans log files
that is bombing) was run as "SACONNECT". Does anyone know why that would
have changed with SVP2? Honestly, I'm not sure what it was prior to SVP2
going in.
What IS the difference between "Target server connection", "SACONNECT", and
"Local server connection"? I just want the one that has the ability to
delete older files in the backup folders.
You didn't mention if there are any errors or what's in the
history for the maintenance plan but this could be related
to some known issues with SP2. The issues are related to the
clean up tasks.
You should still check for logs for errors when the
maintenance plan runs. And then you should try to figure out
what version of SP2 you are running on the server as well as
your client side and see if you are affected by the issues
with SP2. See the following article:
Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup
tasks run at different intervals than intended
http://support.microsoft.com/kb/933508
-Sue
On Mon, 7 May 2007 10:06:40 -0400, "Peter Lux"
<pete.lux@.theheritagegrp.com> wrote:
>I have a job that has run fine for quite a while now. It backs up db and
>trans logs file and then deletes bak and log files older than 2 days. I
>noticed that since 4/23/07, it hadn't deleted the bak files nor the trans
>log files either. I also remembered putting SVP2 on it about that time.
>I'm running SS2005 on Server 2003. The job has 4 'nodes' Back Up Databse
>(full)/ Back Up Databse Trans log/databse cleanup/trans log cleanup. I
>noticed that the backup jobs connection says, "Target Server Connection" but
>the "maintenance" jobs (the ones that delete the old bak and trans log files
>that is bombing) was run as "SACONNECT". Does anyone know why that would
>have changed with SVP2? Honestly, I'm not sure what it was prior to SVP2
>going in.
>What IS the difference between "Target server connection", "SACONNECT", and
>"Local server connection"? I just want the one that has the ability to
>delete older files in the backup folders.
>
|||Hi Peter,
Could you please mail me (changliw_at_microsoft_dot_com) the SQL error logs
for further research?
By default, the error logs were in the folder: %ProgramFiles%\Microsoft SQL
Server\MSSQL\LOG.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:vvlQF1RkHHA.1144@.TK2MSFTNGHUB02.phx.gbl...
> Hi Peter,
> Could you please mail me (changliw_at_microsoft_dot_com) the SQL error
> logs
> for further research?
Charles.. I sent it.
|||Hi Pete,
Thanks for your email response.
After looked through the error logs, I found that your database back files
were stored separately in the subdirectories of MSSQLBackups. I am afraid
that that is the trick.Maintenance tasks in SQL Server 2005 cannot delete
subdirectories. I recommend that you create a separate Maintenance cleanup
for each database.
For more information, please refer to:
Back up Database Task (Maintenance Plan)
http://msdn2.microsoft.com/en-us/library/ms189647.aspx
( refer to the section Create a sub-directory for each database).
If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||SP1 fixed the subfolder delete issue. After applying SP1,
there is a checkbox on the Maintenance Cleanup Task called
"Include first-level subfolders". You select that to delete
files in subfolders. However, You can't configure it using
the wizard. You have to create the Maintenance Plan and then
go back and modify the Maintenance Cleanup Task afterward.
-Sue
On Wed, 09 May 2007 07:19:38 GMT,
changliw@.online.microsoft.com (Charles Wang[MSFT]) wrote:
>Hi Pete,
>Thanks for your email response.
>After looked through the error logs, I found that your database back files
>were stored separately in the subdirectories of MSSQLBackups. I am afraid
>that that is the trick.Maintenance tasks in SQL Server 2005 cannot delete
>subdirectories. I recommend that you create a separate Maintenance cleanup
>for each database.
>For more information, please refer to:
>Back up Database Task (Maintenance Plan)
>http://msdn2.microsoft.com/en-us/library/ms189647.aspx
>( refer to the section Create a sub-directory for each database).
>If you have any other questions or concerns, please feel free to let me
>know. It is my pleasure to be of assistance.
>Best regards,
>Charles Wang
>Microsoft Online Community Support
>================================================= ====
>Get notification to my posts through email? Please refer to:
>http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>ications
>If you are using Outlook Express, please make sure you clear the check box
>"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
>Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
>where an initial response from the community or a Microsoft Support
>Engineer within 1 business day is acceptable. Please note that each follow
>up response may take approximately 2 business days as the support
>professional working with you may need further investigation to reach the
>most efficient resolution. The offering is not appropriate for situations
>that require urgent, real-time or phone-based interactions or complex
>project analysis and dump analysis issues. Issues of this nature are best
>handled working with a dedicated Microsoft Support Engineer by contacting
>Microsoft Customer Support Services (CSS) at
>http://msdn.microsoft.com/subscriptions/support/default.aspx.
>================================================= =====
>When responding to posts, please "Reply to Group" via
>your newsreader so that others may learn and benefit
>from this issue.
>================================================= =====
>This posting is provided "AS IS" with no warranties, and confers no rights.
>================================================= =====
>
|||Hi Sue,
Thanks for your pointing out. I am sorry that I missed that since I checked
a SQL Server 2005 instance with no SP1.
Pete, could you please check the content of the File Extention? The correct
conent should be like ".trn;.bak". Please check if the dot was missed.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
Subscribe to:
Posts (Atom)