Backup Jobs

I am backing up my SQL Server databases to VDM (SAN) but all my backups are
taking very long some times 12 hours and always failing with the following
error.
failed: 64(The specified network name is no longer available.) [SQLSTATE
42000] (Error 3202) A nonrecoverable I/O error occurred on file
Any help will be appreciated.
Thanks!Get your network and SAN people involved, because the problem is something
that they will have to solve. (If you are also the network and SAN person,
the problem is probably not in your SQL Server.)
This is most likely a bottleneck in either the network layers or the SAN
disk or disk controller throughput. I suspect that at the lower levels of
network and/or disk I/O there are a lot of retries happening, until finally
one of them just cannot recover in time. Then your backup fails because it
can no longer see that the file to which it was backing up.
How much data are you backing up? How big is the largest database? How
long would you expect it to take? You are probably having this problem on
your biggest databases, which put the greatest backup load on your
landscape, and the little databases are having no problems.
RLF
<msnews.microsoft.com> wrote in message
news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
> I am backing up my SQL Server databases to VDM (SAN) but all my backups
> are taking very long some times 12 hours and always failing with the
> following error.
> failed: 64(The specified network name is no longer available.) [SQLSTATE
> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
> Any help will be appreciated.
> Thanks!
>|||Are you watching the network traffic and CPU on both your server and the
SAN?
I recommend you do.
Also, if you backup locally, to disk, how long does it take?
<msnews.microsoft.com> wrote in message
news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
> I am backing up my SQL Server databases to VDM (SAN) but all my backups
> are taking very long some times 12 hours and always failing with the
> following error.
> failed: 64(The specified network name is no longer available.) [SQLSTATE
> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
> Any help will be appreciated.
> Thanks!
>|||What is the best way to do that ?
"Jay" <spam@.nospam.org> wrote in message
news:%23AeAq2EGIHA.4684@.TK2MSFTNGP06.phx.gbl...
> Are you watching the network traffic and CPU on both your server and the
> SAN?
> I recommend you do.
> Also, if you backup locally, to disk, how long does it take?
>
> <msnews.microsoft.com> wrote in message
> news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
>> I am backing up my SQL Server databases to VDM (SAN) but all my backups
>> are taking very long some times 12 hours and always failing with the
>> following error.
>> failed: 64(The specified network name is no longer available.) [SQLSTATE
>> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
>> Any help will be appreciated.
>> Thanks!
>|||I am not a SAN or network specialist, although I work with them, so I cannot
tell you exactly what counters to watch. But you should be able to estimate
the throughput that you should get and compare it to what is actually
happening.
For example, if you expect to backup 150 GB an hour, but the 150 GB backup
fails after 12 hours, then something is obviously wrong. Jay asked 'How
long does the backup run to local disk?' Like my questions, it was an
effort to find out how much your backup landscape is differing from what you
would expect.
RLF
<omranu@.Gmail.com> wrote in message
news:OBjXImYGIHA.5544@.TK2MSFTNGP02.phx.gbl...
> What is the best way to do that ?
>
> "Jay" <spam@.nospam.org> wrote in message
> news:%23AeAq2EGIHA.4684@.TK2MSFTNGP06.phx.gbl...
>> Are you watching the network traffic and CPU on both your server and the
>> SAN?
>> I recommend you do.
>> Also, if you backup locally, to disk, how long does it take?
>>
>> <msnews.microsoft.com> wrote in message
>> news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
>> I am backing up my SQL Server databases to VDM (SAN) but all my backups
>> are taking very long some times 12 hours and always failing with the
>> following error.
>> failed: 64(The specified network name is no longer available.) [SQLSTATE
>> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
>> Any help will be appreciated.
>> Thanks!
>>
>|||Are you asking how to monitor the network traffic, or how to backup to disk?
The simplest way to monitor network traffic is to watch the Network tab of
the Task Manager. I was, however, refering to the Performance Monitor
available under "Control Panel->Administrative Tools"..
The simplest way to backup to disk is a right-click on the database name in
EM, of MS.
<omranu@.Gmail.com> wrote in message
news:OBjXImYGIHA.5544@.TK2MSFTNGP02.phx.gbl...
> What is the best way to do that ?
>
> "Jay" <spam@.nospam.org> wrote in message
> news:%23AeAq2EGIHA.4684@.TK2MSFTNGP06.phx.gbl...
>> Are you watching the network traffic and CPU on both your server and the
>> SAN?
>> I recommend you do.
>> Also, if you backup locally, to disk, how long does it take?
>>
>> <msnews.microsoft.com> wrote in message
>> news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
>> I am backing up my SQL Server databases to VDM (SAN) but all my backups
>> are taking very long some times 12 hours and always failing with the
>> following error.
>> failed: 64(The specified network name is no longer available.) [SQLSTATE
>> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
>> Any help will be appreciated.
>> Thanks!
>>
>|||Did you ever find the root cause of this? I am struggling with the same
issue. Windows 2003 x64 / SQL 2005 with SAN backend databases. DB access is
very fast on the attached SAN drives however the SQL backups are way, way
slow. As soon as the job leaves the fiber fabric and moves through the IP
stack and out to the VDM the jobs drag. This is a gig connected box and I am
seeing rates between 5-12MB/s, which is horrible. Staying with in the fiber
frabric is great, but moving out into the IP cloud is horrible. I have tried
all sorts of stuff yet nothing is showing me the problem. The VDM links to a
DataMover that is barely under load; tons of free memory, tons of CPU head
room. I have confirmed with the NE that the edge switches are not under
load, there are no errors on the port, and that the pipes feeding the VDM are
way, way underutilized: 2GB pipe with no more than 40MB/s throughput when the
job is running.
Is there any known issue with 2003 x32 or x64 SP2, SQL2005 and data movement
through a NAS VDM?
~ Jeffrey
"msnews.microsoft.com" wrote:
> I am backing up my SQL Server databases to VDM (SAN) but all my backups are
> taking very long some times 12 hours and always failing with the following
> error.
> failed: 64(The specified network name is no longer available.) [SQLSTATE
> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
> Any help will be appreciated.
> Thanks!
>
>