Is it possible to restore a database if you have not been
doing db backup but you were doing server backups.Or does
server backups include database backups. And how do you
restore the database. Please help.It depends on what you've been using to do the backups.
Ideally you backup SQL Server databases from within SQL Server, the
resulting backup file can then be put onto tape with your file backup
utility. Does your backup software have SQL Server Agents loaded or has it
been skipping the database files as they are in use..?
--
HTH
Ryan Waight, MCDBA, MCSE
"Naz" <milnaz@.hotmail.com> wrote in message
news:110f01c38cc7$0f82d980$a101280a@.phx.gbl...
> Is it possible to restore a database if you have not been
> doing db backup but you were doing server backups.Or does
> server backups include database backups. And how do you
> restore the database. Please help.|||Naz
If you have copies of your .mdf and .ldf files, you may be
able to use sp_attach_db to attach them. Most server
backups do not pick up these files as they show as being
in use, so you might not have them.
Regards
John|||got it. They were some database backups.
>--Original Message--
>Naz
>If you have copies of your .mdf and .ldf files, you may
be
>able to use sp_attach_db to attach them. Most server
>backups do not pick up these files as they show as being
>in use, so you might not have them.
>Regards
>John
>.
>
Showing posts with label backups. Show all posts
Showing posts with label backups. Show all posts
Monday, March 19, 2012
DB Restore
I often have to restore databases from backups sent to me by clients.
I do a
RESTORE FILELISTONLY FROM DISK='c:\db.bak'
which gives me the data and log file names, say 'data_file' and
'data_file_log'
and then a
RESTORE DATABASE DbName
FROM DISK = 'c:\db.bak'
WITH MOVE 'data_file' TO 'c:\test\db.mdf',
MOVE 'data_file_log' TO 'c:\test\db.ldf'
Does anyone know a way that I can read the names of the data and log files
into variables
in the 'RESTORE FILELISTONLY' command and then substitute them
into the 'RESTORE DATABASE' command ?
TIA
SteveYou should be able to do like below:
CREATE TABLE #FileDetails(...)
INSERT #FileDetails(col1, col2...)
EXEC('RESTORE FILELISTDETAILS...')
Now you can read the stuff off of that table and get the stuff into TSQL
variables. And then use those variables in the RESTORE command. In case SQL
Server doesn't accepts variables in RESTORE for the relevant option, you can
use dynamic SQL to execute the RESTORE command.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Steve W" <lsl@.btconnect.com.no_spam> wrote in message
news:OZXew4N7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> I often have to restore databases from backups sent to me by clients.
> I do a
> RESTORE FILELISTONLY FROM DISK='c:\db.bak'
> which gives me the data and log file names, say 'data_file' and
> 'data_file_log'
> and then a
> RESTORE DATABASE DbName
> FROM DISK = 'c:\db.bak'
> WITH MOVE 'data_file' TO 'c:\test\db.mdf',
> MOVE 'data_file_log' TO 'c:\test\db.ldf'
> Does anyone know a way that I can read the names of the data and log files
> into variables
> in the 'RESTORE FILELISTONLY' command and then substitute them
> into the 'RESTORE DATABASE' command ?
> TIA
> Steve
>
I do a
RESTORE FILELISTONLY FROM DISK='c:\db.bak'
which gives me the data and log file names, say 'data_file' and
'data_file_log'
and then a
RESTORE DATABASE DbName
FROM DISK = 'c:\db.bak'
WITH MOVE 'data_file' TO 'c:\test\db.mdf',
MOVE 'data_file_log' TO 'c:\test\db.ldf'
Does anyone know a way that I can read the names of the data and log files
into variables
in the 'RESTORE FILELISTONLY' command and then substitute them
into the 'RESTORE DATABASE' command ?
TIA
SteveYou should be able to do like below:
CREATE TABLE #FileDetails(...)
INSERT #FileDetails(col1, col2...)
EXEC('RESTORE FILELISTDETAILS...')
Now you can read the stuff off of that table and get the stuff into TSQL
variables. And then use those variables in the RESTORE command. In case SQL
Server doesn't accepts variables in RESTORE for the relevant option, you can
use dynamic SQL to execute the RESTORE command.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Steve W" <lsl@.btconnect.com.no_spam> wrote in message
news:OZXew4N7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> I often have to restore databases from backups sent to me by clients.
> I do a
> RESTORE FILELISTONLY FROM DISK='c:\db.bak'
> which gives me the data and log file names, say 'data_file' and
> 'data_file_log'
> and then a
> RESTORE DATABASE DbName
> FROM DISK = 'c:\db.bak'
> WITH MOVE 'data_file' TO 'c:\test\db.mdf',
> MOVE 'data_file_log' TO 'c:\test\db.ldf'
> Does anyone know a way that I can read the names of the data and log files
> into variables
> in the 'RESTORE FILELISTONLY' command and then substitute them
> into the 'RESTORE DATABASE' command ?
> TIA
> Steve
>
DB Restore
I often have to restore databases from backups sent to me by clients.
I do a
RESTORE FILELISTONLY FROM DISK='c:\db.bak'
which gives me the data and log file names, say 'data_file' and
'data_file_log'
and then a
RESTORE DATABASE DbName
FROM DISK = 'c:\db.bak'
WITH MOVE 'data_file' TO 'c:\test\db.mdf',
MOVE 'data_file_log' TO 'c:\test\db.ldf'
Does anyone know a way that I can read the names of the data and log files
into variables
in the 'RESTORE FILELISTONLY' command and then substitute them
into the 'RESTORE DATABASE' command ?
TIA
SteveYou should be able to do like below:
CREATE TABLE #FileDetails(...)
INSERT #FileDetails(col1, col2...)
EXEC('RESTORE FILELISTDETAILS...')
Now you can read the stuff off of that table and get the stuff into TSQL
variables. And then use those variables in the RESTORE command. In case SQL
Server doesn't accepts variables in RESTORE for the relevant option, you can
use dynamic SQL to execute the RESTORE command.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Steve W" <lsl@.btconnect.com.no_spam> wrote in message
news:OZXew4N7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> I often have to restore databases from backups sent to me by clients.
> I do a
> RESTORE FILELISTONLY FROM DISK='c:\db.bak'
> which gives me the data and log file names, say 'data_file' and
> 'data_file_log'
> and then a
> RESTORE DATABASE DbName
> FROM DISK = 'c:\db.bak'
> WITH MOVE 'data_file' TO 'c:\test\db.mdf',
> MOVE 'data_file_log' TO 'c:\test\db.ldf'
> Does anyone know a way that I can read the names of the data and log files
> into variables
> in the 'RESTORE FILELISTONLY' command and then substitute them
> into the 'RESTORE DATABASE' command ?
> TIA
> Steve
>
I do a
RESTORE FILELISTONLY FROM DISK='c:\db.bak'
which gives me the data and log file names, say 'data_file' and
'data_file_log'
and then a
RESTORE DATABASE DbName
FROM DISK = 'c:\db.bak'
WITH MOVE 'data_file' TO 'c:\test\db.mdf',
MOVE 'data_file_log' TO 'c:\test\db.ldf'
Does anyone know a way that I can read the names of the data and log files
into variables
in the 'RESTORE FILELISTONLY' command and then substitute them
into the 'RESTORE DATABASE' command ?
TIA
SteveYou should be able to do like below:
CREATE TABLE #FileDetails(...)
INSERT #FileDetails(col1, col2...)
EXEC('RESTORE FILELISTDETAILS...')
Now you can read the stuff off of that table and get the stuff into TSQL
variables. And then use those variables in the RESTORE command. In case SQL
Server doesn't accepts variables in RESTORE for the relevant option, you can
use dynamic SQL to execute the RESTORE command.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Steve W" <lsl@.btconnect.com.no_spam> wrote in message
news:OZXew4N7DHA.2404@.TK2MSFTNGP12.phx.gbl...
> I often have to restore databases from backups sent to me by clients.
> I do a
> RESTORE FILELISTONLY FROM DISK='c:\db.bak'
> which gives me the data and log file names, say 'data_file' and
> 'data_file_log'
> and then a
> RESTORE DATABASE DbName
> FROM DISK = 'c:\db.bak'
> WITH MOVE 'data_file' TO 'c:\test\db.mdf',
> MOVE 'data_file_log' TO 'c:\test\db.ldf'
> Does anyone know a way that I can read the names of the data and log files
> into variables
> in the 'RESTORE FILELISTONLY' command and then substitute them
> into the 'RESTORE DATABASE' command ?
> TIA
> Steve
>
Saturday, February 25, 2012
DB Maintenenace Plan, Optimizations
Hi All,
I have a database that has not recieved any type of maintenance apart from
daily backups. It has grown to over 30GB. I created some jobs to reindex
tables that I thought were high activity. Query performance increased
substantially but I believe it could be better. Database has also shruck
about 4GB.
After running a showcontig on the table, I could still see lots of
fragmentation on tables that were not included in the job above. So I
created a DB Maintenance Plan to for only optimizations and chose to
reorganize data and index pages, and keep original fillfactor that the index
was created with.
The job ran last night but did not finish because it failed on an unknown
step after 27 mins. I ran this job manually and it ran for 50 mins. before
I
manually stopped the job. The actual database space decreased another 7GB.
The transaction log backup could not be performed becuase there was not
enough disk space, the trans log was 23GB.
My questions are:
How can I enure this optimization job will successfully run in the future?
Is there a way to make the trans log smaller after the optimization job is
run?
Should I be doing a Full DB Backup AFTER the optimization job?
Can I shrink the allocated size of the database by adding to the
optimization job to "remove unused space from database files" safely? I wan
t
to ensure the database will still grow automatically if space is required.
Cheers!First off you should undo the shrink part of the maintenance plan. When you
reindex the tables you need lots of free space in the data and log files in
order for it to do it's job properly. If there isn't it has to grow the
files which is resource intensive. That process will leave free space which
the shrink part of the maintenance plan will not like and then it will
shrink the files. The shrinking process will fragment your tables and
indexes all over again. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
You should leave the size at what ever it needs to be to do what it has to
do. The exception would be the log file. If it just keeps growing you
probably aren't backing up the log files on a regular basis. Full backups
are not enough if you are in the full recovery mode.
Andrew J. Kelly SQL MVP
"AKing" <AKing@.discussions.microsoft.com> wrote in message
news:F9CBB7CC-A53C-498A-A678-E974558EF4C9@.microsoft.com...
> Hi All,
> I have a database that has not recieved any type of maintenance apart from
> daily backups. It has grown to over 30GB. I created some jobs to reindex
> tables that I thought were high activity. Query performance increased
> substantially but I believe it could be better. Database has also shruck
> about 4GB.
> After running a showcontig on the table, I could still see lots of
> fragmentation on tables that were not included in the job above. So I
> created a DB Maintenance Plan to for only optimizations and chose to
> reorganize data and index pages, and keep original fillfactor that the
> index
> was created with.
> The job ran last night but did not finish because it failed on an unknown
> step after 27 mins. I ran this job manually and it ran for 50 mins.
> before I
> manually stopped the job. The actual database space decreased another
> 7GB.
> The transaction log backup could not be performed becuase there was not
> enough disk space, the trans log was 23GB.
> My questions are:
> How can I enure this optimization job will successfully run in the future?
> Is there a way to make the trans log smaller after the optimization job
> is
> run?
> Should I be doing a Full DB Backup AFTER the optimization job?
> Can I shrink the allocated size of the database by adding to the
> optimization job to "remove unused space from database files" safely? I
> want
> to ensure the database will still grow automatically if space is required.
> Cheers!|||Thank you for your reply. You have provided some helpful insight.
I tried to run the optimization job (w/out shrinking db) and I got the same
behaviour. I had to cancel the job after it had been running for 50 minutes
.
Once again the translog was 21GB.
I understand that the reindex job can be intensive, this wil only multiply
if the translog grows from its usual size (~1gb) to 21GB.
Is there a way to run this job w/out the side effect above?
Will the translogs always be this big when running the optimization?
Maybe the only way is to have nightly reindex of portions of the database
until it has reindexed the entire database.
Cheers
"Andrew J. Kelly" wrote:
> First off you should undo the shrink part of the maintenance plan. When y
ou
> reindex the tables you need lots of free space in the data and log files i
n
> order for it to do it's job properly. If there isn't it has to grow the
> files which is resource intensive. That process will leave free space whi
ch
> the shrink part of the maintenance plan will not like and then it will
> shrink the files. The shrinking process will fragment your tables and
> indexes all over again. See here:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> You should leave the size at what ever it needs to be to do what it has to
> do. The exception would be the log file. If it just keeps growing you
> probably aren't backing up the log files on a regular basis. Full backups
> are not enough if you are in the full recovery mode.
> --
> Andrew J. Kelly SQL MVP
>
> "AKing" <AKing@.discussions.microsoft.com> wrote in message
> news:F9CBB7CC-A53C-498A-A678-E974558EF4C9@.microsoft.com...
>
>|||How large are the tables in the db? You might want to skip the actual
maintenance plan and just create a job with DBCC DBREINDEX instead to just
rebuild the ones that are fragmented above a certain level. Or just do a
portion of them each night. There is a script under DBCC SHOWCONTIG in
BooksOnLine to allow you to choose which tables will be reindexed or even
defragged.
Andrew J. Kelly SQL MVP
"AKing" <AKing@.discussions.microsoft.com> wrote in message
news:F06D716A-0ECA-4EDE-8EBD-547715C543CC@.microsoft.com...
> Thank you for your reply. You have provided some helpful insight.
> I tried to run the optimization job (w/out shrinking db) and I got the
> same
> behaviour. I had to cancel the job after it had been running for 50
> minutes.
> Once again the translog was 21GB.
> I understand that the reindex job can be intensive, this wil only multiply
> if the translog grows from its usual size (~1gb) to 21GB.
> Is there a way to run this job w/out the side effect above?
> Will the translogs always be this big when running the optimization?
> Maybe the only way is to have nightly reindex of portions of the database
> until it has reindexed the entire database.
> Cheers
>
> "Andrew J. Kelly" wrote:
>|||Hi Andrew,
The database allocation is ~36GB and at one time only had 50MB of free
space. Although through reindexing some high activity tables I have managed
to reduce the actual size of the database to ~25GB. I plan to shrink some o
f
the free space as I believe it is space wasted.
"Andrew J. Kelly" wrote:
> How large are the tables in the db? You might want to skip the actual
> maintenance plan and just create a job with DBCC DBREINDEX instead to just
> rebuild the ones that are fragmented above a certain level. Or just do a
> portion of them each night. There is a script under DBCC SHOWCONTIG in
> BooksOnLine to allow you to choose which tables will be reindexed or even
> defragged.
> --
> Andrew J. Kelly SQL MVP
>
> "AKing" <AKing@.discussions.microsoft.com> wrote in message
> news:F06D716A-0ECA-4EDE-8EBD-547715C543CC@.microsoft.com...
>
>
I have a database that has not recieved any type of maintenance apart from
daily backups. It has grown to over 30GB. I created some jobs to reindex
tables that I thought were high activity. Query performance increased
substantially but I believe it could be better. Database has also shruck
about 4GB.
After running a showcontig on the table, I could still see lots of
fragmentation on tables that were not included in the job above. So I
created a DB Maintenance Plan to for only optimizations and chose to
reorganize data and index pages, and keep original fillfactor that the index
was created with.
The job ran last night but did not finish because it failed on an unknown
step after 27 mins. I ran this job manually and it ran for 50 mins. before
I
manually stopped the job. The actual database space decreased another 7GB.
The transaction log backup could not be performed becuase there was not
enough disk space, the trans log was 23GB.
My questions are:
How can I enure this optimization job will successfully run in the future?
Is there a way to make the trans log smaller after the optimization job is
run?
Should I be doing a Full DB Backup AFTER the optimization job?
Can I shrink the allocated size of the database by adding to the
optimization job to "remove unused space from database files" safely? I wan
t
to ensure the database will still grow automatically if space is required.
Cheers!First off you should undo the shrink part of the maintenance plan. When you
reindex the tables you need lots of free space in the data and log files in
order for it to do it's job properly. If there isn't it has to grow the
files which is resource intensive. That process will leave free space which
the shrink part of the maintenance plan will not like and then it will
shrink the files. The shrinking process will fragment your tables and
indexes all over again. See here:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
You should leave the size at what ever it needs to be to do what it has to
do. The exception would be the log file. If it just keeps growing you
probably aren't backing up the log files on a regular basis. Full backups
are not enough if you are in the full recovery mode.
Andrew J. Kelly SQL MVP
"AKing" <AKing@.discussions.microsoft.com> wrote in message
news:F9CBB7CC-A53C-498A-A678-E974558EF4C9@.microsoft.com...
> Hi All,
> I have a database that has not recieved any type of maintenance apart from
> daily backups. It has grown to over 30GB. I created some jobs to reindex
> tables that I thought were high activity. Query performance increased
> substantially but I believe it could be better. Database has also shruck
> about 4GB.
> After running a showcontig on the table, I could still see lots of
> fragmentation on tables that were not included in the job above. So I
> created a DB Maintenance Plan to for only optimizations and chose to
> reorganize data and index pages, and keep original fillfactor that the
> index
> was created with.
> The job ran last night but did not finish because it failed on an unknown
> step after 27 mins. I ran this job manually and it ran for 50 mins.
> before I
> manually stopped the job. The actual database space decreased another
> 7GB.
> The transaction log backup could not be performed becuase there was not
> enough disk space, the trans log was 23GB.
> My questions are:
> How can I enure this optimization job will successfully run in the future?
> Is there a way to make the trans log smaller after the optimization job
> is
> run?
> Should I be doing a Full DB Backup AFTER the optimization job?
> Can I shrink the allocated size of the database by adding to the
> optimization job to "remove unused space from database files" safely? I
> want
> to ensure the database will still grow automatically if space is required.
> Cheers!|||Thank you for your reply. You have provided some helpful insight.
I tried to run the optimization job (w/out shrinking db) and I got the same
behaviour. I had to cancel the job after it had been running for 50 minutes
.
Once again the translog was 21GB.
I understand that the reindex job can be intensive, this wil only multiply
if the translog grows from its usual size (~1gb) to 21GB.
Is there a way to run this job w/out the side effect above?
Will the translogs always be this big when running the optimization?
Maybe the only way is to have nightly reindex of portions of the database
until it has reindexed the entire database.
Cheers
"Andrew J. Kelly" wrote:
> First off you should undo the shrink part of the maintenance plan. When y
ou
> reindex the tables you need lots of free space in the data and log files i
n
> order for it to do it's job properly. If there isn't it has to grow the
> files which is resource intensive. That process will leave free space whi
ch
> the shrink part of the maintenance plan will not like and then it will
> shrink the files. The shrinking process will fragment your tables and
> indexes all over again. See here:
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> You should leave the size at what ever it needs to be to do what it has to
> do. The exception would be the log file. If it just keeps growing you
> probably aren't backing up the log files on a regular basis. Full backups
> are not enough if you are in the full recovery mode.
> --
> Andrew J. Kelly SQL MVP
>
> "AKing" <AKing@.discussions.microsoft.com> wrote in message
> news:F9CBB7CC-A53C-498A-A678-E974558EF4C9@.microsoft.com...
>
>|||How large are the tables in the db? You might want to skip the actual
maintenance plan and just create a job with DBCC DBREINDEX instead to just
rebuild the ones that are fragmented above a certain level. Or just do a
portion of them each night. There is a script under DBCC SHOWCONTIG in
BooksOnLine to allow you to choose which tables will be reindexed or even
defragged.
Andrew J. Kelly SQL MVP
"AKing" <AKing@.discussions.microsoft.com> wrote in message
news:F06D716A-0ECA-4EDE-8EBD-547715C543CC@.microsoft.com...
> Thank you for your reply. You have provided some helpful insight.
> I tried to run the optimization job (w/out shrinking db) and I got the
> same
> behaviour. I had to cancel the job after it had been running for 50
> minutes.
> Once again the translog was 21GB.
> I understand that the reindex job can be intensive, this wil only multiply
> if the translog grows from its usual size (~1gb) to 21GB.
> Is there a way to run this job w/out the side effect above?
> Will the translogs always be this big when running the optimization?
> Maybe the only way is to have nightly reindex of portions of the database
> until it has reindexed the entire database.
> Cheers
>
> "Andrew J. Kelly" wrote:
>|||Hi Andrew,
The database allocation is ~36GB and at one time only had 50MB of free
space. Although through reindexing some high activity tables I have managed
to reduce the actual size of the database to ~25GB. I plan to shrink some o
f
the free space as I believe it is space wasted.
"Andrew J. Kelly" wrote:
> How large are the tables in the db? You might want to skip the actual
> maintenance plan and just create a job with DBCC DBREINDEX instead to just
> rebuild the ones that are fragmented above a certain level. Or just do a
> portion of them each night. There is a script under DBCC SHOWCONTIG in
> BooksOnLine to allow you to choose which tables will be reindexed or even
> defragged.
> --
> Andrew J. Kelly SQL MVP
>
> "AKing" <AKing@.discussions.microsoft.com> wrote in message
> news:F06D716A-0ECA-4EDE-8EBD-547715C543CC@.microsoft.com...
>
>
Friday, February 24, 2012
DB maintenance plan backups not removing old files
Hi,
Ok, need a little help here. Here's what I've done: have created a DB
maintenance plan for all my non-system DBs to backup the db's and transaction
logs.
- On the 'General' tab of maintenance plan I selected 'All user
databases'.
- On the 'Complete Backup' tab I selected (among other things):
'Use this directory: R:\SQLBackup'
'create a sub-directory for each database' and
'Remove files older than: 2 days'
However, while this creates individual folders under R:\SQLBackup for each
DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
these directories are not getting deleted.
When I create an individual DB backup plan (on 'General' tab select
individual DB)and point the backup directory path to the name of the DB
folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
get removed.
Should the 'All user databases' method I've setup be removing old files? I
don't see why not. Thanks.Hi
With your maintenance plan, the backup could possibly be removed on day 3
depending on timings. When do they get removed?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and
> transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> files
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
> I
> don't see why not. Thanks.
>|||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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
> get removed.
> Should the 'All user databases' method I've setup be removing old files? I
> don't see why not. Thanks.
>|||That's the problem - they're not getting removed at all with this plan.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> With your maintenance plan, the backup could possibly be removed on day 3
> depending on timings. When do they get removed?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> > Hi,
> > Ok, need a little help here. Here's what I've done: have created a DB
> > maintenance plan for all my non-system DBs to backup the db's and
> > transaction
> > logs.
> > - On the 'General' tab of maintenance plan I selected 'All user
> > databases'.
> > - On the 'Complete Backup' tab I selected (among other things):
> > 'Use this directory: R:\SQLBackup'
> > 'create a sub-directory for each database' and
> > 'Remove files older than: 2 days'
> >
> > However, while this creates individual folders under R:\SQLBackup for each
> > DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> > under
> > these directories are not getting deleted.
> >
> > When I create an individual DB backup plan (on 'General' tab select
> > individual DB)and point the backup directory path to the name of the DB
> > folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> > files
> > get removed.
> >
> > Should the 'All user databases' method I've setup be removing old files?
> > I
> > don't see why not. Thanks.
> >
>
>|||Thanks for the KB article. Don't think that's the problem as I'm not getting
any errors in the backup logs and none of my DBs have a recovery model of
simple.
Looked at the troubleshooting tips and the permission that the
SQLServerAgent account can delete files from the backup directory.
Not a matter of file locking as no backup or AV software runs against these
files..
"Tibor Karaszi" wrote:
> Below KB might help:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
>
Ok, need a little help here. Here's what I've done: have created a DB
maintenance plan for all my non-system DBs to backup the db's and transaction
logs.
- On the 'General' tab of maintenance plan I selected 'All user
databases'.
- On the 'Complete Backup' tab I selected (among other things):
'Use this directory: R:\SQLBackup'
'create a sub-directory for each database' and
'Remove files older than: 2 days'
However, while this creates individual folders under R:\SQLBackup for each
DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
these directories are not getting deleted.
When I create an individual DB backup plan (on 'General' tab select
individual DB)and point the backup directory path to the name of the DB
folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
get removed.
Should the 'All user databases' method I've setup be removing old files? I
don't see why not. Thanks.Hi
With your maintenance plan, the backup could possibly be removed on day 3
depending on timings. When do they get removed?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and
> transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> files
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
> I
> don't see why not. Thanks.
>|||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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
> get removed.
> Should the 'All user databases' method I've setup be removing old files? I
> don't see why not. Thanks.
>|||That's the problem - they're not getting removed at all with this plan.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> With your maintenance plan, the backup could possibly be removed on day 3
> depending on timings. When do they get removed?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> > Hi,
> > Ok, need a little help here. Here's what I've done: have created a DB
> > maintenance plan for all my non-system DBs to backup the db's and
> > transaction
> > logs.
> > - On the 'General' tab of maintenance plan I selected 'All user
> > databases'.
> > - On the 'Complete Backup' tab I selected (among other things):
> > 'Use this directory: R:\SQLBackup'
> > 'create a sub-directory for each database' and
> > 'Remove files older than: 2 days'
> >
> > However, while this creates individual folders under R:\SQLBackup for each
> > DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> > under
> > these directories are not getting deleted.
> >
> > When I create an individual DB backup plan (on 'General' tab select
> > individual DB)and point the backup directory path to the name of the DB
> > folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> > files
> > get removed.
> >
> > Should the 'All user databases' method I've setup be removing old files?
> > I
> > don't see why not. Thanks.
> >
>
>|||Thanks for the KB article. Don't think that's the problem as I'm not getting
any errors in the backup logs and none of my DBs have a recovery model of
simple.
Looked at the troubleshooting tips and the permission that the
SQLServerAgent account can delete files from the backup directory.
Not a matter of file locking as no backup or AV software runs against these
files..
"Tibor Karaszi" wrote:
> Below KB might help:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k
>
DB maintenance plan backups not removing old files
Hi,
Ok, need a little help here. Here's what I've done: have created a DB
maintenance plan for all my non-system DBs to backup the db's and transaction
logs.
- On the 'General' tab of maintenance plan I selected 'All user
databases'.
- On the 'Complete Backup' tab I selected (among other things):
'Use this directory: R:\SQLBackup'
'create a sub-directory for each database' and
'Remove files older than: 2 days'
However, while this creates individual folders under R:\SQLBackup for each
DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
these directories are not getting deleted.
When I create an individual DB backup plan (on 'General' tab select
individual DB)and point the backup directory path to the name of the DB
folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
get removed.
Should the 'All user databases' method I've setup be removing old files? I
don't see why not. Thanks.
Hi
With your maintenance plan, the backup could possibly be removed on day 3
depending on timings. When do they get removed?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and
> transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> files
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
> I
> don't see why not. Thanks.
>
|||Below KB might help:
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://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
> get removed.
> Should the 'All user databases' method I've setup be removing old files? I
> don't see why not. Thanks.
>
|||That's the problem - they're not getting removed at all with this plan.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> With your maintenance plan, the backup could possibly be removed on day 3
> depending on timings. When do they get removed?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
>
>
|||Thanks for the KB article. Don't think that's the problem as I'm not getting
any errors in the backup logs and none of my DBs have a recovery model of
simple.
Looked at the troubleshooting tips and the permission that the
SQLServerAgent account can delete files from the backup directory.
Not a matter of file locking as no backup or AV software runs against these
files..
"Tibor Karaszi" wrote:
> Below KB might help:
> http://support.microsoft.com/default...&Product=sql2k
>
Ok, need a little help here. Here's what I've done: have created a DB
maintenance plan for all my non-system DBs to backup the db's and transaction
logs.
- On the 'General' tab of maintenance plan I selected 'All user
databases'.
- On the 'Complete Backup' tab I selected (among other things):
'Use this directory: R:\SQLBackup'
'create a sub-directory for each database' and
'Remove files older than: 2 days'
However, while this creates individual folders under R:\SQLBackup for each
DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
these directories are not getting deleted.
When I create an individual DB backup plan (on 'General' tab select
individual DB)and point the backup directory path to the name of the DB
folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
get removed.
Should the 'All user databases' method I've setup be removing old files? I
don't see why not. Thanks.
Hi
With your maintenance plan, the backup could possibly be removed on day 3
depending on timings. When do they get removed?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and
> transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> files
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
> I
> don't see why not. Thanks.
>
|||Below KB might help:
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://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older files
> get removed.
> Should the 'All user databases' method I've setup be removing old files? I
> don't see why not. Thanks.
>
|||That's the problem - they're not getting removed at all with this plan.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> With your maintenance plan, the backup could possibly be removed on day 3
> depending on timings. When do they get removed?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
>
>
|||Thanks for the KB article. Don't think that's the problem as I'm not getting
any errors in the backup logs and none of my DBs have a recovery model of
simple.
Looked at the troubleshooting tips and the permission that the
SQLServerAgent account can delete files from the backup directory.
Not a matter of file locking as no backup or AV software runs against these
files..
"Tibor Karaszi" wrote:
> Below KB might help:
> http://support.microsoft.com/default...&Product=sql2k
>
DB maintenance plan backups not removing old files
Hi,
Ok, need a little help here. Here's what I've done: have created a DB
maintenance plan for all my non-system DBs to backup the db's and transactio
n
logs.
- On the 'General' tab of maintenance plan I selected 'All user
databases'.
- On the 'Complete Backup' tab I selected (among other things):
'Use this directory: R:\SQLBackup'
'create a sub-directory for each database' and
'Remove files older than: 2 days'
However, while this creates individual folders under R:\SQLBackup for each
DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days unde
r
these directories are not getting deleted.
When I create an individual DB backup plan (on 'General' tab select
individual DB)and point the backup directory path to the name of the DB
folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older file
s
get removed.
Should the 'All user databases' method I've setup be removing old files? I
don't see why not. Thanks.Hi
With your maintenance plan, the backup could possibly be removed on day 3
depending on timings. When do they get removed?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and
> transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> files
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
> I
> don't see why not. Thanks.
>|||Below KB might help:
http://support.microsoft.com/defaul...2&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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and transact
ion
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days un
der
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older fi
les
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
I
> don't see why not. Thanks.
>|||That's the problem - they're not getting removed at all with this plan.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> With your maintenance plan, the backup could possibly be removed on day 3
> depending on timings. When do they get removed?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
>
>|||Thanks for the KB article. Don't think that's the problem as I'm not gettin
g
any errors in the backup logs and none of my DBs have a recovery model of
simple.
Looked at the troubleshooting tips and the permission that the
SQLServerAgent account can delete files from the backup directory.
Not a matter of file locking as no backup or AV software runs against these
files..
"Tibor Karaszi" wrote:
> Below KB might help:
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k[/ur
l]
>
Ok, need a little help here. Here's what I've done: have created a DB
maintenance plan for all my non-system DBs to backup the db's and transactio
n
logs.
- On the 'General' tab of maintenance plan I selected 'All user
databases'.
- On the 'Complete Backup' tab I selected (among other things):
'Use this directory: R:\SQLBackup'
'create a sub-directory for each database' and
'Remove files older than: 2 days'
However, while this creates individual folders under R:\SQLBackup for each
DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days unde
r
these directories are not getting deleted.
When I create an individual DB backup plan (on 'General' tab select
individual DB)and point the backup directory path to the name of the DB
folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older file
s
get removed.
Should the 'All user databases' method I've setup be removing old files? I
don't see why not. Thanks.Hi
With your maintenance plan, the backup could possibly be removed on day 3
depending on timings. When do they get removed?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and
> transaction
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days
> under
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older
> files
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
> I
> don't see why not. Thanks.
>|||Below KB might help:
http://support.microsoft.com/defaul...2&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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mb" <mb@.discussions.microsoft.com> wrote in message
news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
> Hi,
> Ok, need a little help here. Here's what I've done: have created a DB
> maintenance plan for all my non-system DBs to backup the db's and transact
ion
> logs.
> - On the 'General' tab of maintenance plan I selected 'All user
> databases'.
> - On the 'Complete Backup' tab I selected (among other things):
> 'Use this directory: R:\SQLBackup'
> 'create a sub-directory for each database' and
> 'Remove files older than: 2 days'
> However, while this creates individual folders under R:\SQLBackup for each
> DB (ie R:\SQLBackup\db1, R:SQLBackup\db2, etc), files older than 2 days un
der
> these directories are not getting deleted.
> When I create an individual DB backup plan (on 'General' tab select
> individual DB)and point the backup directory path to the name of the DB
> folder (ie R:\SQLBackup\db1) instead of the R:\SQLBackup root the older fi
les
> get removed.
> Should the 'All user databases' method I've setup be removing old files?
I
> don't see why not. Thanks.
>|||That's the problem - they're not getting removed at all with this plan.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> With your maintenance plan, the backup could possibly be removed on day 3
> depending on timings. When do they get removed?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mb" <mb@.discussions.microsoft.com> wrote in message
> news:7722448E-E02B-47A5-87E9-927E0ED28854@.microsoft.com...
>
>|||Thanks for the KB article. Don't think that's the problem as I'm not gettin
g
any errors in the backup logs and none of my DBs have a recovery model of
simple.
Looked at the troubleshooting tips and the permission that the
SQLServerAgent account can delete files from the backup directory.
Not a matter of file locking as no backup or AV software runs against these
files..
"Tibor Karaszi" wrote:
> Below KB might help:
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;303292&Product=sql2k[/ur
l]
>
db maintanence plan question
On my databases I have a backup maintanence plan on all of them. The plan
also includes a clean of backups that are 4 days old. My backup is working
but the clean up portion is not. I'm backing up the .bak files to a file
server on the network, could that cause the clean up process not to work? If
so, what do I need to do to get the clean up step to remove all the .bak
files that are 4 days old from the file server? Is it even possible to do?
Does the account that is running the SQL Agent service have permissions to
delete files from that network resource?
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
> On my databases I have a backup maintanence plan on all of them. The plan
> also includes a clean of backups that are 4 days old. My backup is working
> but the clean up portion is not. I'm backing up the .bak files to a file
> server on the network, could that cause the clean up process not to work?
> If so, what do I need to do to get the clean up step to remove all the
> .bak files that are 4 days old from the file server? Is it even possible
> to do?
>
>
|||yes, all of databases are configured the same and this did work at one time.
We had the change the location to point to a new folder on the same server
and that folder has the same permissions as the folder did that this worked.
That's the only change and my SQL 2000 db's have no issues in doing this,
its only my SQL 05 servers.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Does the account that is running the SQL Agent service have permissions to
> delete files from that network resource?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>
|||Any errors in the Maintenance Plan logs?
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
> yes, all of databases are configured the same and this did work at one
> time. We had the change the location to point to a new folder on the same
> server and that folder has the same permissions as the folder did that
> this worked.
> That's the only change and my SQL 2000 db's have no issues in doing this,
> its only my SQL 05 servers.
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>
|||No, no errors in the log.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:etPNVb8cIHA.536@.TK2MSFTNGP06.phx.gbl...
> Any errors in the Maintenance Plan logs?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>
|||the backup plan is pointing to the new location. Where do I define the
location for the cleanup?
I just took this task over so I'm figuring out SQL 05 as I go. Everything
was already setup, I just had to point the backup plan to the new location.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
> Did you modify the maintenance cleanup task to reflect the folder?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>
|||I have that and it points to SQL servers and when I try to add the location
for the BAK files it fails to connect.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
> Edit the plan. You should see a task named "Maintenance Cleanup task".
> this is where you specify the location. If you don't have such a task, add
> it. You do *not* specify backup file removal inside the backup task in
> 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>
|||I've done that, 4 times actually and I'm getting the same message when
trying to connect to the new location.
'unable to find sever DbbackUp'
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
> Seems it got messed up somehow. I'd remove the task and add a new one.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>
|||So far I removed the current plans, created a new db backup plan which
points to the location, then I created a seperate cleanup plan and when I
type in the UNC path, I get the error 'unable to find \\nas123\sqlbackups\'
and this is only happening on my SQL 2005 Servers not my SQL 2000 servers.
The SQL 2000 servers are backing up and deleting bak files that are older
then 5 days, the SQL 05 servers - nothing.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OmQ3yDIdIHA.4196@.TK2MSFTNGP04.phx.gbl...
> Where is the failure? The connection (top of that dialog) or the location
> for the folder? If the folder, then I suggest you use an UNC path and type
> the path (not browse).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
>
also includes a clean of backups that are 4 days old. My backup is working
but the clean up portion is not. I'm backing up the .bak files to a file
server on the network, could that cause the clean up process not to work? If
so, what do I need to do to get the clean up step to remove all the .bak
files that are 4 days old from the file server? Is it even possible to do?
Does the account that is running the SQL Agent service have permissions to
delete files from that network resource?
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
> On my databases I have a backup maintanence plan on all of them. The plan
> also includes a clean of backups that are 4 days old. My backup is working
> but the clean up portion is not. I'm backing up the .bak files to a file
> server on the network, could that cause the clean up process not to work?
> If so, what do I need to do to get the clean up step to remove all the
> .bak files that are 4 days old from the file server? Is it even possible
> to do?
>
>
|||yes, all of databases are configured the same and this did work at one time.
We had the change the location to point to a new folder on the same server
and that folder has the same permissions as the folder did that this worked.
That's the only change and my SQL 2000 db's have no issues in doing this,
its only my SQL 05 servers.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Does the account that is running the SQL Agent service have permissions to
> delete files from that network resource?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>
|||Any errors in the Maintenance Plan logs?
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
> yes, all of databases are configured the same and this did work at one
> time. We had the change the location to point to a new folder on the same
> server and that folder has the same permissions as the folder did that
> this worked.
> That's the only change and my SQL 2000 db's have no issues in doing this,
> its only my SQL 05 servers.
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>
|||No, no errors in the log.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:etPNVb8cIHA.536@.TK2MSFTNGP06.phx.gbl...
> Any errors in the Maintenance Plan logs?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>
|||the backup plan is pointing to the new location. Where do I define the
location for the cleanup?
I just took this task over so I'm figuring out SQL 05 as I go. Everything
was already setup, I just had to point the backup plan to the new location.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
> Did you modify the maintenance cleanup task to reflect the folder?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>
|||I have that and it points to SQL servers and when I try to add the location
for the BAK files it fails to connect.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
> Edit the plan. You should see a task named "Maintenance Cleanup task".
> this is where you specify the location. If you don't have such a task, add
> it. You do *not* specify backup file removal inside the backup task in
> 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>
|||I've done that, 4 times actually and I'm getting the same message when
trying to connect to the new location.
'unable to find sever DbbackUp'
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
> Seems it got messed up somehow. I'd remove the task and add a new one.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>
|||So far I removed the current plans, created a new db backup plan which
points to the location, then I created a seperate cleanup plan and when I
type in the UNC path, I get the error 'unable to find \\nas123\sqlbackups\'
and this is only happening on my SQL 2005 Servers not my SQL 2000 servers.
The SQL 2000 servers are backing up and deleting bak files that are older
then 5 days, the SQL 05 servers - nothing.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OmQ3yDIdIHA.4196@.TK2MSFTNGP04.phx.gbl...
> Where is the failure? The connection (top of that dialog) or the location
> for the folder? If the folder, then I suggest you use an UNC path and type
> the path (not browse).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
>
db maintanence plan question
On my databases I have a backup maintanence plan on all of them. The plan
also includes a clean of backups that are 4 days old. My backup is working
but the clean up portion is not. I'm backing up the .bak files to a file
server on the network, could that cause the clean up process not to work? If
so, what do I need to do to get the clean up step to remove all the .bak
files that are 4 days old from the file server? Is it even possible to do?Does the account that is running the SQL Agent service have permissions to
delete files from that network resource?
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
> On my databases I have a backup maintanence plan on all of them. The plan
> also includes a clean of backups that are 4 days old. My backup is working
> but the clean up portion is not. I'm backing up the .bak files to a file
> server on the network, could that cause the clean up process not to work?
> If so, what do I need to do to get the clean up step to remove all the
> .bak files that are 4 days old from the file server? Is it even possible
> to do?
>
>|||yes, all of databases are configured the same and this did work at one time.
We had the change the location to point to a new folder on the same server
and that folder has the same permissions as the folder did that this worked.
That's the only change and my SQL 2000 db's have no issues in doing this,
its only my SQL 05 servers.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Does the account that is running the SQL Agent service have permissions to
> delete files from that network resource?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The plan
>> also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files to
>> a file server on the network, could that cause the clean up process not
>> to work? If so, what do I need to do to get the clean up step to remove
>> all the .bak files that are 4 days old from the file server? Is it even
>> possible to do?
>>
>|||Any errors in the Maintenance Plan logs?
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
> yes, all of databases are configured the same and this did work at one
> time. We had the change the location to point to a new folder on the same
> server and that folder has the same permissions as the folder did that
> this worked.
> That's the only change and my SQL 2000 db's have no issues in doing this,
> its only my SQL 05 servers.
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions
>> to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files
>> to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to
>> remove all the .bak files that are 4 days old from the file server? Is
>> it even possible to do?
>>
>>
>|||No, no errors in the log.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:etPNVb8cIHA.536@.TK2MSFTNGP06.phx.gbl...
> Any errors in the Maintenance Plan logs?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one
>> time. We had the change the location to point to a new folder on the same
>> server and that folder has the same permissions as the folder did that
>> this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this,
>> its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions
>> to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files
>> to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to
>> remove all the .bak files that are 4 days old from the file server? Is
>> it even possible to do?
>>
>>
>>
>|||Did you modify the maintenance cleanup task to reflect the folder?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
> yes, all of databases are configured the same and this did work at one time. We had the change the
> location to point to a new folder on the same server and that folder has the same permissions as
> the folder did that this worked.
> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
> servers.
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions to delete files from that
>> network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The plan also includes a clean
>> of backups that are 4 days old. My backup is working but the clean up portion is not. I'm
>> backing up the .bak files to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to remove all the .bak files
>> that are 4 days old from the file server? Is it even possible to do?
>>
>>
>|||the backup plan is pointing to the new location. Where do I define the
location for the cleanup?
I just took this task over so I'm figuring out SQL 05 as I go. Everything
was already setup, I just had to point the backup plan to the new location.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
> Did you modify the maintenance cleanup task to reflect the folder?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one
>> time. We had the change the location to point to a new folder on the same
>> server and that folder has the same permissions as the folder did that
>> this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this,
>> its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions
>> to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files
>> to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to
>> remove all the .bak files that are 4 days old from the file server? Is
>> it even possible to do?
>>
>>
>>
>|||Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you specify the
location. If you don't have such a task, add it. You do *not* specify backup file removal inside the
backup task in 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
> the backup plan is pointing to the new location. Where do I define the location for the cleanup?
> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup, I
> just had to point the backup plan to the new location.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one time. We had the change
>> the location to point to a new folder on the same server and that folder has the same
>> permissions as the folder did that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
>> servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions to delete files from
>> that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The plan also includes a
>> clean of backups that are 4 days old. My backup is working but the clean up portion is not.
>> I'm backing up the .bak files to a file server on the network, could that cause the clean up
>> process not to work? If so, what do I need to do to get the clean up step to remove all the
>> .bak files that are 4 days old from the file server? Is it even possible to do?
>>
>>
>>
>>
>|||I have that and it points to SQL servers and when I try to add the location
for the BAK files it fails to connect.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
> Edit the plan. You should see a task named "Maintenance Cleanup task".
> this is where you specify the location. If you don't have such a task, add
> it. You do *not* specify backup file removal inside the backup task in
> 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the
>> location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go. Everything
>> was already setup, I just had to point the backup plan to the new
>> location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one
>> time. We had the change the location to point to a new folder on the
>> same server and that folder has the same permissions as the folder did
>> that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing
>> this, its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have
>> permissions to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup
>> is working but the clean up portion is not. I'm backing up the .bak
>> files to a file server on the network, could that cause the clean up
>> process not to work? If so, what do I need to do to get the clean up
>> step to remove all the .bak files that are 4 days old from the file
>> server? Is it even possible to do?
>>
>>
>>
>>
>>
>|||Seems it got messed up somehow. I'd remove the task and add a new one.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>I have that and it points to SQL servers and when I try to add the location for the BAK files it
>fails to connect.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you specify
>> the location. If you don't have such a task, add it. You do *not* specify backup file removal
>> inside the backup task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup, I
>> just had to point the backup plan to the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one time. We had the change
>> the location to point to a new folder on the same server and that folder has the same
>> permissions as the folder did that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
>> servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions to delete files from
>> that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>> On my databases I have a backup maintanence plan on all of them. The plan also includes a
>>> clean of backups that are 4 days old. My backup is working but the clean up portion is not.
>>> I'm backing up the .bak files to a file server on the network, could that cause the clean up
>>> process not to work? If so, what do I need to do to get the clean up step to remove all the
>>> .bak files that are 4 days old from the file server? Is it even possible to do?
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||I've done that, 4 times actually and I'm getting the same message when
trying to connect to the new location.
'unable to find sever DbbackUp'
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
> Seems it got messed up somehow. I'd remove the task and add a new one.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the
>>location for the BAK files it fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task".
>> this is where you specify the location. If you don't have such a task,
>> add it. You do *not* specify backup file removal inside the backup task
>> in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the
>> location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go.
>> Everything was already setup, I just had to point the backup plan to
>> the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at
>> one time. We had the change the location to point to a new folder on
>> the same server and that folder has the same permissions as the
>> folder did that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing
>> this, its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>> Does the account that is running the SQL Agent service have
>>> permissions to delete files from that network resource?
>>>
>>> --
>>>
>>> Kevin3NF
>>> SQL Server dude
>>>
>>> You want fries with that?
>>> http://kevin3nf.blogspot.com/
>>>
>>> I only check the newsgroups during work hours, M-F.
>>> Hit my blog and the contact links if necessary...I may be available.
>>>
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>> On my databases I have a backup maintanence plan on all of them.
>>> The plan also includes a clean of backups that are 4 days old. My
>>> backup is working but the clean up portion is not. I'm backing up
>>> the .bak files to a file server on the network, could that cause
>>> the clean up process not to work? If so, what do I need to do to
>>> get the clean up step to remove all the .bak files that are 4 days
>>> old from the file server? Is it even possible to do?
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Where is the failure? The connection (top of that dialog) or the location for the folder? If the
folder, then I suggest you use an UNC path and type the path (not browse).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
> I've done that, 4 times actually and I'm getting the same message when trying to connect to the
> new location.
> 'unable to find sever DbbackUp'
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
>> Seems it got messed up somehow. I'd remove the task and add a new one.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the location for the BAK files it
>>fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you
>> specify the location. If you don't have such a task, add it. You do *not* specify backup file
>> removal inside the backup task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the location for the
>> cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup, I
>> just had to point the backup plan to the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>>> yes, all of databases are configured the same and this did work at one time. We had the
>>> change the location to point to a new folder on the same server and that folder has the same
>>> permissions as the folder did that this worked.
>>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
>>> servers.
>>>
>>>
>>>
>>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>> Does the account that is running the SQL Agent service have permissions to delete files
>>> from that network resource?
>>>
>>> --
>>>
>>> Kevin3NF
>>> SQL Server dude
>>>
>>> You want fries with that?
>>> http://kevin3nf.blogspot.com/
>>>
>>> I only check the newsgroups during work hours, M-F.
>>> Hit my blog and the contact links if necessary...I may be available.
>>>
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>> On my databases I have a backup maintanence plan on all of them. The plan also includes a
>>> clean of backups that are 4 days old. My backup is working but the clean up portion is
>>> not. I'm backing up the .bak files to a file server on the network, could that cause the
>>> clean up process not to work? If so, what do I need to do to get the clean up step to
>>> remove all the .bak files that are 4 days old from the file server? Is it even possible to
>>> do?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||So far I removed the current plans, created a new db backup plan which
points to the location, then I created a seperate cleanup plan and when I
type in the UNC path, I get the error 'unable to find \\nas123\sqlbackups\'
and this is only happening on my SQL 2005 Servers not my SQL 2000 servers.
The SQL 2000 servers are backing up and deleting bak files that are older
then 5 days, the SQL 05 servers - nothing.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OmQ3yDIdIHA.4196@.TK2MSFTNGP04.phx.gbl...
> Where is the failure? The connection (top of that dialog) or the location
> for the folder? If the folder, then I suggest you use an UNC path and type
> the path (not browse).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> I've done that, 4 times actually and I'm getting the same message when
>> trying to connect to the new location.
>> 'unable to find sever DbbackUp'
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
>> Seems it got messed up somehow. I'd remove the task and add a new one.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the
>>location for the BAK files it fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task".
>> this is where you specify the location. If you don't have such a task,
>> add it. You do *not* specify backup file removal inside the backup
>> task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define
>> the location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go.
>> Everything was already setup, I just had to point the backup plan to
>> the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>>> Did you modify the maintenance cleanup task to reflect the folder?
>>>
>>> --
>>> Tibor Karaszi, SQL Server MVP
>>> http://www.karaszi.com/sqlserver/default.asp
>>> http://sqlblog.com/blogs/tibor_karaszi
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>>> yes, all of databases are configured the same and this did work at
>>> one time. We had the change the location to point to a new folder
>>> on the same server and that folder has the same permissions as the
>>> folder did that this worked.
>>> That's the only change and my SQL 2000 db's have no issues in doing
>>> this, its only my SQL 05 servers.
>>>
>>>
>>>
>>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>> Does the account that is running the SQL Agent service have
>>> permissions to delete files from that network resource?
>>>
>>> --
>>>
>>> Kevin3NF
>>> SQL Server dude
>>>
>>> You want fries with that?
>>> http://kevin3nf.blogspot.com/
>>>
>>> I only check the newsgroups during work hours, M-F.
>>> Hit my blog and the contact links if necessary...I may be
>>> available.
>>>
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>>> On my databases I have a backup maintanence plan on all of them.
>>>> The plan also includes a clean of backups that are 4 days old. My
>>>> backup is working but the clean up portion is not. I'm backing up
>>>> the .bak files to a file server on the network, could that cause
>>>> the clean up process not to work? If so, what do I need to do to
>>>> get the clean up step to remove all the .bak files that are 4
>>>> days old from the file server? Is it even possible to do?
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Seems to be the Maint plan that want to verify that share. First thing I would do is to verify that
both Agent as well as SQL Server service account(s) has permission on the share. If they do, I'd
verify that this problem exist in a recent service pack/CU. If it still exists, it seems that Maint
plans in 2005 don't support removal of old backup files on a share.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:uji14dIdIHA.4312@.TK2MSFTNGP03.phx.gbl...
> So far I removed the current plans, created a new db backup plan which points to the location,
> then I created a seperate cleanup plan and when I type in the UNC path, I get the error 'unable to
> find \\nas123\sqlbackups\'
> and this is only happening on my SQL 2005 Servers not my SQL 2000 servers. The SQL 2000 servers
> are backing up and deleting bak files that are older then 5 days, the SQL 05 servers - nothing.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:OmQ3yDIdIHA.4196@.TK2MSFTNGP04.phx.gbl...
>> Where is the failure? The connection (top of that dialog) or the location for the folder? If the
>> folder, then I suggest you use an UNC path and type the path (not browse).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> I've done that, 4 times actually and I'm getting the same message when trying to connect to the
>> new location.
>> 'unable to find sever DbbackUp'
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
>> Seems it got messed up somehow. I'd remove the task and add a new one.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the location for the BAK files
>>it fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you
>> specify the location. If you don't have such a task, add it. You do *not* specify backup file
>> removal inside the backup task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>>> the backup plan is pointing to the new location. Where do I define the location for the
>>> cleanup?
>>> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup,
>>> I just had to point the backup plan to the new location.
>>>
>>>
>>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>>> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>>> Did you modify the maintenance cleanup task to reflect the folder?
>>>
>>> --
>>> Tibor Karaszi, SQL Server MVP
>>> http://www.karaszi.com/sqlserver/default.asp
>>> http://sqlblog.com/blogs/tibor_karaszi
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>>> yes, all of databases are configured the same and this did work at one time. We had the
>>> change the location to point to a new folder on the same server and that folder has the
>>> same permissions as the folder did that this worked.
>>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL
>>> 05 servers.
>>>
>>>
>>>
>>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>>> Does the account that is running the SQL Agent service have permissions to delete files
>>>> from that network resource?
>>>>
>>>> --
>>>>
>>>> Kevin3NF
>>>> SQL Server dude
>>>>
>>>> You want fries with that?
>>>> http://kevin3nf.blogspot.com/
>>>>
>>>> I only check the newsgroups during work hours, M-F.
>>>> Hit my blog and the contact links if necessary...I may be available.
>>>>
>>>>
>>>>
>>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>>> On my databases I have a backup maintanence plan on all of them. The plan also includes
>>>> a clean of backups that are 4 days old. My backup is working but the clean up portion is
>>>> not. I'm backing up the .bak files to a file server on the network, could that cause the
>>>> clean up process not to work? If so, what do I need to do to get the clean up step to
>>>> remove all the .bak files that are 4 days old from the file server? Is it even possible
>>>> to do?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
also includes a clean of backups that are 4 days old. My backup is working
but the clean up portion is not. I'm backing up the .bak files to a file
server on the network, could that cause the clean up process not to work? If
so, what do I need to do to get the clean up step to remove all the .bak
files that are 4 days old from the file server? Is it even possible to do?Does the account that is running the SQL Agent service have permissions to
delete files from that network resource?
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
> On my databases I have a backup maintanence plan on all of them. The plan
> also includes a clean of backups that are 4 days old. My backup is working
> but the clean up portion is not. I'm backing up the .bak files to a file
> server on the network, could that cause the clean up process not to work?
> If so, what do I need to do to get the clean up step to remove all the
> .bak files that are 4 days old from the file server? Is it even possible
> to do?
>
>|||yes, all of databases are configured the same and this did work at one time.
We had the change the location to point to a new folder on the same server
and that folder has the same permissions as the folder did that this worked.
That's the only change and my SQL 2000 db's have no issues in doing this,
its only my SQL 05 servers.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Does the account that is running the SQL Agent service have permissions to
> delete files from that network resource?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The plan
>> also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files to
>> a file server on the network, could that cause the clean up process not
>> to work? If so, what do I need to do to get the clean up step to remove
>> all the .bak files that are 4 days old from the file server? Is it even
>> possible to do?
>>
>|||Any errors in the Maintenance Plan logs?
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
> yes, all of databases are configured the same and this did work at one
> time. We had the change the location to point to a new folder on the same
> server and that folder has the same permissions as the folder did that
> this worked.
> That's the only change and my SQL 2000 db's have no issues in doing this,
> its only my SQL 05 servers.
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions
>> to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files
>> to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to
>> remove all the .bak files that are 4 days old from the file server? Is
>> it even possible to do?
>>
>>
>|||No, no errors in the log.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:etPNVb8cIHA.536@.TK2MSFTNGP06.phx.gbl...
> Any errors in the Maintenance Plan logs?
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one
>> time. We had the change the location to point to a new folder on the same
>> server and that folder has the same permissions as the folder did that
>> this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this,
>> its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions
>> to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files
>> to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to
>> remove all the .bak files that are 4 days old from the file server? Is
>> it even possible to do?
>>
>>
>>
>|||Did you modify the maintenance cleanup task to reflect the folder?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
> yes, all of databases are configured the same and this did work at one time. We had the change the
> location to point to a new folder on the same server and that folder has the same permissions as
> the folder did that this worked.
> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
> servers.
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions to delete files from that
>> network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The plan also includes a clean
>> of backups that are 4 days old. My backup is working but the clean up portion is not. I'm
>> backing up the .bak files to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to remove all the .bak files
>> that are 4 days old from the file server? Is it even possible to do?
>>
>>
>|||the backup plan is pointing to the new location. Where do I define the
location for the cleanup?
I just took this task over so I'm figuring out SQL 05 as I go. Everything
was already setup, I just had to point the backup plan to the new location.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
> Did you modify the maintenance cleanup task to reflect the folder?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one
>> time. We had the change the location to point to a new folder on the same
>> server and that folder has the same permissions as the folder did that
>> this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this,
>> its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions
>> to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup is
>> working but the clean up portion is not. I'm backing up the .bak files
>> to a file server on the network, could that cause the clean up process
>> not to work? If so, what do I need to do to get the clean up step to
>> remove all the .bak files that are 4 days old from the file server? Is
>> it even possible to do?
>>
>>
>>
>|||Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you specify the
location. If you don't have such a task, add it. You do *not* specify backup file removal inside the
backup task in 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
> the backup plan is pointing to the new location. Where do I define the location for the cleanup?
> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup, I
> just had to point the backup plan to the new location.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one time. We had the change
>> the location to point to a new folder on the same server and that folder has the same
>> permissions as the folder did that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
>> servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions to delete files from
>> that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The plan also includes a
>> clean of backups that are 4 days old. My backup is working but the clean up portion is not.
>> I'm backing up the .bak files to a file server on the network, could that cause the clean up
>> process not to work? If so, what do I need to do to get the clean up step to remove all the
>> .bak files that are 4 days old from the file server? Is it even possible to do?
>>
>>
>>
>>
>|||I have that and it points to SQL servers and when I try to add the location
for the BAK files it fails to connect.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
> Edit the plan. You should see a task named "Maintenance Cleanup task".
> this is where you specify the location. If you don't have such a task, add
> it. You do *not* specify backup file removal inside the backup task in
> 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the
>> location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go. Everything
>> was already setup, I just had to point the backup plan to the new
>> location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one
>> time. We had the change the location to point to a new folder on the
>> same server and that folder has the same permissions as the folder did
>> that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing
>> this, its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have
>> permissions to delete files from that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>> On my databases I have a backup maintanence plan on all of them. The
>> plan also includes a clean of backups that are 4 days old. My backup
>> is working but the clean up portion is not. I'm backing up the .bak
>> files to a file server on the network, could that cause the clean up
>> process not to work? If so, what do I need to do to get the clean up
>> step to remove all the .bak files that are 4 days old from the file
>> server? Is it even possible to do?
>>
>>
>>
>>
>>
>|||Seems it got messed up somehow. I'd remove the task and add a new one.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>I have that and it points to SQL servers and when I try to add the location for the BAK files it
>fails to connect.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you specify
>> the location. If you don't have such a task, add it. You do *not* specify backup file removal
>> inside the backup task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup, I
>> just had to point the backup plan to the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at one time. We had the change
>> the location to point to a new folder on the same server and that folder has the same
>> permissions as the folder did that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
>> servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>> Does the account that is running the SQL Agent service have permissions to delete files from
>> that network resource?
>> --
>> Kevin3NF
>> SQL Server dude
>> You want fries with that?
>> http://kevin3nf.blogspot.com/
>> I only check the newsgroups during work hours, M-F.
>> Hit my blog and the contact links if necessary...I may be available.
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>> On my databases I have a backup maintanence plan on all of them. The plan also includes a
>>> clean of backups that are 4 days old. My backup is working but the clean up portion is not.
>>> I'm backing up the .bak files to a file server on the network, could that cause the clean up
>>> process not to work? If so, what do I need to do to get the clean up step to remove all the
>>> .bak files that are 4 days old from the file server? Is it even possible to do?
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||I've done that, 4 times actually and I'm getting the same message when
trying to connect to the new location.
'unable to find sever DbbackUp'
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
> Seems it got messed up somehow. I'd remove the task and add a new one.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the
>>location for the BAK files it fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task".
>> this is where you specify the location. If you don't have such a task,
>> add it. You do *not* specify backup file removal inside the backup task
>> in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the
>> location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go.
>> Everything was already setup, I just had to point the backup plan to
>> the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>> yes, all of databases are configured the same and this did work at
>> one time. We had the change the location to point to a new folder on
>> the same server and that folder has the same permissions as the
>> folder did that this worked.
>> That's the only change and my SQL 2000 db's have no issues in doing
>> this, its only my SQL 05 servers.
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>> Does the account that is running the SQL Agent service have
>>> permissions to delete files from that network resource?
>>>
>>> --
>>>
>>> Kevin3NF
>>> SQL Server dude
>>>
>>> You want fries with that?
>>> http://kevin3nf.blogspot.com/
>>>
>>> I only check the newsgroups during work hours, M-F.
>>> Hit my blog and the contact links if necessary...I may be available.
>>>
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>> On my databases I have a backup maintanence plan on all of them.
>>> The plan also includes a clean of backups that are 4 days old. My
>>> backup is working but the clean up portion is not. I'm backing up
>>> the .bak files to a file server on the network, could that cause
>>> the clean up process not to work? If so, what do I need to do to
>>> get the clean up step to remove all the .bak files that are 4 days
>>> old from the file server? Is it even possible to do?
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Where is the failure? The connection (top of that dialog) or the location for the folder? If the
folder, then I suggest you use an UNC path and type the path (not browse).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
> I've done that, 4 times actually and I'm getting the same message when trying to connect to the
> new location.
> 'unable to find sever DbbackUp'
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
>> Seems it got messed up somehow. I'd remove the task and add a new one.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the location for the BAK files it
>>fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you
>> specify the location. If you don't have such a task, add it. You do *not* specify backup file
>> removal inside the backup task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define the location for the
>> cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup, I
>> just had to point the backup plan to the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>> Did you modify the maintenance cleanup task to reflect the folder?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>>> yes, all of databases are configured the same and this did work at one time. We had the
>>> change the location to point to a new folder on the same server and that folder has the same
>>> permissions as the folder did that this worked.
>>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL 05
>>> servers.
>>>
>>>
>>>
>>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>> Does the account that is running the SQL Agent service have permissions to delete files
>>> from that network resource?
>>>
>>> --
>>>
>>> Kevin3NF
>>> SQL Server dude
>>>
>>> You want fries with that?
>>> http://kevin3nf.blogspot.com/
>>>
>>> I only check the newsgroups during work hours, M-F.
>>> Hit my blog and the contact links if necessary...I may be available.
>>>
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>> On my databases I have a backup maintanence plan on all of them. The plan also includes a
>>> clean of backups that are 4 days old. My backup is working but the clean up portion is
>>> not. I'm backing up the .bak files to a file server on the network, could that cause the
>>> clean up process not to work? If so, what do I need to do to get the clean up step to
>>> remove all the .bak files that are 4 days old from the file server? Is it even possible to
>>> do?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||So far I removed the current plans, created a new db backup plan which
points to the location, then I created a seperate cleanup plan and when I
type in the UNC path, I get the error 'unable to find \\nas123\sqlbackups\'
and this is only happening on my SQL 2005 Servers not my SQL 2000 servers.
The SQL 2000 servers are backing up and deleting bak files that are older
then 5 days, the SQL 05 servers - nothing.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OmQ3yDIdIHA.4196@.TK2MSFTNGP04.phx.gbl...
> Where is the failure? The connection (top of that dialog) or the location
> for the folder? If the folder, then I suggest you use an UNC path and type
> the path (not browse).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
> news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> I've done that, 4 times actually and I'm getting the same message when
>> trying to connect to the new location.
>> 'unable to find sever DbbackUp'
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
>> Seems it got messed up somehow. I'd remove the task and add a new one.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the
>>location for the BAK files it fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task".
>> this is where you specify the location. If you don't have such a task,
>> add it. You do *not* specify backup file removal inside the backup
>> task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>> the backup plan is pointing to the new location. Where do I define
>> the location for the cleanup?
>> I just took this task over so I'm figuring out SQL 05 as I go.
>> Everything was already setup, I just had to point the backup plan to
>> the new location.
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>>> Did you modify the maintenance cleanup task to reflect the folder?
>>>
>>> --
>>> Tibor Karaszi, SQL Server MVP
>>> http://www.karaszi.com/sqlserver/default.asp
>>> http://sqlblog.com/blogs/tibor_karaszi
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>>> yes, all of databases are configured the same and this did work at
>>> one time. We had the change the location to point to a new folder
>>> on the same server and that folder has the same permissions as the
>>> folder did that this worked.
>>> That's the only change and my SQL 2000 db's have no issues in doing
>>> this, its only my SQL 05 servers.
>>>
>>>
>>>
>>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>> Does the account that is running the SQL Agent service have
>>> permissions to delete files from that network resource?
>>>
>>> --
>>>
>>> Kevin3NF
>>> SQL Server dude
>>>
>>> You want fries with that?
>>> http://kevin3nf.blogspot.com/
>>>
>>> I only check the newsgroups during work hours, M-F.
>>> Hit my blog and the contact links if necessary...I may be
>>> available.
>>>
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>>> On my databases I have a backup maintanence plan on all of them.
>>>> The plan also includes a clean of backups that are 4 days old. My
>>>> backup is working but the clean up portion is not. I'm backing up
>>>> the .bak files to a file server on the network, could that cause
>>>> the clean up process not to work? If so, what do I need to do to
>>>> get the clean up step to remove all the .bak files that are 4
>>>> days old from the file server? Is it even possible to do?
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Seems to be the Maint plan that want to verify that share. First thing I would do is to verify that
both Agent as well as SQL Server service account(s) has permission on the share. If they do, I'd
verify that this problem exist in a recent service pack/CU. If it still exists, it seems that Maint
plans in 2005 don't support removal of old backup files on a share.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
news:uji14dIdIHA.4312@.TK2MSFTNGP03.phx.gbl...
> So far I removed the current plans, created a new db backup plan which points to the location,
> then I created a seperate cleanup plan and when I type in the UNC path, I get the error 'unable to
> find \\nas123\sqlbackups\'
> and this is only happening on my SQL 2005 Servers not my SQL 2000 servers. The SQL 2000 servers
> are backing up and deleting bak files that are older then 5 days, the SQL 05 servers - nothing.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:OmQ3yDIdIHA.4196@.TK2MSFTNGP04.phx.gbl...
>> Where is the failure? The connection (top of that dialog) or the location for the folder? If the
>> folder, then I suggest you use an UNC path and type the path (not browse).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:ODR8bo9cIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> I've done that, 4 times actually and I'm getting the same message when trying to connect to the
>> new location.
>> 'unable to find sever DbbackUp'
>>
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Oyf1Ie9cIHA.1132@.TK2MSFTNGP06.phx.gbl...
>> Seems it got messed up somehow. I'd remove the task and add a new one.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23rQGKd9cIHA.4436@.TK2MSFTNGP05.phx.gbl...
>>I have that and it points to SQL servers and when I try to add the location for the BAK files
>>it fails to connect.
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:OUiuFR9cIHA.288@.TK2MSFTNGP02.phx.gbl...
>> Edit the plan. You should see a task named "Maintenance Cleanup task". this is where you
>> specify the location. If you don't have such a task, add it. You do *not* specify backup file
>> removal inside the backup task in 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>> news:%23eAJZI9cIHA.5984@.TK2MSFTNGP06.phx.gbl...
>>> the backup plan is pointing to the new location. Where do I define the location for the
>>> cleanup?
>>> I just took this task over so I'm figuring out SQL 05 as I go. Everything was already setup,
>>> I just had to point the backup plan to the new location.
>>>
>>>
>>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>>> news:Os%232tv8cIHA.1376@.TK2MSFTNGP02.phx.gbl...
>>> Did you modify the maintenance cleanup task to reflect the folder?
>>>
>>> --
>>> Tibor Karaszi, SQL Server MVP
>>> http://www.karaszi.com/sqlserver/default.asp
>>> http://sqlblog.com/blogs/tibor_karaszi
>>>
>>>
>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>> news:OhPUOO8cIHA.1960@.TK2MSFTNGP02.phx.gbl...
>>> yes, all of databases are configured the same and this did work at one time. We had the
>>> change the location to point to a new folder on the same server and that folder has the
>>> same permissions as the folder did that this worked.
>>> That's the only change and my SQL 2000 db's have no issues in doing this, its only my SQL
>>> 05 servers.
>>>
>>>
>>>
>>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>>> news:eL8fQI8cIHA.4476@.TK2MSFTNGP06.phx.gbl...
>>>> Does the account that is running the SQL Agent service have permissions to delete files
>>>> from that network resource?
>>>>
>>>> --
>>>>
>>>> Kevin3NF
>>>> SQL Server dude
>>>>
>>>> You want fries with that?
>>>> http://kevin3nf.blogspot.com/
>>>>
>>>> I only check the newsgroups during work hours, M-F.
>>>> Hit my blog and the contact links if necessary...I may be available.
>>>>
>>>>
>>>>
>>>> "Mike" <Mike@.aseagullpoopedonmyhead.com> wrote in message
>>>> news:OpVS657cIHA.5668@.TK2MSFTNGP05.phx.gbl...
>>>> On my databases I have a backup maintanence plan on all of them. The plan also includes
>>>> a clean of backups that are 4 days old. My backup is working but the clean up portion is
>>>> not. I'm backing up the .bak files to a file server on the network, could that cause the
>>>> clean up process not to work? If so, what do I need to do to get the clean up step to
>>>> remove all the .bak files that are 4 days old from the file server? Is it even possible
>>>> to do?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
Subscribe to:
Posts (Atom)