Backup Schedules Failing

We have got backups set regularly each day. A full backup early in the
morning then a partial one every hour. These run time and the jobs for them
are in the SQL-SERVER Agent. After a few weeks the partial backups start to
fail. The full backups are fine. There is plenty of space an no errors in
the logs. When looking at the partial backups unser SQL-Server agent and
looking at the the schedule the box matked Enable is unchecked. We reset
the backup by clicking this box. It runs fine for a few wekes when it fials
again and the box has become unchecked? Has anyone got any ideas why this
might happen?
What version and service pack ? Might be related to
FIX: SQLAgent Job with Recurring Schedule is Disabled
Upon Completion of the Schedule for the Day
http://support.microsoft.com/default...;en-us;Q295378
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Scott Bailey" <scott.bailey@.migranthelpline.org> wrote in message
news:cp1jgv$2r3$1$8302bc10@.news.demon.co.uk...
> We have got backups set regularly each day. A full backup early in the
> morning then a partial one every hour. These run time and the jobs for
> them
> are in the SQL-SERVER Agent. After a few weeks the partial backups start
> to
> fail. The full backups are fine. There is plenty of space an no errors in
> the logs. When looking at the partial backups unser SQL-Server agent and
> looking at the the schedule the box matked Enable is unchecked. We reset
> the backup by clicking this box. It runs fine for a few wekes when it
> fials
> again and the box has become unchecked? Has anyone got any ideas why this
> might happen?
>

Backup over network

Hi ,
From last year I have created a backups over network
but form few days for two dbs which are more than 3gb
the backup is failing .
its showing operating system error 64 & 87
any idea
Regards
ajaySystem error 64 says: "The specified network name is no longer available."
Check if the network share is still available. Maybe somebodey renamed
computer?
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"R. Ajay" <ajudba@.yahoo.co.in> wrote in message
news:#tWkBdzrDHA.1996@.TK2MSFTNGP09.phx.gbl...
> Hi ,
> From last year I have created a backups over network
> but form few days for two dbs which are more than 3gb
> the backup is failing .
> its showing operating system error 64 & 87
> any idea
> Regards
> ajay
>
>|||Hi
Thanks for reply
right now more than 100 dbs are getting backed up on the same server all are
getting success but except two which are of 3 gb size .
Regards
Ajay
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:#4yqZe0rDHA.2148@.TK2MSFTNGP12.phx.gbl...
> System error 64 says: "The specified network name is no longer available."
> Check if the network share is still available. Maybe somebodey renamed
> computer?
> --
> Dejan Sarka, SQL Server MVP
> Please reply only to the newsgroups.
> "R. Ajay" <ajudba@.yahoo.co.in> wrote in message
> news:#tWkBdzrDHA.1996@.TK2MSFTNGP09.phx.gbl...
> > Hi ,
> > From last year I have created a backups over network
> > but form few days for two dbs which are more than 3gb
> > the backup is failing .
> > its showing operating system error 64 & 87
> > any idea
> >
> > Regards
> > ajay
> >
> >
> >
> >
>|||We see those problems all the times posted here. Seems like SQL Server isn't that happy with writing
over the network for larger databases. I guess you could open a case with MS Support, don't know how
much that would help, though. One option can be to backup locally and then copy the file (possibly
packing it first).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"R. Ajay" <ajudba@.yahoo.co.in> wrote in message news:%238QOeG1rDHA.2248@.TK2MSFTNGP09.phx.gbl...
> Hi
> Thanks for reply
> right now more than 100 dbs are getting backed up on the same server all are
> getting success but except two which are of 3 gb size .
> Regards
> Ajay
> "Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
> message news:#4yqZe0rDHA.2148@.TK2MSFTNGP12.phx.gbl...
> > System error 64 says: "The specified network name is no longer available."
> > Check if the network share is still available. Maybe somebodey renamed
> > computer?
> >
> > --
> > Dejan Sarka, SQL Server MVP
> > Please reply only to the newsgroups.
> >
> > "R. Ajay" <ajudba@.yahoo.co.in> wrote in message
> > news:#tWkBdzrDHA.1996@.TK2MSFTNGP09.phx.gbl...
> > > Hi ,
> > > From last year I have created a backups over network
> > > but form few days for two dbs which are more than 3gb
> > > the backup is failing .
> > > its showing operating system error 64 & 87
> > > any idea
> > >
> > > Regards
> > > ajay
> > >
> > >
> > >
> > >
> >
> >
>|||Hi Tibor,
Every day I am doing backup over network for the database which has a size
of 56 GB. No issues so far.
I feel Ajay's issue was due to some network problems.
Ajay ,
What you can do is from command prompt put a "Ping" to the network server
and see to that always you are getting reply.
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:uL9$tU1rDHA.1784@.TK2MSFTNGP09.phx.gbl...
> We see those problems all the times posted here. Seems like SQL Server
isn't that happy with writing
> over the network for larger databases. I guess you could open a case with
MS Support, don't know how
> much that would help, though. One option can be to backup locally and then
copy the file (possibly
> packing it first).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "R. Ajay" <ajudba@.yahoo.co.in> wrote in message
news:%238QOeG1rDHA.2248@.TK2MSFTNGP09.phx.gbl...
> > Hi
> > Thanks for reply
> > right now more than 100 dbs are getting backed up on the same server all
are
> > getting success but except two which are of 3 gb size .
> >
> > Regards
> > Ajay
> > "Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote
in
> > message news:#4yqZe0rDHA.2148@.TK2MSFTNGP12.phx.gbl...
> > > System error 64 says: "The specified network name is no longer
available."
> > > Check if the network share is still available. Maybe somebodey renamed
> > > computer?
> > >
> > > --
> > > Dejan Sarka, SQL Server MVP
> > > Please reply only to the newsgroups.
> > >
> > > "R. Ajay" <ajudba@.yahoo.co.in> wrote in message
> > > news:#tWkBdzrDHA.1996@.TK2MSFTNGP09.phx.gbl...
> > > > Hi ,
> > > > From last year I have created a backups over network
> > > > but form few days for two dbs which are more than 3gb
> > > > the backup is failing .
> > > > its showing operating system error 64 & 87
> > > > any idea
> > > >
> > > > Regards
> > > > ajay
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||I now that it work in some installations, but if you check the newsgroup archive, you will see that
this is a frequent post, and frequently smaller databases are OK - which rules out permissions,
share mappings UNC naming etc.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Hari" <hari_prasad_k@.hotmail.com> wrote in message news:%236Dz$W2rDHA.3436@.tk2msftngp13.phx.gbl...
> Hi Tibor,
> Every day I am doing backup over network for the database which has a size
> of 56 GB. No issues so far.
> I feel Ajay's issue was due to some network problems.
> Ajay ,
> What you can do is from command prompt put a "Ping" to the network server
> and see to that always you are getting reply.
>
> Thanks
> Hari
> MCDBA
>
> "Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:uL9$tU1rDHA.1784@.TK2MSFTNGP09.phx.gbl...
> > We see those problems all the times posted here. Seems like SQL Server
> isn't that happy with writing
> > over the network for larger databases. I guess you could open a case with
> MS Support, don't know how
> > much that would help, though. One option can be to backup locally and then
> copy the file (possibly
> > packing it first).
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "R. Ajay" <ajudba@.yahoo.co.in> wrote in message
> news:%238QOeG1rDHA.2248@.TK2MSFTNGP09.phx.gbl...
> > > Hi
> > > Thanks for reply
> > > right now more than 100 dbs are getting backed up on the same server all
> are
> > > getting success but except two which are of 3 gb size .
> > >
> > > Regards
> > > Ajay
> > > "Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote
> in
> > > message news:#4yqZe0rDHA.2148@.TK2MSFTNGP12.phx.gbl...
> > > > System error 64 says: "The specified network name is no longer
> available."
> > > > Check if the network share is still available. Maybe somebodey renamed
> > > > computer?
> > > >
> > > > --
> > > > Dejan Sarka, SQL Server MVP
> > > > Please reply only to the newsgroups.
> > > >
> > > > "R. Ajay" <ajudba@.yahoo.co.in> wrote in message
> > > > news:#tWkBdzrDHA.1996@.TK2MSFTNGP09.phx.gbl...
> > > > > Hi ,
> > > > > From last year I have created a backups over network
> > > > > but form few days for two dbs which are more than 3gb
> > > > > the backup is failing .
> > > > > its showing operating system error 64 & 87
> > > > > any idea
> > > > >
> > > > > Regards
> > > > > ajay
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

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 of Log files

