I've found a lot of people with this same problem, but not really any
solutions. We have scheduled backup jobs that run & backup DBs over
the network to a UNC path on our SAN/NAS. A few nights ago, most of
the larger database backups started failing pretty regularly with the
following errors present in the logs.
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
network name is no longer available.)
BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
'\\UNCPath\msdb_dump.BAK', WITH INIT, Format
BackupMedium::ReportIoError: write failure on backup device
'\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
network name is no longer available.).
Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\UNCPath\DB_dump.BAK
I don't know of a good solution here - can anyone help? I don't have
access to the Event Logs on the systems, but I'm trying to get to them,
and I'll repost if I find anything.
Hi,
The OS error 64 usually indicates the intermittent network connectivity
problems.
To ensure that the backups for the database are taken properly, I recommend
you backup to
the local hard disk drive and then create a OS scheduled job to move the
backup file
to the share upon completion of the SQL Backup.
In parallel Inform your network infrastructure team to investigate this
issu. As well as run the below command from command prompt during backup to
check the network issue.
ping <ipaddress_of_remote_machine> -t >pingtest.txt
Once the problem occur verify the pingtest.txt for any Request time Out.
Thanks
Hari
SQL Server MVP
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegr oups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
> '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>
|||How large is your DB?
Do you have any problem when you copy large files, more than 1GB, to the
SAN/NAS?
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegr oups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
> '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>
|||The failing DBs range from 100mb to 8-10gb. I can copy from my client
to the SAN via a mapped network drive to the same share that the DB is
pointing to, just in windows, no problem (it takes forever for the 8gb
file, but it works).
|||Another thing - the backup appears to run OK - using STATS I can view
it progressing but right before it's done it blows up...
A good one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
BACKUP DATABASE successfully processed 37681 pages in 22.736 seconds
(13.576 MB/sec).
My bad one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
<Then it says something like error 3013, BACKUP DATABASE is terminating
abnormally>
Showing posts with label dbs. Show all posts
Showing posts with label dbs. Show all posts
Wednesday, March 28, 2012
network backups fail - error 64
I've found a lot of people with this same problem, but not really any
solutions. We have scheduled backup jobs that run & backup DBs over
the network to a UNC path on our SAN/NAS. A few nights ago, most of
the larger database backups started failing pretty regularly with the
following errors present in the logs.
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
network name is no longer available.)
BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK = '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
BackupMedium::ReportIoError: write failure on backup device
'\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
network name is no longer available.).
Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\UNCPath\DB_dump.BAK
I don't know of a good solution here - can anyone help? I don't have
access to the Event Logs on the systems, but I'm trying to get to them,
and I'll repost if I find anything.Hi,
The OS error 64 usually indicates the intermittent network connectivity
problems.
To ensure that the backups for the database are taken properly, I recommend
you backup to
the local hard disk drive and then create a OS scheduled job to move the
backup file
to the share upon completion of the SQL Backup.
In parallel Inform your network infrastructure team to investigate this
issu. As well as run the below command from command prompt during backup to
check the network issue.
ping <ipaddress_of_remote_machine> -t >pingtest.txt
Once the problem occur verify the pingtest.txt for any Request time Out.
Thanks
Hari
SQL Server MVP
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK => '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||How large is your DB?
Do you have any problem when you copy large files, more than 1GB, to the
SAN/NAS?
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK => '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||The failing DBs range from 100mb to 8-10gb. I can copy from my client
to the SAN via a mapped network drive to the same share that the DB is
pointing to, just in windows, no problem (it takes forever for the 8gb
file, but it works).|||Another thing - the backup appears to run OK - using STATS I can view
it progressing but right before it's done it blows up...
A good one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
BACKUP DATABASE successfully processed 37681 pages in 22.736 seconds
(13.576 MB/sec).
My bad one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
<Then it says something like error 3013, BACKUP DATABASE is terminating
abnormally>sql
solutions. We have scheduled backup jobs that run & backup DBs over
the network to a UNC path on our SAN/NAS. A few nights ago, most of
the larger database backups started failing pretty regularly with the
following errors present in the logs.
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
network name is no longer available.)
BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK = '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
BackupMedium::ReportIoError: write failure on backup device
'\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
network name is no longer available.).
Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\UNCPath\DB_dump.BAK
I don't know of a good solution here - can anyone help? I don't have
access to the Event Logs on the systems, but I'm trying to get to them,
and I'll repost if I find anything.Hi,
The OS error 64 usually indicates the intermittent network connectivity
problems.
To ensure that the backups for the database are taken properly, I recommend
you backup to
the local hard disk drive and then create a OS scheduled job to move the
backup file
to the share upon completion of the SQL Backup.
In parallel Inform your network infrastructure team to investigate this
issu. As well as run the below command from command prompt during backup to
check the network issue.
ping <ipaddress_of_remote_machine> -t >pingtest.txt
Once the problem occur verify the pingtest.txt for any Request time Out.
Thanks
Hari
SQL Server MVP
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK => '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||How large is your DB?
Do you have any problem when you copy large files, more than 1GB, to the
SAN/NAS?
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK => '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||The failing DBs range from 100mb to 8-10gb. I can copy from my client
to the SAN via a mapped network drive to the same share that the DB is
pointing to, just in windows, no problem (it takes forever for the 8gb
file, but it works).|||Another thing - the backup appears to run OK - using STATS I can view
it progressing but right before it's done it blows up...
A good one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
BACKUP DATABASE successfully processed 37681 pages in 22.736 seconds
(13.576 MB/sec).
My bad one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
<Then it says something like error 3013, BACKUP DATABASE is terminating
abnormally>sql
network backups fail - error 64
I've found a lot of people with this same problem, but not really any
solutions. We have scheduled backup jobs that run & backup DBs over
the network to a UNC path on our SAN/NAS. A few nights ago, most of
the larger database backups started failing pretty regularly with the
following errors present in the logs.
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
network name is no longer available.)
BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
'\\UNCPath\msdb_dump.BAK', WITH INIT, Format
BackupMedium::ReportIoError: write failure on backup device
'\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
network name is no longer available.).
Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\UNCPath\DB_dump.BAK
I don't know of a good solution here - can anyone help? I don't have
access to the Event Logs on the systems, but I'm trying to get to them,
and I'll repost if I find anything.Hi,
The OS error 64 usually indicates the intermittent network connectivity
problems.
To ensure that the backups for the database are taken properly, I recommend
you backup to
the local hard disk drive and then create a OS scheduled job to move the
backup file
to the share upon completion of the SQL Backup.
In parallel Inform your network infrastructure team to investigate this
issu. As well as run the below command from command prompt during backup to
check the network issue.
ping <ipaddress_of_remote_machine> -t >pingtest.txt
Once the problem occur verify the pingtest.txt for any Request time Out.
Thanks
Hari
SQL Server MVP
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
> '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||How large is your DB?
Do you have any problem when you copy large files, more than 1GB, to the
SAN/NAS?
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
> '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||The failing DBs range from 100mb to 8-10gb. I can copy from my client
to the SAN via a mapped network drive to the same share that the DB is
pointing to, just in windows, no problem (it takes forever for the 8gb
file, but it works).|||Another thing - the backup appears to run OK - using STATS I can view
it progressing but right before it's done it blows up...
A good one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
BACKUP DATABASE successfully processed 37681 pages in 22.736 seconds
(13.576 MB/sec).
My bad one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
<Then it says something like error 3013, BACKUP DATABASE is terminating
abnormally>
solutions. We have scheduled backup jobs that run & backup DBs over
the network to a UNC path on our SAN/NAS. A few nights ago, most of
the larger database backups started failing pretty regularly with the
following errors present in the logs.
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
network name is no longer available.)
BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
'\\UNCPath\msdb_dump.BAK', WITH INIT, Format
BackupMedium::ReportIoError: write failure on backup device
'\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
network name is no longer available.).
Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\UNCPath\DB_dump.BAK
I don't know of a good solution here - can anyone help? I don't have
access to the Event Logs on the systems, but I'm trying to get to them,
and I'll repost if I find anything.Hi,
The OS error 64 usually indicates the intermittent network connectivity
problems.
To ensure that the backups for the database are taken properly, I recommend
you backup to
the local hard disk drive and then create a OS scheduled job to move the
backup file
to the share upon completion of the SQL Backup.
In parallel Inform your network infrastructure team to investigate this
issu. As well as run the below command from command prompt during backup to
check the network issue.
ping <ipaddress_of_remote_machine> -t >pingtest.txt
Once the problem occur verify the pingtest.txt for any Request time Out.
Thanks
Hari
SQL Server MVP
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
> '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||How large is your DB?
Do you have any problem when you copy large files, more than 1GB, to the
SAN/NAS?
<unc27932@.yahoo.com> wrote in message
news:1121174032.571685.322230@.o13g2000cwo.googlegroups.com...
> I've found a lot of people with this same problem, but not really any
> solutions. We have scheduled backup jobs that run & backup DBs over
> the network to a UNC path on our SAN/NAS. A few nights ago, most of
> the larger database backups started failing pretty regularly with the
> following errors present in the logs.
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\UNCpath\msdb_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.)
> BACKUP failed to complete the command BACKUP DATABASE msdb TO DISK =
> '\\UNCPath\msdb_dump.BAK', WITH INIT, Format
> BackupMedium::ReportIoError: write failure on backup device
> '\\UNCpath\DB_dump.BAK'. Operating system error 64(The specified
> network name is no longer available.).
> Internal I/O request 0x26485108: Op: Write, pBuffer: 0x28690000, Size:
> 983040, Position: 3191806464, UMS: Internal: 0x0, InternalHigh:
> 0xF0000, Offset: 0xBE3F1A00, OffsetHigh: 0x0, m_buf: 0x28690000, m_len:
> 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\UNCPath\DB_dump.BAK
> I don't know of a good solution here - can anyone help? I don't have
> access to the Event Logs on the systems, but I'm trying to get to them,
> and I'll repost if I find anything.
>|||The failing DBs range from 100mb to 8-10gb. I can copy from my client
to the SAN via a mapped network drive to the same share that the DB is
pointing to, just in windows, no problem (it takes forever for the 8gb
file, but it works).|||Another thing - the backup appears to run OK - using STATS I can view
it progressing but right before it's done it blows up...
A good one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
BACKUP DATABASE successfully processed 37681 pages in 22.736 seconds
(13.576 MB/sec).
My bad one says this:
96 percent backed up.
97 percent backed up.
98 percent backed up.
99 percent backed up.
Processed 37680 pages for database 'DB', file 'DB_dat' on file 1.
100 percent backed up.
Processed 1 pages for database 'DB', file 'DB_log' on file 1.
<Then it says something like error 3013, BACKUP DATABASE is terminating
abnormally>
Monday, March 26, 2012
Netapp issues with SQL2000 SP4
Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get it
back online.
Netapp says it's a Microsoft Issue.
I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:
> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020. We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get it
> back online.
> Netapp says it's a Microsoft Issue.
>
|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...and
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-server-and-network-attached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...[vbcol=seagreen]
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
sql
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get it
back online.
Netapp says it's a Microsoft Issue.
I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:
> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020. We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get it
> back online.
> Netapp says it's a Microsoft Issue.
>
|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...and
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-server-and-network-attached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...[vbcol=seagreen]
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
sql
Netapp issues with SQL2000 SP4
Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get i
t
back online.
Netapp says it's a Microsoft Issue.I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:
> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020.
We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQ
L
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get
it
> back online.
> Netapp says it's a Microsoft Issue.
>|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...an
d
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
>|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-...ttached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...[vbcol=seagreen]
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
>
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get i
t
back online.
Netapp says it's a Microsoft Issue.I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:
> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020.
We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQ
L
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get
it
> back online.
> Netapp says it's a Microsoft Issue.
>|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...an
d
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
>|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-...ttached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...[vbcol=seagreen]
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
>
Netapp issues with SQL2000 SP4
Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get it
back online.
Netapp says it's a Microsoft Issue.I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:
> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020. We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get it
> back online.
> Netapp says it's a Microsoft Issue.
>|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...and
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
> > Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> > application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> > 1-2GB, 10 seperate DBs)
> >
> > We are having major disconnects with SQL when we move to Netapp FAS3020. We
> > followed the Netapp implementation to the T.
> >
> > It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> > on the netapps. It will work for a few hours then all of a sudden, it will
> > "disconnect". There's nothing in the SQL log. Web services will result in
> > "Service Unavailable" We will have to totally reboot the SQL Server to get it
> > back online.
> >
> > Netapp says it's a Microsoft Issue.
> >
> >|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-server-and-network-attached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
>> I don't now Netapps.
>> But you should isolate the problem first. So.
>> Run Profiler On the SQL server...see if you have time-outs long running
>> queries?
>> Check the webserver logs.
>> Check if youre NIC on database and webserver are not the
>> bottleneck...and
>> if it is configured okay.
>> Network performance okay?
>> Greetz.
>>
>>
>>
>> "GSoD" wrote:
>> > Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps?
>> > Main
>> > application is SPS 2007 (5GB of data) and various other smaller DBs
>> > (appox
>> > 1-2GB, 10 seperate DBs)
>> >
>> > We are having major disconnects with SQL when we move to Netapp
>> > FAS3020. We
>> > followed the Netapp implementation to the T.
>> >
>> > It doesn't matter if we have a IIS 7.0, WebService, or directly quering
>> > SQL
>> > on the netapps. It will work for a few hours then all of a sudden, it
>> > will
>> > "disconnect". There's nothing in the SQL log. Web services will result
>> > in
>> > "Service Unavailable" We will have to totally reboot the SQL Server to
>> > get it
>> > back online.
>> >
>> > Netapp says it's a Microsoft Issue.
>> >
>> >
application is SPS 2007 (5GB of data) and various other smaller DBs (appox
1-2GB, 10 seperate DBs)
We are having major disconnects with SQL when we move to Netapp FAS3020. We
followed the Netapp implementation to the T.
It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
on the netapps. It will work for a few hours then all of a sudden, it will
"disconnect". There's nothing in the SQL log. Web services will result in
"Service Unavailable" We will have to totally reboot the SQL Server to get it
back online.
Netapp says it's a Microsoft Issue.I don't now Netapps.
But you should isolate the problem first. So.
Run Profiler On the SQL server...see if you have time-outs long running
queries?
Check the webserver logs.
Check if youre NIC on database and webserver are not the bottleneck...and
if it is configured okay.
Network performance okay?
Greetz.
"GSoD" wrote:
> Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> 1-2GB, 10 seperate DBs)
> We are having major disconnects with SQL when we move to Netapp FAS3020. We
> followed the Netapp implementation to the T.
> It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> on the netapps. It will work for a few hours then all of a sudden, it will
> "disconnect". There's nothing in the SQL log. Web services will result in
> "Service Unavailable" We will have to totally reboot the SQL Server to get it
> back online.
> Netapp says it's a Microsoft Issue.
>|||Did all that. The thing is that no errors are generated. Timeouts vary from
under 30 mins to over 4 hrs. There's no pattern and it would stop in random
locations in a test process. Due to the randomness, it's hard to even begin
to start to isolate the issue.
We have a test script that writes and deletes "hello world" to a text field
and that would also generate a failure.
"Hate_orphaned_users" wrote:
> I don't now Netapps.
> But you should isolate the problem first. So.
> Run Profiler On the SQL server...see if you have time-outs long running
> queries?
> Check the webserver logs.
> Check if youre NIC on database and webserver are not the bottleneck...and
> if it is configured okay.
> Network performance okay?
> Greetz.
>
>
>
> "GSoD" wrote:
> > Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps? Main
> > application is SPS 2007 (5GB of data) and various other smaller DBs (appox
> > 1-2GB, 10 seperate DBs)
> >
> > We are having major disconnects with SQL when we move to Netapp FAS3020. We
> > followed the Netapp implementation to the T.
> >
> > It doesn't matter if we have a IIS 7.0, WebService, or directly quering SQL
> > on the netapps. It will work for a few hours then all of a sudden, it will
> > "disconnect". There's nothing in the SQL log. Web services will result in
> > "Service Unavailable" We will have to totally reboot the SQL Server to get it
> > back online.
> >
> > Netapp says it's a Microsoft Issue.
> >
> >|||I know you used to have to set a trace flag but I am not sure if that still
holds true or not. Anyway maybe this will help:
http://www.sqlteam.com/article/sql-server-and-network-attached-storage
Andrew J. Kelly SQL MVP
"GSoD" <GSoD@.discussions.microsoft.com> wrote in message
news:FBACC353-992D-49D2-B883-6DDE3DBFEBDF@.microsoft.com...
> Did all that. The thing is that no errors are generated. Timeouts vary
> from
> under 30 mins to over 4 hrs. There's no pattern and it would stop in
> random
> locations in a test process. Due to the randomness, it's hard to even
> begin
> to start to isolate the issue.
> We have a test script that writes and deletes "hello world" to a text
> field
> and that would also generate a failure.
> "Hate_orphaned_users" wrote:
>> I don't now Netapps.
>> But you should isolate the problem first. So.
>> Run Profiler On the SQL server...see if you have time-outs long running
>> queries?
>> Check the webserver logs.
>> Check if youre NIC on database and webserver are not the
>> bottleneck...and
>> if it is configured okay.
>> Network performance okay?
>> Greetz.
>>
>>
>>
>> "GSoD" wrote:
>> > Has anyone successfully implemented SQL 2000 or SQL 2005 on Netapps?
>> > Main
>> > application is SPS 2007 (5GB of data) and various other smaller DBs
>> > (appox
>> > 1-2GB, 10 seperate DBs)
>> >
>> > We are having major disconnects with SQL when we move to Netapp
>> > FAS3020. We
>> > followed the Netapp implementation to the T.
>> >
>> > It doesn't matter if we have a IIS 7.0, WebService, or directly quering
>> > SQL
>> > on the netapps. It will work for a few hours then all of a sudden, it
>> > will
>> > "disconnect". There's nothing in the SQL log. Web services will result
>> > in
>> > "Service Unavailable" We will have to totally reboot the SQL Server to
>> > get it
>> > back online.
>> >
>> > Netapp says it's a Microsoft Issue.
>> >
>> >
Subscribe to:
Posts (Atom)