Backup SQL Server DB on Network Drive Big Problem. Please help

Hi All,
I want to using T-SQL execute BACKUP DATABASE command job on the SQL
Server Agent. But, it occured the following error:
My Job Owner is "sa", Category is Database Maintenance
My execute command is ..
BACKUP DATABASE NorthWind TO DISK = '\\servername\Backup\NorthWind.BAK'
The job failed. The Job was invoked by User Machine\Administrator.
The last step to run was step 1 (DBt Backup).
Please advise.Hi
Make sure that your SQL Server Services are running under a Domain Account
and that the user has correct permissions to the share.
To see the error message, run the T-SQL from Query Analyser.
Regards
Mike
"Kelvin" wrote:
> Hi All,
> I want to using T-SQL execute BACKUP DATABASE command job on the SQL
> Server Agent. But, it occured the following error:
> My Job Owner is "sa", Category is Database Maintenance
> My execute command is ..
> BACKUP DATABASE NorthWind TO DISK => '\\servername\Backup\NorthWind.BAK'
> The job failed. The Job was invoked by User Machine\Administrator.
> The last step to run was step 1 (DBt Backup).
> Please advise.
>sql

Backup Restore Fails

Hi,

I ran a backup procedure and BAK file created.
I moved the file to another server, tried to restore and failed with following error:
"Cannot open backup device 'C:\*****.bak'. Operating system error 5(Access is denied.)"

I checked the file on the original server and the file is accessible: I can see its content with RESTORE FILELISTONLY command.

Any clues?

Thanks,
Mark

Hello Mark

Are you using the Restore dialog to do this operation or are you using T-SQL?

Either case, ensure that the account under which SQL server service is running has access to the 'C' drive.

[Venkat]
This posting is provided "AS IS" with no warranties, and confers no rights.

Backup restore fail

Hi,
I am trying to restore database (25 GB) and getting
following error
The backup data in 'F:\BACKUP\ABC.BAK' is incorrectly
formatted. Backups cannot be appended, but existing backup
sets may still be usable.
Has any one solution for this ?
Thanks,
ManojHi Manoj,
This error normally occurs when the filemark in the backup device could not
be read.
The various reasons for this error can be,
1. A media failure on the device where the backup is located.
2. A write failure during the creation of the backup. Eg: Network failre
during a network backup
Solution:
This error normally comes if any one of the file in backup set is
problematic. It might be possible to retrieve other backup sets
from the device by specifying the file number
You can use the RESTORE HEADERONLY command to idenfify the backup file list
and use RESTORE DATABASE to restore the specific file.
Sample code
RESTORE HEADERONLY FROM DISK='c:\backup\dbname.bak'
RESTORE DATABASE mydatabase FROM DISK='C:\backup\dbname.bak' WITH FILE =FileNumber
Have a look into this article,
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q290787
Thanks
Hari
MCDBA
"Manoj" <manoj_raheja@.hotmail.com> wrote in message
news:4d8e01c3ff6e$f2f3df60$a101280a@.phx.gbl...
> Hi,
> I am trying to restore database (25 GB) and getting
> following error
> The backup data in 'F:\BACKUP\ABC.BAK' is incorrectly
> formatted. Backups cannot be appended, but existing backup
> sets may still be usable.
> Has any one solution for this ?
> Thanks,
> Manoj

backup problems error 3202

Hello
We are currently having problems backing in a full backup into maintenance
plan all days, we have this error in log file:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL
Server Driver][SQL Server] write failure in
'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
When I try that in the morning, ( executed manually) the result is ok
Any help would be appreciated.
Hi,
THis type of issue come when there is some hardware issues (RAID). Can you
ask your hardware vendor to run the diagonostic checks
to verify if there is any issue.
Thanks
Hari
SQL Server MVP
"santi" <santi@.discussions.microsoft.com> wrote in message
news:811568D0-F68E-4780-9E57-2661AEEC1FA4@.microsoft.com...
> Hello
> We are currently having problems backing in a full backup into maintenance
> plan all days, we have this error in log file:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server] write failure in
> 'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
> When I try that in the morning, ( executed manually) the result is ok
> Any help would be appreciated.
>
|||Hi
I think this answer is in the correct way, because we have in our server a
RAID system. I will try contact with hardware vendor for disk test, but I
don,t understand why in automatic mode we have error and in manual mode we
don,t have error. Do you understand?
Thank you
"Hari Prasad" escribió:

> Hi,
> THis type of issue come when there is some hardware issues (RAID). Can you
> ask your hardware vendor to run the diagonostic checks
> to verify if there is any issue.
> Thanks
> Hari
> SQL Server MVP
>
> "santi" <santi@.discussions.microsoft.com> wrote in message
> news:811568D0-F68E-4780-9E57-2661AEEC1FA4@.microsoft.com...
>
>

backup problems error 3202

Hello
We are currently having problems backing in a full backup into maintenance
plan all days, we have this error in log file:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL
Server Driver][SQL Server] write failure in
'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
When I try that in the morning, ( executed manually) the result is ok
Any help would be appreciated.Hi,
THis type of issue come when there is some hardware issues (RAID). Can you
ask your hardware vendor to run the diagonostic checks
to verify if there is any issue.
Thanks
Hari
SQL Server MVP
"santi" <santi@.discussions.microsoft.com> wrote in message
news:811568D0-F68E-4780-9E57-2661AEEC1FA4@.microsoft.com...
> Hello
> We are currently having problems backing in a full backup into maintenance
> plan all days, we have this error in log file:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> SQL
> Server Driver][SQL Server] write failure in
> 'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
> When I try that in the morning, ( executed manually) the result is ok
> Any help would be appreciated.
>|||Hi
I think this answer is in the correct way, because we have in our server a
RAID system. I will try contact with hardware vendor for disk test, but I
don,t understand why in automatic mode we have error and in manual mode we
don,t have error. Do you understand?
Thank you
"Hari Prasad" escribió:
> Hi,
> THis type of issue come when there is some hardware issues (RAID). Can you
> ask your hardware vendor to run the diagonostic checks
> to verify if there is any issue.
> Thanks
> Hari
> SQL Server MVP
>
> "santi" <santi@.discussions.microsoft.com> wrote in message
> news:811568D0-F68E-4780-9E57-2661AEEC1FA4@.microsoft.com...
> > Hello
> >
> > We are currently having problems backing in a full backup into maintenance
> > plan all days, we have this error in log file:
> >
> > [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
> > SQL
> > Server Driver][SQL Server] write failure in
> > 'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
> >
> > When I try that in the morning, ( executed manually) the result is ok
> >
> > Any help would be appreciated.
> >
>
>

backup problems error 3202

Hello
We are currently having problems backing in a full backup into maintenance
plan all days, we have this error in log file:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server] write failure in
'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
When I try that in the morning, ( executed manually) the result is ok
Any help would be appreciated.Hi,
THis type of issue come when there is some hardware issues (RAID). Can you
ask your hardware vendor to run the diagonostic checks
to verify if there is any issue.
Thanks
Hari
SQL Server MVP
"santi" <santi@.discussions.microsoft.com> wrote in message
news:811568D0-F68E-4780-9E57-2661AEEC1FA4@.microsoft.com...
> Hello
> We are currently having problems backing in a full backup into maintenance
> plan all days, we have this error in log file:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft]
[ODBC
> SQL
> Server Driver][SQL Server] write failure in
> 'E:\backupsql\ECASH_db_200507120652.BAK', state = 121
> When I try that in the morning, ( executed manually) the result is ok
> Any help would be appreciated.
>|||Hi
I think this answer is in the correct way, because we have in our server a
RAID system. I will try contact with hardware vendor for disk test, but I
don,t understand why in automatic mode we have error and in manual mode we
don,t have error. Do you understand?
Thank you
"Hari Prasad" escribió:

> Hi,
> THis type of issue come when there is some hardware issues (RAID). Can you
> ask your hardware vendor to run the diagonostic checks
> to verify if there is any issue.
> Thanks
> Hari
> SQL Server MVP
>
> "santi" <santi@.discussions.microsoft.com> wrote in message
> news:811568D0-F68E-4780-9E57-2661AEEC1FA4@.microsoft.com...
>
>

Backup Problem - multiple family members

I have a backup that has been working successfully for the past two months, but this weekend the following error message appeared.

"The media set for database 'MyDB' has 2 family members, but only 1 are provided. All members must be provided."

I checked the contents from the previous backups, and they all have 1 family member, and 1 media set?

Any ideas on what has changed, and what I need to do to fix this?i have encountered this. just delete your backup device from the harddisk totally then make a new backup device.

hope it should work for you.|||Thanks, that worked. Though I still wonder what caused the problem.