Dear All,
My nightly backups for log files are failing as there are
users still attached to the database being backup up.
What is the best stratergy for dealing with this ?
Do I
1) Make the DB single user ?
2) Have a script to kill all connections
3) Modify my backup plans
4) Some other
Any help here would be greatly appriciated.
PeterHi Peter,
Which version of SQL Server do you use? SQL Server 2000 and 7 (and probably
some earlier versions as well, but I don't have experience with them) allow
database and log backups when there are users connected to the database.
--
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.
"Peter" <nospam@.thisemailaddress.co.uk> wrote in message
news:05ae01c35fe8$90bfb4c0$a101280a@.phx.gbl...
> Dear All,
> My nightly backups for log files are failing as there are
> users still attached to the database being backup up.
> What is the best stratergy for dealing with this ?
> Do I
> 1) Make the DB single user ?
> 2) Have a script to kill all connections
> 3) Modify my backup plans
> 4) Some other
> Any help here would be greatly appriciated.
> Peter|||Hello,
Thanks for both of your replies.
I am using SQL 2000. However the backups I am doing are
part of the database maintence plan backups.
I do know that you can back up log files when people are
connected (I do this every hour with our production
database) but once a week I perform a backup of all our
databases with all sort of integrity checks, re builds of
indexes and so on. Its these back ups the log file back
ups are failing on.
Thanks
Peter
>--Original Message--
>Dear All,
>My nightly backups for log files are failing as there are
>users still attached to the database being backup up.
>What is the best stratergy for dealing with this ?
>Do I
>1) Make the DB single user ?
>2) Have a script to kill all connections
>3) Modify my backup plans
>4) Some other
>Any help here would be greatly appriciated.
>Peter
>.
>|||How do you know that they are failing because users are attached? Where are
you getting these error messages from ?
What is the exact message from the Maintenance plan history ?
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Peter" <nospam@.thisemailaddress.co.uk> wrote in message
news:060601c35fee$5e973990$a101280a@.phx.gbl...
> Hello,
> Thanks for both of your replies.
> I am using SQL 2000. However the backups I am doing are
> part of the database maintence plan backups.
> I do know that you can back up log files when people are
> connected (I do this every hour with our production
> database) but once a week I perform a backup of all our
> databases with all sort of integrity checks, re builds of
> indexes and so on. Its these back ups the log file back
> ups are failing on.
> Thanks
> Peter
> >--Original Message--
> >Dear All,
> >
> >My nightly backups for log files are failing as there are
> >users still attached to the database being backup up.
> >
> >What is the best stratergy for dealing with this ?
> >
> >Do I
> >1) Make the DB single user ?
> >2) Have a script to kill all connections
> >3) Modify my backup plans
> >4) Some other
> >
> >Any help here would be greatly appriciated.
> >
> >Peter
> >.
> >

Backup Maintenance job failing (-1073548784)

Hi,
I have created a maintenance job that fails at cleaning up the old backup
files. Messages of the Maintenance job are:
Task detail:
>Maintenance Cleanup on Local server connection
>Cleanup Database Backup files
>Age: Older than 3 Days
Error Number:
>-1073548784
Error Message:
>Executing the query "EXECUTE master.dbo.xp_delete_file 0,N'',N'',N'2007-12-09T11:00:24'
>" failed with the following error: "Error executing extended stored procedure: Invalid Parameter". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Any ideas why the cleanup is not working, and how to fix this ?Ensure that you defined a Folder path in the Define Maintanence Cleanup Task
window. It's empty by default and if you leave it empty then you get this
error.
--
Ekrem Ã?nsoy
"Hen" <Hen@.discussions.microsoft.com> wrote in message
news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
> Hi,
> I have created a maintenance job that fails at cleaning up the old backup
> files. Messages of the Maintenance job are:
> Task detail:
>>Maintenance Cleanup on Local server connection
>>Cleanup Database Backup files
>>Age: Older than 3 Days
> Error Number:
>>-1073548784
> Error Message:
>>Executing the query "EXECUTE master.dbo.xp_delete_file
>>0,N'',N'',N'2007-12-09T11:00:24'
>>" failed with the following error: "Error executing extended stored
>>procedure: Invalid Parameter". Possible failure reasons: Problems with the
>>query, "ResultSet" property not set correctly, parameters not set
>>correctly, or connection not established correctly.
> Any ideas why the cleanup is not working, and how to fix this ?|||The path is indeed empty. When I try to modify/edit the database maintenance
cleanup task, the dialogs let me fill in a path but the OK button remains
greyed out. Is there a special procedure required to edit this ?.
"Ekrem Ã?nsoy" wrote:
> Ensure that you defined a Folder path in the Define Maintanence Cleanup Task
> window. It's empty by default and if you leave it empty then you get this
> error.
> --
> Ekrem Ã?nsoy
>
> "Hen" <Hen@.discussions.microsoft.com> wrote in message
> news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
> > Hi,
> >
> > I have created a maintenance job that fails at cleaning up the old backup
> > files. Messages of the Maintenance job are:
> >
> > Task detail:
> >>Maintenance Cleanup on Local server connection
> >>Cleanup Database Backup files
> >>Age: Older than 3 Days
> > Error Number:
> >>-1073548784
> > Error Message:
> >>Executing the query "EXECUTE master.dbo.xp_delete_file
> >>0,N'',N'',N'2007-12-09T11:00:24'
> >>" failed with the following error: "Error executing extended stored
> >>procedure: Invalid Parameter". Possible failure reasons: Problems with the
> >>query, "ResultSet" property not set correctly, parameters not set
> >>correctly, or connection not established correctly.
> >
> > Any ideas why the cleanup is not working, and how to fix this ?
>|||Found it:
Had to fill in the extension, and now the OK button is available.
"Hen" wrote:
> The path is indeed empty. When I try to modify/edit the database maintenance
> cleanup task, the dialogs let me fill in a path but the OK button remains
> greyed out. Is there a special procedure required to edit this ?.
>
> "Ekrem Ã?nsoy" wrote:
> > Ensure that you defined a Folder path in the Define Maintanence Cleanup Task
> > window. It's empty by default and if you leave it empty then you get this
> > error.
> >
> > --
> > Ekrem Ã?nsoy
> >
> >
> >
> > "Hen" <Hen@.discussions.microsoft.com> wrote in message
> > news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
> > > Hi,
> > >
> > > I have created a maintenance job that fails at cleaning up the old backup
> > > files. Messages of the Maintenance job are:
> > >
> > > Task detail:
> > >>Maintenance Cleanup on Local server connection
> > >>Cleanup Database Backup files
> > >>Age: Older than 3 Days
> > > Error Number:
> > >>-1073548784
> > > Error Message:
> > >>Executing the query "EXECUTE master.dbo.xp_delete_file
> > >>0,N'',N'',N'2007-12-09T11:00:24'
> > >>" failed with the following error: "Error executing extended stored
> > >>procedure: Invalid Parameter". Possible failure reasons: Problems with the
> > >>query, "ResultSet" property not set correctly, parameters not set
> > >>correctly, or connection not established correctly.
> > >
> > > Any ideas why the cleanup is not working, and how to fix this ?
> >

Backup Maintenance job failing (-1073548784)

