DB Maintenance Plan

Hi Gurus,
I am getting an error while the backup plan is getting executed. Until last week it is fine working perfectly. Nothing has been changed as far as the settings are concerned. The job is run every night. It is being executed as a domain user (domain\adminis
trator) and the backup is being written to the network mapped drive (\\ipaddress\<driveletter>\Backups\<servername>\<d bname.bak>).
Whenever it is failed, the status is being shown as 64, see the SQL Server error log for details. [SQLState 42000] (Erorr 3202) Backup database is terminating abnormally. [SQLState 42000] (Error 3013). The step failed.
The statement being used is
Backup Database <dbname> to Disk = '\\ipaddress\<driveletter>\Backups\<servername>\<d bname.bak>' With Format
Other details are as follows:
BackupMedium::ReportIoError: read failure on backup device '\\ipaddress\<driveletter>\Backups\<servername>\<d bname_log.bak>'. Operating system error 64(The specified network name is no longer available.).
BACKUP failed to complete the command BACKUP DATABASE REPL TO DISK = '\\ipaddress\<driveletter>\Backups\<servername>\<d bname.bak>' WITH FORMAT
Internal I/O request 0x2B97F408: Op: Read, pBuffer: 0x00000000, Size: 52, Position: 12884901921, RetryCount: 8454144, SubIoCount: 2, UMS: Internal: 0x2, InternalHigh: 0x1, Offset: 0x1, OffsetHigh: 0x1, m_buf: 0x00010001, m_len: 1, m_actualBytes: 0, m_errc
ode: 64, BackupFile: n/a
Any guidance will be highly appreciated as i am trying to find a solution for a long time.
Thanks in advance.
This looks like a network or file system error. Try to determine if it
fails all of the time or some of the time. Does the failure relate to the
size of the database backup. or the space available on the hard drive...
It is not a good idea to use mapped drive letters, because that could change
if someone else logs on to the system...Perhaps that is happening..
Change the backup to use a UNC name ie
backup database prod to disk = '\\server\share\dbname.bak' with format
and see if that makes any difference..
Also check the event logs ( and check with network folks) to see if there
have been any funny network things happening lately.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Ravi" <luckyguy_2200in@.yahoo.co.in> wrote in message
news:515F80F2-A50E-4B6F-8C48-D510724951C6@.microsoft.com...
> Hi Gurus,
> I am getting an error while the backup plan is getting executed. Until
last week it is fine working perfectly. Nothing has been changed as far as
the settings are concerned. The job is run every night. It is being executed
as a domain user (domain\administrator) and the backup is being written to
the network mapped drive
(\\ipaddress\<driveletter>\Backups\<servername>\<d bname.bak>).
> Whenever it is failed, the status is being shown as 64, see the SQL Server
error log for details. [SQLState 42000] (Erorr 3202) Backup database is
terminating abnormally. [SQLState 42000] (Error 3013). The step failed.
> The statement being used is
> Backup Database <dbname> to Disk =
'\\ipaddress\<driveletter>\Backups\<servername>\<d bname.bak>' With Format
> Other details are as follows:
> BackupMedium::ReportIoError: read failure on backup device
'\\ipaddress\<driveletter>\Backups\<servername>\<d bname_log.bak>'. Operating
system error 64(The specified network name is no longer available.).
> BACKUP failed to complete the command BACKUP DATABASE REPL TO DISK =
'\\ipaddress\<driveletter>\Backups\<servername>\<d bname.bak>' WITH FORMAT
> Internal I/O request 0x2B97F408: Op: Read, pBuffer: 0x00000000, Size: 52,
Position: 12884901921, RetryCount: 8454144, SubIoCount: 2, UMS: Internal:
0x2, InternalHigh: 0x1, Offset: 0x1, OffsetHigh: 0x1, m_buf: 0x00010001,
m_len: 1, m_actualBytes: 0, m_errcode: 64, BackupFile: n/a
> Any guidance will be highly appreciated as i am trying to find a solution
for a long time.
> Thanks in advance.
>
|||Hi Wayne,
Thanks for the reply. The failure is happening from time to time. I don't think that the failure is related to the database size, because previously the backup is going on fine.
I will get back to you as soon as some more information is captured at my end to post the same over here.
Thanks once again.