Originally posted by kenz
i have encountered this. just delete your backup device from the harddisk totally then make a new backup device.

hope it should work for you.

backup problem

Hello,

This backup plan i have that works fine when i trigger it manually does not work when scheduled, here is the output of the error I am getting, I am new to sql 2005 and i really need to get this working fast, and dont have alot of time to research the problem right now.

Tdar

Error Message:

05/12/2007 00:00:01,daily backup.Subplan_1,Error,1,IPDDFZ2363ATL2,daily backup.Subplan_1,Subplan_1,,Executed as user: IPDDFZ2363ATL2\MSSQL_USER. ...42.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:00:01 AM Error: 2007-05-12 00:00:20.92 Code: 0xC00291EC Source: {C4C38724-5AEF-4472-9CC9-E24587B74591} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2007-05-12 00:00:20.93 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded<c/> but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2007-05-12 00:00:21.51 Code: 0xC0024104 Source: Back Up Database (Full) ... The package execution fa... The step failed.,00:00:20,0,0,,,,0
05/11/2007 00:00:00,daily backup.Subplan_1,Error,0,IPDDFZ2363ATL2,daily backup.Subplan_1,(Job outcome),,The job failed. The Job was invoked by Schedule 3 (BACKTEST). The last step to run was step 1 (Subplan_1).,00:00:15,0,0,,,,0

Typically, when you are able to run something (espeically DTS) by hand but it fails to work when you schedule it, it is a permissions issue. Check to see which user the job is running under and give that user the permission to execute what needs to be executed.

Tim

backup problem

when i try to take back from sqlserver 2000 enterprise manager it shows the error. wheni tried with NT itsays tape not found.

backup medium ::reportloerror:write failure on backup device\\.\tape0.operating system error 23(data error(cyclic reduncancy check));

pls help out in this issueeDo you have a tape drive?

You'd be better off dumping to disk and then copying to tape (faster)

Have you tried to set up a maint plan with the wizard (easiest)

Backup plan cannot find the path specified

Hello:
In continuing with a posting that I made yesterday here on the Newsgroups, I
have today reviewed the SQL Error Log for a database maintenance plan that I
have that backups my databases to an external hard drive.
The backup to this external hard drive is failing for all of the databases!
The error in the log report says "The system cannot find the path specified".
The drive letter of the hard drive is Q and, therefore, the path to the
backup device (external hard drive) is "Q:".
I tested this a few weeks ago and it worked. But, when we put the plan into
production to run overnight, it failed.
Should I UNC the pathing to the external hard drive? Is there any other
reason as to why it would not be able to find the hard drive?
Thanks!
childofthe1980sHi
"childofthe1980s" wrote:
> Hello:
> In continuing with a posting that I made yesterday here on the Newsgroups, I
> have today reviewed the SQL Error Log for a database maintenance plan that I
> have that backups my databases to an external hard drive.
> The backup to this external hard drive is failing for all of the databases!
> The error in the log report says "The system cannot find the path specified".
> The drive letter of the hard drive is Q and, therefore, the path to the
> backup device (external hard drive) is "Q:".
> I tested this a few weeks ago and it worked. But, when we put the plan into
> production to run overnight, it failed.
> Should I UNC the pathing to the external hard drive? Is there any other
> reason as to why it would not be able to find the hard drive?
> Thanks!
> childofthe1980s
Is this external drive a USB disc? If so can you see it when logged in as
the the service account?
Does a step with that calls xp_fixeddrives return the drive information?
John

Backup plan cannot find the path specified

Hello:
In continuing with a posting that I made yesterday here on the Newsgroups, I
have today reviewed the SQL Error Log for a database maintenance plan that I
have that backups my databases to an external hard drive.
The backup to this external hard drive is failing for all of the databases!
The error in the log report says "The system cannot find the path specified"
.
The drive letter of the hard drive is Q and, therefore, the path to the
backup device (external hard drive) is "Q:".
I tested this a few weeks ago and it worked. But, when we put the plan into
production to run overnight, it failed.
Should I UNC the pathing to the external hard drive? Is there any other
reason as to why it would not be able to find the hard drive?
Thanks!
childofthe1980sHi
"childofthe1980s" wrote:

