Backup File I/o Error

Guys,

Apologies if this is in the wrong section. I have a SQL 2000 database which I backup to a folder on the hard disk using the following command in a Server Agent:

BACKUP DATABASE [Multilog] TO DISK = N'C:\MSSQL7\BACKUP\multilog_backup' WITH INIT , NOUNLOAD , NAME = N'Multilog backup', NOSKIP , STATS = 10, NOFORMAT

Recently it has been failing with the following error message:

Nonrecoverable I/O error occurred on file 'C:\Multilog Database Files\Data\MultiLog_data.MDF'. [SQLSTATE 42000] (Error 3271) Backup or restore operation terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

Any idea what could be causing this?

Any help would be greatly appreciated.

Sean.

Try some of the method(s) in the following kb:

http://support.microsoft.com/default.aspx/kb/904804

Is this an SP4 server? Looks like it may have been upgraded from SQL 7.0, is that correct?

|||

Chad,

Just noticed the following error on the logs:

I/O error 23(Data error (cyclic redundancy check).) detected during read of BUF pointer = 0x14243d80, page ptr = 0x1607c000, pageid = (0x1:0x1ae), dbid = 5, status = 0x801, file = C:\Multilog Database Files\Data\MultiLog_data.MDF..

Would this indicate a fault with the actual database file? Any idea what could be done to check and fix?

|||

Yeah, that would indicate a data integrity issue within your DB file. Try running a DBCC CHECKDB on the database in question and see what you get for output. Depending on the output of that, you could try using the FIX options with the CHECKDB command, rebuilding indexes, etc.

Backup failure

All,
I am receiving the following error when I try to backup to tape from SQL using backup under the Management folder in Enterprise manager. Logged in as administrator. Can backup the pubs, Northwind and master databases with no problem.
The database is approx. 8.5GB and the tape can hold 40GB formatted. Using option to overwrite and initialize.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log for more details, backup database is terminating abnormally.
In the error log;
Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size: 65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000, offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536, m_actualbytes: 65536, m_errcode: 1117, b
ackupfile: \\.\Tape0
Any thought would be appreciated.
Regards,
Dave
can you back it up to disk instead of to tape?
can you backup a large file from disk to tape?
I will do it this way because backup done faster and eliminating the hassle
of dealing with the tape drive.
my 0.02
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:C1CCFEFC-AD93-4715-919F-C468273BD974@.microsoft.com...
> All,
> I am receiving the following error when I try to backup to tape from SQL
using backup under the Management folder in Enterprise manager. Logged in as
administrator. Can backup the pubs, Northwind and master databases with no
problem.
> The database is approx. 8.5GB and the tape can hold 40GB formatted. Using
option to overwrite and initialize.
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log
for more details, backup database is terminating abnormally.
> In the error log;
> Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size:
65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000,
offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536,
m_actualbytes: 65536, m_errcode: 1117, backupfile: \\.\Tape0
> Any thought would be appreciated.
> Regards,
> Dave

Backup failure

All,
I am receiving the following error when I try to backup to tape from SQL usi
ng backup under the Management folder in Enterprise manager. Logged in as ad
ministrator. Can backup the pubs, Northwind and master databases with no pro
blem.
The database is approx. 8.5GB and the tape can hold 40GB formatted. Using op
tion to overwrite and initialize.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log for
more details, backup database is terminating abnormally.
In the error log;
Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size: 65536,
position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000, offse
t: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536, m_actualbytes
: 65536, m_errcode: 1117, b
ackupfile: \\.\Tape0
Any thought would be appreciated.
Regards,
Davecan you back it up to disk instead of to tape?
can you backup a large file from disk to tape?
I will do it this way because backup done faster and eliminating the hassle
of dealing with the tape drive.
my 0.02
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:C1CCFEFC-AD93-4715-919F-C468273BD974@.microsoft.com...
> All,
> I am receiving the following error when I try to backup to tape from SQL
using backup under the Management folder in Enterprise manager. Logged in as
administrator. Can backup the pubs, Northwind and master databases with no
problem.
> The database is approx. 8.5GB and the tape can hold 40GB formatted. Using
option to overwrite and initialize.
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log
for more details, backup database is terminating abnormally.
> In the error log;
> Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size:
65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000,
offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536,
m_actualbytes: 65536, m_errcode: 1117, backupfile: \\.\Tape0
> Any thought would be appreciated.
> Regards,
> Davesql

backup failure

Hi
My DB backup and transaction backup of a database keep on failing with
the following error:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on
'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Any idea what it really means ?
Thanks
DavidYou can get the description of Win32 error codes with NET HELPMSG from a
command prompt:

NET HELPMSG 112

Yields:

There is not enough space on the disk.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"David Greenberg" <davidgr@.iba.org.il> wrote in message
news:444B9239.2010804@.iba.org.il...
> Hi
> My DB backup and transaction backup of a database keep on failing with the
> following error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Write on
> 'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
> SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> Any idea what it really means ?
> Thanks
> David

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
DaveIn order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
Dave
In order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =
10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =
10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
DaveIn order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =
10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =
10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup Fails When DB is Large (2.2 gigs)

