what can I look at to determine why a backup failed. I have a maintence pla
n that does a full backup once a week and another plan that will do a transa
ction log backup every day at 1am. The full backups are running fine. The
daily backup of the trans l
og fails everyday. The SQL Server log does not mention the failed backup.
The History of the job does say failed but gives no reason. The Server (box
) has an entry in the Application Log but it is not much better; it just say
s failed. What can I do to
troubleshoot this?Is your database in Simple recovery mode? You can't back up the
transactionlog in simple recovery mode, only in Bulk Logged or Full recovery
mode.
Jacco Schalkwijk
SQL Server MVP
"rich" <anonymous@.discussions.microsoft.com> wrote in message
news:8354B199-B0F2-4FFD-919B-17841BB1EF66@.microsoft.com...
> what can I look at to determine why a backup failed. I have a maintence
plan that does a full backup once a week and another plan that will do a
transaction log backup every day at 1am. The full backups are running fine.
The daily backup of the trans log fails everyday. The SQL Server log does
not mention the failed backup. The History of the job does say failed but
gives no reason. The Server (box) has an entry in the Application Log but
it is not much better; it just says failed. What can I do to troubleshoot
this?|||Outstanding Jacco! Two out of the fourteen databases I was trying to backup
the transaction log on were set to "simple". Those happen to be the two I
did not make! Thanks for the tip!|||Another thing you can do for the future is go to the Scheduled Task itself,
Go to Steps and edit the Step, Go to Advanced and set an output file. This
way you can always look at the file to see why something failed.
Jeff Duncan
MCDBA, MCSE+I
Showing posts with label determine. Show all posts
Showing posts with label determine. Show all posts
Monday, March 12, 2012
failed backup
what can I look at to determine why a backup failed. I have a maintence plan that does a full backup once a week and another plan that will do a transaction log backup every day at 1am. The full backups are running fine. The daily backup of the trans l
og fails everyday. The SQL Server log does not mention the failed backup. The History of the job does say failed but gives no reason. The Server (box) has an entry in the Application Log but it is not much better; it just says failed. What can I do to
troubleshoot this?
Is your database in Simple recovery mode? You can't back up the
transactionlog in simple recovery mode, only in Bulk Logged or Full recovery
mode.
Jacco Schalkwijk
SQL Server MVP
"rich" <anonymous@.discussions.microsoft.com> wrote in message
news:8354B199-B0F2-4FFD-919B-17841BB1EF66@.microsoft.com...
> what can I look at to determine why a backup failed. I have a maintence
plan that does a full backup once a week and another plan that will do a
transaction log backup every day at 1am. The full backups are running fine.
The daily backup of the trans log fails everyday. The SQL Server log does
not mention the failed backup. The History of the job does say failed but
gives no reason. The Server (box) has an entry in the Application Log but
it is not much better; it just says failed. What can I do to troubleshoot
this?
|||Outstanding Jacco! Two out of the fourteen databases I was trying to backup the transaction log on were set to "simple". Those happen to be the two I did not make! Thanks for the tip!
|||Another thing you can do for the future is go to the Scheduled Task itself, Go to Steps and edit the Step, Go to Advanced and set an output file. This way you can always look at the file to see why something failed.
Jeff Duncan
MCDBA, MCSE+I
og fails everyday. The SQL Server log does not mention the failed backup. The History of the job does say failed but gives no reason. The Server (box) has an entry in the Application Log but it is not much better; it just says failed. What can I do to
troubleshoot this?
Is your database in Simple recovery mode? You can't back up the
transactionlog in simple recovery mode, only in Bulk Logged or Full recovery
mode.
Jacco Schalkwijk
SQL Server MVP
"rich" <anonymous@.discussions.microsoft.com> wrote in message
news:8354B199-B0F2-4FFD-919B-17841BB1EF66@.microsoft.com...
> what can I look at to determine why a backup failed. I have a maintence
plan that does a full backup once a week and another plan that will do a
transaction log backup every day at 1am. The full backups are running fine.
The daily backup of the trans log fails everyday. The SQL Server log does
not mention the failed backup. The History of the job does say failed but
gives no reason. The Server (box) has an entry in the Application Log but
it is not much better; it just says failed. What can I do to troubleshoot
this?
|||Outstanding Jacco! Two out of the fourteen databases I was trying to backup the transaction log on were set to "simple". Those happen to be the two I did not make! Thanks for the tip!
|||Another thing you can do for the future is go to the Scheduled Task itself, Go to Steps and edit the Step, Go to Advanced and set an output file. This way you can always look at the file to see why something failed.
Jeff Duncan
MCDBA, MCSE+I
Friday, February 24, 2012
Extremely high number of pages/sec
Hello!
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
Igor
First of all, I would like to rule out OS as primary suspect. Is there a way
to pinpoint SQL Server SPID as a source?
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:09f001c5146a$630ad3b0$a401280a@.phx.gbl...[vbcol=seagreen]
> You can run profiler, and include textdata, writes/reads
> columns in the trace. You'll be able to see what SPs/SQL
> commands have intensive io operations.
> OJ
> It is averaging over
> determine what process
> SPID. Is there an
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
Igor
First of all, I would like to rule out OS as primary suspect. Is there a way
to pinpoint SQL Server SPID as a source?
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:09f001c5146a$630ad3b0$a401280a@.phx.gbl...[vbcol=seagreen]
> You can run profiler, and include textdata, writes/reads
> columns in the trace. You'll be able to see what SPs/SQL
> commands have intensive io operations.
> OJ
> It is averaging over
> determine what process
> SPID. Is there an
Extremely High number of page/sec
Hello!
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
Igor
Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
I should have added that high Read counts should be looked at as well.
David Gugick
Imceda Software
www.imceda.com
|||Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
Look for transactions with high CPU and/or high duration. You can use
Profiler for this or a number of SQL performance profiling tools (we
offer Coefficient).
David Gugick
Imceda Software
www.imceda.com
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
Igor
Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
I should have added that high Read counts should be looked at as well.
David Gugick
Imceda Software
www.imceda.com
|||Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
Look for transactions with high CPU and/or high duration. You can use
Profiler for this or a number of SQL performance profiling tools (we
offer Coefficient).
David Gugick
Imceda Software
www.imceda.com
Extremely High number of page/sec
Hello!
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
IgorIgor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
I should have added that high Read counts should be looked at as well.
--
David Gugick
Imceda Software
www.imceda.com|||Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
Look for transactions with high CPU and/or high duration. You can use
Profiler for this or a number of SQL performance profiling tools (we
offer Coefficient).
--
David Gugick
Imceda Software
www.imceda.com
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
IgorIgor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
I should have added that high Read counts should be looked at as well.
--
David Gugick
Imceda Software
www.imceda.com|||Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
Look for transactions with high CPU and/or high duration. You can use
Profiler for this or a number of SQL performance profiling tools (we
offer Coefficient).
--
David Gugick
Imceda Software
www.imceda.com
Extremely High number of page/sec
Hello!
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
IgorIgor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
I should have added that high Read counts should be looked at as well.
David Gugick
Imceda Software
www.imceda.com|||Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
Look for transactions with high CPU and/or high duration. You can use
Profiler for this or a number of SQL performance profiling tools (we
offer Coefficient).
David Gugick
Imceda Software
www.imceda.com
I have noticed very high number of page/sec in perfmon. It is averaging over
1000 pages/sec.I would like to isolate this issue to determine what process
is causing excessive pagination and possibly SQL server SPID. Is there an
easy way to troubleshoot the source of pagination?
Thanks,
IgorIgor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
I should have added that high Read counts should be looked at as well.
David Gugick
Imceda Software
www.imceda.com|||Igor Marchenko wrote:
> Hello!
> I have noticed very high number of page/sec in perfmon. It is
> averaging over 1000 pages/sec.I would like to isolate this issue to
> determine what process is causing excessive pagination and possibly
> SQL server SPID. Is there an easy way to troubleshoot the source of
> pagination?
> Thanks,
> Igor
Look for transactions with high CPU and/or high duration. You can use
Profiler for this or a number of SQL performance profiling tools (we
offer Coefficient).
David Gugick
Imceda Software
www.imceda.com
Subscribe to:
Posts (Atom)