Hi,
I have created a maintenance job that fails at cleaning up the old backup
files. Messages of the Maintenance job are:
Task detail:
>Maintenance Cleanup on Local server connection
>Cleanup Database Backup files
>Age: Older than 3 Days
Error Number:
>-1073548784
Error Message:
>Executing the query "EXECUTE master.dbo.xp_delete_file 0,N'',N'',N'2007-12-09T11:00:24'
>" failed with the following error: "Error executing extended stored procedure: Invalid Parameter". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Any ideas why the cleanup is not working, and how to fix this ?
Ensure that you defined a Folder path in the Define Maintanence Cleanup Task
window. It's empty by default and if you leave it empty then you get this
error.
Ekrem ?nsoy
"Hen" <Hen@.discussions.microsoft.com> wrote in message
news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
> Hi,
> I have created a maintenance job that fails at cleaning up the old backup
> files. Messages of the Maintenance job are:
> Task detail:
> Error Number:
> Error Message:
> Any ideas why the cleanup is not working, and how to fix this ?
|||The path is indeed empty. When I try to modify/edit the database maintenance
cleanup task, the dialogs let me fill in a path but the OK button remains
greyed out. Is there a special procedure required to edit this ?.
"Ekrem ?nsoy" wrote:

> Ensure that you defined a Folder path in the Define Maintanence Cleanup Task
> window. It's empty by default and if you leave it empty then you get this
> error.
> --
> Ekrem ?nsoy
>
> "Hen" <Hen@.discussions.microsoft.com> wrote in message
> news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
>
|||Found it:
Had to fill in the extension, and now the OK button is available.
"Hen" wrote:
[vbcol=seagreen]
> The path is indeed empty. When I try to modify/edit the database maintenance
> cleanup task, the dialogs let me fill in a path but the OK button remains
> greyed out. Is there a special procedure required to edit this ?.
>
> "Ekrem ?nsoy" wrote:

Backup Maintenance job failing (-1073548784)

Hi,
I have created a maintenance job that fails at cleaning up the old backup
files. Messages of the Maintenance job are:
Task detail:
>Maintenance Cleanup on Local server connection
>Cleanup Database Backup files
>Age: Older than 3 Days
Error Number:
>-1073548784
Error Message:
>Executing the query "EXECUTE master.dbo.xp_delete_file 0,N'',N'',N'2007-12-
09T11:00:24'
>" failed with the following error: "Error executing extended stored procedure: Inva
lid Parameter". Possible failure reasons: Problems with the query, "ResultSet" prope
rty not set correctly, parameters not set correctly, or connection not established c
orr
ectly.
Any ideas why the cleanup is not working, and how to fix this ?Ensure that you defined a Folder path in the Define Maintanence Cleanup Task
window. It's empty by default and if you leave it empty then you get this
error.
Ekrem ?nsoy
"Hen" <Hen@.discussions.microsoft.com> wrote in message
news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
> Hi,
> I have created a maintenance job that fails at cleaning up the old backup
> files. Messages of the Maintenance job are:
> Task detail:
> Error Number:
> Error Message:
> Any ideas why the cleanup is not working, and how to fix this ?|||The path is indeed empty. When I try to modify/edit the database maintenance
cleanup task, the dialogs let me fill in a path but the OK button remains
greyed out. Is there a special procedure required to edit this ?.
"Ekrem ?nsoy" wrote:

> Ensure that you defined a Folder path in the Define Maintanence Cleanup Ta
sk
> window. It's empty by default and if you leave it empty then you get this
> error.
> --
> Ekrem ?nsoy
>
> "Hen" <Hen@.discussions.microsoft.com> wrote in message
> news:F3B48F39-727F-4364-872D-472A4F0972E7@.microsoft.com...
>|||Found it:
Had to fill in the extension, and now the OK button is available.
"Hen" wrote:
[vbcol=seagreen]
> The path is indeed empty. When I try to modify/edit the database maintenan
ce
> cleanup task, the dialogs let me fill in a path but the OK button remains
> greyed out. Is there a special procedure required to edit this ?.
>
> "Ekrem ?nsoy" wrote:
>

backup log failing

Hi,
All these days full backups and log backups are fine and suddenly the log
backup is failing for the databases with error message in error log as
downgrading backup buffers from 960k to 64k and when ran in QA it says
insufficient system memory.
there is no additiona load on this db server and the server is not busy.
Please suggest how to resolve this problem
thanks
ShamaTry setting the MAX memory setting to allow for several hundred MB's for the
OS at all times.
--
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
> Hi,
> All these days full backups and log backups are fine and suddenly the log
> backup is failing for the databases with error message in error log as
> downgrading backup buffers from 960k to 64k and when ran in QA it says
> insufficient system memory.
> there is no additiona load on this db server and the server is not busy.
> Please suggest how to resolve this problem
> thanks
> Shama|||We have not changed any settings for sp_configure and awe has not been enabled
sql server SE edition with SP4 with 4GB RAM.
MAX memory setting =2147483647
and getting error "not enough storage is available to process this command"
when try to start the backup log job.
all of sudden we r getting this problem.
pl suggest
"Andrew J. Kelly" wrote:
> Try setting the MAX memory setting to allow for several hundred MB's for the
> OS at all times.
> --
> Andrew J. Kelly SQL MVP
> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
> > Hi,
> >
> > All these days full backups and log backups are fine and suddenly the log
> > backup is failing for the databases with error message in error log as
> > downgrading backup buffers from 960k to 64k and when ran in QA it says
> > insufficient system memory.
> >
> > there is no additiona load on this db server and the server is not busy.
> >
> > Please suggest how to resolve this problem
> >
> > thanks
> > Shama
>
>|||SQL 2000 standard edition can only use 2GB max anyway and you have 4GB. I
don't recognize the error messages but it sounds like you may have some kind
of memory leak that is eating up system memory. I don't know if this is
MemToLeave or OS specific memory. Have you tried rebooting?
--
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...
> We have not changed any settings for sp_configure and awe has not been
> enabled
> sql server SE edition with SP4 with 4GB RAM.
> MAX memory setting =2147483647
> and getting error "not enough storage is available to process this
> command"
> when try to start the backup log job.
> all of sudden we r getting this problem.
> pl suggest
> "Andrew J. Kelly" wrote:
>> Try setting the MAX memory setting to allow for several hundred MB's for
>> the
>> OS at all times.
>> --
>> Andrew J. Kelly SQL MVP
>> "Shama" <Shama@.discussions.microsoft.com> wrote in message
>> news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
>> > Hi,
>> >
>> > All these days full backups and log backups are fine and suddenly the
>> > log
>> > backup is failing for the databases with error message in error log as
>> > downgrading backup buffers from 960k to 64k and when ran in QA it says
>> > insufficient system memory.
>> >
>> > there is no additiona load on this db server and the server is not
>> > busy.
>> >
>> > Please suggest how to resolve this problem
>> >
>> > thanks
>> > Shama
>>|||We have restarted the SQL Server and it looks fine now.
when I perform full backup/any query no issues encountered.
when I ran backup log manually in QA few times it says enough memory is not
available to create UMS scheduler,later on it says insufficient system memory
.
when I try start the backup log job it says not enough storage is available
to process this command"
how to find whether it is MemToLeave or OS specific memory ?
what shall I do if it reoccurs,doing restart regularly is not acceptable.
"Andrew J. Kelly" wrote:
> SQL 2000 standard edition can only use 2GB max anyway and you have 4GB. I
> don't recognize the error messages but it sounds like you may have some kind
> of memory leak that is eating up system memory. I don't know if this is
> MemToLeave or OS specific memory. Have you tried rebooting?
> --
> Andrew J. Kelly SQL MVP
> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...
> > We have not changed any settings for sp_configure and awe has not been
> > enabled
> > sql server SE edition with SP4 with 4GB RAM.
> >
> > MAX memory setting =2147483647
> >
> > and getting error "not enough storage is available to process this
> > command"
> > when try to start the backup log job.
> >
> > all of sudden we r getting this problem.
> >
> > pl suggest
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Try setting the MAX memory setting to allow for several hundred MB's for
> >> the
> >> OS at all times.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> >> news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
> >> > Hi,
> >> >
> >> > All these days full backups and log backups are fine and suddenly the
> >> > log
> >> > backup is failing for the databases with error message in error log as
> >> > downgrading backup buffers from 960k to 64k and when ran in QA it says
> >> > insufficient system memory.
> >> >
> >> > there is no additiona load on this db server and the server is not
> >> > busy.
> >> >
> >> > Please suggest how to resolve this problem
> >> >
> >> > thanks
> >> > Shama
> >>
> >>
> >>
>
>|||Are you running any 3rd party software to do backups? In any case this
sounds like a bug and you might best be served by calling MS PSS.
http://www.support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL
Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:797C34AE-7BB3-4FFC-8471-5270675C81AB@.microsoft.com...
> We have restarted the SQL Server and it looks fine now.
> when I perform full backup/any query no issues encountered.
> when I ran backup log manually in QA few times it says enough memory is
> not
> available to create UMS scheduler,later on it says insufficient system
> memory
> .
> when I try start the backup log job it says not enough storage is
> available
> to process this command"
> how to find whether it is MemToLeave or OS specific memory ?
> what shall I do if it reoccurs,doing restart regularly is not acceptable.
>
> "Andrew J. Kelly" wrote:
>> SQL 2000 standard edition can only use 2GB max anyway and you have 4GB.
>> I
>> don't recognize the error messages but it sounds like you may have some
>> kind
>> of memory leak that is eating up system memory. I don't know if this is
>> MemToLeave or OS specific memory. Have you tried rebooting?
>> --
>> Andrew J. Kelly SQL MVP
>> "Shama" <Shama@.discussions.microsoft.com> wrote in message
>> news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...
>> > We have not changed any settings for sp_configure and awe has not been
>> > enabled
>> > sql server SE edition with SP4 with 4GB RAM.
>> >
>> > MAX memory setting =2147483647
>> >
>> > and getting error "not enough storage is available to process this
>> > command"
>> > when try to start the backup log job.
>> >
>> > all of sudden we r getting this problem.
>> >
>> > pl suggest
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Try setting the MAX memory setting to allow for several hundred MB's
>> >> for
>> >> the
>> >> OS at all times.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >> "Shama" <Shama@.discussions.microsoft.com> wrote in message
>> >> news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
>> >> > Hi,
>> >> >
>> >> > All these days full backups and log backups are fine and suddenly
>> >> > the
>> >> > log
>> >> > backup is failing for the databases with error message in error log
>> >> > as
>> >> > downgrading backup buffers from 960k to 64k and when ran in QA it
>> >> > says
>> >> > insufficient system memory.
>> >> >
>> >> > there is no additiona load on this db server and the server is not
>> >> > busy.
>> >> >
>> >> > Please suggest how to resolve this problem
>> >> >
>> >> > thanks
>> >> > Shama
>> >>
>> >>
>> >>
>>

