Backup fails with Operating system error 33

Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...
> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.sql

Backup fails with Operating system error 33

Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...

quote:

---

> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.

---

Backup failed to complete the command backup database

Backup failed to complete the command backup database [ ] TO VIRTUAL DEVICE = ' { 853D3FC0 - 45EA -85B1 - 54F0EA379CAC } 24 ' WITH SNAPSHOT , BUFFERCOUNT = 1 , BLOCKSIZE = 1024

Raghu could pls post the error you get while executing this command ? ? ? anything from the error log ?

Thanks

Deepak

sql

Backup Errors in sqlserver

Hello all,

How can I resolve this error message I keep getting when I try to backup my database?

Thanks in Advance.

"Can't open dump device 'D:\MSSQL\BACKUP\dmpApp_tracker.DAT', device error or device off line. Please consult the SQL Server error log for more details. (Message 3201)"Are you appending to the device? I've seen this happen when an active backup operation gets interrupted. After that the device needs to be re-created. If you were appending backups to it see if you can recover the ones that you intend to keep.|||No, I am not appending to it. This is sqlserver 6.5 and it does not give you that option. It does have a expire after date and I set that to 7. Thanks for the help.|||6.5?

Deal me out...

What did the error log say?|||Yes it does! WITH NOINIT is available in 6.5 SP5a, look closely!

Backup Error: sql-dom sql state 4200

When trying to backup a sql2000 database I receive the following error:
"Microsoft SQL-DOM (odbc sqlstate: 42000)
The Volume on device xxx e:\backupfilename.bak belongs to a different media set.
Backup or restore operation terminating abnormally."
Thanks for any help,
JimIf you have no use for the existing backup file, you could
either delete the file from the file system before doing
the backup or add the FORMAT option to the BACKUP
statement.
Linchi
>--Original Message--
>When trying to backup a sql2000 database I receive the
following error:
>"Microsoft SQL-DOM (odbc sqlstate: 42000)
>The Volume on device xxx e:\backupfilename.bak belongs to
a different media set.
>Backup or restore operation terminating abnormally."
>Thanks for any help,
>Jim
>
>.
>

Backup Error Message

I am receiving a BackupDiskFile::RequestDurableMedia error when backing up to a backup device pointing to a file on the hard drive. This only happens for one of the devices and there are several others, configured similarly, that work just fine. I'm won
dering if anyone has seen this before and can shed some light on what could be causing this. The error message continues with: Operating system error 64 (The specified network name is no longer available).
Sometimes you will see this with the larger backups If you are trying to
backing up locally using a network share. Attempt the backup by using the
file path instead of the share name.
HTH
SQL Server Support
Agnes Panosian

Backup Error Message

I am receiving a BackupDiskFile::RequestDurableMedia error when backing up t
o a backup device pointing to a file on the hard drive. This only happens f
or one of the devices and there are several others, configured similarly, th
at work just fine. I'm won
dering if anyone has seen this before and can shed some light on what could
be causing this. The error message continues with: Operating system error 6
4 (The specified network name is no longer available).Sometimes you will see this with the larger backups If you are trying to
backing up locally using a network share. Attempt the backup by using the
file path instead of the share name.
HTH
SQL Server Support
Agnes Panosiansql

Backup devices and expired backups

Hello, I am having a problem with backup devices, and
hope someone knows a solution.
I have created a backup device on my 100GB D: drive
called Mustang_Backup. The file is located at
D:\MSSQL\BACKUP\Mustang_Backup.BAK.
My maintenance plan is a full backup on Sunday and a
differential on all other days. These are working
correctly.
My server also has a 14 day retention setting.
My problem is that the backup device is not removing the
expired backups. I now have a 75GB backup file for a 3GB
database. I am concerned that the backups are going to
fill the entire drive and then start to fail.
Does anyone know of a way to delete or remove the expired
backups in a device?
Thanks for your help,
SteveYou can't keep the different backups in one device if you want to remove
some of them after a certain time. It's all or nothing in a single device.
If your using the MP then have it create different files for each backup and
it should work as expected.
--
Andrew J. Kelly
SQL Server MVP
"steve" <sgent001@.hotmail.com> wrote in message
news:055b01c35556$78041df0$a301280a@.phx.gbl...
> Hello, I am having a problem with backup devices, and
> hope someone knows a solution.
> I have created a backup device on my 100GB D: drive
> called Mustang_Backup. The file is located at
> D:\MSSQL\BACKUP\Mustang_Backup.BAK.
> My maintenance plan is a full backup on Sunday and a
> differential on all other days. These are working
> correctly.
> My server also has a 14 day retention setting.
> My problem is that the backup device is not removing the
> expired backups. I now have a 75GB backup file for a 3GB
> database. I am concerned that the backups are going to
> fill the entire drive and then start to fail.
> Does anyone know of a way to delete or remove the expired
> backups in a device?
> Thanks for your help,
> Stevesql

