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 failing! HELP!

I'm trying to backup a SQL 7.0 database to a network server (NT) from
Enterprise Manager and am getting the following error:

Title bar: Microsoft SQL DMO (ODBC SQL State: 42000)
Message: Backup or restore operation terminating abnormally.

The SQL Log has the following message:
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\myserver\bu_sql$\bu_mydb1.bak'. Operating system error 64(The
specified network name is no longer available.).

When I run a scheduled job that backs up mydb1, it fails with the
following message: Processed 50968 pages for database 'mydb1', file
'mydb1_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1
pages for database 'mydb1', file 'mydb1_Log' on file 1. [SQLSTATE
01000] (Message 4035) Backup or restore operation terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

This appears to a network problem but the transaction log dumps from
the same database to the same network share work fine as does a full
backup of a different database (on the same SQL Server).

The file bu_mydb1.bak is being created on the network drive. The
network drive has plenty of available space. The file is only 423MB
and the share has 9GB free space.

Any ideas?jeff.strange@.lrc.state.ky.us (Jeff) wrote in message news:<7dafc839.0401130705.1dc48e96@.posting.google.com>...
> I'm trying to backup a SQL 7.0 database to a network server (NT) from
> Enterprise Manager and am getting the following error:
> Title bar: Microsoft SQL DMO (ODBC SQL State: 42000)
> Message: Backup or restore operation terminating abnormally.
> The SQL Log has the following message:
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\myserver\bu_sql$\bu_mydb1.bak'. Operating system error 64(The
> specified network name is no longer available.).
> When I run a scheduled job that backs up mydb1, it fails with the
> following message: Processed 50968 pages for database 'mydb1', file
> 'mydb1_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1
> pages for database 'mydb1', file 'mydb1_Log' on file 1. [SQLSTATE
> 01000] (Message 4035) Backup or restore operation terminating
> abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

There is an MS document that says your destination/remote server 'is
under stress' and you are getting i.o hits, based on error 3013. You
might look at the scheduling of the backup job.

The 3013 error says your remote disk drive 'is user stress'.
Basically, it is a timing/timeout because of the amount of disk
activity on the remote server.
> This appears to a network problem but the transaction log dumps from
> the same database to the same network share work fine as does a full
> backup of a different database (on the same SQL Server).
> The file bu_mydb1.bak is being created on the network drive. The
> network drive has plenty of available space. The file is only 423MB
> and the share has 9GB free space.
> Any ideas?

Backup Exec and MDAC update

I have a client in a Windows 2000 SP4 network environment
that is using Backup Exec 9.0 with a remote agent for
Exchange and a remote server. They ran the Windows
Updates last Friday and now they are receiving errors on
their backup job when it tries to back up the server that
they updated. The event id in the event viewer is 34323
and reads as follows:
Update to catalog file Catalog index database failed.
Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]
Violation of PRIMARY KEY
constraint 'PK_CatMedia_68487DD7'. Cannot insert dupl
cat_RecordSet:Reopen[]
d:\be\tybee\4367r\becat\server\dll\catme
dia.cpp[753]
I also get the following event id 34338 in conjunction
with the above error:
Backup Exec Alert: Catalog Error
[Server:"servername"]ODBC access error. Possible lost
connection to database or unsuccessful access to catalog
index in the database.
I have submitted this to Veritas forum as well but if
anyone has any ideas, I would appreciate it. The Windows
Update apparently applied KB832483 which is an MDAC
update. I don't see where I can roll this back either.
Thanks. DeannaDeanna,
did you ever figure out a solution to this problem? i'm experiencing
the same thing in the same type of environment.
thank you,
Lenny.
Deanna wrote:
> *I have a client in a Windows 2000 SP4 network environment
> that is using Backup Exec 9.0 with a remote agent for
> Exchange and a remote server. They ran the Windows
> Updates last Friday and now they are receiving errors on
> their backup job when it tries to back up the server that
> they updated. The event id in the event viewer is 34323
> and reads as follows:
> Update to catalog file Catalog index database failed.
> Reason: [Microsoft][ODBC SQL Server Driver][SQL Server]
> Violation of PRIMARY KEY
> constraint 'PK_CatMedia_68487DD7'. Cannot insert dupl
> cat_RecordSet:Reopen[]
> d:\be\tybee\4367r\becat\server\dll\catme
dia.cpp[753]
> I also get the following event id 34338 in conjunction
> with the above error:
> Backup Exec Alert: Catalog Error
> [Server:"servername"]ODBC access error. Possible lost
> connection to database or unsuccessful access to catalog
> index in the database.
> I have submitted this to Veritas forum as well but if
> anyone has any ideas, I would appreciate it. The Windows
> Update apparently applied KB832483 which is an MDAC
> update. I don't see where I can roll this back either.
> Thanks. Deanna *
lennyi
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message422513.html