> Hello:
> In continuing with a posting that I made yesterday here on the Newsgroups,
I
> have today reviewed the SQL Error Log for a database maintenance plan that
I
> have that backups my databases to an external hard drive.
> The backup to this external hard drive is failing for all of the databases
!
> The error in the log report says "The system cannot find the path specifie
d".
> The drive letter of the hard drive is Q and, therefore, the path to the
> backup device (external hard drive) is "Q:".
> I tested this a few weeks ago and it worked. But, when we put the plan in
to
> production to run overnight, it failed.
> Should I UNC the pathing to the external hard drive? Is there any other
> reason as to why it would not be able to find the hard drive?
> Thanks!
> childofthe1980s
Is this external drive a USB disc? If so can you see it when logged in as
the the service account?
Does a step with that calls xp_fixeddrives return the drive information?
John

Backup plan cannot find the path specified

Hello:
In continuing with a posting that I made yesterday here on the Newsgroups, I
have today reviewed the SQL Error Log for a database maintenance plan that I
have that backups my databases to an external hard drive.
The backup to this external hard drive is failing for all of the databases!
The error in the log report says "The system cannot find the path specified".
The drive letter of the hard drive is Q and, therefore, the path to the
backup device (external hard drive) is "Q:".
I tested this a few weeks ago and it worked. But, when we put the plan into
production to run overnight, it failed.
Should I UNC the pathing to the external hard drive? Is there any other
reason as to why it would not be able to find the hard drive?
Thanks!
childofthe1980s
Hi
"childofthe1980s" wrote:

> Hello:
> In continuing with a posting that I made yesterday here on the Newsgroups, I
> have today reviewed the SQL Error Log for a database maintenance plan that I
> have that backups my databases to an external hard drive.
> The backup to this external hard drive is failing for all of the databases!
> The error in the log report says "The system cannot find the path specified".
> The drive letter of the hard drive is Q and, therefore, the path to the
> backup device (external hard drive) is "Q:".
> I tested this a few weeks ago and it worked. But, when we put the plan into
> production to run overnight, it failed.
> Should I UNC the pathing to the external hard drive? Is there any other
> reason as to why it would not be able to find the hard drive?
> Thanks!
> childofthe1980s
Is this external drive a USB disc? If so can you see it when logged in as
the the service account?
Does a step with that calls xp_fixeddrives return the drive information?
John

Backup Permissions

Hi,
The user that i use to make backups is in the
db_backupoperator, but when i select the backup
destination the following error appear:
ERROR 229: EXECUTE permission denied on
object 'xp_availablemedia', database 'master', owner 'dbo'
cant understand
Beat regardsHi
An what are the permissions on this stored procedure?
John
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:18f4301c44c93$2caec050$a301280a@.phx
.gbl...
> Hi,
> The user that i use to make backups is in the
> db_backupoperator, but when i select the backup
> destination the following error appear:
> ERROR 229: EXECUTE permission denied on
> object 'xp_availablemedia', database 'master', owner 'dbo'
> cant understand
> Beat regards|||Hi,
Open query analyzer and execute the below command:-
master..xp_availablemedia
Check the drives, the command is displaying. Based on this create the backup
files. I think you are trying to backup to a remote server or a media not
available. If the execution gives you an error try giving execute prev to
this extended procedure to your backup user.
use master
go
sp_adduser <user_name>
go
grant exec on xp_availablemedia to <user>
(Try executing backup database now)
Still if you have errors then try below:- Can you please assign "SYSADMIN"
server fixed role to this user and try backup the database.
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:18f4301c44c93$2caec050$a301280a@.phx
.gbl...
> Hi,
> The user that i use to make backups is in the
> db_backupoperator, but when i select the backup
> destination the following error appear:
> ERROR 229: EXECUTE permission denied on
> object 'xp_availablemedia', database 'master', owner 'dbo'
> cant understand
> Beat regards

Backup Permissions