backup devices

hey all,
i'm trying to do a full backup on my database. there is a disk device
currently assigned to do a differential backup on the db. how do i get my
backup without messing up the current device. because there have been a
couple of times where i ran the backup using osq and it still ended up
changing the device and i didn't want it to do that.
thanks,
rodcharHi,
Use Maintenance Plan in Enterprise manager / SQL Server Management Studio to
do the full database backup. This will automatically create file names based
on Database name
and date and time stamp. Maintenance plan have an option of archival
also...s
Thanks
Hari
"rodchar" <rodchar@.discussions.microsoft.com> wrote in message
news:2DC3B373-0006-4C19-BECC-A277913BC48D@.microsoft.com...
> hey all,
> i'm trying to do a full backup on my database. there is a disk device
> currently assigned to do a differential backup on the db. how do i get my
> backup without messing up the current device. because there have been a
> couple of times where i ran the backup using osq and it still ended up
> changing the device and i didn't want it to do that.
> thanks,
> rodchar
>|||thank you for your help. rod.
"Hari Prasad" wrote:
> Hi,
> Use Maintenance Plan in Enterprise manager / SQL Server Management Studio to
> do the full database backup. This will automatically create file names based
> on Database name
> and date and time stamp. Maintenance plan have an option of archival
> also...s
> Thanks
> Hari
> "rodchar" <rodchar@.discussions.microsoft.com> wrote in message
> news:2DC3B373-0006-4C19-BECC-A277913BC48D@.microsoft.com...
> > hey all,
> > i'm trying to do a full backup on my database. there is a disk device
> > currently assigned to do a differential backup on the db. how do i get my
> > backup without messing up the current device. because there have been a
> > couple of times where i ran the backup using osq and it still ended up
> > changing the device and i didn't want it to do that.
> >
> > thanks,
> > rodchar
> >
>
>

Backup device?

Hi all,
I want to store bakup file on the computer on netword, so make a backup device on the other computer, it ok. after that i make an full backup, there is an error : "Can not open the bakup device " .
please show me,
best regard.share that network PC drive and if u still have any problem login into both pc with same login id...

that will surely resolve ur problem..

Cheers!!|||Originally posted by thanhtung2003
Hi all,

I want to store bakup file on the computer on netword, so make a backup device on the other computer, it ok. after that i make an full backup, there is an error : "Can not open the bakup device " .
please show me,
best regard.
Make sure you have write permission in that folder.
Or create log on credential at that newwork PC.

Backup Device vs backup command

Hi,

Will backup get completed quickly (the time taken for backing up large databases) on backup device or using backup command? If backup device, why?

You are talking about 2 different things here. You use the backup command to backup the DB and the backup device to store the backed up files.

Unless I dont understand your question.

|||Hi Dinakar,

I need to know which one completes backup faster, backup device or by using backup command. I heard that backup device completes backup quicker than using backup command.

Thanks|||

It's the same procedure, whether you commit it via a GUI (window menu->next->next...) or command prompt (BACKUP command) it makes no difference.

In both cases you use a backup device to backup your database. If you are a learner you'll probably use the user friendly windows menu. If you are advanced you'll probably use the SQL command: BACKUP

|||

Have you checked the same on your environment?

IMHO I don't see much difference in between and it makes a lot of difference betwen normal disks & RAID based ones.