I have many databases that I can backup just fine on my SQL Server. However, there is one database that I cannot backup without the following message:
"backup database is terminating abnormally".
The strange thing is that the database really does get backed up despite the messages; I've even done restores from the backup.
When I checked the event log, there are two errors.
ONE:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/25/2003
Time: 08:23:59
User: MARIN\aaronosheroff
Computer: IS-DBS2
Description:
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '\\Ivcserv1
\SqlServerBackups\HP_STUREC_MCC_CES.BAK'. Operating system error 64(The specified network name is no longer available.).
Data:
0000: 22 47 00 00 10 00 00 00 "G.....
0008: 08 00 00 00 49 00 53 00 ...I.S.
0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
0018: 32 00 00 00 00 00 00 00 2......
and TWO:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 17055
Date: 8/25/2003
Time: 08:23:59
User: MARIN\aaronosheroff
Computer: IS-DBS2
Description:
3041 :
BACKUP failed to complete the command BACKUP DATABASE [HP_STUREC_MCC_CES] TO DISK =3D N'\\Ivcserv1
\SqlServerBackups\HP_STUREC_MCC_CES.BAK' WITH INIT , NOUNLOAD , NAME =3D N'HP_STUREC_MCC_CES backup', NOSKIP , STATS =3D 10, NOFORMAT Data:
0000: e1 0b 00 00 10 00 00 00 =E1......
0008: 08 00 00 00 49 00 53 00 ...I.S.
0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
0018: 32 00 00 00 00 00 00 00 2......
Can someone help me out here? Thanks...
.Thanks for the post, but this is not the problem...
>--Original Message--
>does the network share exist? See if you can run
>BACKUP DATABASE [HP_STUREC_MCC_CES] TO DISK =3D 'c:\mybakup.bak'
>"Aaron" <aaron.osheroff@.marin.cc.ca.us> wrote in message
>news:064101c36b45$8a492230$a101280a@.phx.gbl...
>I have many databases that I can backup just fine on my
>SQL Server. However, there is one database that I cannot
>backup without the following message:
>"backup database is terminating abnormally".
>The strange thing is that the database really does get
>backed up despite the messages; I've even done restores
>from the backup.
>When I checked the event log, there are two errors.
>ONE:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 8/25/2003
>Time: 08:23:59
>User: MARIN\aaronosheroff
>Computer: IS-DBS2
>Description:
>18210 :
>BackupDiskFile::RequestDurableMedia: failure on backup
>device '\\Ivcserv1
>\SqlServerBackups\HP_STUREC_MCC_CES.BAK'. Operating system
>error 64(The specified network name is no longer
>available.).
>Data:
>0000: 22 47 00 00 10 00 00 00 "G.....
>0008: 08 00 00 00 49 00 53 00 ...I.S.
>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>0018: 32 00 00 00 00 00 00 00 2......
>and TWO:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (6)
>Event ID: 17055
>Date: 8/25/2003
>Time: 08:23:59
>User: MARIN\aaronosheroff
>Computer: IS-DBS2
>Description:
>3041 :
>BACKUP failed to complete the command BACKUP DATABASE
>[HP_STUREC_MCC_CES] TO DISK =3D N'\\Ivcserv1
>\SqlServerBackups\HP_STUREC_MCC_CES.BAK' WITH INIT ,
>NOUNLOAD , NAME =3D N'HP_STUREC_MCC_CES backup', NOSKIP ,
>STATS =3D 10, NOFORMAT
>Data:
>0000: e1 0b 00 00 10 00 00 00 =E1......
>0008: 08 00 00 00 49 00 53 00 ...I.S.
>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>0018: 32 00 00 00 00 00 00 00 2......
>Can someone help me out here? Thanks...
>
>
>..
>
>.
>|||normally this seems to be a network issue.
>--Original Message--
>Thanks for the post, but this is not the problem...
>
>>--Original Message--
>>does the network share exist? See if you can run
>>BACKUP DATABASE [HP_STUREC_MCC_CES] TO DISK >=3D 'c:\mybakup.bak'
>>"Aaron" <aaron.osheroff@.marin.cc.ca.us> wrote in message
>>news:064101c36b45$8a492230$a101280a@.phx.gbl...
>>I have many databases that I can backup just fine on my
>>SQL Server. However, there is one database that I cannot
>>backup without the following message:
>>"backup database is terminating abnormally".
>>The strange thing is that the database really does get
>>backed up despite the messages; I've even done restores
>>from the backup.
>>When I checked the event log, there are two errors.
>>ONE:
>>Event Type: Error
>>Event Source: MSSQLSERVER
>>Event Category: (2)
>>Event ID: 17055
>>Date: 8/25/2003
>>Time: 08:23:59
>>User: MARIN\aaronosheroff
>>Computer: IS-DBS2
>>Description:
>>18210 :
>>BackupDiskFile::RequestDurableMedia: failure on backup
>>device '\\Ivcserv1
>>\SqlServerBackups\HP_STUREC_MCC_CES.BAK'. Operating system
>>error 64(The specified network name is no longer
>>available.).
>>Data:
>>0000: 22 47 00 00 10 00 00 00 "G.....
>>0008: 08 00 00 00 49 00 53 00 ...I.S.
>>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>>0018: 32 00 00 00 00 00 00 00 2......
>>and TWO:
>>Event Type: Error
>>Event Source: MSSQLSERVER
>>Event Category: (6)
>>Event ID: 17055
>>Date: 8/25/2003
>>Time: 08:23:59
>>User: MARIN\aaronosheroff
>>Computer: IS-DBS2
>>Description:
>>3041 :
>>BACKUP failed to complete the command BACKUP DATABASE
>>[HP_STUREC_MCC_CES] TO DISK =3D N'\\Ivcserv1
>>\SqlServerBackups\HP_STUREC_MCC_CES.BAK' WITH INIT ,
>>NOUNLOAD , NAME =3D N'HP_STUREC_MCC_CES backup', NOSKIP ,
>>STATS =3D 10, NOFORMAT
>>Data:
>>0000: e1 0b 00 00 10 00 00 00 =E1......
>>0008: 08 00 00 00 49 00 53 00 ...I.S.
>>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>>0018: 32 00 00 00 00 00 00 00 2......
>>Can someone help me out here? Thanks...
>>
>>
>>..
>>
>>.
>.
>|||yeah, I missed the fact that you can backup even SQL shows error messages.
"Aaron" <aaron.osheroff@.marin.cc.ca.us> wrote in message
news:06fb01c36b4e$3bde2060$a101280a@.phx.gbl...
Thanks for the post, but this is not the problem...
>--Original Message--
>does the network share exist? See if you can run
>BACKUP DATABASE [HP_STUREC_MCC_CES] TO DISK
= 'c:\mybakup.bak'
>"Aaron" <aaron.osheroff@.marin.cc.ca.us> wrote in message
>news:064101c36b45$8a492230$a101280a@.phx.gbl...
>I have many databases that I can backup just fine on my
>SQL Server. However, there is one database that I cannot
>backup without the following message:
>"backup database is terminating abnormally".
>The strange thing is that the database really does get
>backed up despite the messages; I've even done restores
>from the backup.
>When I checked the event log, there are two errors.
>ONE:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 8/25/2003
>Time: 08:23:59
>User: MARIN\aaronosheroff
>Computer: IS-DBS2
>Description:
>18210 :
>BackupDiskFile::RequestDurableMedia: failure on backup
>device '\\Ivcserv1
>\SqlServerBackups\HP_STUREC_MCC_CES.BAK'. Operating system
>error 64(The specified network name is no longer
>available.).
>Data:
>0000: 22 47 00 00 10 00 00 00 "G.....
>0008: 08 00 00 00 49 00 53 00 ...I.S.
>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>0018: 32 00 00 00 00 00 00 00 2......
>and TWO:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (6)
>Event ID: 17055
>Date: 8/25/2003
>Time: 08:23:59
>User: MARIN\aaronosheroff
>Computer: IS-DBS2
>Description:
>3041 :
>BACKUP failed to complete the command BACKUP DATABASE
>[HP_STUREC_MCC_CES] TO DISK = N'\\Ivcserv1
>\SqlServerBackups\HP_STUREC_MCC_CES.BAK' WITH INIT ,
>NOUNLOAD , NAME = N'HP_STUREC_MCC_CES backup', NOSKIP ,
>STATS = 10, NOFORMAT
>Data:
>0000: e1 0b 00 00 10 00 00 00 á......
>0008: 08 00 00 00 49 00 53 00 ...I.S.
>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>0018: 32 00 00 00 00 00 00 00 2......
>Can someone help me out here? Thanks...
>
>
>..
>
>.
>|||Thank you!!! This works!
>--Original Message--
>If it works locally then would an option not be to back up locally and then
>move the backup file to the network share ? This would be quicker and
>probably less error prone. This is assuming you have the required local
>diskspace.
>-- >HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Aaron" <aaron.osheroff@.marin.cc.ca.us> wrote in message
>news:064101c36b45$8a492230$a101280a@.phx.gbl...
>I have many databases that I can backup just fine on my
>SQL Server. However, there is one database that I cannot
>backup without the following message:
>"backup database is terminating abnormally".
>The strange thing is that the database really does get
>backed up despite the messages; I've even done restores
>from the backup.
>When I checked the event log, there are two errors.
>ONE:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 8/25/2003
>Time: 08:23:59
>User: MARIN\aaronosheroff
>Computer: IS-DBS2
>Description:
>18210 :
>BackupDiskFile::RequestDurableMedia: failure on backup
>device '\\Ivcserv1
>\SqlServerBackups\HP_STUREC_MCC_CES.BAK'. Operating system
>error 64(The specified network name is no longer
>available.).
>Data:
>0000: 22 47 00 00 10 00 00 00 "G.....
>0008: 08 00 00 00 49 00 53 00 ...I.S.
>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>0018: 32 00 00 00 00 00 00 00 2......
>and TWO:
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (6)
>Event ID: 17055
>Date: 8/25/2003
>Time: 08:23:59
>User: MARIN\aaronosheroff
>Computer: IS-DBS2
>Description:
>3041 :
>BACKUP failed to complete the command BACKUP DATABASE
>[HP_STUREC_MCC_CES] TO DISK =3D N'\\Ivcserv1
>\SqlServerBackups\HP_STUREC_MCC_CES.BAK' WITH INIT ,
>NOUNLOAD , NAME =3D N'HP_STUREC_MCC_CES backup', NOSKIP ,
>STATS =3D 10, NOFORMAT
>Data:
>0000: e1 0b 00 00 10 00 00 00 =E1......
>0008: 08 00 00 00 49 00 53 00 ...I.S.
>0010: 2d 00 44 00 42 00 53 00 -.D.B.S.
>0018: 32 00 00 00 00 00 00 00 2......
>Can someone help me out here? Thanks...
>
>
>..
>
>.
>|||The company were I work is ecperiencing the exact same error message
backing up our 30GB SQL Database. Backing up locally then transferring
to a network drive is not an option. Has anyone successfully resolved
this problem.
Thank you.
Posted via http://dbforums.com|||Amang,
I dont know if its a problem with my newsreader, but I dont see any error
description or the original post contents.What is the error that you are
facing?
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"amang" <member38559@.dbforums.com> wrote in message
news:3343101.1063031172@.dbforums.com...
> The company were I work is ecperiencing the exact same error message
> backing up our 30GB SQL Database. Backing up locally then transferring
> to a network drive is not an option. Has anyone successfully resolved
> this problem.
>
> Thank you.
>
> --
> Posted via http://dbforums.com

