Re: RTVTCPINF times

Why back up the performance data as part of the normal backups at all? Exclude the *MGTCOL object from the save. What if the performance data is needed to diagnose a problem with the save or other functions running at that time?

Then, later when it's more convenient back up the performance data if you want to. Once a week is plenty.

Performance data is not critical data for a DR or data recovery. It's only value at that point is to assist IBM with forensics if that's needed.

Save it for comparative analysis when doing upgrades hardware or software. Save it for use when you do updates to OEM or internal applications, but it should not be part of the recovery backups if it is disruptive at all.


Jim Oberholtzer
Agile Technology Architects

On Apr 24, 2019, at 8:47 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

Unfortunately, we have to stop performance monitoring during backup due to object locks.

-----Original Message-----
From: Jack Kingsley [mailto:iseriesflorida@xxxxxxxxx]
Sent: Wednesday, April 24, 2019 4:52 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: RTVTCPINF times

Justin, here is a link on everything that this does. Have you looked at your performance data to see what might be going on during the times that this is being ran. Is it spending more time in a specific step one day 'vs' another day.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1021215


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com