Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\DatabaseName. bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK =
\\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Server
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
Michael
Michael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer available.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k'. Operating system error
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\DatabaseName. bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK =
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Server
> Agent account which has full access permission to the backup network drive.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michael

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.
).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\Dat
abaseName.bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK =
\\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Serve
r
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
MichaelMichael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3
-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer availabl
e.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak'. Operating system err
or
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\Dat
abaseName.bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK =
> \\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Ser
ver
> Agent account which has full access permission to the backup network drive
.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michael

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK = \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Server
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
MichaelMichael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer available.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system error
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK => \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Server
> Agent account which has full access permission to the backup network drive.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michaelsql

Backup and DTS....@ the same time....

I am launching full backup of user database and at the same time loading the
data to the tables using a DTS package. Will this be a performance issue?
I am using SQL2K.
Thanks,
CarlWell, it will potentially slow down both the load and the backup a little,
mostly simply because of the disc io involved. But is it an issue? - depends
on manythings - how biug the db is, how long the backup takes, how many rows
DTS is loading etc.
You will need to consider things like how long do the 2 steps take
seperately, how long together?, when is it happening? - will anyone else
know - ie is the db idle anyway when you do this?
Mike John
"Carl San" <Carl_San@.hotmail.com> wrote in message
news:un0FX8aMFHA.244@.TK2MSFTNGP12.phx.gbl...
>I am launching full backup of user database and at the same time loading
>the
> data to the tables using a DTS package. Will this be a performance issue?
> I am using SQL2K.
> Thanks,
> Carl
>

Backup and DTS....@ the same time....

I am launching full backup of user database and at the same time loading the
data to the tables using a DTS package. Will this be a performance issue?
I am using SQL2K.
Thanks,
CarlWell, it will potentially slow down both the load and the backup a little,
mostly simply because of the disc io involved. But is it an issue? - depends
on manythings - how biug the db is, how long the backup takes, how many rows
DTS is loading etc.
You will need to consider things like how long do the 2 steps take
seperately, how long together?, when is it happening? - will anyone else
know - ie is the db idle anyway when you do this?
Mike John
"Carl San" <Carl_San@.hotmail.com> wrote in message
news:un0FX8aMFHA.244@.TK2MSFTNGP12.phx.gbl...
>I am launching full backup of user database and at the same time loading
>the
> data to the tables using a DTS package. Will this be a performance issue?
> I am using SQL2K.
> Thanks,
> Carl
>

Backup and DTS....@ the same time....

I am launching full backup of user database and at the same time loading the
data to the tables using a DTS package. Will this be a performance issue?
I am using SQL2K.
Thanks,
Carl
Well, it will potentially slow down both the load and the backup a little,
mostly simply because of the disc io involved. But is it an issue? - depends
on manythings - how biug the db is, how long the backup takes, how many rows
DTS is loading etc.
You will need to consider things like how long do the 2 steps take
seperately, how long together?, when is it happening? - will anyone else
know - ie is the db idle anyway when you do this?
Mike John
"Carl San" <Carl_San@.hotmail.com> wrote in message
news:un0FX8aMFHA.244@.TK2MSFTNGP12.phx.gbl...
>I am launching full backup of user database and at the same time loading
>the
> data to the tables using a DTS package. Will this be a performance issue?
> I am using SQL2K.
> Thanks,
> Carl
>

BackUp

I have a real time database and backup database. I want to create a DTS package to copy the data from real time to backup in bulk mode.You might think about using standard backup and restore, it is faster than a DTS copy of any sort. I use a utility called robocopy from one of the res kits for Windows to copy only the new files to a remote server (tran logs and backups)

HTH|||you can use log shipping to transfer transaction logs to another server