BACKUP failing! HELP!

I'm trying to backup a SQL 7.0 database to a network server (NT) from
Enterprise Manager and am getting the following error:

Title bar: Microsoft SQL DMO (ODBC SQL State: 42000)
Message: Backup or restore operation terminating abnormally.

The SQL Log has the following message:
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\myserver\bu_sql$\bu_mydb1.bak'. Operating system error 64(The
specified network name is no longer available.).

When I run a scheduled job that backs up mydb1, it fails with the
following message: Processed 50968 pages for database 'mydb1', file
'mydb1_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1
pages for database 'mydb1', file 'mydb1_Log' on file 1. [SQLSTATE
01000] (Message 4035) Backup or restore operation terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

This appears to a network problem but the transaction log dumps from
the same database to the same network share work fine as does a full
backup of a different database (on the same SQL Server).

The file bu_mydb1.bak is being created on the network drive. The
network drive has plenty of available space. The file is only 423MB
and the share has 9GB free space.

Any ideas?jeff.strange@.lrc.state.ky.us (Jeff) wrote in message news:<7dafc839.0401130705.1dc48e96@.posting.google.com>...
> I'm trying to backup a SQL 7.0 database to a network server (NT) from
> Enterprise Manager and am getting the following error:
> Title bar: Microsoft SQL DMO (ODBC SQL State: 42000)
> Message: Backup or restore operation terminating abnormally.
> The SQL Log has the following message:
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\myserver\bu_sql$\bu_mydb1.bak'. Operating system error 64(The
> specified network name is no longer available.).
> When I run a scheduled job that backs up mydb1, it fails with the
> following message: Processed 50968 pages for database 'mydb1', file
> 'mydb1_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1
> pages for database 'mydb1', file 'mydb1_Log' on file 1. [SQLSTATE
> 01000] (Message 4035) Backup or restore operation terminating
> abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

There is an MS document that says your destination/remote server 'is
under stress' and you are getting i.o hits, based on error 3013. You
might look at the scheduling of the backup job.

The 3013 error says your remote disk drive 'is user stress'.
Basically, it is a timing/timeout because of the amount of disk
activity on the remote server.
> This appears to a network problem but the transaction log dumps from
> the same database to the same network share work fine as does a full
> backup of a different database (on the same SQL Server).
> The file bu_mydb1.bak is being created on the network drive. The
> network drive has plenty of available space. The file is only 423MB
> and the share has 9GB free space.
> Any ideas?

backup faild to VDM

I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
am getting the following failure any idea.
2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
on backup device
'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArch ive\MercuryArchive.bak'.
Operating system error 64(The specified network name is no longer
available.).
2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchi ve\MercuryArchive.bak
The connection to the backup server is dropping. It could be
a lot of things - the size of the backup file makes a
difference - large backup files can be problematic, the
hardware involved may not be able to handle the load of the
backup, if the destination is having resource issues you can
hit this error, or if you just have something unstable in
network mix, you can get dropped connections in general.
If you have the space and it's SQL Server having the problem
writing the backup across the network, you could try backing
up locally and then do a copy of the backup over to the
network location.
-Sue
On Mon, 2 Apr 2007 09:02:41 -0700, <msnews.microsoft.com>
wrote:

>I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
>am getting the following failure any idea.
>
>2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
>on backup device
>'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArc hive\MercuryArchive.bak'.
>Operating system error 64(The specified network name is no longer
>available.).
>2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
>pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
>0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
>0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
>\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArch ive\MercuryArchive.bak
>

backup faild to VDM

I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
am getting the following failure any idea.
2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
on backup device
'\\Na00vdmdba01\ProductionBackup\PSSQL\M
ercuryArchive\MercuryArchive.bak'.
Operating system error 64(The specified network name is no longer
available.).
2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Na00vdmdba01\ProductionBackup\PSSQL\Me
rcuryArchive\MercuryArchive.bakThe connection to the backup server is dropping. It could be
a lot of things - the size of the backup file makes a
difference - large backup files can be problematic, the
hardware involved may not be able to handle the load of the
backup, if the destination is having resource issues you can
hit this error, or if you just have something unstable in
network mix, you can get dropped connections in general.
If you have the space and it's SQL Server having the problem
writing the backup across the network, you could try backing
up locally and then do a copy of the backup over to the
network location.
-Sue
On Mon, 2 Apr 2007 09:02:41 -0700, <msnews.microsoft.com>
wrote:

>I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
>am getting the following failure any idea.
>
>2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
>on backup device
> '\\Na00vdmdba01\ProductionBackup\PSSQL\M
ercuryArchive\MercuryArchive.bak'.
>Operating system error 64(The specified network name is no longer
>available.).
>2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write
,
>pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
>0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
>0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\Na00vdmdba01\ProductionBackup\PSSQL\Me
rcuryArchive\MercuryArchive.bak
>

backup faild to VDM

I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
am getting the following failure any idea.
2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
on backup device
'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bak'.
Operating system error 64(The specified network name is no longer
available.).
2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bakThe connection to the backup server is dropping. It could be
a lot of things - the size of the backup file makes a
difference - large backup files can be problematic, the
hardware involved may not be able to handle the load of the
backup, if the destination is having resource issues you can
hit this error, or if you just have something unstable in
network mix, you can get dropped connections in general.
If you have the space and it's SQL Server having the problem
writing the backup across the network, you could try backing
up locally and then do a copy of the backup over to the
network location.
-Sue
On Mon, 2 Apr 2007 09:02:41 -0700, <msnews.microsoft.com>
wrote:
>I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
>am getting the following failure any idea.
>
>2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
>on backup device
>'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bak'.
>Operating system error 64(The specified network name is no longer
>available.).
>2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
>pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
>0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
>0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
>\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bak
>sql

Backup Error: sql-dom sql state 4200

When trying to backup a sql2000 database I receive the following error:
"Microsoft SQL-DOM (odbc sqlstate: 42000)
The Volume on device xxx e:\backupfilename.bak belongs to a different media set.
Backup or restore operation terminating abnormally."
Thanks for any help,
JimIf you have no use for the existing backup file, you could
either delete the file from the file system before doing
the backup or add the FORMAT option to the BACKUP
statement.
Linchi
>--Original Message--
>When trying to backup a sql2000 database I receive the
following error:
>"Microsoft SQL-DOM (odbc sqlstate: 42000)
>The Volume on device xxx e:\backupfilename.bak belongs to
a different media set.
>Backup or restore operation terminating abnormally."
>Thanks for any help,
>Jim
>
>.
>

Backup Error

After applying Win2K SP3 earlier this month, our Veritas
tape backups started failing with the following errors:
BackupMedium::ReportIoError: write failure on backup
device 'VNBU0-2000-2912'. Operating system error 995(The
I/O operation has been aborted because of either a thread
exit or an application request.).
Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
0x28A70200, Size: 512, Position: 0, UMS: Internal:
0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
m_errcode: 995, BackupFile: VNBU0-2000-2912
I also started getting the following error reported around
the same time of day:
The SQL Server cannot obtain a LOCK resource at this time.
Rerun your statement when there are fewer active users or
ask the system administrator to check the SQL Server lock
and memory configuration..
I am able to do a regular dump to disk with no errors.
Any ideas on resolution here?
Thanks for your time.
MilesI think veritas.com will have more helpful info.
Are you using BackupExec to backup SQL databases?
"Miles" <miles.schor@.echostar.com> wrote in message
news:016b01c36742$ecf70520$a401280a@.phx.gbl...
> After applying Win2K SP3 earlier this month, our Veritas
> tape backups started failing with the following errors:
> BackupMedium::ReportIoError: write failure on backup
> device 'VNBU0-2000-2912'. Operating system error 995(The
> I/O operation has been aborted because of either a thread
> exit or an application request.).
> Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
> 0x28A70200, Size: 512, Position: 0, UMS: Internal:
> 0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
> 0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
> m_errcode: 995, BackupFile: VNBU0-2000-2912
> I also started getting the following error reported around
> the same time of day:
> The SQL Server cannot obtain a LOCK resource at this time.
> Rerun your statement when there are fewer active users or
> ask the system administrator to check the SQL Server lock
> and memory configuration..
> I am able to do a regular dump to disk with no errors.
> Any ideas on resolution here?
> Thanks for your time.
> Miles

