We hit the problem at 6.3.6 per this document <http://www-01.ibm.com/support/docview.wss?uid=swg1IT17642> which says:
*After upgrading the server to 6.3.6.000 (or higher) and 7.1.3 (or higher) expiration might "hang" on a node while expiring backup data only. Expiration is not actually hung it is still processing but very slowly due to a non-optimized* *SQL/Select. A change to this SQL/Select occurred between 6.3.5.0 and 6.3.6.0. This code change was implemented in servers 6.3.6.0+ and 7.1.3.0 to 7.1.7. There have been no reported problems at 7.1.3 or above.* On Wed, Oct 11, 2017 at 8:35 AM, Hans Christian Riksheim <bull...@gmail.com> wrote: > I have noticed that expiration suddenly takes a lot more time. The first > million objects are expired/deleted very quickly but it slows down to an > almost hang with the last 10%. > > The DB has reached 2 TB and server is 7.1.3.100. Any performance > enhancements in later levels? > > Hans Chr. > -- *Zoltan Forray* Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator Xymon Monitor Administrator VMware Administrator Virginia Commonwealth University UCC/Office of Technology Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/
