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 database by maintenance plan

1. create new MaintenancePlan to get a full backup of myDb by Wizzard,... the message is:
create failed for JobStep 'Subplan' ... the specified '@.subsystem' is invalid .. Error 14234

2. create new MaintenancePlan without the Wizzard, by drag and drop "Back Up Database Task" and configured to full backup myDb scheduled daily the message is: create failed for Job 'MaintenancePlan'
the plan exists without scheduling, after modifying get the message
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-...).
? can I get help ? - Thanks

sorry, the problem was solving by installation SSIS - Integration Services... Greetings!|||Thx! After installing SSIS, this strange problem was happily solved!!|||

There is a KB article to resolve the above error.

http://support.microsoft.com/?kbid=922651

backup database by maintenance plan

1. create new MaintenancePlan to get a full backup of myDb by Wizzard,... the message is:
create failed for JobStep 'Subplan' ... the specified '@.subsystem' is invalid .. Error 14234

2. create new MaintenancePlan without the Wizzard, by drag and drop "Back Up Database Task" and configured to full backup myDb scheduled daily the message is: create failed for Job 'MaintenancePlan'
the plan exists without scheduling, after modifying get the message
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-...).
? can I get help ? - Thanks

sorry, the problem was solving by installation SSIS - Integration Services... Greetings!|||Thx! After installing SSIS, this strange problem was happily solved!!|||

There is a KB article to resolve the above error.

http://support.microsoft.com/?kbid=922651

backup database by maintenance plan

1. create new MaintenancePlan to get a full backup of myDb by Wizzard,... the message is:
create failed for JobStep 'Subplan' ... the specified '@.subsystem' is invalid .. Error 14234

2. create new MaintenancePlan without the Wizzard, by drag and drop "Back Up Database Task" and configured to full backup myDb scheduled daily the message is: create failed for Job 'MaintenancePlan'
the plan exists without scheduling, after modifying get the message
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-...).
? can I get help ? - Thanks

sorry, the problem was solving by installation SSIS - Integration Services... Greetings!|||Thx! After installing SSIS, this strange problem was happily solved!!|||

There is a KB article to resolve the above error.

http://support.microsoft.com/?kbid=922651

backup

Who could tell me how I can know when the specified database was backup and
how long I dnt backup my database and who does the backup?
Thanks
huiIf you simply need to know when the DB was last backup you can select
TaskPadview in EM. If you need a little more you can open a backup file
using RESTORE HEADERONLY.
M|||This information is available in the four backup history tables in the msdb
database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"hui" <gary1971_cn@.163.com> wrote in message news:uyvRKfJ1FHA.3300@.TK2MSFTNGP15.phx.gbl...[v
bcol=seagreen]
> Who could tell me how I can know when the specified database was backup an
d
> how long I dnt backup my database and who does the backup?
> Thanks
> hui
>[/vbcol]

backup

Who could tell me how I can know when the specified database was backup and
how long I dnt backup my database and who does the backup?
Thanks
hui
If you simply need to know when the DB was last backup you can select
TaskPadview in EM. If you need a little more you can open a backup file
using RESTORE HEADERONLY.
M
|||This information is available in the four backup history tables in the msdb database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"hui" <gary1971_cn@.163.com> wrote in message news:uyvRKfJ1FHA.3300@.TK2MSFTNGP15.phx.gbl...
> Who could tell me how I can know when the specified database was backup and
> how long I dnt backup my database and who does the backup?
> Thanks
> hui
>

backup

Who could tell me how I can know when the specified database was backup and
how long I dnt backup my database and who does the backup?
Thanks
huiIf you simply need to know when the DB was last backup you can select
TaskPadview in EM. If you need a little more you can open a backup file
using RESTORE HEADERONLY.
M|||This information is available in the four backup history tables in the msdb database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"hui" <gary1971_cn@.163.com> wrote in message news:uyvRKfJ1FHA.3300@.TK2MSFTNGP15.phx.gbl...
> Who could tell me how I can know when the specified database was backup and
> how long I dnt backup my database and who does the backup?
> Thanks
> hui
>