Hi
Im running a Windows 2003 server and MSSQL 2000 that manages some 45
databases. I created an maintenance plan that does an integrity check,
backups all databases, and backup all transactionlogs.
If I look at the "Jobs" list it looks like backing up the databases runs OK,
but both the integrity check and transaction log seams to fail.
If I look at the folder holding the backupfiles all transactionfiles looks
to be there (backup of all the transaction logs). So what makes the job
fail? If I look at the event log all transaction-log-backups complete OK,
but still the job ends in failure and the eventlog only states that the job
faild - not why it failed.
How can I track this problem? And is this why the transaction logs are not
truncated?
Regards
Jan Agermose
Hi
Within a job specify an output file to see what is going on.
<msde@.csite.com> wrote in message
news:epoOEnVUFHA.1044@.TK2MSFTNGP10.phx.gbl...
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs
OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the
job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>
|||Hello Jan,
Go to your maintenance plan in enterprise manager and right click on it.
Select "Maintenance Plan History...". In the Status dropdown, select
"Failed". You should now see a list of failed tasks in your plan. Look for a
plan with an activity of "Backup Transaction Log" and double click it. The
reason for failure will appear. My guess is that the database is in simple
recovery mode and you will get an error similar to "Backup can not be
performed on this database. This sub task is ignored".
All you have to do in this instance is remove databases that have simple
recovery from your maintenance plan, or change them to a different recovery
model (if that's what you need).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"msde@.csite.com" wrote:
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>
|||Ahhh :-) Of cause - I selsected to backup all databases - this includes
"master", "tempdb" and the test database "northwind". Doing a backup of the
transaction log fails.
I guess that means I need two plans
One for all user databases but not the system databases - this plan does a
databasebackup and a transactionlog backup.
And one for the system databases that does not try to backup the
transactionlog?
Regards
Jan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...[vbcol=seagreen]
> Hello Jan,
> Go to your maintenance plan in enterprise manager and right click on it.
> Select "Maintenance Plan History...". In the Status dropdown, select
> "Failed". You should now see a list of failed tasks in your plan. Look for
> a
> plan with an activity of "Backup Transaction Log" and double click it. The
> reason for failure will appear. My guess is that the database is in simple
> recovery mode and you will get an error similar to "Backup can not be
> performed on this database. This sub task is ignored".
> All you have to do in this instance is remove databases that have simple
> recovery from your maintenance plan, or change them to a different
> recovery
> model (if that's what you need).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> "msde@.csite.com" wrote:
|||You got the point, Jan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<msde@.csite.com> wrote in message news:O8YUBjbUFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Ahhh :-) Of cause - I selsected to backup all databases - this includes "master", "tempdb" and the
> test database "northwind". Doing a backup of the transaction log fails.
> I guess that means I need two plans
> One for all user databases but not the system databases - this plan does a databasebackup and a
> transactionlog backup.
> And one for the system databases that does not try to backup the transactionlog?
> Regards
> Jan
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
>
Showing posts with label mssql. Show all posts
Showing posts with label mssql. Show all posts
Friday, March 23, 2012
maintenance fails
Hi
Im running a Windows 2003 server and MSSQL 2000 that manages some 45
databases. I created an maintenance plan that does an integrity check,
backups all databases, and backup all transactionlogs.
If I look at the "Jobs" list it looks like backing up the databases runs OK,
but both the integrity check and transaction log seams to fail.
If I look at the folder holding the backupfiles all transactionfiles looks
to be there (backup of all the transaction logs). So what makes the job
fail? If I look at the event log all transaction-log-backups complete OK,
but still the job ends in failure and the eventlog only states that the job
faild - not why it failed.
How can I track this problem? And is this why the transaction logs are not
truncated?
Regards
Jan AgermoseHi
Within a job specify an output file to see what is going on.
<msde@.csite.com> wrote in message
news:epoOEnVUFHA.1044@.TK2MSFTNGP10.phx.gbl...
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs
OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the
job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Hello Jan,
Go to your maintenance plan in enterprise manager and right click on it.
Select "Maintenance Plan History...". In the Status dropdown, select
"Failed". You should now see a list of failed tasks in your plan. Look for a
plan with an activity of "Backup Transaction Log" and double click it. The
reason for failure will appear. My guess is that the database is in simple
recovery mode and you will get an error similar to "Backup can not be
performed on this database. This sub task is ignored".
All you have to do in this instance is remove databases that have simple
recovery from your maintenance plan, or change them to a different recovery
model (if that's what you need).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"msde@.csite.com" wrote:
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Ahhh :-) Of cause - I selsected to backup all databases - this includes
"master", "tempdb" and the test database "northwind". Doing a backup of the
transaction log fails.
I guess that means I need two plans
One for all user databases but not the system databases - this plan does a
databasebackup and a transactionlog backup.
And one for the system databases that does not try to backup the
transactionlog?
Regards
Jan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
> Hello Jan,
> Go to your maintenance plan in enterprise manager and right click on it.
> Select "Maintenance Plan History...". In the Status dropdown, select
> "Failed". You should now see a list of failed tasks in your plan. Look for
> a
> plan with an activity of "Backup Transaction Log" and double click it. The
> reason for failure will appear. My guess is that the database is in simple
> recovery mode and you will get an error similar to "Backup can not be
> performed on this database. This sub task is ignored".
> All you have to do in this instance is remove databases that have simple
> recovery from your maintenance plan, or change them to a different
> recovery
> model (if that's what you need).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> "msde@.csite.com" wrote:
>> Hi
>> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
>> databases. I created an maintenance plan that does an integrity check,
>> backups all databases, and backup all transactionlogs.
>> If I look at the "Jobs" list it looks like backing up the databases runs
>> OK,
>> but both the integrity check and transaction log seams to fail.
>> If I look at the folder holding the backupfiles all transactionfiles
>> looks
>> to be there (backup of all the transaction logs). So what makes the job
>> fail? If I look at the event log all transaction-log-backups complete OK,
>> but still the job ends in failure and the eventlog only states that the
>> job
>> faild - not why it failed.
>> How can I track this problem? And is this why the transaction logs are
>> not
>> truncated?
>> Regards
>> Jan Agermose
>>
>>|||You got the point, Jan.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<msde@.csite.com> wrote in message news:O8YUBjbUFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Ahhh :-) Of cause - I selsected to backup all databases - this includes "master", "tempdb" and the
> test database "northwind". Doing a backup of the transaction log fails.
> I guess that means I need two plans
> One for all user databases but not the system databases - this plan does a databasebackup and a
> transactionlog backup.
> And one for the system databases that does not try to backup the transactionlog?
> Regards
> Jan
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
>> Hello Jan,
>> Go to your maintenance plan in enterprise manager and right click on it.
>> Select "Maintenance Plan History...". In the Status dropdown, select
>> "Failed". You should now see a list of failed tasks in your plan. Look for a
>> plan with an activity of "Backup Transaction Log" and double click it. The
>> reason for failure will appear. My guess is that the database is in simple
>> recovery mode and you will get an error similar to "Backup can not be
>> performed on this database. This sub task is ignored".
>> All you have to do in this instance is remove databases that have simple
>> recovery from your maintenance plan, or change them to a different recovery
>> model (if that's what you need).
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> "msde@.csite.com" wrote:
>> Hi
>> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
>> databases. I created an maintenance plan that does an integrity check,
>> backups all databases, and backup all transactionlogs.
>> If I look at the "Jobs" list it looks like backing up the databases runs OK,
>> but both the integrity check and transaction log seams to fail.
>> If I look at the folder holding the backupfiles all transactionfiles looks
>> to be there (backup of all the transaction logs). So what makes the job
>> fail? If I look at the event log all transaction-log-backups complete OK,
>> but still the job ends in failure and the eventlog only states that the job
>> faild - not why it failed.
>> How can I track this problem? And is this why the transaction logs are not
>> truncated?
>> Regards
>> Jan Agermose
>>
>>
>sql
Im running a Windows 2003 server and MSSQL 2000 that manages some 45
databases. I created an maintenance plan that does an integrity check,
backups all databases, and backup all transactionlogs.
If I look at the "Jobs" list it looks like backing up the databases runs OK,
but both the integrity check and transaction log seams to fail.
If I look at the folder holding the backupfiles all transactionfiles looks
to be there (backup of all the transaction logs). So what makes the job
fail? If I look at the event log all transaction-log-backups complete OK,
but still the job ends in failure and the eventlog only states that the job
faild - not why it failed.
How can I track this problem? And is this why the transaction logs are not
truncated?
Regards
Jan AgermoseHi
Within a job specify an output file to see what is going on.
<msde@.csite.com> wrote in message
news:epoOEnVUFHA.1044@.TK2MSFTNGP10.phx.gbl...
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs
OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the
job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Hello Jan,
Go to your maintenance plan in enterprise manager and right click on it.
Select "Maintenance Plan History...". In the Status dropdown, select
"Failed". You should now see a list of failed tasks in your plan. Look for a
plan with an activity of "Backup Transaction Log" and double click it. The
reason for failure will appear. My guess is that the database is in simple
recovery mode and you will get an error similar to "Backup can not be
performed on this database. This sub task is ignored".
All you have to do in this instance is remove databases that have simple
recovery from your maintenance plan, or change them to a different recovery
model (if that's what you need).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"msde@.csite.com" wrote:
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Ahhh :-) Of cause - I selsected to backup all databases - this includes
"master", "tempdb" and the test database "northwind". Doing a backup of the
transaction log fails.
I guess that means I need two plans
One for all user databases but not the system databases - this plan does a
databasebackup and a transactionlog backup.
And one for the system databases that does not try to backup the
transactionlog?
Regards
Jan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
> Hello Jan,
> Go to your maintenance plan in enterprise manager and right click on it.
> Select "Maintenance Plan History...". In the Status dropdown, select
> "Failed". You should now see a list of failed tasks in your plan. Look for
> a
> plan with an activity of "Backup Transaction Log" and double click it. The
> reason for failure will appear. My guess is that the database is in simple
> recovery mode and you will get an error similar to "Backup can not be
> performed on this database. This sub task is ignored".
> All you have to do in this instance is remove databases that have simple
> recovery from your maintenance plan, or change them to a different
> recovery
> model (if that's what you need).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> "msde@.csite.com" wrote:
>> Hi
>> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
>> databases. I created an maintenance plan that does an integrity check,
>> backups all databases, and backup all transactionlogs.
>> If I look at the "Jobs" list it looks like backing up the databases runs
>> OK,
>> but both the integrity check and transaction log seams to fail.
>> If I look at the folder holding the backupfiles all transactionfiles
>> looks
>> to be there (backup of all the transaction logs). So what makes the job
>> fail? If I look at the event log all transaction-log-backups complete OK,
>> but still the job ends in failure and the eventlog only states that the
>> job
>> faild - not why it failed.
>> How can I track this problem? And is this why the transaction logs are
>> not
>> truncated?
>> Regards
>> Jan Agermose
>>
>>|||You got the point, Jan.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<msde@.csite.com> wrote in message news:O8YUBjbUFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Ahhh :-) Of cause - I selsected to backup all databases - this includes "master", "tempdb" and the
> test database "northwind". Doing a backup of the transaction log fails.
> I guess that means I need two plans
> One for all user databases but not the system databases - this plan does a databasebackup and a
> transactionlog backup.
> And one for the system databases that does not try to backup the transactionlog?
> Regards
> Jan
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
>> Hello Jan,
>> Go to your maintenance plan in enterprise manager and right click on it.
>> Select "Maintenance Plan History...". In the Status dropdown, select
>> "Failed". You should now see a list of failed tasks in your plan. Look for a
>> plan with an activity of "Backup Transaction Log" and double click it. The
>> reason for failure will appear. My guess is that the database is in simple
>> recovery mode and you will get an error similar to "Backup can not be
>> performed on this database. This sub task is ignored".
>> All you have to do in this instance is remove databases that have simple
>> recovery from your maintenance plan, or change them to a different recovery
>> model (if that's what you need).
>> --
>> Mark Allison, SQL Server MVP
>> http://www.markallison.co.uk
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602m.html
>>
>>
>> "msde@.csite.com" wrote:
>> Hi
>> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
>> databases. I created an maintenance plan that does an integrity check,
>> backups all databases, and backup all transactionlogs.
>> If I look at the "Jobs" list it looks like backing up the databases runs OK,
>> but both the integrity check and transaction log seams to fail.
>> If I look at the folder holding the backupfiles all transactionfiles looks
>> to be there (backup of all the transaction logs). So what makes the job
>> fail? If I look at the event log all transaction-log-backups complete OK,
>> but still the job ends in failure and the eventlog only states that the job
>> faild - not why it failed.
>> How can I track this problem? And is this why the transaction logs are not
>> truncated?
>> Regards
>> Jan Agermose
>>
>>
>sql
maintenance fails
Hi
Im running a Windows 2003 server and MSSQL 2000 that manages some 45
databases. I created an maintenance plan that does an integrity check,
backups all databases, and backup all transactionlogs.
If I look at the "Jobs" list it looks like backing up the databases runs OK,
but both the integrity check and transaction log seams to fail.
If I look at the folder holding the backupfiles all transactionfiles looks
to be there (backup of all the transaction logs). So what makes the job
fail? If I look at the event log all transaction-log-backups complete OK,
but still the job ends in failure and the eventlog only states that the job
faild - not why it failed.
How can I track this problem? And is this why the transaction logs are not
truncated?
Regards
Jan AgermoseHi
Within a job specify an output file to see what is going on.
<msde@.csite.com> wrote in message
news:epoOEnVUFHA.1044@.TK2MSFTNGP10.phx.gbl...
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs
OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the
job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Hello Jan,
Go to your maintenance plan in enterprise manager and right click on it.
Select "Maintenance Plan History...". In the Status dropdown, select
"Failed". You should now see a list of failed tasks in your plan. Look for a
plan with an activity of "Backup Transaction Log" and double click it. The
reason for failure will appear. My guess is that the database is in simple
recovery mode and you will get an error similar to "Backup can not be
performed on this database. This sub task is ignored".
All you have to do in this instance is remove databases that have simple
recovery from your maintenance plan, or change them to a different recovery
model (if that's what you need).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"msde@.csite.com" wrote:
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs O
K,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the jo
b
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Ahhh :-) Of cause - I selsected to backup all databases - this includes
"master", "tempdb" and the test database "northwind". Doing a backup of the
transaction log fails.
I guess that means I need two plans
One for all user databases but not the system databases - this plan does a
databasebackup and a transactionlog backup.
And one for the system databases that does not try to backup the
transactionlog?
Regards
Jan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...[vbcol=seagreen]
> Hello Jan,
> Go to your maintenance plan in enterprise manager and right click on it.
> Select "Maintenance Plan History...". In the Status dropdown, select
> "Failed". You should now see a list of failed tasks in your plan. Look for
> a
> plan with an activity of "Backup Transaction Log" and double click it. The
> reason for failure will appear. My guess is that the database is in simple
> recovery mode and you will get an error similar to "Backup can not be
> performed on this database. This sub task is ignored".
> All you have to do in this instance is remove databases that have simple
> recovery from your maintenance plan, or change them to a different
> recovery
> model (if that's what you need).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> "msde@.csite.com" wrote:
>|||You got the point, Jan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<msde@.csite.com> wrote in message news:O8YUBjbUFHA.3280@.TK2MSFTNGP09.phx.gbl...en">
> Ahhh :-) Of cause - I selsected to backup all databases - this includes "m
aster", "tempdb" and the
> test database "northwind". Doing a backup of the transaction log fails.
> I guess that means I need two plans
> One for all user databases but not the system databases - this plan does a
databasebackup and a
> transactionlog backup.
> And one for the system databases that does not try to backup the transacti
onlog?
> Regards
> Jan
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
>
Im running a Windows 2003 server and MSSQL 2000 that manages some 45
databases. I created an maintenance plan that does an integrity check,
backups all databases, and backup all transactionlogs.
If I look at the "Jobs" list it looks like backing up the databases runs OK,
but both the integrity check and transaction log seams to fail.
If I look at the folder holding the backupfiles all transactionfiles looks
to be there (backup of all the transaction logs). So what makes the job
fail? If I look at the event log all transaction-log-backups complete OK,
but still the job ends in failure and the eventlog only states that the job
faild - not why it failed.
How can I track this problem? And is this why the transaction logs are not
truncated?
Regards
Jan AgermoseHi
Within a job specify an output file to see what is going on.
<msde@.csite.com> wrote in message
news:epoOEnVUFHA.1044@.TK2MSFTNGP10.phx.gbl...
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs
OK,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the
job
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Hello Jan,
Go to your maintenance plan in enterprise manager and right click on it.
Select "Maintenance Plan History...". In the Status dropdown, select
"Failed". You should now see a list of failed tasks in your plan. Look for a
plan with an activity of "Backup Transaction Log" and double click it. The
reason for failure will appear. My guess is that the database is in simple
recovery mode and you will get an error similar to "Backup can not be
performed on this database. This sub task is ignored".
All you have to do in this instance is remove databases that have simple
recovery from your maintenance plan, or change them to a different recovery
model (if that's what you need).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"msde@.csite.com" wrote:
> Hi
> Im running a Windows 2003 server and MSSQL 2000 that manages some 45
> databases. I created an maintenance plan that does an integrity check,
> backups all databases, and backup all transactionlogs.
> If I look at the "Jobs" list it looks like backing up the databases runs O
K,
> but both the integrity check and transaction log seams to fail.
> If I look at the folder holding the backupfiles all transactionfiles looks
> to be there (backup of all the transaction logs). So what makes the job
> fail? If I look at the event log all transaction-log-backups complete OK,
> but still the job ends in failure and the eventlog only states that the jo
b
> faild - not why it failed.
> How can I track this problem? And is this why the transaction logs are not
> truncated?
> Regards
> Jan Agermose
>
>|||Ahhh :-) Of cause - I selsected to backup all databases - this includes
"master", "tempdb" and the test database "northwind". Doing a backup of the
transaction log fails.
I guess that means I need two plans
One for all user databases but not the system databases - this plan does a
databasebackup and a transactionlog backup.
And one for the system databases that does not try to backup the
transactionlog?
Regards
Jan
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...[vbcol=seagreen]
> Hello Jan,
> Go to your maintenance plan in enterprise manager and right click on it.
> Select "Maintenance Plan History...". In the Status dropdown, select
> "Failed". You should now see a list of failed tasks in your plan. Look for
> a
> plan with an activity of "Backup Transaction Log" and double click it. The
> reason for failure will appear. My guess is that the database is in simple
> recovery mode and you will get an error similar to "Backup can not be
> performed on this database. This sub task is ignored".
> All you have to do in this instance is remove databases that have simple
> recovery from your maintenance plan, or change them to a different
> recovery
> model (if that's what you need).
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> "msde@.csite.com" wrote:
>|||You got the point, Jan.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<msde@.csite.com> wrote in message news:O8YUBjbUFHA.3280@.TK2MSFTNGP09.phx.gbl...en">
> Ahhh :-) Of cause - I selsected to backup all databases - this includes "m
aster", "tempdb" and the
> test database "northwind". Doing a backup of the transaction log fails.
> I guess that means I need two plans
> One for all user databases but not the system databases - this plan does a
databasebackup and a
> transactionlog backup.
> And one for the system databases that does not try to backup the transacti
onlog?
> Regards
> Jan
>
> "Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
> news:7D5CF0AB-9C9C-4675-8CCA-BFFA2E3092FB@.microsoft.com...
>
Saturday, February 25, 2012
Ok, folks, a question for you. I wanna send email through MSSQL Server 2000
using SMTP protocol.HOW?Check out
using SMTP protocol.HOW?Check out
http://www.sqldev.net/xp/xpsmtp.htm
John
"Licemjer" <licemjer@.licemjer.hr> wrote in message
news:bqq62m$op5$1@.ls219.htnet.hr...
> Ok, folks, a question for you. I wanna send email through MSSQL Server
2000
> using SMTP protocol.HOW?
Monday, February 20, 2012
LSASS.exe taking over CPU on incremental update (FT-Catalog)
Hello everyone,
I've managed to get FT-Population running after being at war with a changed user-account of mssql service (switched both back to localsystem, now the population works fine).
But if i want to do an incremental update, LSASS.EXE takes over CPU (as much as it gets) and my SQL is not available for any other queries.
I've tried this on similar tables with less records, but the error is the same (none, peaking cpu until completion).
The main problem is that the big table seems to take ~3-5 hours for an incremental update, and i cannot have the system running 100% (on 4 cpus) at this time...
System information:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 on Windows NT 5.0 (Build 2195: Service Pack 4)
CPU: 4x CPU (don't know the clock)
Memory: 1.5 G
I have browsed newsgroups and other forums for a solution, but couldn't find any answer.
I've checked the service trough TokenMon and FileMon (sysinternals) but couldnt find any errors...
I would really appreciate any help!!
Thank you for every post!no one?|||This sounds like a fairly obvious and severe infinite-loop problem that surely must have been reported on Microsoft's support-site, and possibly fixed there. This sounds like a pretty severe "fire" and you can't possibly be the first one to have smelled that smoke.|||i've searched newsposts, kb's - found nothing... nothing with the exact same error, but in combination with other services...|||found it!
- rename main admin account back to main setting (administrator)
- re-install sp3a (sql)
now it works fine! :D
I've managed to get FT-Population running after being at war with a changed user-account of mssql service (switched both back to localsystem, now the population works fine).
But if i want to do an incremental update, LSASS.EXE takes over CPU (as much as it gets) and my SQL is not available for any other queries.
I've tried this on similar tables with less records, but the error is the same (none, peaking cpu until completion).
The main problem is that the big table seems to take ~3-5 hours for an incremental update, and i cannot have the system running 100% (on 4 cpus) at this time...
System information:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright (c) 1988-2000 on Windows NT 5.0 (Build 2195: Service Pack 4)
CPU: 4x CPU (don't know the clock)
Memory: 1.5 G
I have browsed newsgroups and other forums for a solution, but couldn't find any answer.
I've checked the service trough TokenMon and FileMon (sysinternals) but couldnt find any errors...
I would really appreciate any help!!
Thank you for every post!no one?|||This sounds like a fairly obvious and severe infinite-loop problem that surely must have been reported on Microsoft's support-site, and possibly fixed there. This sounds like a pretty severe "fire" and you can't possibly be the first one to have smelled that smoke.|||i've searched newsposts, kb's - found nothing... nothing with the exact same error, but in combination with other services...|||found it!
- rename main admin account back to main setting (administrator)
- re-install sp3a (sql)
now it works fine! :D
Subscribe to:
Posts (Atom)