Hi, i´ve created a manteinance plan to backup all my databases, it
makes it right. I´ve checked the "delete previous files older than X
days (translared)" option, but it doesnt work, backups are piling up
and we have to delete them manually.
Any idea? permissions are ok, i think ...

thanks in advance

What version of SQL Server? One common reason is that you have databases in simple recovery mode
included in the plan.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Juan Perez" <juan@juasito.com> wrote in message news:eh1gwQSxHHA.4580@TK2MSFTNGP05.phx.gbl...
>
>
> Hi, i´ve created a manteinance plan to backup all my databases, it
> makes it right. I´ve checked the "delete previous files older than X
> days (translared)" option, but it doesnt work, backups are piling up
> and we have to delete them manually.
> Any idea? permissions are ok, i think ...
>
> thanks in advance

If you are on the initial release of SQL Server 2005, you may benefit from
installing Service Pack 1. From Books Online in the topic What's New in SQL
Server 2005 SP1:
- You can now use cleanup tasks in a maintenance plan to delete backup files
from subdirectories.
There are also some maintenance plan improvements in Service Pack 2.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.co m> wrote in
message news:06AE3892-680B-4D2A-8DB9-012FFFEDD1C8@microsoft.com...
> What version of SQL Server? One common reason is that you have databases
> in simple recovery mode included in the plan.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
>
> "Juan Perez" <juan@juasito.com> wrote in message
> news:eh1gwQSxHHA.4580@TK2MSFTNGP05.phx.gbl...
>>
>>
>> Hi, i´ve created a manteinance plan to backup all my databases, it
>> makes it right. I´ve checked the "delete previous files older than X
>> days (translared)" option, but it doesnt work, backups are piling up
>> and we have to delete them manually.
>> Any idea? permissions are ok, i think ...
>>
>> thanks in advance
>

Tibor Karaszi wrote:

> What version of SQL Server? One common reason is that you have
> databases in simple recovery mode included in the plan.

it is sqlserver 2000

--

What about the other question? Do you have databases in simple recovery mode included in your plaint
plan?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Juan Perez" <juan@juasito.com> wrote in message news:O9d0D05xHHA.3536@TK2MSFTNGP03.phx.gbl...
> Tibor Karaszi wrote:
>
>> What version of SQL Server? One common reason is that you have
>> databases in simple recovery mode included in the plan.
>
> it is sqlserver 2000
>
> --
>

I'm sorry, I just realized that you didn't say that this was lg backups,. I forsome reason assumed
it was.Is this log backups? If so, check my thoughts on simple recovery mode. Also below are some
elaborations on the topic:

Below KB might :
http://support.microsoft.com/default...&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://sqlblog.com/blogs/tibor_karaszi


"Juan Perez" <juan@juasito.com> wrote in message news:O9d0D05xHHA.3536@TK2MSFTNGP03.phx.gbl...
> Tibor Karaszi wrote:
>
>> What version of SQL Server? One common reason is that you have
>> databases in simple recovery mode included in the plan.
>
> it is sqlserver 2000
>
> --
>