backup log failing

Hi,
All these days full backups and log backups are fine and suddenly the log
backup is failing for the databases with error message in error log as
downgrading backup buffers from 960k to 64k and when ran in QA it says
insufficient system memory.
there is no additiona load on this db server and the server is not busy.
Please suggest how to resolve this problem
thanks
ShamaTry setting the MAX memory setting to allow for several hundred MB's for the
OS at all times.
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
> Hi,
> All these days full backups and log backups are fine and suddenly the log
> backup is failing for the databases with error message in error log as
> downgrading backup buffers from 960k to 64k and when ran in QA it says
> insufficient system memory.
> there is no additiona load on this db server and the server is not busy.
> Please suggest how to resolve this problem
> thanks
> Shama|||We have not changed any settings for sp_configure and awe has not been enabl
ed
sql server SE edition with SP4 with 4GB RAM.
MAX memory setting =2147483647
and getting error "not enough storage is available to process this command"
when try to start the backup log job.
all of sudden we r getting this problem.
pl suggest
"Andrew J. Kelly" wrote:

> Try setting the MAX memory setting to allow for several hundred MB's for t
he
> OS at all times.
> --
> Andrew J. Kelly SQL MVP
> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
>
>|||SQL 2000 standard edition can only use 2GB max anyway and you have 4GB. I
don't recognize the error messages but it sounds like you may have some kind
of memory leak that is eating up system memory. I don't know if this is
MemToLeave or OS specific memory. Have you tried rebooting?
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...[vbcol=seagreen]
> We have not changed any settings for sp_configure and awe has not been
> enabled
> sql server SE edition with SP4 with 4GB RAM.
> MAX memory setting =2147483647
> and getting error "not enough storage is available to process this
> command"
> when try to start the backup log job.
> all of sudden we r getting this problem.
> pl suggest
> "Andrew J. Kelly" wrote:
>|||We have restarted the SQL Server and it looks fine now.
when I perform full backup/any query no issues encountered.
when I ran backup log manually in QA few times it says enough memory is not
available to create UMS scheduler,later on it says insufficient system memor
y
.
when I try start the backup log job it says not enough storage is available
to process this command"
how to find whether it is MemToLeave or OS specific memory ?
what shall I do if it reoccurs,doing restart regularly is not acceptable.
"Andrew J. Kelly" wrote:

> SQL 2000 standard edition can only use 2GB max anyway and you have 4GB. I
> don't recognize the error messages but it sounds like you may have some ki
nd
> of memory leak that is eating up system memory. I don't know if this is
> MemToLeave or OS specific memory. Have you tried rebooting?
> --
> Andrew J. Kelly SQL MVP
> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...
>
>|||Are you running any 3rd party software to do backups? In any case this
sounds like a bug and you might best be served by calling MS PSS.
http://www.support.microsoft.com/de...id=fh;EN-US;sql SQL
Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:797C34AE-7BB3-4FFC-8471-5270675C81AB@.microsoft.com...[vbcol=seagreen]
> We have restarted the SQL Server and it looks fine now.
> when I perform full backup/any query no issues encountered.
> when I ran backup log manually in QA few times it says enough memory is
> not
> available to create UMS scheduler,later on it says insufficient system
> memory
> .
> when I try start the backup log job it says not enough storage is
> available
> to process this command"
> how to find whether it is MemToLeave or OS specific memory ?
> what shall I do if it reoccurs,doing restart regularly is not acceptable.
>
> "Andrew J. Kelly" wrote:
>

backup log failing

Hi,
All these days full backups and log backups are fine and suddenly the log
backup is failing for the databases with error message in error log as
downgrading backup buffers from 960k to 64k and when ran in QA it says
insufficient system memory.
there is no additiona load on this db server and the server is not busy.
Please suggest how to resolve this problem
thanks
Shama
Try setting the MAX memory setting to allow for several hundred MB's for the
OS at all times.
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
> Hi,
> All these days full backups and log backups are fine and suddenly the log
> backup is failing for the databases with error message in error log as
> downgrading backup buffers from 960k to 64k and when ran in QA it says
> insufficient system memory.
> there is no additiona load on this db server and the server is not busy.
> Please suggest how to resolve this problem
> thanks
> Shama
|||We have not changed any settings for sp_configure and awe has not been enabled
sql server SE edition with SP4 with 4GB RAM.
MAX memory setting =2147483647
and getting error "not enough storage is available to process this command"
when try to start the backup log job.
all of sudden we r getting this problem.
pl suggest
"Andrew J. Kelly" wrote:

> Try setting the MAX memory setting to allow for several hundred MB's for the
> OS at all times.
> --
> Andrew J. Kelly SQL MVP
> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> news:6A0FFA49-7098-464E-9B8D-05CF0145FB10@.microsoft.com...
>
>
|||SQL 2000 standard edition can only use 2GB max anyway and you have 4GB. I
don't recognize the error messages but it sounds like you may have some kind
of memory leak that is eating up system memory. I don't know if this is
MemToLeave or OS specific memory. Have you tried rebooting?
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...[vbcol=seagreen]
> We have not changed any settings for sp_configure and awe has not been
> enabled
> sql server SE edition with SP4 with 4GB RAM.
> MAX memory setting =2147483647
> and getting error "not enough storage is available to process this
> command"
> when try to start the backup log job.
> all of sudden we r getting this problem.
> pl suggest
> "Andrew J. Kelly" wrote:
|||We have restarted the SQL Server and it looks fine now.
when I perform full backup/any query no issues encountered.
when I ran backup log manually in QA few times it says enough memory is not
available to create UMS scheduler,later on it says insufficient system memory
..
when I try start the backup log job it says not enough storage is available
to process this command"
how to find whether it is MemToLeave or OS specific memory ?
what shall I do if it reoccurs,doing restart regularly is not acceptable.
"Andrew J. Kelly" wrote:

> SQL 2000 standard edition can only use 2GB max anyway and you have 4GB. I
> don't recognize the error messages but it sounds like you may have some kind
> of memory leak that is eating up system memory. I don't know if this is
> MemToLeave or OS specific memory. Have you tried rebooting?
> --
> Andrew J. Kelly SQL MVP
> "Shama" <Shama@.discussions.microsoft.com> wrote in message
> news:46434329-39B4-4ACE-BBED-B376FC70EE16@.microsoft.com...
>
>
|||Are you running any 3rd party software to do backups? In any case this
sounds like a bug and you might best be served by calling MS PSS.
http://www.support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL
Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Shama" <Shama@.discussions.microsoft.com> wrote in message
news:797C34AE-7BB3-4FFC-8471-5270675C81AB@.microsoft.com...[vbcol=seagreen]
> We have restarted the SQL Server and it looks fine now.
> when I perform full backup/any query no issues encountered.
> when I ran backup log manually in QA few times it says enough memory is
> not
> available to create UMS scheduler,later on it says insufficient system
> memory
> .
> when I try start the backup log job it says not enough storage is
> available
> to process this command"
> how to find whether it is MemToLeave or OS specific memory ?
> what shall I do if it reoccurs,doing restart regularly is not acceptable.
>
> "Andrew J. Kelly" wrote:

BACKUP LOG <database name> WITH TRUNCATE_ONLY failing

SQL Server2K, SP3a. Attempt to run in EM:
BACKUP LOG <database_name> WITH TRUNCATE_ONLY
The error returned is:
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near
'WITHTRUNCATE_ONLY'.
The two keywords are concatenated in the error message, as shown above.
Database name works in other statements. Command is straight out of books
online! Have searched web & news groups (1 hit at a pay site).
Many thanks for any info/help.Have you tried running this in Query Analyzer? How are you running it in
EM?
"Mailing Lists" <ml010241@.berkea.com> wrote in message
news:erRGwuOlEHA.896@.TK2MSFTNGP12.phx.gbl...
> SQL Server2K, SP3a. Attempt to run in EM:
> BACKUP LOG <database_name> WITH TRUNCATE_ONLY
> The error returned is:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax
near
> 'WITHTRUNCATE_ONLY'.
> The two keywords are concatenated in the error message, as shown above.
> Database name works in other statements. Command is straight out of books
> online! Have searched web & news groups (1 hit at a pay site).
> Many thanks for any info/help.
>|||Below is a copy& paste from what I just executed in Query Analyzer:
BACKUP LOG pubs WITH TRUNCATE_ONLY
Can you copy your exact command you executed? Also, try executing it from Query Analyzer.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mailing Lists" <ml010241@.berkea.com> wrote in message news:erRGwuOlEHA.896@.TK2MSFTNGP12.phx.gbl...
> SQL Server2K, SP3a. Attempt to run in EM:
> BACKUP LOG <database_name> WITH TRUNCATE_ONLY
> The error returned is:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near
> 'WITHTRUNCATE_ONLY'.
> The two keywords are concatenated in the error message, as shown above.
> Database name works in other statements. Command is straight out of books
> online! Have searched web & news groups (1 hit at a pay site).
> Many thanks for any info/help.
>|||That did the trick (I'm ashamed to say). I considered this earlier but
wrote it off as identical to executing the SQL statement in EM--SQL is SQL,
darn it. :-) To answer your question, open the SQL view on any query and
type away.
Thank you very much!
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:%2305Xx6OlEHA.3816@.TK2MSFTNGP14.phx.gbl...
> Have you tried running this in Query Analyzer? How are you running it in
> EM?
>
> "Mailing Lists" <ml010241@.berkea.com> wrote in message
> news:erRGwuOlEHA.896@.TK2MSFTNGP12.phx.gbl...
> > SQL Server2K, SP3a. Attempt to run in EM:
> >
> > BACKUP LOG <database_name> WITH TRUNCATE_ONLY
> >
> > The error returned is:
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax
> near
> > 'WITHTRUNCATE_ONLY'.
> >
> > The two keywords are concatenated in the error message, as shown above.
> > Database name works in other statements. Command is straight out of
books
> > online! Have searched web & news groups (1 hit at a pay site).
> >
> > Many thanks for any info/help.
> >
> >
>|||"Mailing Lists" <ml010241@.berkea.com> wrote in message
news:erOtp%23OlEHA.3356@.TK2MSFTNGP15.phx.gbl...
> wrote it off as identical to executing the SQL statement in EM--SQL is
SQL,
> darn it. :-) To answer your question, open the SQL view on any query and
> type away.
SQL is SQL, but EM pre-parses the SQL according to its own rules when
you go into that SQL view mode. I recommend only using EM for
administrative tools (e.g. adding Agent jobs), and use QA for everything
else. It's a far superior tool.|||Yes, apparently this statement must be run in Query Analyzer. Thank you for
the quick reply.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23lU5I9OlEHA.896@.TK2MSFTNGP12.phx.gbl...
> Below is a copy& paste from what I just executed in Query Analyzer:
> BACKUP LOG pubs WITH TRUNCATE_ONLY
> Can you copy your exact command you executed? Also, try executing it from
Query Analyzer.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Mailing Lists" <ml010241@.berkea.com> wrote in message
news:erRGwuOlEHA.896@.TK2MSFTNGP12.phx.gbl...
> > SQL Server2K, SP3a. Attempt to run in EM:
> >
> > BACKUP LOG <database_name> WITH TRUNCATE_ONLY
> >
> > The error returned is:
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax
near
> > 'WITHTRUNCATE_ONLY'.
> >
> > The two keywords are concatenated in the error message, as shown above.
> > Database name works in other statements. Command is straight out of
books
> > online! Have searched web & news groups (1 hit at a pay site).
> >
> > Many thanks for any info/help.
> >
> >
>|||After this "amusing" detour I couldn't agree more--thanks again!
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:OHYMUAPlEHA.952@.TK2MSFTNGP14.phx.gbl...
> "Mailing Lists" <ml010241@.berkea.com> wrote in message
> news:erOtp%23OlEHA.3356@.TK2MSFTNGP15.phx.gbl...
> > wrote it off as identical to executing the SQL statement in EM--SQL is
> SQL,
> > darn it. :-) To answer your question, open the SQL view on any query
and
> > type away.
> SQL is SQL, but EM pre-parses the SQL according to its own rules when
> you go into that SQL view mode. I recommend only using EM for
> administrative tools (e.g. adding Agent jobs), and use QA for everything
> else. It's a far superior tool.
>

backup jobs not runing on mssql7

