This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
What is the actual backup command your using?
Andrew J. Kelly SQL MVP
"Garrett Taylor" <gtaylor@.westerntitle.net> wrote in message
news:1049DD05-2DBF-499D-AE0F-C263FAB62C90@.microsoft.com...
> This is the error I get for the database named, "NoteServe4005". I get
this error for all databases whether I attempt to backup manually or
automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination:
[c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC
SQL Server Driver][SQL Server]The media family on device
'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating
abnormally.
> I searched support for the error pulling up only KB:297104 which says that
this can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a workaround which involves setting the trace flag to
3111, but that didn't seem to make a difference either.
> Ideas?
|||I'm running it from Enterprise Manager both as a scheduled
job and manually.
>--Original Message--
>What is the actual backup command your using?
>--
>Andrew J. Kelly SQL MVP
>
>"Garrett Taylor" <gtaylor@.westerntitle.net> wrote in
message[vbcol=seagreen]
>news:1049DD05-2DBF-499D-AE0F-C263FAB62C90@.microsoft.com...
named, "NoteServe4005". I get
>this error for all databases whether I attempt to backup
manually or
>automatically.
>[c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN][vbcol=seagreen]
[Microsoft][ODBC
>SQL Server Driver][SQL Server]The media family on device
>'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly[vbcol=seagreen]
>formed. SQL Server cannot process this media family.
LOG is terminating[vbcol=seagreen]
>abnormally.
KB:297104 which says that
>this can happen when transaction log files exceed 4GB.
However, the T-Log in
>this example is only 50MB. It also says the error is
fixed by SP1 and I have
>SP3a. There's also a workaround which involves setting
the trace flag to
>3111, but that didn't seem to make a difference either.
>
>.
>
|||You might want to give MS PSS a call.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Garrett Taylor" <gtaylor@.westerntitle.net> wrote in message
news:95f101c43380$92fb9c10$a301280a@.phx.gbl...[vbcol=seagreen]
> I'm running it from Enterprise Manager both as a scheduled
> job and manually.
> message
> named, "NoteServe4005". I get
> manually or
> \NoteServe4005_tlog_200405041500.TRN]
> [Microsoft][ODBC
> \NoteServe4005_tlog_200405041500.TRN' is incorrectly
> LOG is terminating
> KB:297104 which says that
> However, the T-Log in
> fixed by SP1 and I have
> the trace flag to
Showing posts with label backing. Show all posts
Showing posts with label backing. Show all posts
Sunday, February 19, 2012
Error backing up Transaction Logs
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup..
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN' is incorrectly formed. SQL Server cannot process this media family
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either
IdeasIf this file "c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN" exists, delete it.Make sure that you also have sufficient disk space to store the new backup(s). HTH
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup..
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN' is incorrectly formed. SQL Server cannot process this media family
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either
Ideas|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>
[4] Database NoteServe4005: Transaction Log Backup..
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN' is incorrectly formed. SQL Server cannot process this media family
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either
IdeasIf this file "c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN" exists, delete it.Make sure that you also have sufficient disk space to store the new backup(s). HTH
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup..
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405041500.TRN' is incorrectly formed. SQL Server cannot process this media family
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either
Ideas|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>
Error backing up Transaction Logs
This is the error I get for the database named, "NoteServe4005". I get this
error for all databases whether I attempt to backup manually or automaticall
y.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: & #91;c:\backup\NoteServe4005\NoteServe400
5_tlog_200405041500.TR
N]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The media family on device 'c:\bac
kup\NoteServe4005\NoteServe4005_tlog_200
405041500.TRN' is incorrectly formed
. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is ter
minating abnormally.
I searched support for the error pulling up only KB:297104 which says that t
his can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to
make a difference either.
Ideas?If this file " c:\backup\NoteServe4005\NoteServe4005_tl
og_200405041500.TRN" e
xists, delete it.Make sure that you also have sufficient disk space to store
the new backup(s). HTH.
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this
error for all databases whether I attempt to backup manually or automaticall
y.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: & #91;c:\backup\NoteServe4005\NoteServe400
5_tlog_200405041500.TR
N]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The media family on device 'c:\bac
kup\NoteServe4005\NoteServe4005_tlog_200
405041500.TRN' is incorrectly formed
. SQL Server cannot process this media
family.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is ter
minating abnormally.
I searched support for the error pulling up only KB:297104 which says that t
his can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a
workaround which involves setting the trace flag to 3111, but that didn't se
em to make a difference either.
Ideas?|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>
error for all databases whether I attempt to backup manually or automaticall
y.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: & #91;c:\backup\NoteServe4005\NoteServe400
5_tlog_200405041500.TR
N]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The media family on device 'c:\bac
kup\NoteServe4005\NoteServe4005_tlog_200
405041500.TRN' is incorrectly formed
. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is ter
minating abnormally.
I searched support for the error pulling up only KB:297104 which says that t
his can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to
make a difference either.
Ideas?If this file " c:\backup\NoteServe4005\NoteServe4005_tl
og_200405041500.TRN" e
xists, delete it.Make sure that you also have sufficient disk space to store
the new backup(s). HTH.
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this
error for all databases whether I attempt to backup manually or automaticall
y.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: & #91;c:\backup\NoteServe4005\NoteServe400
5_tlog_200405041500.TR
N]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The media family on device 'c:\bac
kup\NoteServe4005\NoteServe4005_tlog_200
405041500.TRN' is incorrectly formed
. SQL Server cannot process this media
family.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is ter
minating abnormally.
I searched support for the error pulling up only KB:297104 which says that t
his can happen when transaction log files exceed 4GB. However, the T-Log in
this example is only 50MB. It also says the error is fixed by SP1 and I have
SP3a. There's also a
workaround which involves setting the trace flag to 3111, but that didn't se
em to make a difference either.
Ideas?|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>
Error backing up Transaction Logs
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
If this file "c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN" exists, delete it.Make sure that you also have sufficient disk space to store the new backup(s). HTH.
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media
family.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a
workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media fami
ly.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a worka
round which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
If this file "c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN" exists, delete it.Make sure that you also have sufficient disk space to store the new backup(s). HTH.
-- Garrett Taylor wrote: --
This is the error I get for the database named, "NoteServe4005". I get this error for all databases whether I attempt to backup manually or automatically.
[4] Database NoteServe4005: Transaction Log Backup...
Destination: [c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The media family on device 'c:\backup\NoteServe4005\NoteServe4005_tlog_200405 041500.TRN' is incorrectly formed. SQL Server cannot process this media
family.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally.
I searched support for the error pulling up only KB:297104 which says that this can happen when transaction log files exceed 4GB. However, the T-Log in this example is only 50MB. It also says the error is fixed by SP1 and I have SP3a. There's also a
workaround which involves setting the trace flag to 3111, but that didn't seem to make a difference either.
Ideas?
|||The file doesn't already exist and I have more than 50GB
free where my transaction file is only 50MB.
>--Original Message--
>If this file "c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN" exists, delete
it.Make sure that you also have sufficient disk space to
store the new backup(s). HTH.
> -- Garrett Taylor wrote: --
> This is the error I get for the database
named, "NoteServe4005". I get this error for all databases
whether I attempt to backup manually or automatically.
> [4] Database NoteServe4005: Transaction Log Backup...
> Destination: [c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN]
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error
3241: [Microsoft][ODBC SQL Server Driver][SQL Server]The
media family on device 'c:\backup\NoteServe4005
\NoteServe4005_tlog_200405041500.TRN' is incorrectly
formed. SQL Server cannot process this media family.
> [Microsoft][ODBC SQL Server Driver][SQL Server]
BACKUP LOG is terminating abnormally.
> I searched support for the error pulling up only
KB:297104 which says that this can happen when transaction
log files exceed 4GB. However, the T-Log in this example
is only 50MB. It also says the error is fixed by SP1 and I
have SP3a. There's also a workaround which involves
setting the trace flag to 3111, but that didn't seem to
make a difference either.
> Ideas?
>.
>
Error backing up database to tape
I am trying to backup a database to tape. I'm using
Microsoft SQL Server 2000 Enterprise Edition and Windows
Server 2003.
When I try to do the backup using Enterprise Manager I see
the following message:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Cannot open backup device '\\.\Tape0'. Device error or
device off-line. See the SQL Server error log for more
details.
BACKUP DATABASE is terminating abnormally.
In the Event Viewer is logged the following message:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 14/1/2004
Time: 10:29:20
User: N/A
Computer: MySQLName
Description:
18204 :
BackupTapeFile::OpenMedia: Backup device '\\.\Tape0'
failed to open. Operating system error = 5(Access is
denied.).
If I try do it using OSQL (I want to do using OSQL), the
same error is logged on Event Viewer.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I try use the Administrator user, but I get the same error.
I can do the backup to disk normally, but I need to do to
tape.
Can any one help me to solve this problem?
Thank you.Can't say I've tried backing up to tape directly.
Can you not backup to file & then backup to tape using NT Backup or similar?
I prefer to backup to file initially because it means I can normally restore
from file which is much faster than tape. Only if something goes wrong with
the file or server itself do I need to resort to the tape...
It sounds like it cannot find the media. Is the correct media inserted, with
the correct name?
Can you backup to this tape through NT backup or similar to verify it is
related to SQL Server & not Windows?
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||I need backup database directly to tape.
I'm using a tape that never was used and another tape,
that was used by NTBACKUP. I see the same error with
everyone.
I can use NTBACKUP to backup files to tape without
problems.
Backup or similar?
can normally restore
something goes wrong with
tape...
media inserted, with
to verify it is
Microsoft SQL Server 2000 Enterprise Edition and Windows
Server 2003.
When I try to do the backup using Enterprise Manager I see
the following message:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Cannot open backup device '\\.\Tape0'. Device error or
device off-line. See the SQL Server error log for more
details.
BACKUP DATABASE is terminating abnormally.
In the Event Viewer is logged the following message:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 14/1/2004
Time: 10:29:20
User: N/A
Computer: MySQLName
Description:
18204 :
BackupTapeFile::OpenMedia: Backup device '\\.\Tape0'
failed to open. Operating system error = 5(Access is
denied.).
If I try do it using OSQL (I want to do using OSQL), the
same error is logged on Event Viewer.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I try use the Administrator user, but I get the same error.
I can do the backup to disk normally, but I need to do to
tape.
Can any one help me to solve this problem?
Thank you.Can't say I've tried backing up to tape directly.
Can you not backup to file & then backup to tape using NT Backup or similar?
I prefer to backup to file initially because it means I can normally restore
from file which is much faster than tape. Only if something goes wrong with
the file or server itself do I need to resort to the tape...
It sounds like it cannot find the media. Is the correct media inserted, with
the correct name?
Can you backup to this tape through NT backup or similar to verify it is
related to SQL Server & not Windows?
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||I need backup database directly to tape.
I'm using a tape that never was used and another tape,
that was used by NTBACKUP. I see the same error with
everyone.
I can use NTBACKUP to backup files to tape without
problems.
quote:
>--Original Message--
>Can't say I've tried backing up to tape directly.
>Can you not backup to file & then backup to tape using NT
Backup or similar?
quote:
>I prefer to backup to file initially because it means I
can normally restore
quote:
>from file which is much faster than tape. Only if
something goes wrong with
quote:
>the file or server itself do I need to resort to the
tape...
quote:
>It sounds like it cannot find the media. Is the correct
media inserted, with
quote:
>the correct name?
>Can you backup to this tape through NT backup or similar
to verify it is
quote:
>related to SQL Server & not Windows?
>
>--
>Cheers,
>
>James Goodman MCSE, MCDBA
>http://www.angelfire.com/sports/f1pictures
>
>.
>
Error backing up database to tape
I am trying to backup a database to tape. I'm using
Microsoft SQL Server 2000 Enterprise Edition and Windows
Server 2003.
When I try to do the backup using Enterprise Manager I see
the following message:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Cannot open backup device '\\.\Tape0'. Device error or
device off-line. See the SQL Server error log for more
details.
BACKUP DATABASE is terminating abnormally.
In the Event Viewer is logged the following message:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 14/1/2004
Time: 10:29:20
User: N/A
Computer: MySQLName
Description:
18204 :
BackupTapeFile::OpenMedia: Backup device '\\.\Tape0'
failed to open. Operating system error = 5(Access is
denied.).
If I try do it using OSQL (I want to do using OSQL), the
same error is logged on Event Viewer.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I try use the Administrator user, but I get the same error.
I can do the backup to disk normally, but I need to do to
tape.
Can any one help me to solve this problem?
Thank you.Can't say I've tried backing up to tape directly.
Can you not backup to file & then backup to tape using NT Backup or similar?
I prefer to backup to file initially because it means I can normally restore
from file which is much faster than tape. Only if something goes wrong with
the file or server itself do I need to resort to the tape...
It sounds like it cannot find the media. Is the correct media inserted, with
the correct name?
Can you backup to this tape through NT backup or similar to verify it is
related to SQL Server & not Windows?
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||I need backup database directly to tape.
I'm using a tape that never was used and another tape,
that was used by NTBACKUP. I see the same error with
everyone.
I can use NTBACKUP to backup files to tape without
problems.
>--Original Message--
>Can't say I've tried backing up to tape directly.
>Can you not backup to file & then backup to tape using NT
Backup or similar?
>I prefer to backup to file initially because it means I
can normally restore
>from file which is much faster than tape. Only if
something goes wrong with
>the file or server itself do I need to resort to the
tape...
>It sounds like it cannot find the media. Is the correct
media inserted, with
>the correct name?
>Can you backup to this tape through NT backup or similar
to verify it is
>related to SQL Server & not Windows?
>
>--
>Cheers,
>
>James Goodman MCSE, MCDBA
>http://www.angelfire.com/sports/f1pictures
>
>.
>|||I found the solution for my problem.
There is some pre-requisites to run/install SQL Server. If
SQL Server services are running with a Domain User
Account, this account must be member of Administrators or
Power Users group. I put the account that are running the
services in Administrators group and my problem was
solved. This pre-requisite is documented in SQL Server
Books On Line.
>--Original Message--
>I am trying to backup a database to tape. I'm using
>Microsoft SQL Server 2000 Enterprise Edition and Windows
>Server 2003.
>When I try to do the backup using Enterprise Manager I
see
>the following message:
>Microsoft SQL-DMO (ODBC SQLState: 42000)
>Cannot open backup device '\\.\Tape0'. Device error or
>device off-line. See the SQL Server error log for more
>details.
>BACKUP DATABASE is terminating abnormally.
>
>In the Event Viewer is logged the following message:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 14/1/2004
>Time: 10:29:20
>User: N/A
>Computer: MySQLName
>Description:
>18204 :
>BackupTapeFile::OpenMedia: Backup device '\\.\Tape0'
>failed to open. Operating system error = 5(Access is
>denied.).
>If I try do it using OSQL (I want to do using OSQL), the
>same error is logged on Event Viewer.
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>I try use the Administrator user, but I get the same
error.
>I can do the backup to disk normally, but I need to do to
>tape.
>Can any one help me to solve this problem?
>Thank you.
>.
>
Microsoft SQL Server 2000 Enterprise Edition and Windows
Server 2003.
When I try to do the backup using Enterprise Manager I see
the following message:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Cannot open backup device '\\.\Tape0'. Device error or
device off-line. See the SQL Server error log for more
details.
BACKUP DATABASE is terminating abnormally.
In the Event Viewer is logged the following message:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 14/1/2004
Time: 10:29:20
User: N/A
Computer: MySQLName
Description:
18204 :
BackupTapeFile::OpenMedia: Backup device '\\.\Tape0'
failed to open. Operating system error = 5(Access is
denied.).
If I try do it using OSQL (I want to do using OSQL), the
same error is logged on Event Viewer.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I try use the Administrator user, but I get the same error.
I can do the backup to disk normally, but I need to do to
tape.
Can any one help me to solve this problem?
Thank you.Can't say I've tried backing up to tape directly.
Can you not backup to file & then backup to tape using NT Backup or similar?
I prefer to backup to file initially because it means I can normally restore
from file which is much faster than tape. Only if something goes wrong with
the file or server itself do I need to resort to the tape...
It sounds like it cannot find the media. Is the correct media inserted, with
the correct name?
Can you backup to this tape through NT backup or similar to verify it is
related to SQL Server & not Windows?
Cheers,
James Goodman MCSE, MCDBA
http://www.angelfire.com/sports/f1pictures|||I need backup database directly to tape.
I'm using a tape that never was used and another tape,
that was used by NTBACKUP. I see the same error with
everyone.
I can use NTBACKUP to backup files to tape without
problems.
>--Original Message--
>Can't say I've tried backing up to tape directly.
>Can you not backup to file & then backup to tape using NT
Backup or similar?
>I prefer to backup to file initially because it means I
can normally restore
>from file which is much faster than tape. Only if
something goes wrong with
>the file or server itself do I need to resort to the
tape...
>It sounds like it cannot find the media. Is the correct
media inserted, with
>the correct name?
>Can you backup to this tape through NT backup or similar
to verify it is
>related to SQL Server & not Windows?
>
>--
>Cheers,
>
>James Goodman MCSE, MCDBA
>http://www.angelfire.com/sports/f1pictures
>
>.
>|||I found the solution for my problem.
There is some pre-requisites to run/install SQL Server. If
SQL Server services are running with a Domain User
Account, this account must be member of Administrators or
Power Users group. I put the account that are running the
services in Administrators group and my problem was
solved. This pre-requisite is documented in SQL Server
Books On Line.
>--Original Message--
>I am trying to backup a database to tape. I'm using
>Microsoft SQL Server 2000 Enterprise Edition and Windows
>Server 2003.
>When I try to do the backup using Enterprise Manager I
see
>the following message:
>Microsoft SQL-DMO (ODBC SQLState: 42000)
>Cannot open backup device '\\.\Tape0'. Device error or
>device off-line. See the SQL Server error log for more
>details.
>BACKUP DATABASE is terminating abnormally.
>
>In the Event Viewer is logged the following message:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 14/1/2004
>Time: 10:29:20
>User: N/A
>Computer: MySQLName
>Description:
>18204 :
>BackupTapeFile::OpenMedia: Backup device '\\.\Tape0'
>failed to open. Operating system error = 5(Access is
>denied.).
>If I try do it using OSQL (I want to do using OSQL), the
>same error is logged on Event Viewer.
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>I try use the Administrator user, but I get the same
error.
>I can do the backup to disk normally, but I need to do to
>tape.
>Can any one help me to solve this problem?
>Thank you.
>.
>
Subscribe to:
Posts (Atom)