Help please
I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
Is there an easy way to get DB/table statistics, table name, rows, last
accessed.
Thanks for any direction and assistance.
George
Hi,
sp_monitor -- Gives the SQL Server statistics
sp_helpdb <dbname> -- Gives you the details of database size, Options set,
FIle group information , File details...
Table -- Query the sysobjects table for name, created date
Number of rows -- sp_spaceused <table name>
Last accessesed date for table will not be stored by default , you may neeed
to write a trigger or use Log explorer from Lumigent.com
sp_configure -- Gives you all the parameter list and its values.
Thanks
Hari
MCDBA
"george collins" <george@.nospan.com> wrote in message
news:e44UTyvJEHA.620@.TK2MSFTNGP10.phx.gbl...
> Help please
> I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
> Is there an easy way to get DB/table statistics, table name, rows, last
> accessed.
> Thanks for any direction and assistance.
> George
>
Showing posts with label old. Show all posts
Showing posts with label old. Show all posts
Thursday, March 22, 2012
DB Statistics
Help please
I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
Is there an easy way to get DB/table statistics, table name, rows, last
accessed.
Thanks for any direction and assistance.
GeorgeHi,
sp_monitor -- Gives the SQL Server statistics
sp_helpdb <dbname> -- Gives you the details of database size, Options set,
FIle group information , File details...
Table -- Query the sysobjects table for name, created date
Number of rows -- sp_spaceused <table name>
Last accessesed date for table will not be stored by default , you may neeed
to write a trigger or use Log explorer from Lumigent.com
sp_configure -- Gives you all the parameter list and its values.
Thanks
Hari
MCDBA
"george collins" <george@.nospan.com> wrote in message
news:e44UTyvJEHA.620@.TK2MSFTNGP10.phx.gbl...
> Help please
> I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
> Is there an easy way to get DB/table statistics, table name, rows, last
> accessed.
> Thanks for any direction and assistance.
> George
>sql
I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
Is there an easy way to get DB/table statistics, table name, rows, last
accessed.
Thanks for any direction and assistance.
GeorgeHi,
sp_monitor -- Gives the SQL Server statistics
sp_helpdb <dbname> -- Gives you the details of database size, Options set,
FIle group information , File details...
Table -- Query the sysobjects table for name, created date
Number of rows -- sp_spaceused <table name>
Last accessesed date for table will not be stored by default , you may neeed
to write a trigger or use Log explorer from Lumigent.com
sp_configure -- Gives you all the parameter list and its values.
Thanks
Hari
MCDBA
"george collins" <george@.nospan.com> wrote in message
news:e44UTyvJEHA.620@.TK2MSFTNGP10.phx.gbl...
> Help please
> I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
> Is there an easy way to get DB/table statistics, table name, rows, last
> accessed.
> Thanks for any direction and assistance.
> George
>sql
DB Statistics
Help please
I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
Is there an easy way to get DB/table statistics, table name, rows, last
accessed.
Thanks for any direction and assistance.
GeorgeHi,
sp_monitor -- Gives the SQL Server statistics
sp_helpdb <dbname> -- Gives you the details of database size, Options set,
FIle group information , File details...
Table -- Query the sysobjects table for name, created date
Number of rows -- sp_spaceused <table name>
Last accessesed date for table will not be stored by default , you may neeed
to write a trigger or use Log explorer from Lumigent.com
sp_configure -- Gives you all the parameter list and its values.
Thanks
Hari
MCDBA
"george collins" <george@.nospan.com> wrote in message
news:e44UTyvJEHA.620@.TK2MSFTNGP10.phx.gbl...
> Help please
> I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
> Is there an easy way to get DB/table statistics, table name, rows, last
> accessed.
> Thanks for any direction and assistance.
> George
>
I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
Is there an easy way to get DB/table statistics, table name, rows, last
accessed.
Thanks for any direction and assistance.
GeorgeHi,
sp_monitor -- Gives the SQL Server statistics
sp_helpdb <dbname> -- Gives you the details of database size, Options set,
FIle group information , File details...
Table -- Query the sysobjects table for name, created date
Number of rows -- sp_spaceused <table name>
Last accessesed date for table will not be stored by default , you may neeed
to write a trigger or use Log explorer from Lumigent.com
sp_configure -- Gives you all the parameter list and its values.
Thanks
Hari
MCDBA
"george collins" <george@.nospan.com> wrote in message
news:e44UTyvJEHA.620@.TK2MSFTNGP10.phx.gbl...
> Help please
> I am an old UNIFY guy and I am doing some work on SQL2000 for a customer.
> Is there an easy way to get DB/table statistics, table name, rows, last
> accessed.
> Thanks for any direction and assistance.
> George
>
Wednesday, March 21, 2012
DB Size - Urgent help please
Hi all
Last week I was moving my site to a new server
My SQL database in old host without Log file was 180 MB, and after shrink it became 170 MB,
I asked my old host support to give me DB back up for moving to new server, it was friday and they told me we will do that on monday, but I wanted it soon, so I logged in ino Enterprise manager to my old server sql, and also I opened connection to my new server sql ,I go to Export Wizard of my database on old host so I chose to export all of the tables from my database on old host to a new database on new server,
it took about 2 hour (with a 128 kb net connection) after finishing I tested the new database it was working fine and all of the tables and rows was in new database,
but some thing that is wondering is the size of the database the new database on new server is 109 MB now :shocked:
why ?
I have shrinked the old database and without log files it was 170 MB so why on my destination database its 109 MB , and very thing is working fine
I want to know what was in old database that increased file size about 60 MB ?
and can I use my new database which its size is 109 MB ?
Please tell me soon , I need thatAre the tables themselves all you need. If so, then apparantly you're ready to go. If not, then you're probably not ready to go.
Copying all the tables from one instance to another is not the same as copying the whole database...|||tell me, what it has that I didn't copy ?
I also use stored procedure and views, but I have copied them also,|||somebody help me|||The only way I know to effectively help you is for you to post a copy of your database for us to examine. You told us that the copy is smaller than the original, which implies that something is missing. The only way I know to figure out what is missing is for one of us to repeat the process you've described, veryify that we get the same results, then figure out what is missing.
What you are asking is kind of like playing "Where's Waldo" via posting... If we can't see the picture, there's very little hope that we can guess where Waldo is. Without access to your original database, I don't know of any way that I'm willing to pursue to help you solve the problem.
One thing that might help you find the more obvious and potentially serious problems would be to script the database objects out to a text file for both your source and destination databases. You could then compare the scripts to see what objects (tables, indexes, views, procedures, etc) are missing. If all of the objects are present in the destination, then it is highly unlikely you are missing anything important.
-PatP|||if you go the scripting route for comparison, you can use scriptdb to script out both all objects and data in any 2000 or 2005 database:
http://www.dbforums.com/showthread.php?t=1610270|||I can see two possible reasons
1) No indexes were brought over from the old database. I don't believe the export data wizard brings indexes over. You may want to check for that.
if the indexes were brought over, then
2) Index defragmentation has occurred. All the empty space in the individual data pages has now been reclaimed. FOr more information, google around for defragmentation.
Last week I was moving my site to a new server
My SQL database in old host without Log file was 180 MB, and after shrink it became 170 MB,
I asked my old host support to give me DB back up for moving to new server, it was friday and they told me we will do that on monday, but I wanted it soon, so I logged in ino Enterprise manager to my old server sql, and also I opened connection to my new server sql ,I go to Export Wizard of my database on old host so I chose to export all of the tables from my database on old host to a new database on new server,
it took about 2 hour (with a 128 kb net connection) after finishing I tested the new database it was working fine and all of the tables and rows was in new database,
but some thing that is wondering is the size of the database the new database on new server is 109 MB now :shocked:
why ?
I have shrinked the old database and without log files it was 170 MB so why on my destination database its 109 MB , and very thing is working fine
I want to know what was in old database that increased file size about 60 MB ?
and can I use my new database which its size is 109 MB ?
Please tell me soon , I need thatAre the tables themselves all you need. If so, then apparantly you're ready to go. If not, then you're probably not ready to go.
Copying all the tables from one instance to another is not the same as copying the whole database...|||tell me, what it has that I didn't copy ?
I also use stored procedure and views, but I have copied them also,|||somebody help me|||The only way I know to effectively help you is for you to post a copy of your database for us to examine. You told us that the copy is smaller than the original, which implies that something is missing. The only way I know to figure out what is missing is for one of us to repeat the process you've described, veryify that we get the same results, then figure out what is missing.
What you are asking is kind of like playing "Where's Waldo" via posting... If we can't see the picture, there's very little hope that we can guess where Waldo is. Without access to your original database, I don't know of any way that I'm willing to pursue to help you solve the problem.
One thing that might help you find the more obvious and potentially serious problems would be to script the database objects out to a text file for both your source and destination databases. You could then compare the scripts to see what objects (tables, indexes, views, procedures, etc) are missing. If all of the objects are present in the destination, then it is highly unlikely you are missing anything important.
-PatP|||if you go the scripting route for comparison, you can use scriptdb to script out both all objects and data in any 2000 or 2005 database:
http://www.dbforums.com/showthread.php?t=1610270|||I can see two possible reasons
1) No indexes were brought over from the old database. I don't believe the export data wizard brings indexes over. You may want to check for that.
if the indexes were brought over, then
2) Index defragmentation has occurred. All the empty space in the individual data pages has now been reclaimed. FOr more information, google around for defragmentation.
Monday, March 19, 2012
DB Restored to New Server, ODBC Says Database is Not Valid
I'm setting up a replacement server for SQL 2000 and have restored a DB from old server to new server using backup/restore. All seems to work, DB listed in Enterprise Manager, I can see data. When I try to setup an ODBC connection on same server, however, the DB is not listed in drop-down list and if I enter the name, it responds with "the database entered is not valid". What is left to do?
Detaching the database and then attaching it solved this problem.
Detaching the database and then attaching it solved this problem.
DB restore error to new server
Hi,
We have just built a new Windows 2003 Std Ed, SP1 server with SQL
Server 2005 no SP.
We are attempting to restore the databases from an old server to this
new one, however after the restore process gets to 100% we recive the
following error:
SQL Server detected a logical consistency-based I/O error: incorrect
checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
error log or system event log may provide more detail. This is a severe
error condition that threatens database integrity and must be corrected
immediately. Complete a full database consistency check (DBCC CHECKDB)
Does anybody know what might be the problem?
Regards
Paul RobertsBob wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>
Sounds like a corrupt backup. That error is occurring as SQL tries to
"recover" the new database to bring it online. It's telling you that
database has an internal problem of some kind. I would run a new backup
of the original database to restore from. Barring that, use DBCC
CHECKDB to attempt a repair of the restored database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi,
We tried that too with no luck.
This database is from a replicated database being restored to a
non-replication system.|||Bob wrote:
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>
Tried the new backup, or tried running DBCC? If the new backup gave the
same error, you might want to run DBCC CHECKDB against the original
database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The RESTORE command has a CONTINUE_AFTER_ERROR option. That should at lest g
et the database there,
so you can do something with it (like last resort emergency mode). But you s
hould really CHECKDB the
source database. If that db is clean, you shouldn't get corrupted backups.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob" <pmroberts@.talk21.com> wrote in message
news:1152811634.990074.129800@.p79g2000cwp.googlegroups.com...
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>|||2 questions -
1. How are you copying over the .bak file between the 2 machines?
2. Is the file sie the same?
"Bob" wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>|||Hi,
The files are being copied using windows drag and drop.
The file sizes are the same.
I am using SQL server management studio, I cannot see the RESTORE
command has a CONTINUE_AFTER_ERROR, I tried this option under the
backup option but with no luck.
I also tried new backups.
Is there a limit to the size of the backups?|||How do I use DBCC CHECKDB?|||Bob wrote:
> Hi,
> The files are being copied using windows drag and drop.
> The file sizes are the same.
> I am using SQL server management studio, I cannot see the RESTORE
> command has a CONTINUE_AFTER_ERROR, I tried this option under the
> backup option but with no luck.
> I also tried new backups.
> Is there a limit to the size of the backups?
>
You might need to do the restore with the sql command in order to
specify the CONTINUE AFTER ERROR option.
Try to look up RESTORE Database in Books On Line.
Also, have you tried to restore the files to a different drive? It might
not be the case, but you could have a bad spot on the disk and that's
why it fails (..I know it's a wild guess but it should be fairly easy to
try...).
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||Hi,
Problem solved.
The issue is due to the fact that they are replication databases.
Since I am restoring to a different server, without replication, the
SQL server is supposed to realise this and remove replication status,
however it does not and you have to remove this manually with the
command: sp_removedbreplication dbname
You can then bring the database online.
See http://msdn2.microsoft.com/en-us/library/ms151782(d=ide).aspx
for more information.
We have just built a new Windows 2003 Std Ed, SP1 server with SQL
Server 2005 no SP.
We are attempting to restore the databases from an old server to this
new one, however after the restore process gets to 100% we recive the
following error:
SQL Server detected a logical consistency-based I/O error: incorrect
checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
error log or system event log may provide more detail. This is a severe
error condition that threatens database integrity and must be corrected
immediately. Complete a full database consistency check (DBCC CHECKDB)
Does anybody know what might be the problem?
Regards
Paul RobertsBob wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>
Sounds like a corrupt backup. That error is occurring as SQL tries to
"recover" the new database to bring it online. It's telling you that
database has an internal problem of some kind. I would run a new backup
of the original database to restore from. Barring that, use DBCC
CHECKDB to attempt a repair of the restored database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi,
We tried that too with no luck.
This database is from a replicated database being restored to a
non-replication system.|||Bob wrote:
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>
Tried the new backup, or tried running DBCC? If the new backup gave the
same error, you might want to run DBCC CHECKDB against the original
database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The RESTORE command has a CONTINUE_AFTER_ERROR option. That should at lest g
et the database there,
so you can do something with it (like last resort emergency mode). But you s
hould really CHECKDB the
source database. If that db is clean, you shouldn't get corrupted backups.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob" <pmroberts@.talk21.com> wrote in message
news:1152811634.990074.129800@.p79g2000cwp.googlegroups.com...
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>|||2 questions -
1. How are you copying over the .bak file between the 2 machines?
2. Is the file sie the same?
"Bob" wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>|||Hi,
The files are being copied using windows drag and drop.
The file sizes are the same.
I am using SQL server management studio, I cannot see the RESTORE
command has a CONTINUE_AFTER_ERROR, I tried this option under the
backup option but with no luck.
I also tried new backups.
Is there a limit to the size of the backups?|||How do I use DBCC CHECKDB?|||Bob wrote:
> Hi,
> The files are being copied using windows drag and drop.
> The file sizes are the same.
> I am using SQL server management studio, I cannot see the RESTORE
> command has a CONTINUE_AFTER_ERROR, I tried this option under the
> backup option but with no luck.
> I also tried new backups.
> Is there a limit to the size of the backups?
>
You might need to do the restore with the sql command in order to
specify the CONTINUE AFTER ERROR option.
Try to look up RESTORE Database in Books On Line.
Also, have you tried to restore the files to a different drive? It might
not be the case, but you could have a bad spot on the disk and that's
why it fails (..I know it's a wild guess but it should be fairly easy to
try...).
Regards
Steen Schlter Persson
Databaseadministrator / Systemadministrator|||Hi,
Problem solved.
The issue is due to the fact that they are replication databases.
Since I am restoring to a different server, without replication, the
SQL server is supposed to realise this and remove replication status,
however it does not and you have to remove this manually with the
command: sp_removedbreplication dbname
You can then bring the database online.
See http://msdn2.microsoft.com/en-us/library/ms151782(d=ide).aspx
for more information.
DB restore error to new server
Hi,
We have just built a new Windows 2003 Std Ed, SP1 server with SQL
Server 2005 no SP.
We are attempting to restore the databases from an old server to this
new one, however after the restore process gets to 100% we recive the
following error:
SQL Server detected a logical consistency-based I/O error: incorrect
checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
error log or system event log may provide more detail. This is a severe
error condition that threatens database integrity and must be corrected
immediately. Complete a full database consistency check (DBCC CHECKDB)
Does anybody know what might be the problem?
Regards
Paul RobertsBob wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>
Sounds like a corrupt backup. That error is occurring as SQL tries to
"recover" the new database to bring it online. It's telling you that
database has an internal problem of some kind. I would run a new backup
of the original database to restore from. Barring that, use DBCC
CHECKDB to attempt a repair of the restored database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi,
We tried that too with no luck.
This database is from a replicated database being restored to a
non-replication system.|||Bob wrote:
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>
Tried the new backup, or tried running DBCC? If the new backup gave the
same error, you might want to run DBCC CHECKDB against the original
database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The RESTORE command has a CONTINUE_AFTER_ERROR option. That should at lest get the database there,
so you can do something with it (like last resort emergency mode). But you should really CHECKDB the
source database. If that db is clean, you shouldn't get corrupted backups.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob" <pmroberts@.talk21.com> wrote in message
news:1152811634.990074.129800@.p79g2000cwp.googlegroups.com...
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>|||2 questions -
1. How are you copying over the .bak file between the 2 machines?
2. Is the file sie the same?
"Bob" wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>|||Hi,
The files are being copied using windows drag and drop.
The file sizes are the same.
I am using SQL server management studio, I cannot see the RESTORE
command has a CONTINUE_AFTER_ERROR, I tried this option under the
backup option but with no luck.
I also tried new backups.
Is there a limit to the size of the backups?|||How do I use DBCC CHECKDB?|||This is a multi-part message in MIME format.
--090202070601080406010907
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Bob wrote:
> Hi,
> The files are being copied using windows drag and drop.
> The file sizes are the same.
> I am using SQL server management studio, I cannot see the RESTORE
> command has a CONTINUE_AFTER_ERROR, I tried this option under the
> backup option but with no luck.
> I also tried new backups.
> Is there a limit to the size of the backups?
>
You might need to do the restore with the sql command in order to
specify the CONTINUE AFTER ERROR option.
Try to look up RESTORE Database in Books On Line.
Also, have you tried to restore the files to a different drive? It might
not be the case, but you could have a bad spot on the disk and that's
why it fails (..I know it's a wild guess but it should be fairly easy to
try...).
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--090202070601080406010907
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bob wrote:
<blockquote
cite="mid1152874083.247364.97190@.35g2000cwc.googlegroups.com"
type="cite">
<pre wrap="">Hi,
The files are being copied using windows drag and drop.
The file sizes are the same.
I am using SQL server management studio, I cannot see the RESTORE
command has a CONTINUE_AFTER_ERROR, I tried this option under the
backup option but with no luck.
I also tried new backups.
Is there a limit to the size of the backups?
</pre>
</blockquote>
<font size="-1"><font face="Arial">You might need to do the restore
with the sql command in order to specify the CONTINUE AFTER ERROR
option.<br>
Try to look up RESTORE Database in Books On Line.<br>
<br>
Also, have you tried to restore the files to a different drive? It
might not be the case, but you could have a bad spot on the disk and
that's why it fails (..I know it's a wild guess but it should be fairly
easy to try...).<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--090202070601080406010907--|||Hi,
Problem solved.
The issue is due to the fact that they are replication databases.
Since I am restoring to a different server, without replication, the
SQL server is supposed to realise this and remove replication status,
however it does not and you have to remove this manually with the
command: sp_removedbreplication dbname
You can then bring the database online.
See http://msdn2.microsoft.com/en-us/library/ms151782(d=ide).aspx
for more information.
We have just built a new Windows 2003 Std Ed, SP1 server with SQL
Server 2005 no SP.
We are attempting to restore the databases from an old server to this
new one, however after the restore process gets to 100% we recive the
following error:
SQL Server detected a logical consistency-based I/O error: incorrect
checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
error log or system event log may provide more detail. This is a severe
error condition that threatens database integrity and must be corrected
immediately. Complete a full database consistency check (DBCC CHECKDB)
Does anybody know what might be the problem?
Regards
Paul RobertsBob wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>
Sounds like a corrupt backup. That error is occurring as SQL tries to
"recover" the new database to bring it online. It's telling you that
database has an internal problem of some kind. I would run a new backup
of the original database to restore from. Barring that, use DBCC
CHECKDB to attempt a repair of the restored database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi,
We tried that too with no luck.
This database is from a replicated database being restored to a
non-replication system.|||Bob wrote:
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>
Tried the new backup, or tried running DBCC? If the new backup gave the
same error, you might want to run DBCC CHECKDB against the original
database.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||The RESTORE command has a CONTINUE_AFTER_ERROR option. That should at lest get the database there,
so you can do something with it (like last resort emergency mode). But you should really CHECKDB the
source database. If that db is clean, you shouldn't get corrupted backups.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bob" <pmroberts@.talk21.com> wrote in message
news:1152811634.990074.129800@.p79g2000cwp.googlegroups.com...
> Hi,
> We tried that too with no luck.
> This database is from a replicated database being restored to a
> non-replication system.
>|||2 questions -
1. How are you copying over the .bak file between the 2 machines?
2. Is the file sie the same?
"Bob" wrote:
> Hi,
> We have just built a new Windows 2003 Std Ed, SP1 server with SQL
> Server 2005 no SP.
> We are attempting to restore the databases from an old server to this
> new one, however after the restore process gets to 100% we recive the
> following error:
> SQL Server detected a logical consistency-based I/O error: incorrect
> checksum (expected: 0x65f3e4dc; actual: 0x65f3e4de). It occurred during
> a read of page (1:32625) in database ID 7 at offset 0x0000000fee2000 in
> file 'D:\sqldata\filename.mdf'. Additional messages in the SQL Server
> error log or system event log may provide more detail. This is a severe
> error condition that threatens database integrity and must be corrected
> immediately. Complete a full database consistency check (DBCC CHECKDB)
> Does anybody know what might be the problem?
> Regards
> Paul Roberts
>|||Hi,
The files are being copied using windows drag and drop.
The file sizes are the same.
I am using SQL server management studio, I cannot see the RESTORE
command has a CONTINUE_AFTER_ERROR, I tried this option under the
backup option but with no luck.
I also tried new backups.
Is there a limit to the size of the backups?|||How do I use DBCC CHECKDB?|||This is a multi-part message in MIME format.
--090202070601080406010907
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Bob wrote:
> Hi,
> The files are being copied using windows drag and drop.
> The file sizes are the same.
> I am using SQL server management studio, I cannot see the RESTORE
> command has a CONTINUE_AFTER_ERROR, I tried this option under the
> backup option but with no luck.
> I also tried new backups.
> Is there a limit to the size of the backups?
>
You might need to do the restore with the sql command in order to
specify the CONTINUE AFTER ERROR option.
Try to look up RESTORE Database in Books On Line.
Also, have you tried to restore the files to a different drive? It might
not be the case, but you could have a bad spot on the disk and that's
why it fails (..I know it's a wild guess but it should be fairly easy to
try...).
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator
--090202070601080406010907
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bob wrote:
<blockquote
cite="mid1152874083.247364.97190@.35g2000cwc.googlegroups.com"
type="cite">
<pre wrap="">Hi,
The files are being copied using windows drag and drop.
The file sizes are the same.
I am using SQL server management studio, I cannot see the RESTORE
command has a CONTINUE_AFTER_ERROR, I tried this option under the
backup option but with no luck.
I also tried new backups.
Is there a limit to the size of the backups?
</pre>
</blockquote>
<font size="-1"><font face="Arial">You might need to do the restore
with the sql command in order to specify the CONTINUE AFTER ERROR
option.<br>
Try to look up RESTORE Database in Books On Line.<br>
<br>
Also, have you tried to restore the files to a different drive? It
might not be the case, but you could have a bad spot on the disk and
that's why it fails (..I know it's a wild guess but it should be fairly
easy to try...).<br>
<br>
<br>
-- <br>
Regards<br>
Steen Schlüter Persson<br>
Databaseadministrator / Systemadministrator<br>
</font></font>
</body>
</html>
--090202070601080406010907--|||Hi,
Problem solved.
The issue is due to the fact that they are replication databases.
Since I am restoring to a different server, without replication, the
SQL server is supposed to realise this and remove replication status,
however it does not and you have to remove this manually with the
command: sp_removedbreplication dbname
You can then bring the database online.
See http://msdn2.microsoft.com/en-us/library/ms151782(d=ide).aspx
for more information.
Wednesday, March 7, 2012
DB Mirroring Monitor Job - Purge Old Data?
Hi,
Not sure if this question makes sense, but is it necessary to purge old data in msdb tables used by the db mirroring monitor job?
I'm just wondering if an insert into the data table every minute of the day would still be needed a month from now. I'm thinking this data would be useful for the purpose of "alerts" and to have access to its recent history, but other than that, is it recommended (or necessary)? Would these records keep accumulating until manually purged?
TIA.
You can manually purge the data using SP_DELETE_BACKUPHISTORY and you can set to retain number of rows or worth of data from SQLAgent properties in this case. If there is a business case in your situation you can set it to higher value and use the logs for analysis.
BOL refers about tables used:
SQL Server includes the following backup history tables that track backup activity:
backupfile (Transact-SQL)
backupfilegroup (Transact-SQL)
backupmediafamily (Transact-SQL)
backupmediaset (Transact-SQL)
backupset (Transact-SQL)
|||
Thanks for the info.
I checked the SQLAgent properties for the "history log size" setting (currently set to 1000 rows). However, if I check the "msdb.dbm_monitor_data" table, the rows just keep increasing every minute - I believe the Database Mirroring Monitor job executes a stored procedure that inserts a row every minute into this table.... and this log is not affected by the history log size setting.
I did however check the "time" in that table and noticed that exactly 1 week's worth of data is kept. Seems like something is automatically purging records older than 1 week. I think this would sort of answer my question.
|||Yes and by default that is the setting to keep the job log history.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 maintenance job filed to delete old backup files
Hi,
I am working on sql server 2000.
It happened few times to me now, one of my database
maintenance backup job failed to delete the old backup
file. And it always happend to the same database. I set
the job to delete any backup file that is older than 1
day. Any thought on this?
Thanks.
JJCheck 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
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JJ Wang" <jwang@.leapwireless.com> wrote in message news:051b01c36ac3$e8a1a320$a301280a@.phx.gbl...
> Hi,
> I am working on sql server 2000.
> It happened few times to me now, one of my database
> maintenance backup job failed to delete the old backup
> file. And it always happend to the same database. I set
> the job to delete any backup file that is older than 1
> day. Any thought on this?
> Thanks.
> JJ
>|||>--Original Message--
>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
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:051b01c36ac3$e8a1a320$a301280a@.phx.gbl...
>> Hi,
>> I am working on sql server 2000.
>> It happened few times to me now, one of my database
>> maintenance backup job failed to delete the old backup
>> file. And it always happend to the same database. I
set
>> the job to delete any backup file that is older than 1
>> day. Any thought on this?
>> Thanks.
>> JJ
>
>.
>
I am working on sql server 2000.
It happened few times to me now, one of my database
maintenance backup job failed to delete the old backup
file. And it always happend to the same database. I set
the job to delete any backup file that is older than 1
day. Any thought on this?
Thanks.
JJCheck 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
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"JJ Wang" <jwang@.leapwireless.com> wrote in message news:051b01c36ac3$e8a1a320$a301280a@.phx.gbl...
> Hi,
> I am working on sql server 2000.
> It happened few times to me now, one of my database
> maintenance backup job failed to delete the old backup
> file. And it always happend to the same database. I set
> the job to delete any backup file that is older than 1
> day. Any thought on this?
> Thanks.
> JJ
>|||>--Original Message--
>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
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:051b01c36ac3$e8a1a320$a301280a@.phx.gbl...
>> Hi,
>> I am working on sql server 2000.
>> It happened few times to me now, one of my database
>> maintenance backup job failed to delete the old backup
>> file. And it always happend to the same database. I
set
>> the job to delete any backup file that is older than 1
>> day. Any thought on this?
>> Thanks.
>> JJ
>
>.
>
DB Maintenance - Purging Old File feature
Hi,
I'm using SQL2K with SP4 2187. I have created a DB Maintenance wizard where the purging older than 1 day is set.
However, this feature seems not to be working, even if I tried two ways. Delete the scheduled job and recreate it - not successful, 2nd) delete the Maintenance Plan, still not successful.
Is this a bug or do I miss something here.Hi.
I've had the same issue. But with mine sometimes it works and sometimes it doesn't. I did notice that if there isn't enough room on the drive it will not delete the previous files.
What I did is create a job that deletes the backups everynight at 6pm. By 6pm the Enterprise backup has already taken the backups off of the server.
It's very simple. Create a batch file that does a del *.bak and call the batch file from the job step.
I hope this helps.|||Many times concerning automation system for deleting data, manual data deleting is good. In any case if something goes wrong you will be loss everything...|||We found that if you have a data base using the SIMPLE model but still do a transaction log backup then this feature may not work for ANY of the databases in the same maintenance plan. The number of backup files just grew and grew.|||I found that same issue with the transaction log bkup. Microsoft ...
If you have the time everyday and remember to do it, I guess a manual bkup is better.
On my end, we update our databases from our old cobol dos system with txt files so if we loose a day it's not a big deal. We can just reload the data.
The other option would be to talk to who ever is doing the enterprise bkups off of the server. Maybe they can move instead of copy the files.
I'm using SQL2K with SP4 2187. I have created a DB Maintenance wizard where the purging older than 1 day is set.
However, this feature seems not to be working, even if I tried two ways. Delete the scheduled job and recreate it - not successful, 2nd) delete the Maintenance Plan, still not successful.
Is this a bug or do I miss something here.Hi.
I've had the same issue. But with mine sometimes it works and sometimes it doesn't. I did notice that if there isn't enough room on the drive it will not delete the previous files.
What I did is create a job that deletes the backups everynight at 6pm. By 6pm the Enterprise backup has already taken the backups off of the server.
It's very simple. Create a batch file that does a del *.bak and call the batch file from the job step.
I hope this helps.|||Many times concerning automation system for deleting data, manual data deleting is good. In any case if something goes wrong you will be loss everything...|||We found that if you have a data base using the SIMPLE model but still do a transaction log backup then this feature may not work for ANY of the databases in the same maintenance plan. The number of backup files just grew and grew.|||I found that same issue with the transaction log bkup. Microsoft ...
If you have the time everyday and remember to do it, I guess a manual bkup is better.
On my end, we update our databases from our old cobol dos system with txt files so if we loose a day it's not a big deal. We can just reload the data.
The other option would be to talk to who ever is doing the enterprise bkups off of the server. Maybe they can move instead of copy the files.
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)