Model backup failed

Good morning,
I am new to sql server and I have an issue with my backups.
So I set up these jobs:
Backup for System database:
Model, Master, MSDB DATABASE separately (every day at 22h)
Model, Master, MSDB log separately (every hour, between 5h-21h)
Backup for User Database
Database User (every day at 23h)
Database Log (every hour, between 02h-21h)
2 Plan Maintenance
Integrity Checks for all Database (System + User)
Optimization Job for all Database (System + User)
Why does my model backup and msdb log failed ? any idea?
Thanks
InaCan you post us the contents of your error log file please!
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> Good morning,
> I am new to sql server and I have an issue with my backups.
> So I set up these jobs:
> Backup for System database:
> Model, Master, MSDB DATABASE separately (every day at 22h)
> Model, Master, MSDB log separately (every hour, between 5h-21h)
> Backup for User Database
> Database User (every day at 23h)
> Database Log (every hour, between 02h-21h)
> 2 Plan Maintenance
> Integrity Checks for all Database (System + User)
> Optimization Job for all Database (System + User)
> Why does my model backup and msdb log failed ? any idea?
> Thanks
> Ina
>|||Immy wrote:
> Can you post us the contents of your error log file please!
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> > Good morning,
> >
> > I am new to sql server and I have an issue with my backups.
> >
> > So I set up these jobs:
> >
> > Backup for System database:
> >
> > Model, Master, MSDB DATABASE separately (every day at 22h)
> > Model, Master, MSDB log separately (every hour, between 5h-21h)
> >
> > Backup for User Database
> >
> > Database User (every day at 23h)
> > Database Log (every hour, between 02h-21h)
> >
> > 2 Plan Maintenance
> > Integrity Checks for all Database (System + User)
> > Optimization Job for all Database (System + User)
> >
> > Why does my model backup and msdb log failed ? any idea?
> >
> > Thanks
> >
> > Ina
> >
What is recovery model msdb database? If it is simple you log backup
will fail
For model database backup failure look in error log , it will have
detailed information about it.
Regards
Amish Shah|||"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> Good morning,
> I am new to sql server and I have an issue with my backups.
> So I set up these jobs:
> Backup for System database:
> Model, Master, MSDB DATABASE separately (every day at 22h)
> Model, Master, MSDB log separately (every hour, between 5h-21h)
> Backup for User Database
> Database User (every day at 23h)
> Database Log (every hour, between 02h-21h)
> 2 Plan Maintenance
> Integrity Checks for all Database (System + User)
> Optimization Job for all Database (System + User)
> Why does my model backup and msdb log failed ? any idea?
Beacuse they are in SIMPLE recovery mode and there's no need for a
logbackup.
The full should work fine though.
> Thanks
> Ina
>|||Hi,
What is the error you are getting?
First of all there is no need to backup the log for Model and Master
database; this is because we
are not supposed to do manipulations into these system databases.
Incase if you are getting errors in transaction log backup then verify the
recovery model for MSDB and Model databases.
For transaction log backup the recovery model should be either Bulk_logged
or Full.
Thanks
Hari
SQL Server MVP
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> Good morning,
> I am new to sql server and I have an issue with my backups.
> So I set up these jobs:
> Backup for System database:
> Model, Master, MSDB DATABASE separately (every day at 22h)
> Model, Master, MSDB log separately (every hour, between 5h-21h)
> Backup for User Database
> Database User (every day at 23h)
> Database Log (every hour, between 02h-21h)
> 2 Plan Maintenance
> Integrity Checks for all Database (System + User)
> Optimization Job for all Database (System + User)
> Why does my model backup and msdb log failed ? any idea?
> Thanks
> Ina
>|||Thanks guys.
It was because the MSDB Database was set up to simple instead of Full.
I changed it
but the model DB backup I do not know why it is failing
The job failed. The Job was invoked by Schedule 26 (Schedule 1). The
last step to run was step 1 (Step 1).
This is the job error I get.
Ina
I thing
Hari Prasad wrote:
> Hi,
> What is the error you are getting?
> First of all there is no need to backup the log for Model and Master
> database; this is because we
> are not supposed to do manipulations into these system databases.
> Incase if you are getting errors in transaction log backup then verify the
> recovery model for MSDB and Model databases.
> For transaction log backup the recovery model should be either Bulk_logged
> or Full.
> Thanks
> Hari
> SQL Server MVP
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> > Good morning,
> >
> > I am new to sql server and I have an issue with my backups.
> >
> > So I set up these jobs:
> >
> > Backup for System database:
> >
> > Model, Master, MSDB DATABASE separately (every day at 22h)
> > Model, Master, MSDB log separately (every hour, between 5h-21h)
> >
> > Backup for User Database
> >
> > Database User (every day at 23h)
> > Database Log (every hour, between 02h-21h)
> >
> > 2 Plan Maintenance
> > Integrity Checks for all Database (System + User)
> > Optimization Job for all Database (System + User)
> >
> > Why does my model backup and msdb log failed ? any idea?
> >
> > Thanks
> >
> > Ina
> >|||Specify a report file for the Maint Plan and check for the SQL Server errors in that report file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1155043376.504435.46880@.n13g2000cwa.googlegroups.com...
> Thanks guys.
> It was because the MSDB Database was set up to simple instead of Full.
> I changed it
> but the model DB backup I do not know why it is failing
> The job failed. The Job was invoked by Schedule 26 (Schedule 1). The
> last step to run was step 1 (Step 1).
> This is the job error I get.
> Ina
> I thing
> Hari Prasad wrote:
>> Hi,
>> What is the error you are getting?
>> First of all there is no need to backup the log for Model and Master
>> database; this is because we
>> are not supposed to do manipulations into these system databases.
>> Incase if you are getting errors in transaction log backup then verify the
>> recovery model for MSDB and Model databases.
>> For transaction log backup the recovery model should be either Bulk_logged
>> or Full.
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "ina" <roberta.inalbon@.gmail.com> wrote in message
>> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
>> > Good morning,
>> >
>> > I am new to sql server and I have an issue with my backups.
>> >
>> > So I set up these jobs:
>> >
>> > Backup for System database:
>> >
>> > Model, Master, MSDB DATABASE separately (every day at 22h)
>> > Model, Master, MSDB log separately (every hour, between 5h-21h)
>> >
>> > Backup for User Database
>> >
>> > Database User (every day at 23h)
>> > Database Log (every hour, between 02h-21h)
>> >
>> > 2 Plan Maintenance
>> > Integrity Checks for all Database (System + User)
>> > Optimization Job for all Database (System + User)
>> >
>> > Why does my model backup and msdb log failed ? any idea?
>> >
>> > Thanks
>> >
>> > Ina
>> >
>|||Thank you all for this good advice I will check it.
Ina
Tibor Karaszi wrote:
> Specify a report file for the Maint Plan and check for the SQL Server errors in that report file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1155043376.504435.46880@.n13g2000cwa.googlegroups.com...
> > Thanks guys.
> >
> > It was because the MSDB Database was set up to simple instead of Full.
> > I changed it
> > but the model DB backup I do not know why it is failing
> >
> > The job failed. The Job was invoked by Schedule 26 (Schedule 1). The
> > last step to run was step 1 (Step 1).
> >
> > This is the job error I get.
> >
> > Ina
> >
> > I thing
> > Hari Prasad wrote:
> >> Hi,
> >>
> >> What is the error you are getting?
> >>
> >> First of all there is no need to backup the log for Model and Master
> >> database; this is because we
> >> are not supposed to do manipulations into these system databases.
> >>
> >> Incase if you are getting errors in transaction log backup then verify the
> >> recovery model for MSDB and Model databases.
> >> For transaction log backup the recovery model should be either Bulk_logged
> >> or Full.
> >>
> >> Thanks
> >> Hari
> >> SQL Server MVP
> >>
> >>
> >> "ina" <roberta.inalbon@.gmail.com> wrote in message
> >> news:1155022867.432337.303640@.75g2000cwc.googlegroups.com...
> >> > Good morning,
> >> >
> >> > I am new to sql server and I have an issue with my backups.
> >> >
> >> > So I set up these jobs:
> >> >
> >> > Backup for System database:
> >> >
> >> > Model, Master, MSDB DATABASE separately (every day at 22h)
> >> > Model, Master, MSDB log separately (every hour, between 5h-21h)
> >> >
> >> > Backup for User Database
> >> >
> >> > Database User (every day at 23h)
> >> > Database Log (every hour, between 02h-21h)
> >> >
> >> > 2 Plan Maintenance
> >> > Integrity Checks for all Database (System + User)
> >> > Optimization Job for all Database (System + User)
> >> >
> >> > Why does my model backup and msdb log failed ? any idea?
> >> >
> >> > Thanks
> >> >
> >> > Ina
> >> >
> >