Hi,
The user that i use to make backups is in the
db_backupoperator, but when i select the backup
destination the following error appear:
ERROR 229: EXECUTE permission denied on
object 'xp_availablemedia', database 'master', owner 'dbo'
cant understand
Beat regardsHi
An what are the permissions on this stored procedure?
John
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:18f4301c44c93$2caec050$a301280a@.phx.gbl...
> Hi,
> The user that i use to make backups is in the
> db_backupoperator, but when i select the backup
> destination the following error appear:
> ERROR 229: EXECUTE permission denied on
> object 'xp_availablemedia', database 'master', owner 'dbo'
> cant understand
> Beat regards|||Hi,
Open query analyzer and execute the below command:-
master..xp_availablemedia
Check the drives, the command is displaying. Based on this create the backup
files. I think you are trying to backup to a remote server or a media not
available. If the execution gives you an error try giving execute prev to
this extended procedure to your backup user.
use master
go
sp_adduser <user_name>
go
grant exec on xp_availablemedia to <user>
(Try executing backup database now)
Still if you have errors then try below:- Can you please assign "SYSADMIN"
server fixed role to this user and try backup the database.
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:18f4301c44c93$2caec050$a301280a@.phx.gbl...
> Hi,
> The user that i use to make backups is in the
> db_backupoperator, but when i select the backup
> destination the following error appear:
> ERROR 229: EXECUTE permission denied on
> object 'xp_availablemedia', database 'master', owner 'dbo'
> cant understand
> Beat regards

Backup Permissions

Hi,
The user that i use to make backups is in the
db_backupoperator, but when i select the backup
destination the following error appear:
ERROR 229: EXECUTE permission denied on
object 'xp_availablemedia', database 'master', owner 'dbo'
cant understand
Beat regards
Hi
An what are the permissions on this stored procedure?
John
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:18f4301c44c93$2caec050$a301280a@.phx.gbl...
> Hi,
> The user that i use to make backups is in the
> db_backupoperator, but when i select the backup
> destination the following error appear:
> ERROR 229: EXECUTE permission denied on
> object 'xp_availablemedia', database 'master', owner 'dbo'
> cant understand
> Beat regards
|||Hi,
Open query analyzer and execute the below command:-
master..xp_availablemedia
Check the drives, the command is displaying. Based on this create the backup
files. I think you are trying to backup to a remote server or a media not
available. If the execution gives you an error try giving execute prev to
this extended procedure to your backup user.
use master
go
sp_adduser <user_name>
go
grant exec on xp_availablemedia to <user>
(Try executing backup database now)
Still if you have errors then try below:- Can you please assign "SYSADMIN"
server fixed role to this user and try backup the database.
Thanks
Hari
MCDBA
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:18f4301c44c93$2caec050$a301280a@.phx.gbl...
> Hi,
> The user that i use to make backups is in the
> db_backupoperator, but when i select the backup
> destination the following error appear:
> ERROR 229: EXECUTE permission denied on
> object 'xp_availablemedia', database 'master', owner 'dbo'
> cant understand
> Beat regards

Backup on Local Disk Failing! urgent help plz!

Folks, this is the error i get when backing up user db to local disk:

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.

Connection Broken

If i copy a file (2gb) to local disk from network it works. The disk have much space. Any ideas;;; :confused:

I get the same error when backuping up even MSDB to a network path using UNC [\\].How large is the db you're trying to back up. How much disk space do you have? Can you backup a very small database?|||As i mentioned; i get the error even backing up MSDB(system) db either on network or local disk. Strangely; when i try backing up any db to local disk using EM; i get the message; backup successfully completed. and the file disappears(0 kb during backup) disappears on the disk!
Killing me!|||How is your SQL Server registered? Are you using the server name or are you using (local) or . ?
Whenever you use the 2 last options to register your server in EM it uses the shared memory driver, If you use the name of your server/instance, It should make it use the network librbary instead. I say that only to get to the point that if it is not a diskspace issue, it may be a memory issue, perhaps RAM going out.

