RE: RTVTCPINF times

I doubt the decision was made specifically to save performance data. Most likely, it happened to be saved and caused locking issues. The "easiest" fix was to end performance collection.

This is an situation where it would be beneficial. Since moving from POWER7 to POWER9, our backup times have varied wildly and inexplicably (Monday was 40 minutes, while Tuesday was only 25). I'll see if I can get permission to not end performance collection.

Thanks



-----Original Message-----
From: Jim Oberholtzer [mailto:midrangel@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, April 24, 2019 8:13 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: 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