Re: Transaction log backup

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 08/04/04 

Date: Wed, 4 Aug 2004 11:28:11 +0200

Main plan is totally reworked in SQL Server 2005. Unfortunately, I haven't had the time to look at this yet.
If you have MSDN, you can download and have a look. I doubt it will be changed in 2000. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andrew Loree" <nospam@please.com> wrote in message news:%236qtsQceEHA.236@tk2msftngp13.phx.gbl...
> Any word on if this will ever be "fixed".  Just one of those annoying things
> that create log term headaches (pun intented).  Why sqlmaint would every try
> to issue a BACKUP log to a db in SIMPLE recovery makes zero sense.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in
> message news:eDFJwzWeEHA.2352@TK2MSFTNGP09.phx.gbl...
> > Below KB might help:
> >
> http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
> >
> >
> > Also, check out below great troubleshooting suggestions from Bill H at MS:
> >
> >
> > ------   Log files don't delete   ----
> > This is likely to be either a permissions problem or a sharing violation
> > problem. The maintenance plan is run as a job, and jobs are run by the
> > SQLServerAgent service.
> >
> > Permissions:
> > 1. Determine the startup account for the SQLServerAgent service
> > (Start|Programs|Administrative tools|Services|SQLServerAgent|Startup).
> This
> > account is the security context for jobs, and thus the maintenance plan.
> > 2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
> > account) then skip step 3.
> > 3. On that box, log onto NT as that account. Using Explorer, attempt to
> > delete an expired backup. If that succeeds then go to Sharing Violation
> > section.
> > 4. Log onto NT with an account that is an administrator and use Explorer
> to
> > look at the Properties|Security of the folder (where the backups reside)
> > and ensure the SQLServerAgent startup account has Full Control. If the
> > SQLServerAgent startup account is LocalSystem, then the account to
> consider
> > is SYSTEM.
> > 5. In NT, if an account is a member of an NT group, and if that group has
> > Access is Denied, then that account will have Access is Denied, even if
> > that account is also a member of the Administrators group. Thus you may
> > need to check group permissions (if the Startup Account is a member of a
> > group).
> > 6. Keep in mind that permissions (by default) are inherited from a parent
> > folder. Thus, if the backups are stored in C:\bak, and if someone had
> > denied permission to the SQLServerAgent startup account for C:\, then
> > C:\bak will inherit access is denied.
> >
> > Sharing violation:
> > This is likely to be rooted in a timing issue, with the most likely cause
> > being another scheduled process (such as NT Backup or Anti-Virus software)
> > having the backup file open at the time when the SQLServerAgent (i.e., the
> > maintenance plan job) tried to delete it.
> > 1. Download filemon and handle from www.sysinternals.com.
> > 2. I am not sure whether filemon can be scheduled, or you might be able to
> > use NT scheduling services to start filemon just before the maintenance
> > plan job is started, but the filemon log can become very large, so it
> would
> > be best to start it some short time before the maintenance plan starts.
> > 3. Inspect the filemon log for another process that has that backup file
> > open (if your lucky enough to have started filemon before this other
> > process grabs the backup folder), and inspect the log for the results when
> > the SQLServerAgent agent attempts to open that same file.
> > 4. Schedule the job or that other process to do their work at different
> > times.
> > 5. You can use the handle utility if you are around at the time when the
> > job is scheduled to run.
> >
> > If the backup files are going to a \\share or a mapped drive (as opposed
> to
> > local drive), then you will need to modify the above (with respect to
> where
> > the tests and utilities are run).
> >
> > Finally, inspection of the maintenance plan's history report might be
> > useful.
> >
> > Thanks,
> >
> > Bill Hollinshead
> > Microsoft, SQL Server
> >
> >
> > -- 
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Rjean" <anonymous@discussions.microsoft.com> wrote in message
> news:ae1d01c4796b$f199b320$a401280a@phx.gbl...
> > > HI,
> > >
> > > each day, im backing up a  dozen database with the options
> > > to delete 2 days older previous backup .  It works with
> > > the databes but not for the transaction logs.  It doesn't
> > > delete at all previous backups.  I recreate the data
> > > maintenace plan without success , it still keep the old
> > > trtansaction log backups .  so i have to manually delete
> > > them (very annoying )
> > >
> > > im running sq2000 (with latest SP) on a windows 2003
> > > server
> > >
> > > WHAT CAN I DO ??
> > >
> >
> >
>
>

Relevant Pages

  • Re: Unable to Backup on Network
    ... service accoutn from the 'Local System' account to a specific account. ... I like to log in to the SQL server console as the service account to test ... > The operating system on which my SQL Server 2000 is there is Windows 2000> Server while i want to take the backup on another computer on network which> also has same operating system. ...
    (microsoft.public.sqlserver.security)
  • Re: backing up to network share issue.
    ... I guess I was confused by your later text where I read it as if you stated that it would be the Agent account ... Tibor Karaszi, SQL Server MVP ... >> impersonation when it accesses the backup file on behalf of the SQL Server ... >>> As Tibor stated, this is not an SQL Server issue, it is a network ...
    (microsoft.public.sqlserver.msde)
  • Re: Sql 2000 Maintenance Plan not deleting old transaction logs
    ... Did you include any databases in simple recovery in that plan? ... account is the security context for jobs, ... delete an expired backup. ... I'd rather not have to delete these extra backup files manually or with an extraneous script. ...
    (microsoft.public.sqlserver.tools)
  • Re: User authentication
    ... There are 2 SQL Server 2005 ... 1 SQL Server 2000 installed on another server ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: backing up to network share issue.
    ... impersonation when it accesses the backup file on behalf of the SQL Server uses that executed the backup ... SQL Server just uses the SQL Server service account when accessing the backup share. ... > As Tibor stated, this is not an SQL Server issue, it is a network ...
    (microsoft.public.sqlserver.msde)