Hi there,
I have a mssql-7 and 2/5 dbs get backed up nightly through
the scheduled backup jobs. 3 dbs keep failing at nights
and if I run the job manually. I can manually backup the
DBs through ALL TASKS..BACKUP DATABASE.
I've Checked:
SP-4
service running
sql agent running as admin
Job enabled
MDAC (latest)
jobs are 15mins apart
Any suggestions are appriciated.
ThanXHave you checked the logs and Agent history? What is the error that gets
produced?
Andrew J. Kelly SQL MVP
"Emil" <anonymous@.discussions.microsoft.com> wrote in message
news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
> Hi there,
> I have a mssql-7 and 2/5 dbs get backed up nightly through
> the scheduled backup jobs. 3 dbs keep failing at nights
> and if I run the job manually. I can manually backup the
> DBs through ALL TASKS..BACKUP DATABASE.
> I've Checked:
> SP-4
> service running
> sql agent running as admin
> Job enabled
> MDAC (latest)
> jobs are 15mins apart
> Any suggestions are appriciated.
> ThanX
>|||Andrew,
I have cheched the agent log and its clean! and the server
log doesn't mention anything regarding the job failure.
ThanX
>--Original Message--
>Have you checked the logs and Agent history? What is the
error that gets
>produced?
>--
>Andrew J. Kelly SQL MVP
>
>"Emil" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
through[vbcol=seagreen]
>
>.
>|||What about the Job History? Right click on thjob in EM and choose Show
History. Then check the checkbox labeled Show Details and see what that
says.
Andrew J. Kelly SQL MVP
"Emil" <anonymous@.discussions.microsoft.com> wrote in message
news:f29b01c43dad$56d3bc90$a601280a@.phx.gbl...[vbcol=seagreen]
> Andrew,
> I have cheched the agent log and its clean! and the server
> log doesn't mention anything regarding the job failure.
> ThanX
> error that gets
> message
> through

backup jobs not runing on mssql7

Hi there,
I have a mssql-7 and 2/5 dbs get backed up nightly through
the scheduled backup jobs. 3 dbs keep failing at nights
and if I run the job manually. I can manually backup the
DBs through ALL TASKS..BACKUP DATABASE.
I've Checked:
SP-4
service running
sql agent running as admin
Job enabled
MDAC (latest)
jobs are 15mins apart
Any suggestions are appriciated.
ThanX
Have you checked the logs and Agent history? What is the error that gets
produced?
Andrew J. Kelly SQL MVP
"Emil" <anonymous@.discussions.microsoft.com> wrote in message
news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
> Hi there,
> I have a mssql-7 and 2/5 dbs get backed up nightly through
> the scheduled backup jobs. 3 dbs keep failing at nights
> and if I run the job manually. I can manually backup the
> DBs through ALL TASKS..BACKUP DATABASE.
> I've Checked:
> SP-4
> service running
> sql agent running as admin
> Job enabled
> MDAC (latest)
> jobs are 15mins apart
> Any suggestions are appriciated.
> ThanX
>
|||Andrew,
I have cheched the agent log and its clean! and the server
log doesn't mention anything regarding the job failure.
ThanX
>--Original Message--
>Have you checked the logs and Agent history? What is the
error that gets
>produced?
>--
>Andrew J. Kelly SQL MVP
>
>"Emil" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
through
>
>.
>
|||What about the Job History? Right click on thjob in EM and choose Show
History. Then check the checkbox labeled Show Details and see what that
says.
Andrew J. Kelly SQL MVP
"Emil" <anonymous@.discussions.microsoft.com> wrote in message
news:f29b01c43dad$56d3bc90$a601280a@.phx.gbl...[vbcol=seagreen]
> Andrew,
> I have cheched the agent log and its clean! and the server
> log doesn't mention anything regarding the job failure.
> ThanX
> error that gets
> message
> through

backup jobs not runing on mssql7

Hi there,
I have a mssql-7 and 2/5 dbs get backed up nightly through
the scheduled backup jobs. 3 dbs keep failing at nights
and if I run the job manually. I can manually backup the
DBs through ALL TASKS..BACKUP DATABASE.
I've Checked:
SP-4
service running
sql agent running as admin
Job enabled
MDAC (latest)
jobs are 15mins apart
Any suggestions are appriciated.
ThanXHave you checked the logs and Agent history? What is the error that gets
produced?
--
Andrew J. Kelly SQL MVP
"Emil" <anonymous@.discussions.microsoft.com> wrote in message
news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
> Hi there,
> I have a mssql-7 and 2/5 dbs get backed up nightly through
> the scheduled backup jobs. 3 dbs keep failing at nights
> and if I run the job manually. I can manually backup the
> DBs through ALL TASKS..BACKUP DATABASE.
> I've Checked:
> SP-4
> service running
> sql agent running as admin
> Job enabled
> MDAC (latest)
> jobs are 15mins apart
> Any suggestions are appriciated.
> ThanX
>|||Andrew,
I have cheched the agent log and its clean! and the server
log doesn't mention anything regarding the job failure.
ThanX
>--Original Message--
>Have you checked the logs and Agent history? What is the
error that gets
>produced?
>--
>Andrew J. Kelly SQL MVP
>
>"Emil" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
>> Hi there,
>> I have a mssql-7 and 2/5 dbs get backed up nightly
through
>> the scheduled backup jobs. 3 dbs keep failing at nights
>> and if I run the job manually. I can manually backup the
>> DBs through ALL TASKS..BACKUP DATABASE.
>> I've Checked:
>> SP-4
>> service running
>> sql agent running as admin
>> Job enabled
>> MDAC (latest)
>> jobs are 15mins apart
>> Any suggestions are appriciated.
>> ThanX
>>
>
>.
>|||What about the Job History? Right click on thjob in EM and choose Show
History. Then check the checkbox labeled Show Details and see what that
says.
--
Andrew J. Kelly SQL MVP
"Emil" <anonymous@.discussions.microsoft.com> wrote in message
news:f29b01c43dad$56d3bc90$a601280a@.phx.gbl...
> Andrew,
> I have cheched the agent log and its clean! and the server
> log doesn't mention anything regarding the job failure.
> ThanX
> >--Original Message--
> >Have you checked the logs and Agent history? What is the
> error that gets
> >produced?
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Emil" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:ed5901c43d33$cbb41660$a101280a@.phx.gbl...
> >> Hi there,
> >> I have a mssql-7 and 2/5 dbs get backed up nightly
> through
> >> the scheduled backup jobs. 3 dbs keep failing at nights
> >> and if I run the job manually. I can manually backup the
> >> DBs through ALL TASKS..BACKUP DATABASE.
> >>
> >> I've Checked:
> >> SP-4
> >> service running
> >> sql agent running as admin
> >> Job enabled
> >> MDAC (latest)
> >> jobs are 15mins apart
> >>
> >> Any suggestions are appriciated.
> >> ThanX
> >>
> >>
> >
> >
> >.
> >

Backup Jobs