Backup Error - Operating system error 1450

Hi,
Backing up 70Gb database to the network drive on the backup server. Was
working for long time until now. I think the database size is growing and
the OS cannot handle it. Error messages are as follows,
"Operating system error 1450(Insufficient system resources exist to complete
the requested service."
Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
Not sure which server should add the registry key PoolUsageMaximum ? (On
backup server or SQL server ?)
Had set the registry key PoolUsageMaximum to 40 on backup server but no good.
Please advise !
in general, I think it's better to backup to a local disk. that way if the
network goes down during the backup, you still have a backup. when the
backup succeeds, you can copy it to the network share then delete the local
copy.
if you backup to the share only, you are toast if the network hiccups. then
you have data loss and are soon looking for a new job.
http://elsasoft.org
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:9BB1A66C-170D-49DE-9667-2AF306E75996@.microsoft.com...
> Hi,
> Backing up 70Gb database to the network drive on the backup server. Was
> working for long time until now. I think the database size is growing and
> the OS cannot handle it. Error messages are as follows,
> "Operating system error 1450(Insufficient system resources exist to
> complete
> the requested service."
> Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
> Not sure which server should add the registry key PoolUsageMaximum ? (On
> backup server or SQL server ?)
> Had set the registry key PoolUsageMaximum to 40 on backup server but no
> good.
> Please advise !
>
>
>
>
|||I know it is highly recommended to backup SQL databases on local drive. This
working place is gradually changing the practice to do the right things but
takes times.
I really need to fix this issues right now.
Any solutions ?
"Jesse Hersch" wrote:

> in general, I think it's better to backup to a local disk. that way if the
> network goes down during the backup, you still have a backup. when the
> backup succeeds, you can copy it to the network share then delete the local
> copy.
> if you backup to the share only, you are toast if the network hiccups. then
> you have data loss and are soon looking for a new job.
> --
> http://elsasoft.org
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:9BB1A66C-170D-49DE-9667-2AF306E75996@.microsoft.com...
>
>

Backup Error - Operating system error 1450

Hi,
Backing up 70Gb database to the network drive on the backup server. Was
working for long time until now. I think the database size is growing and
the OS cannot handle it. Error messages are as follows,
"Operating system error 1450(Insufficient system resources exist to complete
the requested service."
Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
Not sure which server should add the registry key PoolUsageMaximum ? (On
backup server or SQL server ?)
Had set the registry key PoolUsageMaximum to 40 on backup server but no good
.
Please advise !in general, I think it's better to backup to a local disk. that way if the
network goes down during the backup, you still have a backup. when the
backup succeeds, you can copy it to the network share then delete the local
copy.
if you backup to the share only, you are toast if the network hiccups. then
you have data loss and are soon looking for a new job.
http://elsasoft.org
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:9BB1A66C-170D-49DE-9667-2AF306E75996@.microsoft.com...
> Hi,
> Backing up 70Gb database to the network drive on the backup server. Was
> working for long time until now. I think the database size is growing and
> the OS cannot handle it. Error messages are as follows,
> "Operating system error 1450(Insufficient system resources exist to
> complete
> the requested service."
> Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
> Not sure which server should add the registry key PoolUsageMaximum ? (On
> backup server or SQL server ?)
> Had set the registry key PoolUsageMaximum to 40 on backup server but no
> good.
> Please advise !
>
>
>
>|||I know it is highly recommended to backup SQL databases on local drive. Thi
s
working place is gradually changing the practice to do the right things but
takes times.
I really need to fix this issues right now.
Any solutions ?
"Jesse Hersch" wrote:

> in general, I think it's better to backup to a local disk. that way if th
e
> network goes down during the backup, you still have a backup. when the
> backup succeeds, you can copy it to the network share then delete the loca
l
> copy.
> if you backup to the share only, you are toast if the network hiccups. th
en
> you have data loss and are soon looking for a new job.
> --
> http://elsasoft.org
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:9BB1A66C-170D-49DE-9667-2AF306E75996@.microsoft.com...
>
>

Backup Error - Operating system error 1450

Hi,
Backing up 70Gb database to the network drive on the backup server. Was
working for long time until now. I think the database size is growing and
the OS cannot handle it. Error messages are as follows,
"Operating system error 1450(Insufficient system resources exist to complete
the requested service."
Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
Not sure which server should add the registry key PoolUsageMaximum ? (On
backup server or SQL server ?)
Had set the registry key PoolUsageMaximum to 40 on backup server but no good.
Please advise !in general, I think it's better to backup to a local disk. that way if the
network goes down during the backup, you still have a backup. when the
backup succeeds, you can copy it to the network share then delete the local
copy.
if you backup to the share only, you are toast if the network hiccups. then
you have data loss and are soon looking for a new job. :)
--
http://elsasoft.org
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:9BB1A66C-170D-49DE-9667-2AF306E75996@.microsoft.com...
> Hi,
> Backing up 70Gb database to the network drive on the backup server. Was
> working for long time until now. I think the database size is growing and
> the OS cannot handle it. Error messages are as follows,
> "Operating system error 1450(Insufficient system resources exist to
> complete
> the requested service."
> Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
> Not sure which server should add the registry key PoolUsageMaximum ? (On
> backup server or SQL server ?)
> Had set the registry key PoolUsageMaximum to 40 on backup server but no
> good.
> Please advise !
>
>
>
>|||I know it is highly recommended to backup SQL databases on local drive. This
working place is gradually changing the practice to do the right things but
takes times.
I really need to fix this issues right now.
Any solutions ?
"Jesse Hersch" wrote:
> in general, I think it's better to backup to a local disk. that way if the
> network goes down during the backup, you still have a backup. when the
> backup succeeds, you can copy it to the network share then delete the local
> copy.
> if you backup to the share only, you are toast if the network hiccups. then
> you have data loss and are soon looking for a new job. :)
> --
> http://elsasoft.org
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:9BB1A66C-170D-49DE-9667-2AF306E75996@.microsoft.com...
> > Hi,
> >
> > Backing up 70Gb database to the network drive on the backup server. Was
> > working for long time until now. I think the database size is growing and
> > the OS cannot handle it. Error messages are as follows,
> >
> > "Operating system error 1450(Insufficient system resources exist to
> > complete
> > the requested service."
> >
> > Looking at MS KB - http://support.microsoft.com/default.aspx/kb/304101
> >
> > Not sure which server should add the registry key PoolUsageMaximum ? (On
> > backup server or SQL server ?)
> > Had set the registry key PoolUsageMaximum to 40 on backup server but no
> > good.
> >
> > Please advise !
> >
> >
> >
> >
> >
> >
> >
>
>

BackUp error

I had a backup scheduled for a a time when people are using the website.
I got this error...
59System.Data.SqlClient.SqlException: General network error. Check your
network documentation
Shouldn't you be able to backup while people are using the database ?
It is about 4.5 Gigs in size -- would that make a difference ?
Thanks,
CraigThere is a timeout property that you need to increase.
It seems like backup in your case takes for a while and client
just doesn't wait til end of it.
Connection timeou
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdatasqlclientsqlconnectionclassconnectionstringtopic.asp
Command timeou
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdatasqlclientsqlcommandclasscommandtimeouttopic.asp
Regards.
"Craig HB" wrote:
> I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig|||Hi
Yes you should be able to backup. General network error may mean that the
client is timing out, therefore you may want to increase the timeout or use a
scheduled task instead.
John
"Craig HB" wrote:
> I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig|||Hi,
Yes, Backup is an online operation. Database size is not an issue for the
backup. Could you install SP3a or SP 4 (if not AWE enabled)
and try to do a backup again from Server machine Query analyzer (USE the
below command).
Backup database <dbname> to disk='d:\backup\dbname.bak' with init,stats=10
Thanks
Hari
SQL Server MVP
"Craig HB" <CraigHB@.discussions.microsoft.com> wrote in message
news:532C1A36-2C2E-4F06-B0F0-7F2342D144E6@.microsoft.com...
>I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig

Backup Error

Hi Guys,
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a écrit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_200602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.

Backup Error

Hi Guys,
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.
Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a crit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.
|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30.231\dbbackups\rptserver\Revenues_db_ 200602280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30.231\dbbackups\rptserver\Revenues_db_2 00602280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.

BackUp error

I had a backup scheduled for a a time when people are using the website.
I got this error...
59System.Data.SqlClient.SqlException: General network error. Check your
network documentation
Shouldn't you be able to backup while people are using the database ?
It is about 4.5 Gigs in size -- would that make a difference ?
Thanks,
Craig
Hi
Yes you should be able to backup. General network error may mean that the
client is timing out, therefore you may want to increase the timeout or use a
scheduled task instead.
John
"Craig HB" wrote:

> I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig
|||Hi,
Yes, Backup is an online operation. Database size is not an issue for the
backup. Could you install SP3a or SP 4 (if not AWE enabled)
and try to do a backup again from Server machine Query analyzer (USE the
below command).
Backup database <dbname> to disk='d:\backup\dbname.bak' with init,stats=10
Thanks
Hari
SQL Server MVP
"Craig HB" <CraigHB@.discussions.microsoft.com> wrote in message
news:532C1A36-2C2E-4F06-B0F0-7F2342D144E6@.microsoft.com...
>I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig

Backup Error

Hi Guys,
I am facing a problem with sql server 2000 sp3 backup to network.This backuP
is as part of scheduled backup to another server in the same network and was
working fine for the last 3 yrs But Recently the backUP is failing with
following errors
BackupMedium::ReportIoError: write failure on backup device
'\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
Operating system error 121(The semaphore timeout period has expired.).
Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
m_actualBytes: 0, m_errcode: 121, BackupFile:
\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
I have formateed the destination drive to where backup is taking place but
still same error.
the backup file size is 8.5 GB.
Pls Aedvice.Not to alarm you but I found something out on the web about this strange
error...
http://www.thescripts.com/forum/thread78842.html
might worth the look...
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> a crit
dans le message de news:
281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.|||my daily backup failed one night after I applied one of monthly patches from
MS. Removing the patch fixed the problem. I called MS. At first they
asked me to update the drivers but I did everything before I called them.
Then they blamed the hardware but I threw back I was using a Compaq server
with compatible h/w to run the system per MS. Later they showed me to
generate a server dump and sent it to MS.
After more than a week with lot of calls, and 3 dumps sent to MS, they said
it was a bug but won't fix it since it just happen to this server with this
controller.
p.s. my server is Compaq DL380, windows 2000, sql 2000 sp4.
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:281CE432-4B50-44CE-A299-19653E1AEF37@.microsoft.com...
> Hi Guys,
> I am facing a problem with sql server 2000 sp3 backup to network.This
> backuP
> is as part of scheduled backup to another server in the same network and
> was
> working fine for the last 3 yrs But Recently the backUP is failing with
> following errors
> BackupMedium::ReportIoError: write failure on backup device
> '\\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK'.
> Operating system error 121(The semaphore timeout period has expired.).
> Internal I/O request 0x3CF14628: Op: Write, pBuffer: 0x08260000, Size:
> 983040, Position: 12786176, UMS: Internal: 0x0, InternalHigh: 0xF0000,
> Offset: 0xC31A00, OffsetHigh: 0x0, m_buf: 0x08260000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 121, BackupFile:
> \\192.168.30. 231\dbbackups\rptserver\Revenues_db_2006
02280100.BAK
> I have formateed the destination drive to where backup is taking place but
> still same error.
> the backup file size is 8.5 GB.
> Pls Aedvice.

BackUp error

I had a backup scheduled for a a time when people are using the website.
I got this error...
59System.Data.SqlClient.SqlException: General network error. Check your
network documentation
Shouldn't you be able to backup while people are using the database ?
It is about 4.5 Gigs in size -- would that make a difference ?
Thanks,
CraigHi
Yes you should be able to backup. General network error may mean that the
client is timing out, therefore you may want to increase the timeout or use
a
scheduled task instead.
John
"Craig HB" wrote:

> I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig|||Hi,
Yes, Backup is an online operation. Database size is not an issue for the
backup. Could you install SP3a or SP 4 (if not AWE enabled)
and try to do a backup again from Server machine Query analyzer (USE the
below command).
Backup database <dbname> to disk='d:\backup\dbname.bak' with init,stats=10
Thanks
Hari
SQL Server MVP
"Craig HB" <CraigHB@.discussions.microsoft.com> wrote in message
news:532C1A36-2C2E-4F06-B0F0-7F2342D144E6@.microsoft.com...
>I had a backup scheduled for a a time when people are using the website.
> I got this error...
> 59System.Data.SqlClient.SqlException: General network error. Check your
> network documentation
> Shouldn't you be able to backup while people are using the database ?
> It is about 4.5 Gigs in size -- would that make a difference ?
> Thanks,
> Craig

Backup Device Location

Is it possible to point a backup device to a network location? I have a mapp
ed drive on my SQL Server to a share on another server (Q: drive). The backu
p device points to that Q drive. However, everytime I run the backup, it say
s it cannot reach the speci
fied location. The drive is mapped and the administrator is logged onto the
server, so there should not be a rights issue.
-BrianBrian,
You are better to use UNC names \\server\share\etc instead of mapped =
drive letters. Mapped drives are local to the account that mapped them, =
and therefore may not be visible to the account that the SQl Server =
service is running under. You need to check what account is being used =
for the MSSQLSERVER service and ensure that account has the necessary =
access rights to the remote server. Who is logged on at the other =
machine will make no difference.
Mike John
"Brian" <anonymous@.discussions.microsoft.com> wrote in message =
news:69161F98-4357-4CD0-900E-A229A9917C95@.microsoft.com...
> Is it possible to point a backup device to a network location? I have =
a mapped drive on my SQL Server to a share on another server (Q: drive). =
The backup device points to that Q drive. However, everytime I run the =
backup, it says it cannot reach the specified location. The drive is =
mapped and the administrator is logged onto the server, so there should =
not be a rights issue.
>=20
> -Brian|||Try using a UNC name instead of a mapped drive letter ie
backup database master to disk = '\\server2\backupshare\master.mak' with
init
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.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
"Brian" <anonymous@.discussions.microsoft.com> wrote in message
news:69161F98-4357-4CD0-900E-A229A9917C95@.microsoft.com...
> Is it possible to point a backup device to a network location? I have a
mapped drive on my SQL Server to a share on another server (Q: drive). The
backup device points to that Q drive. However, everytime I run the backup,
it says it cannot reach the specified location. The drive is mapped and the
administrator is logged onto the server, so there should not be a rights
issue.
> -Brian|||The UNC path worked. Thanks.sql

BACKUP db to network machine

Hi all
win 2k pro (on all machines)
sql 2k (1 machine)
in our maintance plan I have the DB backing up every 24 hours - this
backup is into the default BACKUPS folder - on the SAME machine &
drive.
I would also like the maintance plan to back up the DB accross the
network to a 2nd machine (where we keep all our backups of other
files) but in the "backup device" bit it's only listing the c:\ and
not any netword paths...
Q) How can i get it to back up across the network to a 2nd machine in
the maintance plan?
thanks
AlIN SEM simply select backup... then choose Add button and type in the unc
name ie
\\london\sqlshare\mybackup.bak and you will be good ( as long as permissions
allow.)
"Harag" <harag@.softhome.net> wrote in message
news:kd47kvcm6qrpmbda1jes9rk1pm8oqgg5bn@.4ax.com...
> Hi all
> win 2k pro (on all machines)
> sql 2k (1 machine)
> in our maintance plan I have the DB backing up every 24 hours - this
> backup is into the default BACKUPS folder - on the SAME machine &
> drive.
> I would also like the maintance plan to back up the DB accross the
> network to a 2nd machine (where we keep all our backups of other
> files) but in the "backup device" bit it's only listing the c:\ and
> not any netword paths...
> Q) How can i get it to back up across the network to a 2nd machine in
> the maintance plan?
> thanks
> Al|||Harag,
Set up a share in the destination server and use UNC pattern, as in
BACKUP DATABASE <dbname>
TO DISK = '\\destserver\d$\dbbackup.BAK'
That said, I have seen that backing across the network can slow things
down.Do the backup locally and then have some process to copy the file over.
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Harag" <harag@.softhome.net> wrote in message
news:kd47kvcm6qrpmbda1jes9rk1pm8oqgg5bn@.4ax.com...
> Hi all
> win 2k pro (on all machines)
> sql 2k (1 machine)
> in our maintance plan I have the DB backing up every 24 hours - this
> backup is into the default BACKUPS folder - on the SAME machine &
> drive.
> I would also like the maintance plan to back up the DB accross the
> network to a 2nd machine (where we keep all our backups of other
> files) but in the "backup device" bit it's only listing the c:\ and
> not any netword paths...
> Q) How can i get it to back up across the network to a 2nd machine in
> the maintance plan?
> thanks
> Al

