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
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Sunday, March 25, 2012
Backup Error
Hi Guys,
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a écrit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a écrit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
Backup Error
Hi Guys,
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.
Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a crit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.
Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a crit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
Thursday, March 22, 2012
Backup Error
Hi Guys,
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a crit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a crit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
Thursday, February 16, 2012
Backup
We are running SQL Server 2000, SP3. Do we need to stop SQL service before
backing up all the database (master, msdb, etc.)?
Thanks.No, SQL Server has always allowed you to back up a database while the server
is running.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:#TVYkJfZDHA.4020@.tk2msftngp13.phx.gbl...
> We are running SQL Server 2000, SP3. Do we need to stop SQL service
before
> backing up all the database (master, msdb, etc.)?
> Thanks.
>|||Thank you, Kalen.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uaBGjNfZDHA.1280@.tk2msftngp13.phx.gbl...
> No, SQL Server has always allowed you to back up a database while the
server
> is running.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> news:#TVYkJfZDHA.4020@.tk2msftngp13.phx.gbl...
> > We are running SQL Server 2000, SP3. Do we need to stop SQL service
> before
> > backing up all the database (master, msdb, etc.)?
> >
> > Thanks.
> >
> >
>
backing up all the database (master, msdb, etc.)?
Thanks.No, SQL Server has always allowed you to back up a database while the server
is running.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:#TVYkJfZDHA.4020@.tk2msftngp13.phx.gbl...
> We are running SQL Server 2000, SP3. Do we need to stop SQL service
before
> backing up all the database (master, msdb, etc.)?
> Thanks.
>|||Thank you, Kalen.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uaBGjNfZDHA.1280@.tk2msftngp13.phx.gbl...
> No, SQL Server has always allowed you to back up a database while the
server
> is running.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> news:#TVYkJfZDHA.4020@.tk2msftngp13.phx.gbl...
> > We are running SQL Server 2000, SP3. Do we need to stop SQL service
> before
> > backing up all the database (master, msdb, etc.)?
> >
> > Thanks.
> >
> >
>
Sunday, February 12, 2012
Backing up Windows Server with SQL server installed
I'm trying to find a way to shutdown the SQL server service on a Windows
Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
I'm currently backuping the SQL server throught the SQL server maintenance
plans and it works fine.
Now when I try to backup the entire server with netbackup the SQL database
files are not getting backed up because they are open. We currently do not
have a SQL client agent license for the netbackup so I want to shut down the
SQL server durning the netbackup process and turn it back on after.
I have tried to use net stop and start but SQL seems to restart on it's own
before the backup process is finished. Does anyone know of another method
to shut down the SQL server gracefully and start it back up again through a
batch file or script ? Any help would be great.
Thank you
Chris IThis is the wrong way to back up SQL Server database files. Either you run
a sp_detach_db statement first, then back up the files, or you use the
standard BACKUP T-SQL commands. Stopping the service and backing up the
files is wrong.
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Chris I" <dmagic@.nycap.rr.com> wrote in message
news:%23$ekzEmpEHA.1952@.TK2MSFTNGP12.phx.gbl...
> I'm trying to find a way to shutdown the SQL server service on a Windows
> Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
> I'm currently backuping the SQL server throught the SQL server maintenance
> plans and it works fine.
> Now when I try to backup the entire server with netbackup the SQL database
> files are not getting backed up because they are open. We currently do
not
> have a SQL client agent license for the netbackup so I want to shut down
the
> SQL server durning the netbackup process and turn it back on after.
> I have tried to use net stop and start but SQL seems to restart on it's
own
> before the backup process is finished. Does anyone know of another method
> to shut down the SQL server gracefully and start it back up again through
a
> batch file or script ? Any help would be great.
> Thank you
> Chris I
>
Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
I'm currently backuping the SQL server throught the SQL server maintenance
plans and it works fine.
Now when I try to backup the entire server with netbackup the SQL database
files are not getting backed up because they are open. We currently do not
have a SQL client agent license for the netbackup so I want to shut down the
SQL server durning the netbackup process and turn it back on after.
I have tried to use net stop and start but SQL seems to restart on it's own
before the backup process is finished. Does anyone know of another method
to shut down the SQL server gracefully and start it back up again through a
batch file or script ? Any help would be great.
Thank you
Chris IThis is the wrong way to back up SQL Server database files. Either you run
a sp_detach_db statement first, then back up the files, or you use the
standard BACKUP T-SQL commands. Stopping the service and backing up the
files is wrong.
--
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Chris I" <dmagic@.nycap.rr.com> wrote in message
news:%23$ekzEmpEHA.1952@.TK2MSFTNGP12.phx.gbl...
> I'm trying to find a way to shutdown the SQL server service on a Windows
> Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
> I'm currently backuping the SQL server throught the SQL server maintenance
> plans and it works fine.
> Now when I try to backup the entire server with netbackup the SQL database
> files are not getting backed up because they are open. We currently do
not
> have a SQL client agent license for the netbackup so I want to shut down
the
> SQL server durning the netbackup process and turn it back on after.
> I have tried to use net stop and start but SQL seems to restart on it's
own
> before the backup process is finished. Does anyone know of another method
> to shut down the SQL server gracefully and start it back up again through
a
> batch file or script ? Any help would be great.
> Thank you
> Chris I
>
Backing up Windows Server with SQL server installed
I'm trying to find a way to shutdown the SQL server service on a Windows
Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
I'm currently backuping the SQL server throught the SQL server maintenance
plans and it works fine.
Now when I try to backup the entire server with netbackup the SQL database
files are not getting backed up because they are open. We currently do not
have a SQL client agent license for the netbackup so I want to shut down the
SQL server durning the netbackup process and turn it back on after.
I have tried to use net stop and start but SQL seems to restart on it's own
before the backup process is finished. Does anyone know of another method
to shut down the SQL server gracefully and start it back up again through a
batch file or script ? Any help would be great.
Thank you
Chris I
This is the wrong way to back up SQL Server database files. Either you run
a sp_detach_db statement first, then back up the files, or you use the
standard BACKUP T-SQL commands. Stopping the service and backing up the
files is wrong.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Chris I" <dmagic@.nycap.rr.com> wrote in message
news:%23$ekzEmpEHA.1952@.TK2MSFTNGP12.phx.gbl...
> I'm trying to find a way to shutdown the SQL server service on a Windows
> Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
> I'm currently backuping the SQL server throught the SQL server maintenance
> plans and it works fine.
> Now when I try to backup the entire server with netbackup the SQL database
> files are not getting backed up because they are open. We currently do
not
> have a SQL client agent license for the netbackup so I want to shut down
the
> SQL server durning the netbackup process and turn it back on after.
> I have tried to use net stop and start but SQL seems to restart on it's
own
> before the backup process is finished. Does anyone know of another method
> to shut down the SQL server gracefully and start it back up again through
a
> batch file or script ? Any help would be great.
> Thank you
> Chris I
>
Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
I'm currently backuping the SQL server throught the SQL server maintenance
plans and it works fine.
Now when I try to backup the entire server with netbackup the SQL database
files are not getting backed up because they are open. We currently do not
have a SQL client agent license for the netbackup so I want to shut down the
SQL server durning the netbackup process and turn it back on after.
I have tried to use net stop and start but SQL seems to restart on it's own
before the backup process is finished. Does anyone know of another method
to shut down the SQL server gracefully and start it back up again through a
batch file or script ? Any help would be great.
Thank you
Chris I
This is the wrong way to back up SQL Server database files. Either you run
a sp_detach_db statement first, then back up the files, or you use the
standard BACKUP T-SQL commands. Stopping the service and backing up the
files is wrong.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Use MiniSQLBackup Lite, free!
"Chris I" <dmagic@.nycap.rr.com> wrote in message
news:%23$ekzEmpEHA.1952@.TK2MSFTNGP12.phx.gbl...
> I'm trying to find a way to shutdown the SQL server service on a Windows
> Server 2003, SQL server 2000 SP3. Veritas Netbackup 4.5.
> I'm currently backuping the SQL server throught the SQL server maintenance
> plans and it works fine.
> Now when I try to backup the entire server with netbackup the SQL database
> files are not getting backed up because they are open. We currently do
not
> have a SQL client agent license for the netbackup so I want to shut down
the
> SQL server durning the netbackup process and turn it back on after.
> I have tried to use net stop and start but SQL seems to restart on it's
own
> before the backup process is finished. Does anyone know of another method
> to shut down the SQL server gracefully and start it back up again through
a
> batch file or script ? Any help would be great.
> Thank you
> Chris I
>
Subscribe to:
Posts (Atom)