BTW do you have any issues in your environment for such behaviour, if so let us know.

|||Hi Satya,

Im using RAID disks, when backing up 200GB of database, backup device completes faster than backup command. A 30 min difference..

Thanks|||If SQL Server stripes physical devices that have different input/output (I/O) throughputs, SQL Server optimizes for speed. This means that faster devices receive more backup data that is written to disk than the slower device in the same period of time. In SQL Server 2000, regardless of the I/O throughput differences, SQL Server tries to distribute the backup data evenly to the devices. In this case, the slower disk may become a backup bottleneck in terms of performance. If increasing performance is your primary goal, you must avoid using the slow disk in striping and use disks with comparable throughputs instead.

Backup Device size

I am looking for a way to retrieve the size of my backup devices. When I run sp_helpdevice, the backup devices with a cntrltype = 2 (which happen to be the only ones I am interested in), all return a size = 0. Any idea how to get the size using T-SQL?
Message posted via http://www.sqlmonster.com
How about the file_size in the BackupFile system table?
Andrew J. Kelly SQL MVP
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:a46bfcae27494128849870935f2de9b3@.SQLMonster.c om...
>I am looking for a way to retrieve the size of my backup devices. When I
>run sp_helpdevice, the backup devices with a cntrltype = 2 (which happen to
>be the only ones I am interested in), all return a size = 0. Any idea how
>to get the size using T-SQL?
> --
> Message posted via http://www.sqlmonster.com
|||That does not provide the size of the backup files (as in *.bak), but instead provides the files that are being backed up. I am looking for the size of the *.bak files.
Message posted via http://www.sqlmonster.com
|||OK then how about Backup_Size in sysbackuphistory?
Andrew J. Kelly SQL MVP
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:5d56319a8f704287b2cbe0cc361395fc@.SQLMonster.c om...
> That does not provide the size of the backup files (as in *.bak), but
> instead provides the files that are being backed up. I am looking for the
> size of the *.bak files.
> --
> Message posted via http://www.sqlmonster.com
|||I am running SQL 2000 and do not seem to be able to find sysbackuphistory.
Message posted via http://www.sqlmonster.com
|||I am sorry I meant the BackupSet system table.
Andrew J. Kelly SQL MVP
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:13e45dbcb76d4537a615b957827d5d8a@.SQLMonster.c om...
>I am running SQL 2000 and do not seem to be able to find sysbackuphistory.
> --
> Message posted via http://www.sqlmonster.com
sql

Backup Device size

I am looking for a way to retrieve the size of my backup devices. When I run
sp_helpdevice, the backup devices with a cntrltype = 2 (which happen to be
the only ones I am interested in), all return a size = 0. Any idea how to ge
t the size using T-SQL?
Message posted via http://www.droptable.comHow about the file_size in the BackupFile system table?
Andrew J. Kelly SQL MVP
"Robert Richards via droptable.com" <forum@.droptable.com> wrote in message
news:a46bfcae27494128849870935f2de9b3@.SQ
droptable.com...
>I am looking for a way to retrieve the size of my backup devices. When I
>run sp_helpdevice, the backup devices with a cntrltype = 2 (which happen to
>be the only ones I am interested in), all return a size = 0. Any idea how
>to get the size using T-SQL?
> --
> Message posted via http://www.droptable.com|||That does not provide the size of the backup files (as in *.bak), but instea
d provides the files that are being backed up. I am looking for the size of
the *.bak files.
Message posted via http://www.droptable.com|||OK then how about Backup_Size in sysbackuphistory?
Andrew J. Kelly SQL MVP
"Robert Richards via droptable.com" <forum@.droptable.com> wrote in message
news:5d56319a8f704287b2cbe0cc361395fc@.SQ
droptable.com...
> That does not provide the size of the backup files (as in *.bak), but
> instead provides the files that are being backed up. I am looking for the
> size of the *.bak files.
> --
> Message posted via http://www.droptable.com|||I am running SQL 2000 and do not seem to be able to find sysbackuphistory.
Message posted via http://www.droptable.com|||I am sorry I meant the BackupSet system table.
Andrew J. Kelly SQL MVP
"Robert Richards via droptable.com" <forum@.droptable.com> wrote in message
news:13e45dbcb76d4537a615b957827d5d8a@.SQ
droptable.com...
>I am running SQL 2000 and do not seem to be able to find sysbackuphistory.
> --
> Message posted via http://www.droptable.com

