Re: SQL2k backups not deleted per maintenance plan
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 10/20/04
- Next message: Kendo Nagasaki: "Re: Error updating AS400 table"
- Previous message: Tibor Karaszi: "Re: cant get the correct num of rows from Oracle. in 2 SQL servers ( sql 7.0 and SQL 2000)"
- In reply to: SJohnson: "RE: SQL2k backups not deleted per maintenance plan"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 20 Oct 2004 18:32:49 +0200
Some other possibilities:
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/ "SJohnson" <SJohnson@discussions.microsoft.com> wrote in message news:C3513964-B632-42A1-804F-2E8FA2F76FAB@microsoft.com... > GYK- > > Thank you for this information. I will monitor the plan over the next two > days with this in mind. > > -Shannon > > "GYK" wrote: > >> Hi SJohnson, >> >> The way backup process works is, it takes the backup of the database and >> then deletes the old backup file, based on the retention period specified. >> >> For ex: if your .bak file size is 10 GB, you need a more than 20 GB of >> diskspace. 10 Gb for the actual backup you will be taking and another 10 GB >> for the old backup it has taken. Once the maintenance job gets executed >> successfully, you will again have 10 Gb free space, as it deletes the old >> backup. >> >> Thanks >> GYK >> >> "SJohnson" wrote: >> >> > Even though the maintenance plan specifies that backups older than 20 hours >> > should be deleted, they are not being deleted. >> > >> > Can anyone suggest a reason why? I've not seen anything in the SQL logs >> > other than "out of disk space" messages once the backups fill up the disk. >> > >> > The backups are done to disk on a nightly basis. The nightly scheme is >> > supposed to be: >> > 1. SQL maintenance plan creates the backups, deleting the backups from the >> > previous night as it goes. >> > 2. BackupExec diffs run, committing the .bak files to tape. >> > >> > For some reason, the SQL plan just isn't deleting the old files anymore... >> > help? >> > >> > TIA, >> > Shannon
- Next message: Kendo Nagasaki: "Re: Error updating AS400 table"
- Previous message: Tibor Karaszi: "Re: cant get the correct num of rows from Oracle. in 2 SQL servers ( sql 7.0 and SQL 2000)"
- In reply to: SJohnson: "RE: SQL2k backups not deleted per maintenance plan"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
