Hi Mladen,
These are SBT channels using Oracle Secure Backup Cloud Module (OSBWS).
No backup suite is being used - these are simply command line RMAN jobs run
from a scheduler. I'll have a look at profiling the CPU usage a bit more and
see where that takes me. Unfortunately, as mentioned, I do not have a
baseline available for the "good" backups.
Thanks,
Charlotte
On Tuesday, November 5, 2019, 12:14:19 PM GMT, Mladen Gogala
<gogala.mladen@xxxxxxxxx> wrote:
Hi Charlotte!
What kind of a channel do you allocate, disk or SBT? If SBT, what kind of
backup suite are you using? Stuff like NetBackup, Commvault or TSM is highly
complex and dependent on may factors.
Regards
On 11/5/19 3:27 AM, Charlotte Hammond (Redacted sender charlottejanehammond
for DMARC) wrote:
Hi Nenad,
The average run queue is about 20 (peaking at about 25) whilst the backup is
running. The figure is the same for both the slow and fast runs. I've
graphed them out and they look pretty much the same. This is a fairly high
figure but it doesn't seem to have changed.
We have 16 backup channels and 16 CPUs (2 threads per processor).
Yes, the compression is "basic" but that has not changed.
Thanks, Charlotte
On Monday, November 4, 2019, 09:26:33 PM GMT, Noveljic Nenad
<nenad.noveljic@xxxxxxxxxxxx> wrote:
Hi Charlotte,
Run queue length of 20-25 means the number of processes competing for CPU.
How many CPUs do you have? How many RMAN channels are configured?
What was the average length of run queues during a good run?
With regard to backup compression, basic will use significantly more CPU than
the others, but as you mentioned that the backup size is the same, the backup
algorithm probably hasn‘t changed.
I‘d therefore suggest first clarifying the CPU load on the server.
Best regards,
Nenad
Von: Charlotte Hammond <charlottejanehammond@xxxxxxxxx> Datum Montag, 04.
Nov. 2019, 6:15 PM An: dmarc-noreply@xxxxxxxxxxxxx
<dmarc-noreply@xxxxxxxxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>, Noveljic
Nenad <nenad.noveljic@xxxxxxxxxxxx> Betreff: Re: Sudden Backup Slowdown
Hi Nenad,
The only real difference between the AWR reports is that the statistic "RMAN
cpu time (backup/restore)" is about 50% longer than before. Sar shows the run
queues as 0 (or close to 0) before and after the backup in both cases and
similar during the backup (about 20-25).
Thanks, Charlotte On Monday, November 4, 2019, 02:51:38 PM GMT,
Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx> wrote:
#yiv4923083433 -- -- filtered {font-family:Helvetica;}#yiv4923083433
filtered {}#yiv4923083433 filtered {font-family:Calibri;}#yiv4923083433
p.yiv4923083433MsoNormal, #yiv4923083433 li.yiv4923083433MsoNormal,
#yiv4923083433 div.yiv4923083433MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New
serif;}#yiv4923083433 a:link, #yiv4923083433 span.yiv4923083433MsoHyperlink
{color:blue;text-decoration:underline;}#yiv4923083433 a:visited, #yiv4923083433
span.yiv4923083433MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv4923083433
p.yiv4923083433msonormal0, #yiv4923083433 li.yiv4923083433msonormal0,
#yiv4923083433 div.yiv4923083433msonormal0
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:New
serif;}#yiv4923083433 span.yiv4923083433EmailStyle18
{font-family:sans-serif;color:#1F497D;}#yiv4923083433
.yiv4923083433MsoChpDefault {font-size:10.0pt;}#yiv4923083433 filtered
{margin:70.85pt 70.85pt 2.0cm 70.85pt;}#yiv4923083433
If there weren’t any idle CPUs during backup, I’d first verify the statement
“The server itself has no other activity during the backup window.” by
measuring the length of the run queues. In other words, to confirm there
aren’t any other processes competing for CPUs.
What differences do you see in AWR reports?
Best regards,
Nenad
https://nenadnoveljic.com/blog/
From: oracle-l-bounce@xxxxxxxxxxxxx<oracle-l-bounce@xxxxxxxxxxxxx> On Behalf Of
Charlotte Hammond
Sent: Montag, 4. November 2019 15:22
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: Sudden Backup Slowdown
Hello All,
I'm trying to explain why my level 0 rman backups have suddenly jumped from
8hours to 12 hours. The size of the backup has barely changed and there has
been no configuration changes. AWR and O/S statistics show that CPU for all
the channels are maxed out at ~99% (presumably backup compression) for most of
this time, both in the 8 hour case and 12 hour case. The server itself has no
other activity during the backup window.
This is on 11.2.0.4 on AWS EC2 backing up to S3 storage.
I'm not looking for tuning advise here (thanks though!) - I'm really hoping
for some advise on finding an explanation for the change in times. Given that
all it's doing is sitting on CPU I'm not sure what else I can investigate -
especially with limited ability to cross-reference it with the "good old" runs.
It's been 8 hours for months and months, and has now been 12 hours for the
last 3 weeks. There was no gradual increase - just a step change.
Thanks!
Charlotte
#yiv4923083433 -- p.yiv4923083433MsoNormal
{margin-bottom:.0001pt;font-size:11.0pt;margin-left:0cm;margin-right:0cm;margin-top:0cm;}#yiv4923083433
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
#yiv4923083433 -- p {font-family:Arial;font-size:9pt;}#yiv4923083433
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee you
should in particular not disseminate, distribute, modify or copy this e-mail.
Please notify the sender immediately by e-mail, if you have received this
message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall
prevail in any case, we take it as your authorization to correspond with you by
e-mail if you send us messages by e-mail. However, we reserve the right not to
execute orders and instructions transmitted by e-mail at any time and without
further explanation.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of Vontobel
Holding Ltd. and any of its affiliates (hereinafter collectively referred to as
"Vontobel Group") for any damages resulting from e-mail use is excluded. You
are advised that urgent and time sensitive messages should not be sent by
e-mail and if verification is required please request a printed version. Please
note that all e-mail communications to and from the Vontobel Group are subject
to electronic storage and review by Vontobel Group. Unless stated to the
contrary and without prejudice to any contractual agreements between you and
Vontobel Group which shall prevail in any case, e-mail-communication is for
informational purposes only and is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your consent
to forward you commercial communications. You can exercise, at any time and
under the terms established under current regulation, your rights. If you
prefer not to receive any further communications, please contact your client
relationship manager if you are a client of Vontobel Group or notify the
sender. Please note for an exact reference to the affected group entity the
corporate e-mail signature. For further information about data privacy at
Vontobel Group please consult www.vontobel.com.
#yiv4923083433 p {font-family:Arial;font-size:9pt;}
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee you
should in particular not disseminate, distribute, modify or copy this e-mail.
Please notify the sender immediately by e-mail, if you have received this
message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which shall
prevail in any case, we take it as your authorization to correspond with you by
e-mail if you send us messages by e-mail. However, we reserve the right not to
execute orders and instructions transmitted by e-mail at any time and without
further explanation.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of Vontobel
Holding Ltd. and any of its affiliates (hereinafter collectively referred to
as "Vontobel Group") for any damages resulting from e-mail use is excluded. You
are advised that urgent and time sensitive messages should not be sent by
e-mail and if verification is required please request a printed version. Please
note that all e-mail communications to and from the Vontobel Group are subject
to electronic storage and review by Vontobel Group. Unless stated to the
contrary and without prejudice to any contractual agreements between you and
Vontobel Group which shall prevail in any case, e-mail-communication is for
informational purposes only and is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your consent
to forward you commercial communications. You can exercise, at any time and
under the terms established under current regulation, your rights. If you
prefer not to receive any further communications, please contact your client
relationship manager if you are a client of Vontobel Group or notify the
sender. Please note for an exact reference to the affected group entity the
corporate e-mail signature. For further information about data privacy at
Vontobel Group please consult www.vontobel.com.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