I know that's not really a solution, but perhaps it can help you troubleshoot.|||How is the SQLServerAgent service and the MSSQLServer Service configured on the Log On tab in services? Are they configured to log on as "Local System"? Also, are there any messages in the SQL Server errorlog, or the NT Application event log?|||I don't quite understand "disappears from the disk" part. But in your first post you mentioned something about copying the file (2GB) from a share to a local drive and the backup would work. This leads me to believe that you're appending to the same backup file. I've seen cases when an interupted backup/restore would corrupt the device and no further appends are possible. The only solution would be to re-create the backup file by deleting the old one and creating a new one by backing up your database. Appending is a bad idea because it leads to what I've just described, in which case you DR is down the drain.|||Hi folks, thanx so much for ur input.
RESTARTING the instance just squared it away; so i suspect as mentioned by the fellow, memory problem (but what's the permanent fix?)
I didn't change any SQL-AGENT of SQL changes so far nor did this production machine had been restarted for last 2 months. I just saw my scheduled backup job failed last night and since then i tried restarting the job; backing the databases manually using QA or EM. So i didn't change any settings so far. I couldn't restart the instance during working times so i posted for the suggestion. After the restart it's working.
And, guru? believe me the file on the disk was of zero kb while backing up the db, then after the success message on EM i coldn't find the file; while in QA i get the GENERAL NETWORK error. Wasn't using the append db option!

Howdy!|||See this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;827452|||Hmmm, and I had this in my Favorites for while it was still in the Premier section...Good catch, pshisbey!|||Many thanx to ya all!

Backup not working in 2005

I am trying to backup a database that was moved from 2000 to 2005 and I get
the following error message:
The backup of full-text catalog ‘Attachment’ is not permitted because it is
not online. Check errorlog file for the reason that full-text catalog becomes
offline and bring it online. Or BACKUP can be performed by using the
FILEGROUP or FILE clauses to restrict the selection to include only online
data.
Why am I getting this message and how do I fix it?
Thanks,
Emma
My guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>
|||Please disregard this post. I enabled full-text indexing in the backup worked
fine.
Thanks
"Emma" wrote:

> I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>
|||Thanks for the response. I will try that as well. For now, enabling the Use
full-text indexing took care of the error message as well.
Thanks.
"Tibor Karaszi" wrote:

> My guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
> 2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
> don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
> the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Emma" <Emma@.discussions.microsoft.com> wrote in message
> news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>

Backup not working in 2005

I am trying to backup a database that was moved from 2000 to 2005 and I get
the following error message:
The backup of full-text catalog ‘Attachment’ is not permitted because it
is
not online. Check errorlog file for the reason that full-text catalog become
s
offline and bring it online. Or BACKUP can be performed by using the
FILEGROUP or FILE clauses to restrict the selection to include only online
data.
Why am I getting this message and how do I fix it?
Thanks,
EmmaMy guess is that the 2000 database had full.text catalogs which for some rea
son isn't there anymore.
2005 treats a full text catalog as a filegroup when it comes to backup and r
estore. Perhaps you
don't want this full-text meta-data hanging around? If so, I'd remove it so
it won't interfere with
the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because
it is
> not online. Check errorlog file for the reason that full-text catalog beco
mes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Please disregard this post. I enabled full-text indexing in the backup worke
d
fine.
Thanks
"Emma" wrote:

> I am trying to backup a database that was moved from 2000 to 2005 and I ge
t
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because
it is
> not online. Check errorlog file for the reason that full-text catalog beco
mes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Thanks for the response. I will try that as well. For now, enabling the Use
full-text indexing took care of the error message as well.
Thanks.
"Tibor Karaszi" wrote:

> My guess is that the 2000 database had full.text catalogs which for some r
eason isn't there anymore.
> 2005 treats a full text catalog as a filegroup when it comes to backup and
restore. Perhaps you
> don't want this full-text meta-data hanging around? If so, I'd remove it s
o it won't interfere with
> the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Emma" <Emma@.discussions.microsoft.com> wrote in message
> news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>

Backup not working in 2005

I am trying to backup a database that was moved from 2000 to 2005 and I get
the following error message:
The backup of full-text catalog â'Attachmentâ' is not permitted because it is
not online. Check errorlog file for the reason that full-text catalog becomes
offline and bring it online. Or BACKUP can be performed by using the
FILEGROUP or FILE clauses to restrict the selection to include only online
data.
Why am I getting this message and how do I fix it?
Thanks,
EmmaMy guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog â'Attachmentâ' is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Please disregard this post. I enabled full-text indexing in the backup worked
fine.
Thanks
"Emma" wrote:
> I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog â'Attachmentâ' is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Thanks for the response. I will try that as well. For now, enabling the Use
full-text indexing took care of the error message as well.
Thanks.
"Tibor Karaszi" wrote:
> My guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
> 2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
> don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
> the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Emma" <Emma@.discussions.microsoft.com> wrote in message
> news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
> >I am trying to backup a database that was moved from 2000 to 2005 and I get
> > the following error message:
> >
> > The backup of full-text catalog â'Attachmentâ' is not permitted because it is
> > not online. Check errorlog file for the reason that full-text catalog becomes
> > offline and bring it online. Or BACKUP can be performed by using the
> > FILEGROUP or FILE clauses to restrict the selection to include only online
> > data.
> >
> > Why am I getting this message and how do I fix it?
> >
> > Thanks,
> > Emma
> >
>

Backup Maintence Plan Fails

I get the error every day. i've checked everything i know
of to make sure that nothing including the backup job is
accessing the database. This job has run for years and is
suddenly failing for the last few weeks. Any help would be
appreciated. Win2k Server SQL2000 with SP3.
Lamar
App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
3041 : BACKUP failed to complete the command BACKUP
DATABASE [DMD1] TO DISK = N'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT "
App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
18210 : BackupMedium::ReportIoError: write failure on
backup device 'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). "Seems like some other program is using and locking the backup file. You have to hunt that down.
Could be some anti-virus program, for instance. I thinks that www.sysinternals has tools for this.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Lamar Mrris" <LamarMorris@.ti.com> wrote in message news:064701c39d5b$2d38fc80$a001280a@.phx.gbl...
> I get the error every day. i've checked everything i know
> of to make sure that nothing including the backup job is
> accessing the database. This job has run for years and is
> suddenly failing for the last few weeks. Any help would be
> appreciated. Win2k Server SQL2000 with SP3.
> Lamar
> App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
> 3041 : BACKUP failed to complete the command BACKUP
> DATABASE [DMD1] TO DISK => N'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT "
> App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
> 18210 : BackupMedium::ReportIoError: write failure on
> backup device 'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). "
>
>|||... or maybe the backup file is being backed up -- to tape, for example.
Whatever the case, checking with the system admin should provide some help,
at least eliminate some candidate problem sources.
Quentin
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:u3gxJDWnDHA.2652@.TK2MSFTNGP09.phx.gbl...
> Seems like some other program is using and locking the backup file. You
have to hunt that down.
> Could be some anti-virus program, for instance. I thinks that
www.sysinternals has tools for this.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Lamar Mrris" <LamarMorris@.ti.com> wrote in message
news:064701c39d5b$2d38fc80$a001280a@.phx.gbl...
> > I get the error every day. i've checked everything i know
> > of to make sure that nothing including the backup job is
> > accessing the database. This job has run for years and is
> > suddenly failing for the last few weeks. Any help would be
> > appreciated. Win2k Server SQL2000 with SP3.
> >
> > Lamar
> > App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
> > 3041 : BACKUP failed to complete the command BACKUP
> > DATABASE [DMD1] TO DISK => > N'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK' WITH INIT ,
> > NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT "
> > App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
> > 18210 : BackupMedium::ReportIoError: write failure on
> > backup device 'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK'.
> > Operating system error 33(The process cannot access the
> > file because another process has locked a portion of the
> > file.). "
> >
> >
> >
>|||Thanks for the input, i've already excluded the whole directory from
Virus scanning or realtime protection.
Lamar
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!|||To add to what Tibor said, you can get a utility called
nthandle.exe from www.sysinternals.com.
To help you determine what process is holding that backup
file, you can modify your backup job to add a step before
the backup step. In this step, run:
path>nthandle.exe DMD1_db
and make sure that you specify the output file for this
step.
When the backup job fails, you can then review the output
file for the first step to identify the offending process
that was holding your backup file.
My guess would be: it's your tape backup process if you
are running a tape backup process to backup the files on
the disk.
Linchi
>--Original Message--
>Seems like some other program is using and locking the
backup file. You have to hunt that down.
>Could be some anti-virus program, for instance. I thinks
that www.sysinternals has tools for this.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Lamar Mrris" <LamarMorris@.ti.com> wrote in message
news:064701c39d5b$2d38fc80$a001280a@.phx.gbl...
>> I get the error every day. i've checked everything i
know
>> of to make sure that nothing including the backup job is
>> accessing the database. This job has run for years and
is
>> suddenly failing for the last few weeks. Any help would
be
>> appreciated. Win2k Server SQL2000 with SP3.
>> Lamar
>> App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
>> 3041 : BACKUP failed to complete the command BACKUP
>> DATABASE [DMD1] TO DISK =>> N'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK' WITH INIT ,
>> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT "
>> App: E 'Wed Oct 01 00:24:26 2003': MSSQLSERVER - "
>> 18210 : BackupMedium::ReportIoError: write failure on
>> backup
device 'd:\MSSQL\BACKUP\DMD1_db_200309302200.BAK'.
>> Operating system error 33(The process cannot access the
>> file because another process has locked a portion of the
>> file.). "
>>
>
>.
>