Backup Device size

I am looking for a way to retrieve the size of my backup devices. When I run sp_helpdevice, the backup devices with a cntrltype = 2 (which happen to be the only ones I am interested in), all return a size = 0. Any idea how to get the size using T-SQL?
--
Message posted via http://www.sqlmonster.comHow about the file_size in the BackupFile system table?
--
Andrew J. Kelly SQL MVP
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:a46bfcae27494128849870935f2de9b3@.SQLMonster.com...
>I am looking for a way to retrieve the size of my backup devices. When I
>run sp_helpdevice, the backup devices with a cntrltype = 2 (which happen to
>be the only ones I am interested in), all return a size = 0. Any idea how
>to get the size using T-SQL?
> --
> Message posted via http://www.sqlmonster.com|||That does not provide the size of the backup files (as in *.bak), but instead provides the files that are being backed up. I am looking for the size of the *.bak files.
--
Message posted via http://www.sqlmonster.com|||OK then how about Backup_Size in sysbackuphistory?
--
Andrew J. Kelly SQL MVP
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:5d56319a8f704287b2cbe0cc361395fc@.SQLMonster.com...
> That does not provide the size of the backup files (as in *.bak), but
> instead provides the files that are being backed up. I am looking for the
> size of the *.bak files.
> --
> Message posted via http://www.sqlmonster.com|||I am running SQL 2000 and do not seem to be able to find sysbackuphistory.
--
Message posted via http://www.sqlmonster.com|||I am sorry I meant the BackupSet system table.
--
Andrew J. Kelly SQL MVP
"Robert Richards via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:13e45dbcb76d4537a615b957827d5d8a@.SQLMonster.com...
>I am running SQL 2000 and do not seem to be able to find sysbackuphistory.
> --
> Message posted via http://www.sqlmonster.com

Backup Device setup

I am a novice and have setup a backup device for the
database and one for logs. When I attempt a backup I
recevie a device error. Status = 112. The error log
gives me no definitive reason for the error. CAn anyone
help?Run below from a DOS prompt to get explanation for OS error 112:
NET HELPMSG 112
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<cneeley@.co.pierce.wi.us> wrote in message
news:09e301c3bf57$e2c38430$3101280a@.phx.gbl...
> I am a novice and have setup a backup device for the
> database and one for logs. When I attempt a backup I
> recevie a device error. Status = 112. The error log
> gives me no definitive reason for the error. CAn anyone
> help?

Backup Device Locations Help

I am a newbie in SQL Server Administration. I decided to make the move within my company that no one else wanted.

I have SQL Server 2000 running at this time; users are connecting and using it. My question I guess pertains to the backups.

I have two drives setup for data and transactions logs (D: E:)

My backups are running but backups are being sent to the d:systems data\mssql\backup folder. once backups are comlete I normally copy the backups to a network share that is being backed up nightly to tape.

My question is this:

How do i create a device location under backup properties to point to a network share? i would like for the backups to go straight to a network drive so i do not have to copy the backups every morning when i come in.Its not good idea to perform backup over network share.
Instead schedule the job to copy those backup files to the network share using norma DOS Copy commands.

Ensure SQLAgent has required privileges to carry on this task of copying files on the network share.|||Originally posted by Satya
Its not good idea to perform backup over network share.
Instead schedule the job to copy those backup files to the network share using norma DOS Copy commands.

Ensure SQLAgent has required privileges to carry on this task of copying files on the network share.

--------------------------
Can you explain or point me to an article on using the DOS Copy command and how to use it with SQL Server? It's not something that I have used.

And what required permissions should the SQLAgent have in order to perform this type of task? the account that I created for the server itself has domain admin privileges. Would this pertain to the SQLAgent and help it perfrom the above tasks?|||Originally posted by Arra2
--------------------------
Can you explain or point me to an article on using the DOS Copy command and how to use it with SQL Server? It's not something that I have used.