Missing History for Jobs (msdb.dbo.sysjobhistory)

New server running our SQL... upgrade from Advanced 2000 to Enterprise
2003... our SQL Instance normally records all history (View History from Job
s
in SQL Agent). For some reason, currently unknown, history disappears every
so often. In this case, all history from 11/24 going backward is gone. All
history from 11/25 through today is here. This happened previously. Is
there any logical explanation for this? I'd settle for a server reboot, but
to my knowledge, this did not happen either.
Also there is a disk space problem on one of the drives. The msdb does not
touch that drive so, in my way of thinking the drive space issue cannot be
connected to the missing history (sysjobhistory). Is this logical to assume
?
An additional thought comes to mind. The jobs were imported from one server
to another. The owner was either the service account (with plenty of
permission) or the sa account, but the jobs were recreated from script using
the sa login. Could this have an effect on the job history?
--
Regards,
JamieAlso I believe this is happenning each week. Saturday night or Sunday
morning to be sure.
--
Regards,
Jamie
"thejamie" wrote:

> New server running our SQL... upgrade from Advanced 2000 to Enterprise
> 2003... our SQL Instance normally records all history (View History from J
obs
> in SQL Agent). For some reason, currently unknown, history disappears eve
ry
> so often. In this case, all history from 11/24 going backward is gone. A
ll
> history from 11/25 through today is here. This happened previously. Is
> there any logical explanation for this? I'd settle for a server reboot, b
ut
> to my knowledge, this did not happen either.
> Also there is a disk space problem on one of the drives. The msdb does no
t
> touch that drive so, in my way of thinking the drive space issue cannot be
> connected to the missing history (sysjobhistory). Is this logical to assu
me?
> An additional thought comes to mind. The jobs were imported from one serv
er
> to another. The owner was either the service account (with plenty of
> permission) or the sa account, but the jobs were recreated from script usi
ng
> the sa login. Could this have an effect on the job history?
> --
> Regards,
> Jamie|||thejamie,
Recreating the jobs would cause them to have a new job_id, so any history
records that might still exist in sysjobhistory will no longer join to
existing jobs. (If you still have your previous server and can figure out
the old job_id to new job_id mapping, you could update rowsn in your
sysjobhistory and all would be well.)
Also, make sure that your SQL Agent Properties - History settings are the
same on you new server as your old, or you will find SQL Agent (by default)
deleting history fairly frequently.
RLF
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:C078BDDA-ED20-4F42-AD0E-2FF1AED4EE7F@.microsoft.com...
> New server running our SQL... upgrade from Advanced 2000 to Enterprise
> 2003... our SQL Instance normally records all history (View History from
> Jobs
> in SQL Agent). For some reason, currently unknown, history disappears
> every
> so often. In this case, all history from 11/24 going backward is gone.
> All
> history from 11/25 through today is here. This happened previously. Is
> there any logical explanation for this? I'd settle for a server reboot,
> but
> to my knowledge, this did not happen either.
> Also there is a disk space problem on one of the drives. The msdb does
> not
> touch that drive so, in my way of thinking the drive space issue cannot be
> connected to the missing history (sysjobhistory). Is this logical to
> assume?
> An additional thought comes to mind. The jobs were imported from one
> server
> to another. The owner was either the service account (with plenty of
> permission) or the sa account, but the jobs were recreated from script
> using
> the sa login. Could this have an effect on the job history?
> --
> Regards,
> Jamie|||Thanks for the reply Russell. Actually, I moved the data over on 11/4. I
didn't expect any history to go back before the move. What bothers me is
that on Saturday I had history going back to 11/4. On Sunday, it extended
only from 11/25. Everything prior to 11/24 is wiped. It still exists in
sysjobhistory. I am not the sole DBA so it is possible that someone other
than myself wiped it, but I have to presume that is not the case. It isn't
vital. I can filter the log for a given job to get the history. The histor
y
was set to 1000 - I have lots of disk space at the moment so I moved it to
10000 and from 100 to 1000 on the rows. Still a mystery. I suspect that
the disk space on the one drive being low may have something to do with the
history disappearing.
--
Regards,
Jamie
"Russell Fields" wrote:

> thejamie,
> Recreating the jobs would cause them to have a new job_id, so any history
> records that might still exist in sysjobhistory will no longer join to
> existing jobs. (If you still have your previous server and can figure out
> the old job_id to new job_id mapping, you could update rowsn in your
> sysjobhistory and all would be well.)
> Also, make sure that your SQL Agent Properties - History settings are the
> same on you new server as your old, or you will find SQL Agent (by default
)
> deleting history fairly frequently.
> RLF
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:C078BDDA-ED20-4F42-AD0E-2FF1AED4EE7F@.microsoft.com...
>
>|||Jamie,
If the rows are still in sysjobhistory then they should connect to the jobs.
If the jobs will not show history further back than 11/24, then did someone
redeploy the jobs again, such that they got new job_ids?
RLF
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:A8C507C7-D1B6-46FF-AD2F-9E9EBCF829F5@.microsoft.com...[vbcol=seagreen]
> Thanks for the reply Russell. Actually, I moved the data over on 11/4. I
> didn't expect any history to go back before the move. What bothers me is
> that on Saturday I had history going back to 11/4. On Sunday, it extended
> only from 11/25. Everything prior to 11/24 is wiped. It still exists in
> sysjobhistory. I am not the sole DBA so it is possible that someone other
> than myself wiped it, but I have to presume that is not the case. It
> isn't
> vital. I can filter the log for a given job to get the history. The
> history
> was set to 1000 - I have lots of disk space at the moment so I moved it to
> 10000 and from 100 to 1000 on the rows. Still a mystery. I suspect that
> the disk space on the one drive being low may have something to do with
> the
> history disappearing.
> --
> Regards,
> Jamie
>
> "Russell Fields" wrote:
>|||Sounds very possible. Thanks.
--
Regards,
Jamie
"Russell Fields" wrote:

> Jamie,
> If the rows are still in sysjobhistory then they should connect to the job
s.
> If the jobs will not show history further back than 11/24, then did someon
e
> redeploy the jobs again, such that they got new job_ids?
> RLF
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:A8C507C7-D1B6-46FF-AD2F-9E9EBCF829F5@.microsoft.com...
>
>