Backup database over network not working.

The database server is on computer P4.
Computer P3 has a shared folder with full access.
Computer P5 on which I have my Backup Device and will execute the Backup Database Command using Query Analyzer.

On P5 I created the Backup Device:

USE master
EXEC sp_addumpdevice 'disk', 'myDevice',
'\\P3\temp\test.bak'

Then I executed the following on P5 Query Analyzer:

Backup Database myDatabase TO myDevice

But I get this error:

Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'myDevice'. Device error or device off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.

Any idea? Thanks and regards.Originally posted by juniper
The database server is on computer P4.
Computer P3 has a shared folder with full access.
Computer P5 on which I have my Backup Device and will execute the Backup Database Command using Query Analyzer.

On P5 I created the Backup Device:

USE master
EXEC sp_addumpdevice 'disk', 'myDevice',
'\\P3\temp\test.bak'

Then I executed the following on P5 Query Analyzer:

Backup Database myDatabase TO myDevice

But I get this error:

Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'myDevice'. Device error or device off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.

Any idea? Thanks and regards.

yeah, go into Enterprise Manager, right click on the db you are trying to backup and all tasks - bring online|||Better yet...don't dump across a network...

It'll be much slower and be at risk for blips in the network...

Dump local then copy...|||Hi guys, thanks for your advice. Brett, I am doing it the way you suggested. However, it would mean that the computer running the database server would have to have a folder permanently shared for my program to copy the file across the network.

Any workaround so that I do not need to share folders? The user might inadvertently unshare the folder and would create problems.

Thanks and regards.|||Ensure the account used to execute this task does have required privileges to access the share specified.

If you're scheduling this task then ensure SQLAgent account used does have admin privileges or a domain account to access so.

Backup Database on the network

I tried to backup the database on the network, which is in the same
workgroup; i received an ERROR message, Which says
"BackupDiskFile::CreateMedia: Backup device
'\\Servername\SharedName\FileName.BAK' failed to create. Operating system
error = 5(Access is denied.)."
Is there anyone have an idia to solve my problem. I appreciate your help.
Thanks.
The account that SQL Server runs under must have permissions to read and
write to that share.
Andrew J. Kelly SQL MVP
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>I tried to backup the database on the network, which is in the same
> workgroup; i received an ERROR message, Which says
> "BackupDiskFile::CreateMedia: Backup device
> '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> error = 5(Access is denied.)."
> Is there anyone have an idia to solve my problem. I appreciate your help.
> Thanks.
|||Also, check to make sure your SQL Service account is a domain account (but i
guess that would be implied).
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>I tried to backup the database on the network, which is in the same
> workgroup; i received an ERROR message, Which says
> "BackupDiskFile::CreateMedia: Backup device
> '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> error = 5(Access is denied.)."
> Is there anyone have an idia to solve my problem. I appreciate your help.
> Thanks.
|||We don't have any Domain, we are working in Workgroup model. The SQL Server
and the Server which I want to have backup on it, are in different Workgroup.
Is there any methode to solve this?
"Shaun Beane" wrote:

> Also, check to make sure your SQL Service account is a domain account (but i
> guess that would be implied).
> "betrek" <betrek@.discussions.microsoft.com> wrote in message
> news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>
>
|||Hi
Make sure SQL Server runs under an account where there is the same account
on both machines, with exactly the same passwords.
BTW, You can not use the Maintenance Plan Wizard as you need to use UNC
names. So you have to write T-SQL with the BACKUP command in it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:CB7AE853-4204-49EC-8684-889CF1FBB9B0@.microsoft.com...
> We don't have any Domain, we are working in Workgroup model. The SQL
Server
> and the Server which I want to have backup on it, are in different
Workgroup.[vbcol=seagreen]
> Is there any methode to solve this?
>
> "Shaun Beane" wrote:
(but i[vbcol=seagreen]
system[vbcol=seagreen]
help.[vbcol=seagreen]
|||There is a way to use Maintenance plans and UNC names together.
Here is a comprehensive set of instructions on exactly how to do it.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default...b;en-us;555128
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecSnti9MFHA.1308@.TK2MSFTNGP15.phx.gbl...
> Hi
> Make sure SQL Server runs under an account where there is the same account
> on both machines, with exactly the same passwords.
> BTW, You can not use the Maintenance Plan Wizard as you need to use UNC
> names. So you have to write T-SQL with the BACKUP command in it.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "betrek" <betrek@.discussions.microsoft.com> wrote in message
> news:CB7AE853-4204-49EC-8684-889CF1FBB9B0@.microsoft.com...
> Server
> Workgroup.
> (but i
> system
> help.
>

Backup Database on the network

I tried to backup the database on the network, which is in the same
workgroup; i received an ERROR message, Which says
"BackupDiskFile::CreateMedia: Backup device
'\\Servername\SharedName\FileName.BAK' failed to create. Operating system
error = 5(Access is denied.)."
Is there anyone have an idia to solve my problem. I appreciate your help.
Thanks.The account that SQL Server runs under must have permissions to read and
write to that share.
--
Andrew J. Kelly SQL MVP
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>I tried to backup the database on the network, which is in the same
> workgroup; i received an ERROR message, Which says
> "BackupDiskFile::CreateMedia: Backup device
> '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> error = 5(Access is denied.)."
> Is there anyone have an idia to solve my problem. I appreciate your help.
> Thanks.|||Also, check to make sure your SQL Service account is a domain account (but i
guess that would be implied).
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>I tried to backup the database on the network, which is in the same
> workgroup; i received an ERROR message, Which says
> "BackupDiskFile::CreateMedia: Backup device
> '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> error = 5(Access is denied.)."
> Is there anyone have an idia to solve my problem. I appreciate your help.
> Thanks.|||We don't have any Domain, we are working in Workgroup model. The SQL Server
and the Server which I want to have backup on it, are in different Workgroup.
Is there any methode to solve this?
"Shaun Beane" wrote:
> Also, check to make sure your SQL Service account is a domain account (but i
> guess that would be implied).
> "betrek" <betrek@.discussions.microsoft.com> wrote in message
> news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
> >I tried to backup the database on the network, which is in the same
> > workgroup; i received an ERROR message, Which says
> > "BackupDiskFile::CreateMedia: Backup device
> > '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> > error = 5(Access is denied.)."
> > Is there anyone have an idia to solve my problem. I appreciate your help.
> >
> > Thanks.
>
>|||Hi
Make sure SQL Server runs under an account where there is the same account
on both machines, with exactly the same passwords.
BTW, You can not use the Maintenance Plan Wizard as you need to use UNC
names. So you have to write T-SQL with the BACKUP command in it.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:CB7AE853-4204-49EC-8684-889CF1FBB9B0@.microsoft.com...
> We don't have any Domain, we are working in Workgroup model. The SQL
Server
> and the Server which I want to have backup on it, are in different
Workgroup.
> Is there any methode to solve this?
>
> "Shaun Beane" wrote:
> > Also, check to make sure your SQL Service account is a domain account
(but i
> > guess that would be implied).
> >
> > "betrek" <betrek@.discussions.microsoft.com> wrote in message
> > news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
> > >I tried to backup the database on the network, which is in the same
> > > workgroup; i received an ERROR message, Which says
> > > "BackupDiskFile::CreateMedia: Backup device
> > > '\\Servername\SharedName\FileName.BAK' failed to create. Operating
system
> > > error = 5(Access is denied.)."
> > > Is there anyone have an idia to solve my problem. I appreciate your
help.
> > >
> > > Thanks.
> >
> >
> >|||There is a way to use Maintenance plans and UNC names together.
Here is a comprehensive set of instructions on exactly how to do it.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecSnti9MFHA.1308@.TK2MSFTNGP15.phx.gbl...
> Hi
> Make sure SQL Server runs under an account where there is the same account
> on both machines, with exactly the same passwords.
> BTW, You can not use the Maintenance Plan Wizard as you need to use UNC
> names. So you have to write T-SQL with the BACKUP command in it.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "betrek" <betrek@.discussions.microsoft.com> wrote in message
> news:CB7AE853-4204-49EC-8684-889CF1FBB9B0@.microsoft.com...
>> We don't have any Domain, we are working in Workgroup model. The SQL
> Server
>> and the Server which I want to have backup on it, are in different
> Workgroup.
>> Is there any methode to solve this?
>>
>> "Shaun Beane" wrote:
>> > Also, check to make sure your SQL Service account is a domain account
> (but i
>> > guess that would be implied).
>> >
>> > "betrek" <betrek@.discussions.microsoft.com> wrote in message
>> > news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>> > >I tried to backup the database on the network, which is in the same
>> > > workgroup; i received an ERROR message, Which says
>> > > "BackupDiskFile::CreateMedia: Backup device
>> > > '\\Servername\SharedName\FileName.BAK' failed to create. Operating
> system
>> > > error = 5(Access is denied.)."
>> > > Is there anyone have an idia to solve my problem. I appreciate your
> help.
>> > >
>> > > Thanks.
>> >
>> >
>> >
>

Backup Database on the network

I tried to backup the database on the network, which is in the same
workgroup; i received an ERROR message, Which says
"BackupDiskFile::CreateMedia: Backup device
'\\Servername\SharedName\FileName.BAK' failed to create. Operating system
error = 5(Access is denied.)."
Is there anyone have an idia to solve my problem. I appreciate your help.
Thanks.The account that SQL Server runs under must have permissions to read and
write to that share.
Andrew J. Kelly SQL MVP
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>I tried to backup the database on the network, which is in the same
> workgroup; i received an ERROR message, Which says
> "BackupDiskFile::CreateMedia: Backup device
> '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> error = 5(Access is denied.)."
> Is there anyone have an idia to solve my problem. I appreciate your help.
> Thanks.|||Also, check to make sure your SQL Service account is a domain account (but i
guess that would be implied).
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>I tried to backup the database on the network, which is in the same
> workgroup; i received an ERROR message, Which says
> "BackupDiskFile::CreateMedia: Backup device
> '\\Servername\SharedName\FileName.BAK' failed to create. Operating system
> error = 5(Access is denied.)."
> Is there anyone have an idia to solve my problem. I appreciate your help.
> Thanks.|||We don't have any Domain, we are working in Workgroup model. The SQL Server
and the Server which I want to have backup on it, are in different Workgroup
.
Is there any methode to solve this?
"Shaun Beane" wrote:

> Also, check to make sure your SQL Service account is a domain account (but
i
> guess that would be implied).
> "betrek" <betrek@.discussions.microsoft.com> wrote in message
> news:6387F0CA-A717-467A-9F4B-F0EF7AED2D5A@.microsoft.com...
>
>|||Hi
Make sure SQL Server runs under an account where there is the same account
on both machines, with exactly the same passwords.
BTW, You can not use the Maintenance Plan Wizard as you need to use UNC
names. So you have to write T-SQL with the BACKUP command in it.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"betrek" <betrek@.discussions.microsoft.com> wrote in message
news:CB7AE853-4204-49EC-8684-889CF1FBB9B0@.microsoft.com...
> We don't have any Domain, we are working in Workgroup model. The SQL
Server
> and the Server which I want to have backup on it, are in different
Workgroup.[vbcol=seagreen]
> Is there any methode to solve this?
>
> "Shaun Beane" wrote:
>
(but i[vbcol=seagreen]
system[vbcol=seagreen]
help.[vbcol=seagreen]|||There is a way to use Maintenance plans and UNC names together.
Here is a comprehensive set of instructions on exactly how to do it.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/defaul...kb;en-us;555128
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ecSnti9MFHA.1308@.TK2MSFTNGP15.phx.gbl...
> Hi
> Make sure SQL Server runs under an account where there is the same account
> on both machines, with exactly the same passwords.
> BTW, You can not use the Maintenance Plan Wizard as you need to use UNC
> names. So you have to write T-SQL with the BACKUP command in it.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "betrek" <betrek@.discussions.microsoft.com> wrote in message
> news:CB7AE853-4204-49EC-8684-889CF1FBB9B0@.microsoft.com...
> Server
> Workgroup.
> (but i
> system
> help.
>