I am backing up my SQL Server databases to VDM (SAN) but all my backups are
taking very long some times 12 hours and always failing with the following
error.
failed: 64(The specified network name is no longer available.) [SQLSTATE
42000] (Error 3202) A nonrecoverable I/O error occurred on file
Any help will be appreciated.
Thanks!Get your network and SAN people involved, because the problem is something
that they will have to solve. (If you are also the network and SAN person,
the problem is probably not in your SQL Server.)
This is most likely a bottleneck in either the network layers or the SAN
disk or disk controller throughput. I suspect that at the lower levels of
network and/or disk I/O there are a lot of retries happening, until finally
one of them just cannot recover in time. Then your backup fails because it
can no longer see that the file to which it was backing up.
How much data are you backing up? How big is the largest database? How
long would you expect it to take? You are probably having this problem on
your biggest databases, which put the greatest backup load on your
landscape, and the little databases are having no problems.
RLF
<msnews.microsoft.com> wrote in message
news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
> I am backing up my SQL Server databases to VDM (SAN) but all my backups
> are taking very long some times 12 hours and always failing with the
> following error.
> failed: 64(The specified network name is no longer available.) [SQLSTATE
> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
> Any help will be appreciated.
> Thanks!
>|||Are you watching the network traffic and CPU on both your server and the
SAN?
I recommend you do.
Also, if you backup locally, to disk, how long does it take?
<msnews.microsoft.com> wrote in message
news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
> I am backing up my SQL Server databases to VDM (SAN) but all my backups
> are taking very long some times 12 hours and always failing with the
> following error.
> failed: 64(The specified network name is no longer available.) [SQLSTATE
> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
> Any help will be appreciated.
> Thanks!
>|||What is the best way to do that ?
"Jay" <spam@.nospam.org> wrote in message
news:%23AeAq2EGIHA.4684@.TK2MSFTNGP06.phx.gbl...
> Are you watching the network traffic and CPU on both your server and the
> SAN?
> I recommend you do.
> Also, if you backup locally, to disk, how long does it take?
>
> <msnews.microsoft.com> wrote in message
> news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
>> I am backing up my SQL Server databases to VDM (SAN) but all my backups
>> are taking very long some times 12 hours and always failing with the
>> following error.
>> failed: 64(The specified network name is no longer available.) [SQLSTATE
>> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
>> Any help will be appreciated.
>> Thanks!
>|||I am not a SAN or network specialist, although I work with them, so I cannot
tell you exactly what counters to watch. But you should be able to estimate
the throughput that you should get and compare it to what is actually
happening.
For example, if you expect to backup 150 GB an hour, but the 150 GB backup
fails after 12 hours, then something is obviously wrong. Jay asked 'How
long does the backup run to local disk?' Like my questions, it was an
effort to find out how much your backup landscape is differing from what you
would expect.
RLF
<omranu@.Gmail.com> wrote in message
news:OBjXImYGIHA.5544@.TK2MSFTNGP02.phx.gbl...
> What is the best way to do that ?
>
> "Jay" <spam@.nospam.org> wrote in message
> news:%23AeAq2EGIHA.4684@.TK2MSFTNGP06.phx.gbl...
>> Are you watching the network traffic and CPU on both your server and the
>> SAN?
>> I recommend you do.
>> Also, if you backup locally, to disk, how long does it take?
>>
>> <msnews.microsoft.com> wrote in message
>> news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
>> I am backing up my SQL Server databases to VDM (SAN) but all my backups
>> are taking very long some times 12 hours and always failing with the
>> following error.
>> failed: 64(The specified network name is no longer available.) [SQLSTATE
>> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
>> Any help will be appreciated.
>> Thanks!
>>
>|||Are you asking how to monitor the network traffic, or how to backup to disk?
The simplest way to monitor network traffic is to watch the Network tab of
the Task Manager. I was, however, refering to the Performance Monitor
available under "Control Panel->Administrative Tools"..
The simplest way to backup to disk is a right-click on the database name in
EM, of MS.
<omranu@.Gmail.com> wrote in message
news:OBjXImYGIHA.5544@.TK2MSFTNGP02.phx.gbl...
> What is the best way to do that ?
>
> "Jay" <spam@.nospam.org> wrote in message
> news:%23AeAq2EGIHA.4684@.TK2MSFTNGP06.phx.gbl...
>> Are you watching the network traffic and CPU on both your server and the
>> SAN?
>> I recommend you do.
>> Also, if you backup locally, to disk, how long does it take?
>>
>> <msnews.microsoft.com> wrote in message
>> news:u%23CF2Z$FIHA.5980@.TK2MSFTNGP04.phx.gbl...
>> I am backing up my SQL Server databases to VDM (SAN) but all my backups
>> are taking very long some times 12 hours and always failing with the
>> following error.
>> failed: 64(The specified network name is no longer available.) [SQLSTATE
>> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
>> Any help will be appreciated.
>> Thanks!
>>
>|||Did you ever find the root cause of this? I am struggling with the same
issue. Windows 2003 x64 / SQL 2005 with SAN backend databases. DB access is
very fast on the attached SAN drives however the SQL backups are way, way
slow. As soon as the job leaves the fiber fabric and moves through the IP
stack and out to the VDM the jobs drag. This is a gig connected box and I am
seeing rates between 5-12MB/s, which is horrible. Staying with in the fiber
frabric is great, but moving out into the IP cloud is horrible. I have tried
all sorts of stuff yet nothing is showing me the problem. The VDM links to a
DataMover that is barely under load; tons of free memory, tons of CPU head
room. I have confirmed with the NE that the edge switches are not under
load, there are no errors on the port, and that the pipes feeding the VDM are
way, way underutilized: 2GB pipe with no more than 40MB/s throughput when the
job is running.
Is there any known issue with 2003 x32 or x64 SP2, SQL2005 and data movement
through a NAS VDM?
~ Jeffrey
"msnews.microsoft.com" wrote:
> I am backing up my SQL Server databases to VDM (SAN) but all my backups are
> taking very long some times 12 hours and always failing with the following
> error.
> failed: 64(The specified network name is no longer available.) [SQLSTATE
> 42000] (Error 3202) A nonrecoverable I/O error occurred on file
> Any help will be appreciated.
> Thanks!
>
>

Backup Job Failing

I have an SSIS package that does one simple thing: perform a FULL backup of a database.

I executed this package yesterday at 2:00. The package backs up to four individual files on a network share. The network share is accessible from the SQL Server. THe database in question is 245GB in size.

The package was running fine when I left for the day. When I got in today, there was an error in the SQL Server log:

Error: 3041, Severity: 16, State: 1.

BACKUP failed to complete the command BACKUP DATABASE ServicingODS. Check the backup application log for detailed messages.

Where is this infamous backup application log?!? The Event Viewer says the same thing. Needless to say, the error message is a bit vague.

There were no "issus" overnight (power outages, network issues, etc.)

Anyone have any ideas?

Thanks!

Hi A.M

If you check the SQL server error log, there should be another line of error above the message that you have posted.

Could you please check and post a few lines from above and below the message you have already posted.

Jag

Backup Issue

My transaction log backup using the maintanance plan is failing with
following error message in the sql error log. Has anybody seen this before
and found a resolution. I have checked and ensured that the CPU has adquete
resources/memory to carry out the operation. Any suggestion would be higly
appreciated. Thanks
BackupIoRequest::WaitForIoCompletion: write failure on backup device
'\\epsql09sa\g$\backup\epsql12sa\sdn_rep
ortingSQL12_log.bak'. Operating
system error 1450(Insufficient system resources exist to complete the
requested service.).b_dba wrote:
> My transaction log backup using the maintanance plan is failing with
> following error message in the sql error log. Has anybody seen this
> before and found a resolution. I have checked and ensured that the
> CPU has adquete resources/memory to carry out the operation. Any
> suggestion would be higly appreciated. Thanks
> BackupIoRequest::WaitForIoCompletion: write failure on backup device
> '\\epsql09sa\g$\backup\epsql12sa\sdn_rep
ortingSQL12_log.bak'.
> Operating system error 1450(Insufficient system resources exist to
> complete the requested service.).
What SQL Version?
http://support.microsoft.com/kb/274310/EN-US/
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=2835
1b29c5611" target="_blank">http://groups.google.com/group/micr...r />
1b29c5611
a
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hello David,
Thanks for your input.
I am using SQL Server 2000 version. I checked on the links u mentioned but
did not find any info on resolving this issue. If you hav any other input,
let me know.
bishal
"David Gugick" wrote:

> b_dba wrote:
> What SQL Version?
> http://support.microsoft.com/kb/274310/EN-US/
> http://sqljunkies.com/Forums/ShowPost.aspx?PostID=2835
> http://groups.google.com/group/micr...n#c89a491b29c56
11a
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||U can check the follwing ling .It may help
http://forums.spywareinfo.com/lofiv...php/t52631.html|||b_dba wrote:
> My transaction log backup using the maintanance plan is failing with
> following error message in the sql error log. Has anybody seen this before
> and found a resolution. I have checked and ensured that the CPU has adquet
e
> resources/memory to carry out the operation. Any suggestion would be higly
> appreciated. Thanks
> BackupIoRequest::WaitForIoCompletion: write failure on backup device
> '\\epsql09sa\g$\backup\epsql12sa\sdn_rep
ortingSQL12_log.bak'. Operating
> system error 1450(Insufficient system resources exist to complete the
> requested service.).
Have you checked that the folder where you're placing the file exists?
Also make sure that you have sufficient disk space. What about
permissions to the folder? You need to have you SQL Server Agent running
under a Domain Account that has sufficient access to the folder.
Regards
Steen

Backup Issue

My transaction log backup using the maintanance plan is failing with
following error message in the sql error log. Has anybody seen this before
and found a resolution. I have checked and ensured that the CPU has adquete
resources/memory to carry out the operation. Any suggestion would be higly
appreciated. Thanks
BackupIoRequest::WaitForIoCompletion: write failure on backup device
'\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL1 2_log.bak'. Operating
system error 1450(Insufficient system resources exist to complete the
requested service.).
b_dba wrote:
> My transaction log backup using the maintanance plan is failing with
> following error message in the sql error log. Has anybody seen this
> before and found a resolution. I have checked and ensured that the
> CPU has adquete resources/memory to carry out the operation. Any
> suggestion would be higly appreciated. Thanks
> BackupIoRequest::WaitForIoCompletion: write failure on backup device
> '\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL1 2_log.bak'.
> Operating system error 1450(Insufficient system resources exist to
> complete the requested service.).
What SQL Version?
http://support.microsoft.com/kb/274310/EN-US/
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=2835
http://groups.google.com/group/micro...a491b29c56 11
a
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Hello David,
Thanks for your input.
I am using SQL Server 2000 version. I checked on the links u mentioned but
did not find any info on resolving this issue. If you hav any other input,
let me know.
bishal
"David Gugick" wrote:

> b_dba wrote:
> What SQL Version?
> http://support.microsoft.com/kb/274310/EN-US/
> http://sqljunkies.com/Forums/ShowPost.aspx?PostID=2835
> http://groups.google.com/group/micro...#c89a491b29c56
11a
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||U can check the follwing ling .It may help
http://forums.spywareinfo.com/lofive...hp/t52631.html
|||b_dba wrote:
> My transaction log backup using the maintanance plan is failing with
> following error message in the sql error log. Has anybody seen this before
> and found a resolution. I have checked and ensured that the CPU has adquete
> resources/memory to carry out the operation. Any suggestion would be higly
> appreciated. Thanks
> BackupIoRequest::WaitForIoCompletion: write failure on backup device
> '\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL1 2_log.bak'. Operating
> system error 1450(Insufficient system resources exist to complete the
> requested service.).
Have you checked that the folder where you're placing the file exists?
Also make sure that you have sufficient disk space. What about
permissions to the folder? You need to have you SQL Server Agent running
under a Domain Account that has sufficient access to the folder.
Regards
Steen

Backup Issue

My transaction log backup using the maintanance plan is failing with
following error message in the sql error log. Has anybody seen this before
and found a resolution. I have checked and ensured that the CPU has adquete
resources/memory to carry out the operation. Any suggestion would be higly
appreciated. Thanks
BackupIoRequest::WaitForIoCompletion: write failure on backup device
'\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL12_log.bak'. Operating
system error 1450(Insufficient system resources exist to complete the
requested service.).b_dba wrote:
> My transaction log backup using the maintanance plan is failing with
> following error message in the sql error log. Has anybody seen this
> before and found a resolution. I have checked and ensured that the
> CPU has adquete resources/memory to carry out the operation. Any
> suggestion would be higly appreciated. Thanks
> BackupIoRequest::WaitForIoCompletion: write failure on backup device
> '\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL12_log.bak'.
> Operating system error 1450(Insufficient system resources exist to
> complete the requested service.).
What SQL Version?
http://support.microsoft.com/kb/274310/EN-US/
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=2835
http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/cf17d0258c48bce0/c89a491b29c5611a?lnk=st&q=1450+%22Insufficient+system+resources+exist+to+complete+the+requested+service%22+%22sql+server%22&rnum=5&hl=en#c89a491b29c5611a
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hello David,
Thanks for your input.
I am using SQL Server 2000 version. I checked on the links u mentioned but
did not find any info on resolving this issue. If you hav any other input,
let me know.
bishal
"David Gugick" wrote:
> b_dba wrote:
> > My transaction log backup using the maintanance plan is failing with
> > following error message in the sql error log. Has anybody seen this
> > before and found a resolution. I have checked and ensured that the
> > CPU has adquete resources/memory to carry out the operation. Any
> > suggestion would be higly appreciated. Thanks
> >
> > BackupIoRequest::WaitForIoCompletion: write failure on backup device
> > '\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL12_log.bak'.
> > Operating system error 1450(Insufficient system resources exist to
> > complete the requested service.).
> What SQL Version?
> http://support.microsoft.com/kb/274310/EN-US/
> http://sqljunkies.com/Forums/ShowPost.aspx?PostID=2835
> http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/cf17d0258c48bce0/c89a491b29c5611a?lnk=st&q=1450+%22Insufficient+system+resources+exist+to+complete+the+requested+service%22+%22sql+server%22&rnum=5&hl=en#c89a491b29c5611a
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||U can check the follwing ling .It may help
http://forums.spywareinfo.com/lofiversion/index.php/t52631.html|||b_dba wrote:
> My transaction log backup using the maintanance plan is failing with
> following error message in the sql error log. Has anybody seen this before
> and found a resolution. I have checked and ensured that the CPU has adquete
> resources/memory to carry out the operation. Any suggestion would be higly
> appreciated. Thanks
> BackupIoRequest::WaitForIoCompletion: write failure on backup device
> '\\epsql09sa\g$\backup\epsql12sa\sdn_reportingSQL12_log.bak'. Operating
> system error 1450(Insufficient system resources exist to complete the
> requested service.).
Have you checked that the folder where you're placing the file exists?
Also make sure that you have sufficient disk space. What about
permissions to the folder? You need to have you SQL Server Agent running
under a Domain Account that has sufficient access to the folder.
Regards
Steen

backup in maint plan failing

Hello, i'm having a problem with a db backup in a maint plan-- i get an
error saying
Msg 3007, Level 16, State 1, Line 2
The backup of the file or filegroup "sysft_ft" is not permitted because it
is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses
to restrict the selection to include only online data.
Msg 3013, Level 16, State 1, Line 2
What is "sysft_ft"? If i search this in google i literally only get one
hit, which is unbelieveable to me. How can I get around this? I really
don't want to do a file backup and would like to get to the bottom of this.
Thanks, NWOP.This looks like an offline full text catalog. If you are using SQL Server
2005 try
select name, state, state_desc from sys.database_files
If one of the names matchs sysft_ft and state_desc is OFFLINE you will need
to fix it first. Perhaps you just need to rebuild the catalog. After the
catalog is ONLINE you will be able to perform your backup.
Hope this helps,
Ben Nevarez
"new_world_order_pigs" wrote:
> Hello, i'm having a problem with a db backup in a maint plan-- i get an
> error saying
> Msg 3007, Level 16, State 1, Line 2
> The backup of the file or filegroup "sysft_ft" is not permitted because it
> is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses
> to restrict the selection to include only online data.
> Msg 3013, Level 16, State 1, Line 2
> What is "sysft_ft"? If i search this in google i literally only get one
> hit, which is unbelieveable to me. How can I get around this? I really
> don't want to do a file backup and would like to get to the bottom of this.
> Thanks, NWOP.|||Ben,
This did seem to work in that it did put the full text cat back "online" so
I'm assuming that when I run the backup in the evening that it should work
just fine. You are officially a "SQL Server Animal" in my book and I
appreciate your help.
Sincerely,
NWOP.
"Ben Nevarez" wrote:
> This looks like an offline full text catalog. If you are using SQL Server
> 2005 try
> select name, state, state_desc from sys.database_files
> If one of the names matchs sysft_ft and state_desc is OFFLINE you will need
> to fix it first. Perhaps you just need to rebuild the catalog. After the
> catalog is ONLINE you will be able to perform your backup.
> Hope this helps,
> Ben Nevarez
>
>
> "new_world_order_pigs" wrote:
> > Hello, i'm having a problem with a db backup in a maint plan-- i get an
> > error saying
> > Msg 3007, Level 16, State 1, Line 2
> > The backup of the file or filegroup "sysft_ft" is not permitted because it
> > is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses
> > to restrict the selection to include only online data.
> > Msg 3013, Level 16, State 1, Line 2
> >
> > What is "sysft_ft"? If i search this in google i literally only get one
> > hit, which is unbelieveable to me. How can I get around this? I really
> > don't want to do a file backup and would like to get to the bottom of this.
> > Thanks, NWOP.