Backup error

When I run the following SQL, either from VB 2005 or directly in SSMS, I get
the subsequent error:
BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
Msg 3271, Level 16, State 1, Line 1
A nonrecoverable I/O error occurred on file "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient system
resources exist to complete the requested service.).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
I'm running Windows XP Professional SP2 with the lastest updates, SQL Server
2005 v. 9.00.3054.00 (which I believe is the latest version), a PC with
dual-core extreme processor with 4GB of memory (although I understand not of
it may be available to XP), and I have plenty of hard drive capacity
available. The file I'm backing up is almost 2.5GB in size. The backup
command worked this morning, although I have received this error a couple
times in the past and shut down various programs and tried again and it
worked. This time I can't seem to get it to work at all. I definitely need
to backup this file! What do I need to do to get it to work? (Note:
Curiously, the error command references subfolder MSSQL.1 even though I'm
trying to back up to MSSQL.2).
Also, why can't I just copy the file
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
to make my backup instead of running the backup command? I've tried this in
the past but I couldn't restore it. Apparently some other files would have
to be copies as well?
--
EdEd,
I am not sure why you are getting the error (maybe the swap file isn't large
enough) but one thing you can do until you get it resolved is to detach the
database wither with SSMS or sp_detach_db. Then you can copy the .mdf & .ldf
files (and any others if there are any) somewhere with windows explorer.
Then you can attach the db back again and do the same with the detached copy
in place of a restore if needed.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed White" <ewhite@.newsgroups.nospam> wrote in message
news:E13A0680-D110-4EB3-8B96-0102120AF59A@.microsoft.com...
> When I run the following SQL, either from VB 2005 or directly in SSMS, I
> get
> the subsequent error:
> BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
> Msg 3271, Level 16, State 1, Line 1
> A nonrecoverable I/O error occurred on file "C:\Program Files\Microsoft
> SQL
> Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient system
> resources exist to complete the requested service.).
> Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> I'm running Windows XP Professional SP2 with the lastest updates, SQL
> Server
> 2005 v. 9.00.3054.00 (which I believe is the latest version), a PC with
> dual-core extreme processor with 4GB of memory (although I understand not
> of
> it may be available to XP), and I have plenty of hard drive capacity
> available. The file I'm backing up is almost 2.5GB in size. The backup
> command worked this morning, although I have received this error a couple
> times in the past and shut down various programs and tried again and it
> worked. This time I can't seem to get it to work at all. I definitely
> need
> to backup this file! What do I need to do to get it to work? (Note:
> Curiously, the error command references subfolder MSSQL.1 even though I'm
> trying to back up to MSSQL.2).
> Also, why can't I just copy the file
> C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
> to make my backup instead of running the backup command? I've tried this
> in
> the past but I couldn't restore it. Apparently some other files would
> have
> to be copies as well?
> --
> Ed|||I still occasionally get the error using the SQL, and the only way to avoid
it is to reboot and try again, which usually works.
Couple of question about Detach and Attach:
When I Detach and then re-Attach, after Attach a message appears:
"The dependent aliases were dropped."
What does this mean? What are "dependent aliases"?
Also, which files in all do I need to copy to backup? Just the ...DBSQL.mdf
and the ...DBSQL_log.ldf, or are there others?
--
Ed
"Andrew J. Kelly" wrote:
> Ed,
> I am not sure why you are getting the error (maybe the swap file isn't large
> enough) but one thing you can do until you get it resolved is to detach the
> database wither with SSMS or sp_detach_db. Then you can copy the .mdf & .ldf
> files (and any others if there are any) somewhere with windows explorer.
> Then you can attach the db back again and do the same with the detached copy
> in place of a restore if needed.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
> news:E13A0680-D110-4EB3-8B96-0102120AF59A@.microsoft.com...
> > When I run the following SQL, either from VB 2005 or directly in SSMS, I
> > get
> > the subsequent error:
> >
> > BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
> >
> > Msg 3271, Level 16, State 1, Line 1
> > A nonrecoverable I/O error occurred on file "C:\Program Files\Microsoft
> > SQL
> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient system
> > resources exist to complete the requested service.).
> > Msg 3013, Level 16, State 1, Line 1
> > BACKUP DATABASE is terminating abnormally.
> >
> > I'm running Windows XP Professional SP2 with the lastest updates, SQL
> > Server
> > 2005 v. 9.00.3054.00 (which I believe is the latest version), a PC with
> > dual-core extreme processor with 4GB of memory (although I understand not
> > of
> > it may be available to XP), and I have plenty of hard drive capacity
> > available. The file I'm backing up is almost 2.5GB in size. The backup
> > command worked this morning, although I have received this error a couple
> > times in the past and shut down various programs and tried again and it
> > worked. This time I can't seem to get it to work at all. I definitely
> > need
> > to backup this file! What do I need to do to get it to work? (Note:
> > Curiously, the error command references subfolder MSSQL.1 even though I'm
> > trying to back up to MSSQL.2).
> >
> > Also, why can't I just copy the file
> >
> > C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
> >
> > to make my backup instead of running the backup command? I've tried this
> > in
> > the past but I couldn't restore it. Apparently some other files would
> > have
> > to be copies as well?
> > --
> > Ed
>|||I am not sure what the "dependent aliases " means for sure but someone
probably setup a database alias that is no longer useful when you drop or
detach the database. How many files depends on how the database was created
or altered. By default there are only 2 files. xxx.mdf and xxx.ldf. But you
can have secondary data files usually with the extension of .ndf and
secondary log files with .ldf as well. If you run sp_helpdb it should show
all the files.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed White" <ewhite@.newsgroups.nospam> wrote in message
news:5D97496D-11BA-4ACC-BCA9-0A3101355C8A@.microsoft.com...
>I still occasionally get the error using the SQL, and the only way to avoid
> it is to reboot and try again, which usually works.
> Couple of question about Detach and Attach:
> When I Detach and then re-Attach, after Attach a message appears:
> "The dependent aliases were dropped."
> What does this mean? What are "dependent aliases"?
> Also, which files in all do I need to copy to backup? Just the
> ...DBSQL.mdf
> and the ...DBSQL_log.ldf, or are there others?
> --
> Ed
>
> "Andrew J. Kelly" wrote:
>> Ed,
>> I am not sure why you are getting the error (maybe the swap file isn't
>> large
>> enough) but one thing you can do until you get it resolved is to detach
>> the
>> database wither with SSMS or sp_detach_db. Then you can copy the .mdf &
>> .ldf
>> files (and any others if there are any) somewhere with windows explorer.
>> Then you can attach the db back again and do the same with the detached
>> copy
>> in place of a restore if needed.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
>> news:E13A0680-D110-4EB3-8B96-0102120AF59A@.microsoft.com...
>> > When I run the following SQL, either from VB 2005 or directly in SSMS,
>> > I
>> > get
>> > the subsequent error:
>> >
>> > BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft SQL
>> > Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
>> >
>> > Msg 3271, Level 16, State 1, Line 1
>> > A nonrecoverable I/O error occurred on file "C:\Program Files\Microsoft
>> > SQL
>> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient system
>> > resources exist to complete the requested service.).
>> > Msg 3013, Level 16, State 1, Line 1
>> > BACKUP DATABASE is terminating abnormally.
>> >
>> > I'm running Windows XP Professional SP2 with the lastest updates, SQL
>> > Server
>> > 2005 v. 9.00.3054.00 (which I believe is the latest version), a PC with
>> > dual-core extreme processor with 4GB of memory (although I understand
>> > not
>> > of
>> > it may be available to XP), and I have plenty of hard drive capacity
>> > available. The file I'm backing up is almost 2.5GB in size. The
>> > backup
>> > command worked this morning, although I have received this error a
>> > couple
>> > times in the past and shut down various programs and tried again and it
>> > worked. This time I can't seem to get it to work at all. I definitely
>> > need
>> > to backup this file! What do I need to do to get it to work? (Note:
>> > Curiously, the error command references subfolder MSSQL.1 even though
>> > I'm
>> > trying to back up to MSSQL.2).
>> >
>> > Also, why can't I just copy the file
>> >
>> > C:\Program Files\Microsoft SQL
>> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
>> >
>> > to make my backup instead of running the backup command? I've tried
>> > this
>> > in
>> > the past but I couldn't restore it. Apparently some other files would
>> > have
>> > to be copies as well?
>> > --
>> > Ed
>>|||"Dependent aliases" could also possible mean logins aliased to some user in the db. This has been
deprecated since 7.0, and the functionality might not even be in 2005.
...just a thought...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23txZDRXMIHA.820@.TK2MSFTNGP06.phx.gbl...
>I am not sure what the "dependent aliases " means for sure but someone probably setup a database
>alias that is no longer useful when you drop or detach the database. How many files depends on how
>the database was created or altered. By default there are only 2 files. xxx.mdf and xxx.ldf. But
>you can have secondary data files usually with the extension of .ndf and secondary log files with
>.ldf as well. If you run sp_helpdb it should show all the files.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
> news:5D97496D-11BA-4ACC-BCA9-0A3101355C8A@.microsoft.com...
>>I still occasionally get the error using the SQL, and the only way to avoid
>> it is to reboot and try again, which usually works.
>> Couple of question about Detach and Attach:
>> When I Detach and then re-Attach, after Attach a message appears:
>> "The dependent aliases were dropped."
>> What does this mean? What are "dependent aliases"?
>> Also, which files in all do I need to copy to backup? Just the ...DBSQL.mdf
>> and the ...DBSQL_log.ldf, or are there others?
>> --
>> Ed
>>
>> "Andrew J. Kelly" wrote:
>> Ed,
>> I am not sure why you are getting the error (maybe the swap file isn't large
>> enough) but one thing you can do until you get it resolved is to detach the
>> database wither with SSMS or sp_detach_db. Then you can copy the .mdf & .ldf
>> files (and any others if there are any) somewhere with windows explorer.
>> Then you can attach the db back again and do the same with the detached copy
>> in place of a restore if needed.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
>> news:E13A0680-D110-4EB3-8B96-0102120AF59A@.microsoft.com...
>> > When I run the following SQL, either from VB 2005 or directly in SSMS, I
>> > get
>> > the subsequent error:
>> >
>> > BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft SQL
>> > Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
>> >
>> > Msg 3271, Level 16, State 1, Line 1
>> > A nonrecoverable I/O error occurred on file "C:\Program Files\Microsoft
>> > SQL
>> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient system
>> > resources exist to complete the requested service.).
>> > Msg 3013, Level 16, State 1, Line 1
>> > BACKUP DATABASE is terminating abnormally.
>> >
>> > I'm running Windows XP Professional SP2 with the lastest updates, SQL
>> > Server
>> > 2005 v. 9.00.3054.00 (which I believe is the latest version), a PC with
>> > dual-core extreme processor with 4GB of memory (although I understand not
>> > of
>> > it may be available to XP), and I have plenty of hard drive capacity
>> > available. The file I'm backing up is almost 2.5GB in size. The backup
>> > command worked this morning, although I have received this error a couple
>> > times in the past and shut down various programs and tried again and it
>> > worked. This time I can't seem to get it to work at all. I definitely
>> > need
>> > to backup this file! What do I need to do to get it to work? (Note:
>> > Curiously, the error command references subfolder MSSQL.1 even though I'm
>> > trying to back up to MSSQL.2).
>> >
>> > Also, why can't I just copy the file
>> >
>> > C:\Program Files\Microsoft SQL
>> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
>> >
>> > to make my backup instead of running the backup command? I've tried this
>> > in
>> > the past but I couldn't restore it. Apparently some other files would
>> > have
>> > to be copies as well?
>> > --
>> > Ed
>>
>|||Are all the files that I need to copy stored in the same folder, i.e.
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
There are also a MSSQL.2, .3, and .4 directories that contain some data. In
the MSSLQ.1\MSSQL\Data folder, I only see the .mdf and _log.ldf files
associated with my database. If there are additional files, would they be in
the same folder or do I need to look elsewhere?
--
Ed
"Andrew J. Kelly" wrote:
> I am not sure what the "dependent aliases " means for sure but someone
> probably setup a database alias that is no longer useful when you drop or
> detach the database. How many files depends on how the database was created
> or altered. By default there are only 2 files. xxx.mdf and xxx.ldf. But you
> can have secondary data files usually with the extension of .ndf and
> secondary log files with .ldf as well. If you run sp_helpdb it should show
> all the files.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
> news:5D97496D-11BA-4ACC-BCA9-0A3101355C8A@.microsoft.com...
> >I still occasionally get the error using the SQL, and the only way to avoid
> > it is to reboot and try again, which usually works.
> >
> > Couple of question about Detach and Attach:
> > When I Detach and then re-Attach, after Attach a message appears:
> > "The dependent aliases were dropped."
> > What does this mean? What are "dependent aliases"?
> >
> > Also, which files in all do I need to copy to backup? Just the
> > ...DBSQL.mdf
> > and the ...DBSQL_log.ldf, or are there others?
> > --
> > Ed
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Ed,
> >>
> >> I am not sure why you are getting the error (maybe the swap file isn't
> >> large
> >> enough) but one thing you can do until you get it resolved is to detach
> >> the
> >> database wither with SSMS or sp_detach_db. Then you can copy the .mdf &
> >> .ldf
> >> files (and any others if there are any) somewhere with windows explorer.
> >> Then you can attach the db back again and do the same with the detached
> >> copy
> >> in place of a restore if needed.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
> >>
> >> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
> >> news:E13A0680-D110-4EB3-8B96-0102120AF59A@.microsoft.com...
> >> > When I run the following SQL, either from VB 2005 or directly in SSMS,
> >> > I
> >> > get
> >> > the subsequent error:
> >> >
> >> > BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft SQL
> >> > Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
> >> >
> >> > Msg 3271, Level 16, State 1, Line 1
> >> > A nonrecoverable I/O error occurred on file "C:\Program Files\Microsoft
> >> > SQL
> >> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient system
> >> > resources exist to complete the requested service.).
> >> > Msg 3013, Level 16, State 1, Line 1
> >> > BACKUP DATABASE is terminating abnormally.
> >> >
> >> > I'm running Windows XP Professional SP2 with the lastest updates, SQL
> >> > Server
> >> > 2005 v. 9.00.3054.00 (which I believe is the latest version), a PC with
> >> > dual-core extreme processor with 4GB of memory (although I understand
> >> > not
> >> > of
> >> > it may be available to XP), and I have plenty of hard drive capacity
> >> > available. The file I'm backing up is almost 2.5GB in size. The
> >> > backup
> >> > command worked this morning, although I have received this error a
> >> > couple
> >> > times in the past and shut down various programs and tried again and it
> >> > worked. This time I can't seem to get it to work at all. I definitely
> >> > need
> >> > to backup this file! What do I need to do to get it to work? (Note:
> >> > Curiously, the error command references subfolder MSSQL.1 even though
> >> > I'm
> >> > trying to back up to MSSQL.2).
> >> >
> >> > Also, why can't I just copy the file
> >> >
> >> > C:\Program Files\Microsoft SQL
> >> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
> >> >
> >> > to make my backup instead of running the backup command? I've tried
> >> > this
> >> > in
> >> > the past but I couldn't restore it. Apparently some other files would
> >> > have
> >> > to be copies as well?
> >> > --
> >> > Ed
> >>
> >>
>|||That depends on where they were put when the db or files were created. By
default they will be there but they don't have to be. The other folders are
for other instances or things like Reporting services or Integration
services etc. If all you care about is that one db then you don't need
anything in the other folders. But I can't say that for sure since I don't
know what they were used for.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed White" <ewhite@.newsgroups.nospam> wrote in message
news:5229C645-EF08-4777-8C12-F5D8E9F9E14D@.microsoft.com...
> Are all the files that I need to copy stored in the same folder, i.e.
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> There are also a MSSQL.2, .3, and .4 directories that contain some data.
> In
> the MSSLQ.1\MSSQL\Data folder, I only see the .mdf and _log.ldf files
> associated with my database. If there are additional files, would they be
> in
> the same folder or do I need to look elsewhere?
> --
> Ed
>
> "Andrew J. Kelly" wrote:
>> I am not sure what the "dependent aliases " means for sure but someone
>> probably setup a database alias that is no longer useful when you drop or
>> detach the database. How many files depends on how the database was
>> created
>> or altered. By default there are only 2 files. xxx.mdf and xxx.ldf. But
>> you
>> can have secondary data files usually with the extension of .ndf and
>> secondary log files with .ldf as well. If you run sp_helpdb it should
>> show
>> all the files.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
>> news:5D97496D-11BA-4ACC-BCA9-0A3101355C8A@.microsoft.com...
>> >I still occasionally get the error using the SQL, and the only way to
>> >avoid
>> > it is to reboot and try again, which usually works.
>> >
>> > Couple of question about Detach and Attach:
>> > When I Detach and then re-Attach, after Attach a message appears:
>> > "The dependent aliases were dropped."
>> > What does this mean? What are "dependent aliases"?
>> >
>> > Also, which files in all do I need to copy to backup? Just the
>> > ...DBSQL.mdf
>> > and the ...DBSQL_log.ldf, or are there others?
>> > --
>> > Ed
>> >
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Ed,
>> >>
>> >> I am not sure why you are getting the error (maybe the swap file isn't
>> >> large
>> >> enough) but one thing you can do until you get it resolved is to
>> >> detach
>> >> the
>> >> database wither with SSMS or sp_detach_db. Then you can copy the .mdf
>> >> &
>> >> .ldf
>> >> files (and any others if there are any) somewhere with windows
>> >> explorer.
>> >> Then you can attach the db back again and do the same with the
>> >> detached
>> >> copy
>> >> in place of a restore if needed.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>> >>
>> >> "Ed White" <ewhite@.newsgroups.nospam> wrote in message
>> >> news:E13A0680-D110-4EB3-8B96-0102120AF59A@.microsoft.com...
>> >> > When I run the following SQL, either from VB 2005 or directly in
>> >> > SSMS,
>> >> > I
>> >> > get
>> >> > the subsequent error:
>> >> >
>> >> > BACKUP DATABASE [Companies DB] TO DISK='C:\Program Files\Microsoft
>> >> > SQL
>> >> > Server\MSSQL.2\MSSQL\Backup\Companies DB.bak'
>> >> >
>> >> > Msg 3271, Level 16, State 1, Line 1
>> >> > A nonrecoverable I/O error occurred on file "C:\Program
>> >> > Files\Microsoft
>> >> > SQL
>> >> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf:" 1450(Insufficient
>> >> > system
>> >> > resources exist to complete the requested service.).
>> >> > Msg 3013, Level 16, State 1, Line 1
>> >> > BACKUP DATABASE is terminating abnormally.
>> >> >
>> >> > I'm running Windows XP Professional SP2 with the lastest updates,
>> >> > SQL
>> >> > Server
>> >> > 2005 v. 9.00.3054.00 (which I believe is the latest version), a PC
>> >> > with
>> >> > dual-core extreme processor with 4GB of memory (although I
>> >> > understand
>> >> > not
>> >> > of
>> >> > it may be available to XP), and I have plenty of hard drive capacity
>> >> > available. The file I'm backing up is almost 2.5GB in size. The
>> >> > backup
>> >> > command worked this morning, although I have received this error a
>> >> > couple
>> >> > times in the past and shut down various programs and tried again and
>> >> > it
>> >> > worked. This time I can't seem to get it to work at all. I
>> >> > definitely
>> >> > need
>> >> > to backup this file! What do I need to do to get it to work?
>> >> > (Note:
>> >> > Curiously, the error command references subfolder MSSQL.1 even
>> >> > though
>> >> > I'm
>> >> > trying to back up to MSSQL.2).
>> >> >
>> >> > Also, why can't I just copy the file
>> >> >
>> >> > C:\Program Files\Microsoft SQL
>> >> > Server\MSSQL.1\MSSQL\Data\CompaniesDBSQL.mdf
>> >> >
>> >> > to make my backup instead of running the backup command? I've tried
>> >> > this
>> >> > in
>> >> > the past but I couldn't restore it. Apparently some other files
>> >> > would
>> >> > have
>> >> > to be copies as well?
>> >> > --
>> >> > Ed
>> >>
>> >>
>>|||Hi Ed,
Normally the error 3271 often indicates that the backup medium is full. You
may refer to:
MSSQLSERVER_3271
http://msdn2.microsoft.com/en-us/library/aa337272.aspx
However I noticed that you said that there were enough disk space on your
computer and your SQL Server 2005 was SP2. In this case, I recommend that
you first run DBCC CHECKDB/DBCC CHECKALLOC to check if there are any errors
in your database. If there are no errors, this pushes me think that it
might be related to your hard drive, and I would like to check with you
whether or not you can reproduce this issue on your other machines? You may
copy your .mdf file to a test server, attach the file to the SQL Server
2005 instance on the test server, and then run BACKUP DATABASE to see if
this issue persists.
I recommend that you try the above methods and let us know the result.
Thanks for your cooperation and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================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.
======================================================|||My hard drive partition has 172GB, with only 64GB used. My DB uses about
2.5GB, so there's way more than enough space on the HD. I'll try running the
program on another PC to see if the problem recurs. The problem is
intermittent, although it tends to occur the more often I run my program
which accesses the DB.
I've had the problem again a couple times recently, and I checked the Task
Manager after each occurance. I found that my Available Memory is unusally
low (only about 140GB), and when I sorted the Processes by Memory Usage, I
found that sqlserver.exe is using 1,584,920K of memory (I have almost 3GB
total--I'm running XP Professional). It continues to hog the memory even
after I shut down both SSMS and VS (the only programs using SQL Server on my
PC). Last night, after closing SSMS and VS, I re-opened SSMS, and Restarted
SQL Server. The memory usage went back to normal, and the backup worked.
This morning, however, while restarting SQL Server did cause memory usage to
go back to normal, I still can't backup.
I can think of only two reasons why this problem my have started to occur
(the backup command has worked flawlessly on my DB for over a year). First,
my DB grows in size continuously, so it just may have gotten so big that the
problem has started. Second, I recently added more memory to my PC. I used
to have 2GB, but I upgraded to 4GB. I'm using Windows XP Professional. In
order to get the PC to recognize the extra memory, my computer guy added
"/usepmtimer /3GB /userva=3072" to the boot.ini file. I don't know if this
could be contributing to the problem.
--
Ed
"Charles Wang[MSFT]" wrote:
> Hi Ed,
> Normally the error 3271 often indicates that the backup medium is full. You
> may refer to:
> MSSQLSERVER_3271
> http://msdn2.microsoft.com/en-us/library/aa337272.aspx
> However I noticed that you said that there were enough disk space on your
> computer and your SQL Server 2005 was SP2. In this case, I recommend that
> you first run DBCC CHECKDB/DBCC CHECKALLOC to check if there are any errors
> in your database. If there are no errors, this pushes me think that it
> might be related to your hard drive, and I would like to check with you
> whether or not you can reproduce this issue on your other machines? You may
> copy your .mdf file to a test server, attach the file to the SQL Server
> 2005 instance on the test server, and then run BACKUP DATABASE to see if
> this issue persists.
> I recommend that you try the above methods and let us know the result.
> Thanks for your cooperation and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> 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.
> ======================================================>
>|||HELP! I'm in real trouble now. I changed the default DB to my own DB from
master, and then Detached the DB. Now, when I pull up SSMS and try to do
anything, it says "Cannot open user default database. Login failed." The
default DB is my own, and it is Detached. I try using sp_defaultdb to change
the default DB, but it keeps saying I do not have a vaild login or do not
have permission. I use local system as my login, and I've tried multple
variations on that for the login and keep getting the same message. I'm now
locked out of my DB. How do I get back in' !!!
--
Ed
"Ed White" wrote:
> My hard drive partition has 172GB, with only 64GB used. My DB uses about
> 2.5GB, so there's way more than enough space on the HD. I'll try running the
> program on another PC to see if the problem recurs. The problem is
> intermittent, although it tends to occur the more often I run my program
> which accesses the DB.
> I've had the problem again a couple times recently, and I checked the Task
> Manager after each occurance. I found that my Available Memory is unusally
> low (only about 140GB), and when I sorted the Processes by Memory Usage, I
> found that sqlserver.exe is using 1,584,920K of memory (I have almost 3GB
> total--I'm running XP Professional). It continues to hog the memory even
> after I shut down both SSMS and VS (the only programs using SQL Server on my
> PC). Last night, after closing SSMS and VS, I re-opened SSMS, and Restarted
> SQL Server. The memory usage went back to normal, and the backup worked.
> This morning, however, while restarting SQL Server did cause memory usage to
> go back to normal, I still can't backup.
> I can think of only two reasons why this problem my have started to occur
> (the backup command has worked flawlessly on my DB for over a year). First,
> my DB grows in size continuously, so it just may have gotten so big that the
> problem has started. Second, I recently added more memory to my PC. I used
> to have 2GB, but I upgraded to 4GB. I'm using Windows XP Professional. In
> order to get the PC to recognize the extra memory, my computer guy added
> "/usepmtimer /3GB /userva=3072" to the boot.ini file. I don't know if this
> could be contributing to the problem.
> --
> Ed
>
> "Charles Wang[MSFT]" wrote:
> > Hi Ed,
> > Normally the error 3271 often indicates that the backup medium is full. You
> > may refer to:
> > MSSQLSERVER_3271
> > http://msdn2.microsoft.com/en-us/library/aa337272.aspx
> >
> > However I noticed that you said that there were enough disk space on your
> > computer and your SQL Server 2005 was SP2. In this case, I recommend that
> > you first run DBCC CHECKDB/DBCC CHECKALLOC to check if there are any errors
> > in your database. If there are no errors, this pushes me think that it
> > might be related to your hard drive, and I would like to check with you
> > whether or not you can reproduce this issue on your other machines? You may
> > copy your .mdf file to a test server, attach the file to the SQL Server
> > 2005 instance on the test server, and then run BACKUP DATABASE to see if
> > this issue persists.
> >
> > I recommend that you try the above methods and let us know the result.
> > Thanks for your cooperation and have a nice day!
> >
> > Best regards,
> > Charles Wang
> > Microsoft Online Community Support
> >
> > ======================================================> > 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.
> > ======================================================> >
> >
> >|||I just figured out how to change the default DB. I looked under Security on
SSMS and found the login names.
So if my default DB is my own instead of master, I would have to change the
default DB back to master before I Detach.
Anyway, the problem with the memory remains.
--
Ed
"Ed White" wrote:
> HELP! I'm in real trouble now. I changed the default DB to my own DB from
> master, and then Detached the DB. Now, when I pull up SSMS and try to do
> anything, it says "Cannot open user default database. Login failed." The
> default DB is my own, and it is Detached. I try using sp_defaultdb to change
> the default DB, but it keeps saying I do not have a vaild login or do not
> have permission. I use local system as my login, and I've tried multple
> variations on that for the login and keep getting the same message. I'm now
> locked out of my DB. How do I get back in' !!!
> --
> Ed
>
> "Ed White" wrote:
> > My hard drive partition has 172GB, with only 64GB used. My DB uses about
> > 2.5GB, so there's way more than enough space on the HD. I'll try running the
> > program on another PC to see if the problem recurs. The problem is
> > intermittent, although it tends to occur the more often I run my program
> > which accesses the DB.
> >
> > I've had the problem again a couple times recently, and I checked the Task
> > Manager after each occurance. I found that my Available Memory is unusally
> > low (only about 140GB), and when I sorted the Processes by Memory Usage, I
> > found that sqlserver.exe is using 1,584,920K of memory (I have almost 3GB
> > total--I'm running XP Professional). It continues to hog the memory even
> > after I shut down both SSMS and VS (the only programs using SQL Server on my
> > PC). Last night, after closing SSMS and VS, I re-opened SSMS, and Restarted
> > SQL Server. The memory usage went back to normal, and the backup worked.
> > This morning, however, while restarting SQL Server did cause memory usage to
> > go back to normal, I still can't backup.
> >
> > I can think of only two reasons why this problem my have started to occur
> > (the backup command has worked flawlessly on my DB for over a year). First,
> > my DB grows in size continuously, so it just may have gotten so big that the
> > problem has started. Second, I recently added more memory to my PC. I used
> > to have 2GB, but I upgraded to 4GB. I'm using Windows XP Professional. In
> > order to get the PC to recognize the extra memory, my computer guy added
> > "/usepmtimer /3GB /userva=3072" to the boot.ini file. I don't know if this
> > could be contributing to the problem.
> > --
> > Ed
> >
> >
> > "Charles Wang[MSFT]" wrote:
> >
> > > Hi Ed,
> > > Normally the error 3271 often indicates that the backup medium is full. You
> > > may refer to:
> > > MSSQLSERVER_3271
> > > http://msdn2.microsoft.com/en-us/library/aa337272.aspx
> > >
> > > However I noticed that you said that there were enough disk space on your
> > > computer and your SQL Server 2005 was SP2. In this case, I recommend that
> > > you first run DBCC CHECKDB/DBCC CHECKALLOC to check if there are any errors
> > > in your database. If there are no errors, this pushes me think that it
> > > might be related to your hard drive, and I would like to check with you
> > > whether or not you can reproduce this issue on your other machines? You may
> > > copy your .mdf file to a test server, attach the file to the SQL Server
> > > 2005 instance on the test server, and then run BACKUP DATABASE to see if
> > > this issue persists.
> > >
> > > I recommend that you try the above methods and let us know the result.
> > > Thanks for your cooperation and have a nice day!
> > >
> > > Best regards,
> > > Charles Wang
> > > Microsoft Online Community Support
> > >
> > > ======================================================> > > 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.
> > > ======================================================> > >
> > >
> > >|||Ed,
SQL Server will not release memory while running unless the OS specifically
asks for it. So the behavior you mention is expected. If you want to control
how much memory SQL Server uses you can set the MAX Memory setting to
xxxMB's. This is actually for the buffer pool and you can have up to 384MB's
on top of that for other parts of SQL Server as well so keep that in mind.
Try setting it to 1.0GB and see how that works out. Setting the /3GB is
probably not a good thing in your case. Even though you have 4GB of memory
installed chances are your laptop will only be able to use 3GB of it to
begin with so you can starve the OS. I would take that back out along with
the userva setting.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed White" <ewhite@.newsgroups.nospam> wrote in message
news:98B4973C-E73A-4D2B-892F-D409781DF26D@.microsoft.com...
> My hard drive partition has 172GB, with only 64GB used. My DB uses about
> 2.5GB, so there's way more than enough space on the HD. I'll try running
> the
> program on another PC to see if the problem recurs. The problem is
> intermittent, although it tends to occur the more often I run my program
> which accesses the DB.
> I've had the problem again a couple times recently, and I checked the Task
> Manager after each occurance. I found that my Available Memory is
> unusally
> low (only about 140GB), and when I sorted the Processes by Memory Usage, I
> found that sqlserver.exe is using 1,584,920K of memory (I have almost 3GB
> total--I'm running XP Professional). It continues to hog the memory even
> after I shut down both SSMS and VS (the only programs using SQL Server on
> my
> PC). Last night, after closing SSMS and VS, I re-opened SSMS, and
> Restarted
> SQL Server. The memory usage went back to normal, and the backup worked.
> This morning, however, while restarting SQL Server did cause memory usage
> to
> go back to normal, I still can't backup.
> I can think of only two reasons why this problem my have started to occur
> (the backup command has worked flawlessly on my DB for over a year).
> First,
> my DB grows in size continuously, so it just may have gotten so big that
> the
> problem has started. Second, I recently added more memory to my PC. I
> used
> to have 2GB, but I upgraded to 4GB. I'm using Windows XP Professional.
> In
> order to get the PC to recognize the extra memory, my computer guy added
> "/usepmtimer /3GB /userva=3072" to the boot.ini file. I don't know if
> this
> could be contributing to the problem.
> --
> Ed
>
> "Charles Wang[MSFT]" wrote:
>> Hi Ed,
>> Normally the error 3271 often indicates that the backup medium is full.
>> You
>> may refer to:
>> MSSQLSERVER_3271
>> http://msdn2.microsoft.com/en-us/library/aa337272.aspx
>> However I noticed that you said that there were enough disk space on your
>> computer and your SQL Server 2005 was SP2. In this case, I recommend that
>> you first run DBCC CHECKDB/DBCC CHECKALLOC to check if there are any
>> errors
>> in your database. If there are no errors, this pushes me think that it
>> might be related to your hard drive, and I would like to check with you
>> whether or not you can reproduce this issue on your other machines? You
>> may
>> copy your .mdf file to a test server, attach the file to the SQL Server
>> 2005 instance on the test server, and then run BACKUP DATABASE to see if
>> this issue persists.
>> I recommend that you try the above methods and let us know the result.
>> Thanks for your cooperation and have a nice day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> ======================================================>> 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 Ed,
Thanks for your response.
Since /3GB switch had been enabled and your SQL Server just used 1.5GB
memory, your SQL Server was not in a heavy memory pressure status. Also as
you said, while restarting SQL Server did cause memory usage to go back to
normal, you still could not backup. So it is hard to get a conclusion that
this issue was memory related according these appearances.
If you are concerned with /3GB switch, you may remove it from boot.ini file
and then try using AWE to see if it helps:
Managing Memory for Large Databases
http://technet.microsoft.com/en-us/library/ms191481.aspx
Currently for further research, I recommend that you try my former
suggestions first and let us know the results. Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================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 Charles,
I took Andrew's advice and removed the /3GB and userva settings from the
boot.ini. After doing this, Task Manager still shows the same amount of
memory available (2.75GB). I did this a few days ago, and I have not had the
error message recur since. So far, this seems to have solved the problem.
If the problem reappears, I'll let you know, but I'm confident that, at least
for now, it appears to be fixed.
--
Ed
"Charles Wang[MSFT]" wrote:
> Hi Ed,
> Thanks for your response.
> Since /3GB switch had been enabled and your SQL Server just used 1.5GB
> memory, your SQL Server was not in a heavy memory pressure status. Also as
> you said, while restarting SQL Server did cause memory usage to go back to
> normal, you still could not backup. So it is hard to get a conclusion that
> this issue was memory related according these appearances.
> If you are concerned with /3GB switch, you may remove it from boot.ini file
> and then try using AWE to see if it helps:
> Managing Memory for Large Databases
> http://technet.microsoft.com/en-us/library/ms191481.aspx
> Currently for further research, I recommend that you try my former
> suggestions first and let us know the results. Have a nice day!
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> 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.
> ======================================================>
>
>
>

Backup Error

I saw the following logged in the event log:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 9/14/2005
Time: 12:20:00 AM
User: N/A
Computer: BRADFORDDC01
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'Master Maintenance Plan'' (0x6FF812A8ED86514CBDF51CE01D6147ED) - Status:
Failed - Invoked on: 2005-09-14 00:20:00 - Message: The job failed. The Job
was invoked by Schedule 9 (Schedule 1). The last step to run was step 1
(Step 1).
The error appears to occur when backing up the transaction log of the
"master" database. I have verified that all of the databases are set to a
recovery mode of "Full," and also added the "-SupportComputedColumn" flag to
the job (as per MS KB). I created a new maintenance plan for the master DB
to isolate the
failing job, and I am still receiving this error, can anyone offer any
insight?
Thanks,
RobRobert,
The transaction log of the Master database cannot be backed up. Use a full
database backup for the Master system database.
HTH
Jerry
"Robert Zahm" <robzahm@.hotmail.com> wrote in message
news:eBgoxEVuFHA.1032@.TK2MSFTNGP12.phx.gbl...
>I saw the following logged in the event log:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 9/14/2005
> Time: 12:20:00 AM
> User: N/A
> Computer: BRADFORDDC01
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'Master Maintenance Plan'' (0x6FF812A8ED86514CBDF51CE01D6147ED) -
> Status: Failed - Invoked on: 2005-09-14 00:20:00 - Message: The job
> failed. The Job was invoked by Schedule 9 (Schedule 1). The last step to
> run was step 1 (Step 1).
>
> The error appears to occur when backing up the transaction log of the
> "master" database. I have verified that all of the databases are set to a
> recovery mode of "Full," and also added the "-SupportComputedColumn" flag
> to
> the job (as per MS KB). I created a new maintenance plan for the master
> DB to isolate the
> failing job, and I am still receiving this error, can anyone offer any
> insight?
> Thanks,
> Rob
>
>|||Hi,
You can not backup the trsnaction log backup of Master database. Since you
are not doing any transaction inside Master it is not required
to do a log backup in Master database. It is always if you do a Full
database backup for MASTER database daily once.
It is not good practice to crete tables/ objects in Master database.
Thanks
Hari
SQL Server MVP
"Robert Zahm" <robzahm@.hotmail.com> wrote in message
news:eBgoxEVuFHA.1032@.TK2MSFTNGP12.phx.gbl...
>I saw the following logged in the event log:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 9/14/2005
> Time: 12:20:00 AM
> User: N/A
> Computer: BRADFORDDC01
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'Master Maintenance Plan'' (0x6FF812A8ED86514CBDF51CE01D6147ED) -
> Status: Failed - Invoked on: 2005-09-14 00:20:00 - Message: The job
> failed. The Job was invoked by Schedule 9 (Schedule 1). The last step to
> run was step 1 (Step 1).
>
> The error appears to occur when backing up the transaction log of the
> "master" database. I have verified that all of the databases are set to a
> recovery mode of "Full," and also added the "-SupportComputedColumn" flag
> to
> the job (as per MS KB). I created a new maintenance plan for the master
> DB to isolate the
> failing job, and I am still receiving this error, can anyone offer any
> insight?
> Thanks,
> Rob
>
>

Backup Error

Each time I run a backup the following error appears in
SQL Server's error log: Error: 4035, Severity: 10, State: 1
Can anyone help in explaining why I keep getting the above
error? Your help will be greatly appreciated.
Hi,
Can you run the backup command from query analyzer an check the status of
backup
Backup database <dbname> to disk='c:\backup\dbname.bak' with init
Which version of SQL Server you are running?
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:24d5401c4601f$c79722c0$a301280a@.phx.gbl...
> Each time I run a backup the following error appears in
> SQL Server's error log: Error: 4035, Severity: 10, State: 1
> Can anyone help in explaining why I keep getting the above
> error? Your help will be greatly appreciated.
|||Hi,
I have run the backup command from query analyser and
still getting the same error.
I am running SQL Server 2000 Enterprise SP3.
Thanks
>--Original Message--
>Hi,
>Can you run the backup command from query analyzer an
check the status of
>backup
>Backup database <dbname> to disk='c:\backup\dbname.bak'
with init
>Which version of SQL Server you are running?
>
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:24d5401c4601f$c79722c0$a301280a@.phx.gbl...
State: 1[vbcol=seagreen]
above
>
>.
>
|||Hi,
I feel this is just a informational message.
Can you validate the backup file by restoring it to a diffrent database.
After that run a DBCC CHECKDB on that
new database and confirm things are fine.
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:251cb01c46024$c778ac00$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I have run the backup command from query analyser and
> still getting the same error.
> I am running SQL Server 2000 Enterprise SP3.
> Thanks
> check the status of
> with init
> <anonymous@.discussions.microsoft.com> wrote in message
> State: 1
> above
|||Thanks Hari,
I have restored the backup file to another database and
ran the DBCC Checkdb against the restored database, it
returned no errors. Everything appears to be fine. I
guess I will have to ignore the error message for now.
Thank you very much for your help.
>--Original Message--
>Hi,
>I feel this is just a informational message.
>Can you validate the backup file by restoring it to a
diffrent database.
>After that run a DBCC CHECKDB on that
>new database and confirm things are fine.
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:251cb01c46024$c778ac00$a401280a@.phx.gbl...
in
>
>.
>