And what required permissions should the SQLAgent have in order to perform this type of task? the account that I created for the server itself has domain admin privileges. Would this pertain to the SQLAgent and help it perfrom the above tasks?

easiest thing to do is type xcopy /? or copy /? at a command prompt, which will give you the syntax and definitions of the options

put that in a batch file and schedule it with 'at' or the Task Scheduler, you can also add that step to your MSSQL job if you want|||Thanks. That helps.|||Originally posted by Satya
Its not good idea to perform backup over network share.
Instead schedule the job to copy those backup files to the network share using norma DOS Copy commands.

Ensure SQLAgent has required privileges to carry on this task of copying files on the network share.

I've never heard a valid argument against network backup devices. Here's BOL excerpt:

Add a network disk backup device
This example shows a remote disk backup device. The name under which SQL Server was started must have permissions to that remote file.

USE master
EXEC sp_addumpdevice 'disk', 'networkdevice',
'\\servername\sharename\path\filename.ext'|||Though the facility is provided to perform backups over network, in a real-time environment you will have troubles such as process will block other connections while performing backups.

I agree and allow for small databases which are below 1GB in size, if not I approach other way to copy the local backup file.

As far as my experience is concerned its not a good approach on a enterprise wide network hosted SQL databases.:) :rolleyes:|||Satya,

How will a backup process possibly block other connections? I certainly respect your experience, but it makes me wonder...

Here we have a dedicated file server with 1.5T disk space, that we use to store backup files for a 1-day retention. All 120 (!!!) servers are being backed up onto this server. The disk is organized into subdirectories with names corresponding to source SQL Server names. Once all the backups are complete the tape backup kicks in. The only problems we have occasionally (a couple of times a year) is when there is a network glitch. But the jobs a written in such a way that the backup job continues processing remaining databases after creating an exception job that would contain failed backups. At the end the job would report an error and DBA on-call gets notified and resolves the issue by running the exception job . In the past 5 years that exception job run failed only once, when the network team failed to inform us that the LAN would be down during the certain time frame. Once Change Management was implemented 4 years ago we never had any issues with this approach since!|||rdjabarov

Thanks for your explanation and my intention is not to contradict your statements, I'd delivered what was experienced and you had already facted that situation and if the network and infrastructure is well built then you can test the process and deploy it.

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 device in SQL 2005

Can you still create a backup device in SQL 2005 and if so How?
Thanks!Yes you can still use sp_addumpdevice or in SSMS you can go to the server
objects and add one there.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
<msnews.microsoft.com> wrote in message
news:Obr1jyo6HHA.1900@.TK2MSFTNGP02.phx.gbl...
> Can you still create a backup device in SQL 2005 and if so How?
> Thanks!
>

Backup Device error or device off-line.

I received the error message listed below when the SQL
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.
Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>

Backup Device error or device off-line.

I received the error message listed below when the SQL
Server backup maintenance job runs daily. The server was
Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition and SP3. I can backup the database
manually with SQL Server in the same directory without a
problem.
Please help me resolve this issue.
Thanks,
Dan
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
error or device off-line. See the SQL Server error log for
more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
DATABASE is terminating abnormally.Hi,
Can you check the Windows Event viwer application log for more errors.
Hopefully you will get more explanation of this error there.
Is this K drive a local drive or remote drive? If it is remote drive then
start the SQLServerAgent service using
a domain account with write access to Kdrive
Thanks
Hari
MCDBA
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:1d3fc01c453a1$f0edc190$a401280a@.phx
.gbl...
> I received the error message listed below when the SQL
> Server backup maintenance job runs daily. The server was
> Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition and SP3. I can backup the database
> manually with SQL Server in the same directory without a
> problem.
> Please help me resolve this issue.
> Thanks,
> Dan
>
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open
> backup device 'K:\MARKDEV_db_200406160300.BAK'. Device
> error or device off-line. See the SQL Server error log for
> more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY
> DATABASE is terminating abnormally.
>