Antwort: Re: [ADSM-L] Antwort: Re: [ADSM-L] Any impact on SP client with security vulnerability: CVE-2021-44228

[Alexander Heindl]

that's correct.

for me it's just a workaround until IBM provides a fix for it.

8.1.12 and 8.1.13: both use 2.13.3.

Regards,
Alex Heindl




Von:"Rainer Tammer" 
An: ADSM-L@VM.MARIST.EDU
Datum:  15.12.2021 11:20
Betreff:[EXTERNAL] Re: [ADSM-L] Antwort: Re: [ADSM-L] Any impact
on SP client with security vulnerability: CVE-2021-44228
Gesendet von:   "ADSM: Dist Stor Manager" 








Hello,
You have to be careful with that. The switch does only work if Log4J is
2.10 or higher.

Bye
   Rainer

On 15.12.2021 10:29, Alexander Heindl wrote:
> What I did on Windows with ISP Client 8.1.12, Webrestore installed and
> running:
>
> add the last line (-Dlog4j2.formatMsgNoLookups=true) in
> C:\IBM\SpectrumProtect\webserver\usr\servers\veProfile\jvm.options, so
> that it looks like this:
> --8<--
> #Thu Oct 30 15:00:51 PDT 2014
> -Dcom.ibm.jsse2.sp800-131=transition
> -Dlog4j2.formatMsgNoLookups=true
> --8<--
>
> then restart "IBMWebserver"
>
> Regards,
> Alex Heindl
>
>
>
>
> Von:"Rainer Tammer"
> An:ADSM-L@VM.MARIST.EDU
> Datum:  15.12.2021 08:31
> Betreff:[EXTERNAL] Re: [ADSM-L] Any impact on SP client with
> security vulnerability: CVE-2021-44228
> Gesendet von:   "ADSM: Dist Stor Manager"
>
>
>
>
>
>
>
>
> Hello,
> We are also waiting for the fixes. The problem is quite obvious.
> The risk is high, and there are currently no official fixes/mitigations.
>
> Changing Java parameters/setting environment variables for log4j >= 2.10
> might be tricky.
> It could be hard to find all necessary places
>
> We will try the following fix on OC and on the client.
>
> Sample "fix" for log4j-core-2.13.3.gar included in the client:
>
> zip -q -d log4j-core-2.13.3.jar
> org/apache/logging/log4j/core/lookup/JndiLookup.class
>
> NOTE: The application using this library must be restarted completely
> after the change.
> NOTE: This may pose problems in a FIPS environment.
> NOTE: The problematic Java archive may be inside buried in a .war file,
> in this case the .war must be refreshed with a changed
log4j-core-nnn.jar.
>
> *Anny comments?*
>
> Bye
> Rainer
>
> On 13.12.2021 12:25, Del Hoobler wrote:
>> Please watch this page:
>>
>>
>
https://www.ibm.com/blogs/psirt/an-update-on-the-apache-log4j-cve-2021-44228-vulnerability/

>
>> IBM is actively working on a this.
>>
>> Del
>>
>> 
>>
>>
>> "ADSM: Dist Stor Manager"   wrote on 12/12/2021
>> 01:31:46 AM:
>>
>>> From: "Bommasani, Venu"
>>> To:ADSM-L@VM.MARIST.EDU
>>> Date: 12/12/2021 01:32 AM
>>> Subject: [EXTERNAL] Any impact on SP client with security
>>> vulnerability: CVE-2021-44228
>>> Sent by: "ADSM: Dist Stor Manager"
>>>
>>> Hello All,
>>>
>>> Our security Team reported below file as vulnerability with
>>> reference of CVE-2021-44228 on Linux servers.
>>>
>>> /opt/tivoli/tsm/client/ba/bin/plugins/vcloudsuite/sdk/log4j-1.2.17.jar
>>>
>>> We haven't received any information from IBM yet under a Sev1
>>> ticket, But as per Support Team this recent vulnerability
>>> CVE-2021-44228 is still being investigated.
>>>
>>> Does any one has any idea ? remediation ?
>>>
>>> Since vulnerability CVE-2021-44228  treated as Critical, We are
>>> proceeding with removing file directly from all Linux servers.
>>>
>>> Best Regards,
>>> _
>>> Venu Bommasani
>>> Storage & Data Protection
>>> Mobile: +91 7795213309 /venu.bommas...@capgemini.com<
> mailto:venu.bommas...@capgemini.com>
>>> This message contains information that may be privileged or
>>> confidential and is the property of the Capgemini Group. It is
>>> intended only for the person to whom it is addressed. If you are not
>>> the intended recipient, you are not authorized to read, print,
>>> retain, copy, disseminate, distribute, or use this message or any
>>> part thereof. If you receive this message in error, please notify
>>> the sender immediately and delete all copies of this message.

Antwort: Re: [ADSM-L] Any impact on SP client with security vulnerability: CVE-2021-44228

[Alexander Heindl]

What I did on Windows with ISP Client 8.1.12, Webrestore installed and
running:

add the last line (-Dlog4j2.formatMsgNoLookups=true) in
C:\IBM\SpectrumProtect\webserver\usr\servers\veProfile\jvm.options, so
that it looks like this:
--8<--
#Thu Oct 30 15:00:51 PDT 2014
-Dcom.ibm.jsse2.sp800-131=transition
-Dlog4j2.formatMsgNoLookups=true
--8<--

then restart "IBMWebserver"

Regards,
Alex Heindl




Von:"Rainer Tammer" 
An: ADSM-L@VM.MARIST.EDU
Datum:  15.12.2021 08:31
Betreff:[EXTERNAL] Re: [ADSM-L] Any impact on SP client with
security vulnerability: CVE-2021-44228
Gesendet von:   "ADSM: Dist Stor Manager" 








Hello,
We are also waiting for the fixes. The problem is quite obvious.
The risk is high, and there are currently no official fixes/mitigations.

Changing Java parameters/setting environment variables for log4j >= 2.10
might be tricky.
It could be hard to find all necessary places

We will try the following fix on OC and on the client.

Sample "fix" for log4j-core-2.13.3.gar included in the client:

   zip -q -d log4j-core-2.13.3.jar
org/apache/logging/log4j/core/lookup/JndiLookup.class

NOTE: The application using this library must be restarted completely
after the change.
NOTE: This may pose problems in a FIPS environment.
NOTE: The problematic Java archive may be inside buried in a .war file,
in this case the .war must be refreshed with a changed log4j-core-nnn.jar.

*Anny comments?*

Bye
   Rainer

On 13.12.2021 12:25, Del Hoobler wrote:
> Please watch this page:
>
>
https://www.ibm.com/blogs/psirt/an-update-on-the-apache-log4j-cve-2021-44228-vulnerability/

>
> IBM is actively working on a this.
>
> Del
>
> 
>
>
> "ADSM: Dist Stor Manager"  wrote on 12/12/2021
> 01:31:46 AM:
>
>> From: "Bommasani, Venu"
>> To:ADSM-L@VM.MARIST.EDU
>> Date: 12/12/2021 01:32 AM
>> Subject: [EXTERNAL] Any impact on SP client with security
>> vulnerability: CVE-2021-44228
>> Sent by: "ADSM: Dist Stor Manager"
>>
>> Hello All,
>>
>> Our security Team reported below file as vulnerability with
>> reference of CVE-2021-44228 on Linux servers.
>>
>> /opt/tivoli/tsm/client/ba/bin/plugins/vcloudsuite/sdk/log4j-1.2.17.jar
>>
>> We haven't received any information from IBM yet under a Sev1
>> ticket, But as per Support Team this recent vulnerability
>> CVE-2021-44228 is still being investigated.
>>
>> Does any one has any idea ? remediation ?
>>
>> Since vulnerability CVE-2021-44228  treated as Critical, We are
>> proceeding with removing file directly from all Linux servers.
>>
>> Best Regards,
>> _
>> Venu Bommasani
>> Storage & Data Protection
>> Mobile: +91 7795213309 /venu.bommas...@capgemini.com<
mailto:venu.bommas...@capgemini.com>
>> This message contains information that may be privileged or
>> confidential and is the property of the Capgemini Group. It is
>> intended only for the person to whom it is addressed. If you are not
>> the intended recipient, you are not authorized to read, print,
>> retain, copy, disseminate, distribute, or use this message or any
>> part thereof. If you receive this message in error, please notify
>> the sender immediately and delete all copies of this message.

Re: Real world deduplication rates with TSM 7.1 and container pools

[Alexander Heindl]

Hi,

but already client side compressed data isn't affected, isn't it?
what if data is replicated. Is that data then compressed?

Regards,
Alex




Von:Del Hoobler 
An: ADSM-L@VM.MARIST.EDU,
Datum:  22.03.2016 15:14
Betreff:Re: [ADSM-L] Real world deduplication rates with TSM 7.1
and container pools
Gesendet von:   "ADSM: Dist Stor Manager" 



Hi David,

No. Only newly stored data will be compressed.


Del




"ADSM: Dist Stor Manager"  wrote on 03/22/2016
09:41:27 AM:

> From: David Ehresman 
> To: ADSM-L@VM.MARIST.EDU
> Date: 03/22/2016 09:42 AM
> Subject: Re: Real world deduplication rates with TSM 7.1 and container
pools
> Sent by: "ADSM: Dist Stor Manager" 
>
> Del,
>
> After upgrading to 7.1.5 is there a way to get pre-existing
> container data compressed?
>
> David
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Del Hoobler
> Sent: Monday, March 21, 2016 5:53 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Real world deduplication rates with TSM 7.1
> and container pools
>
> I think most of you know Spectrum Protect just added in-line compression


> to the container and cloud deduplicated pools in version 7.1.5:
>
>
> https://urldefense.proofpoint.com/v2/url?
> u=http-3A__www.ibm.com_support_knowledgecenter_SSGSG7-5F7.1.
>
5_srv.common_r-5Ftechchg-5Fsrv-5Fcompress-5F715.html&d=AwIFAg&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=dOGCMY197NTNH1k_wcsrWS3_fxedKW4rpKJ8cHCD2L8&m=OMHhA4Nmsv9Buo24T83zOFo8w4mvoMyvC_nagZn36T0&s=C4shp8VD_EyXjruT5Lu2v68tMVpfpzHcluAuRJfaIK0&e=
>
> Adding incremental forever, the new in-line deduplication - client or
> server-based (7.1.3), new in-line compression (7.1.5) I think you will
> find that Protect continues to drive overall data reduction. This is
being
> done in the software, so you can choose what disk you want to use.
>
> I encourage folks to try out the the new deduplication along with the
new
> compression to see how it helps with the overall data reduction.
>
>
> Thank you,
>
> Del
>
> 
>
>
>
> "ADSM: Dist Stor Manager"  wrote on 03/18/2016
> 10:41:06 AM:
>
> > From: PAC Brion Arnaud 
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 03/18/2016 10:41 AM
> > Subject: Real world deduplication rates with TSM 7.1 and container
pools
> > Sent by: "ADSM: Dist Stor Manager" 
> >
> > Hi All,
> >
> > We are currently testing TSM 7.1 deduplication feature, in
> > conjunction with container based storage pools.
> > So far, my test TSM instances, installed with such a setup are
> > reporting dedup percentage of 45 %, means dedup factor around 1.81,
> > using a sample of clients which are representative of our production
> > environment.
> > This is unfortunately pretty far from what was promised by IBM
> > (dedup factor of 4) ...
> >
> > I'm wondering if anybody making use of container based storage pools
> > and deduplication would be sharing his deduplication factor, so that
> > I could have a better appreciation of real world figures.
> > If you would be so kind to share your information (possibly with the
> > kind of backed-up data  i.e. VM, DB, NAS, Exchange, and retention
> > values ...) I would be very grateful !
> >
> > Thanks in advance for appreciated feedback.
> >
> > Cheers.
> >
> > Arnaud
> >
> >
>
**
> > Backup and Recovery Systems Administrator
> > Panalpina Management Ltd., Basle, Switzerland,
> > CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
> > Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
> > Direct: +41 (61) 226 19 78
> > e-mail: arnaud.br...@panalpina.com
> > This electronic message transmission contains information from
> > Panalpina and is confidential or privileged. This information is
> > intended only for the person (s) named above. If you are not the
> > intended recipient, any disclosure, copying, distribution or use or
> > any other action based on the contents of this information is
> > strictly prohibited.
> >
> > If you receive this electronic transmission in error, please notify
> > the sender by e-mail, telephone or fax at the numbers listed above.
> Thank you.
> >
>
**
> >
>

Antwort: [ADSM-L] Restores using copypool tapes instead of primary pool tapes on 7.1.1.100

[Alexander Heindl]

Hi,

you are hit by this apar:
IT02929 - ONE RESTORE SESSION MOUNTS BOTH PRIMARY AND COPYPOOL VOLUMES

call for an Efix.

workaround: set your copypool(s) to unavailable or your volumes to offsite
while restoring (but that's pretty uncomfortable in many cases...).

Regards,
Alex




Von:Rick Saylor 
An: ADSM-L@VM.MARIST.EDU,
Datum:  20.01.2015 18:17
Betreff:[ADSM-L] Restores using copypool tapes instead of primary
pool tapes on 7.1.1.100
Gesendet von:   "ADSM: Dist Stor Manager" 



Hello,

Before I open an PMR, I thought I would put this out to see if anyone
else is having a similar issue.

TSM servers are 7.1.1.100 on AIX
TSM client is 6.4.0.1 on AIX

I upgraded my TSM servers from 6.4.0.1 to 7.1.1.100 last week. Since
then I've noticed that restores demand copypool tapes instead of
tapes in the primary pool. Below is a snippet of the server log from
yesterday afternoon during a restore. I have two copypools, one local
and the other on a remote TSM server. You'll notice in the log that
the restore begins with a primary pool tape, A00397, but immediately
closes that volume and requests a remote copypool tape. This request
is refused because I brought the remote TSM server down prior to
starting the restore. TSM again opens then immediately closes primary
tape A00397 and then opens a local copypool tape, ACC308L6. This
continues until the restore completes. It appears that TSM will only
use the primary pool tape if it has exhausted all other sources.

01/19/15   13:04:00  ANR0406I Session 5646 started for node
SCOTTY (AIX)
   (Tcp/Ip scotty.austincc.edu(58986)).
(SESSION: 5646)
01/19/15   13:36:07  ANR8337I 3592 volume A00397 mounted in drive
3584L1D4
   (/dev/rmt5). (SESSION:
5646)
01/19/15   13:36:07  ANR0510I Session 5646 opened input volume
A00397.
   (SESSION:
5646)
01/19/15   13:36:07  ANR0514I Session 5646 closed volume A00397.
(SESSION:
   5646)

01/19/15   13:36:07  ANR8214E Session open with xxx.xxx.xxx.xx
failed due to
   connection refusal. (SESSION:
5646)
01/19/15   13:36:07  ANR1401W Mount request denied for
volume
   ADSM1.BFS.416701672 - mount failed.
(SESSION: 5646)
01/19/15   13:36:07  ANR1410W Access mode for volume
ADSM1.BFS.416701672 now
   set to "unavailable". (SESSION:
5646)
01/19/15   13:36:07  ANR0510I Session 5646 opened input volume
A00397.
   (SESSION:
5646)
01/19/15   13:36:07  ANR0514I Session 5646 closed volume A00397.
(SESSION:
   5646)

01/19/15   13:36:29  ANR8337I LTO volume ACC308L6 mounted in
drive 3584L2D2
   (/dev/rmt8). (SESSION:
5646)
01/19/15   13:36:29  ANR0510I Session 5646 opened input volume
ACC308L6.
   (SESSION:
5646)
01/19/15   13:37:41  ANR0514I Session 5646 closed volume
ACC308L6. (SESSION:
   5646)

01/19/15   13:37:41  ANR0510I Session 5646 opened input volume
A00397.
   (SESSION:
5646)
01/19/15   13:37:41  ANR0514I Session 5646 closed volume A00397.
(SESSION:
   5646)

01/19/15   13:37:41  ANR8214E Session open with xxx.xxx.xxx.xx
failed due to
   connection refusal. (SESSION:
5646)
01/19/15   13:37:41  ANR1401W Mount request denied for
volume
   ADSM1.BFS.401235296 - mount failed.
(SESSION: 5646)
01/19/15   13:37:41  ANR1410W Access mode for volume
ADSM1.BFS.401235296 now
   set to "unavailable". (SESSION:
5646)
01/19/15   13:37:41  ANR0510I Session 5646 opened input volume
A00397.
   (SESSION:
5646)
Thanks,
Rick Saylor
Austin Community College

Antwort: Re: [ADSM-L] Antwort: Re: [ADSM-L] [Pool] Using Dedup with TSM : What kind of Hardware ?

[Alexander Heindl]

Hi,

thanks!
the number of objects is not so critical in comparison to additional space 
for deduplication itself. I'd add max. ~20% (mine to yours).

Regards,
Alex



Von:Matthew McGeary 
An: ADSM-L@VM.MARIST.EDU, 
Datum:  05.03.2014 21:46
Betreff:Re: [ADSM-L] Antwort: Re: [ADSM-L] [Pool] Using Dedup with 
TSM : What kind of Hardware ?
Gesendet von:   "ADSM: Dist Stor Manager" 



Alex,

We are only using server-side at the moment but my intention is to start 
rolling out client-side this year.  The number I quoted you was the 
logical GB stored for backup/archive data.  The space utilization is 
currently 114TB.
As for the 4TB disks, I have no complaints thus far.  With an extent pool 
backed by 84 spindles, even NL-SAS can support a decent level of IOPS.  I 
wouldn't bother with a 'cache' pool for backups as we typically see ingest 

rates in excess of 350 MB/s during busy periods of the backup window.  The 

limiting factor on backup performance is the network link providing the 
data, in our case.
We have far fewer objects stored than you do, with 106,000,000 in the 
primary storage pool.  Object count is the best predictor of database 
size, so you will see a larger database size than we do, I'd think.


Matthew McGeary
Technical Specialist
PotashCorp - Saskatoon
306.933.8921



From:   Alexander Heindl 
To: ADSM-L@VM.MARIST.EDU
Date:   03/05/2014 11:52 AM
Subject:[ADSM-L] Antwort: Re: [ADSM-L] [Pool] Using Dedup with TSM 

: What kind of Hardware ?
Sent by:"ADSM: Dist Stor Manager" 



Hi Matthew,

I was quite happy when I read your message, because your system (size) 
seems to be very similar to mine with just one difference: your's is 
allready deduplicated.
A lot of numbers really fit my system, so yours gives me a glue, what I 
need to size it, and: it confirms the numbers I calculated whith this 
document (which is highly recommended ro read!):
https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/Tivoli%20Storage%20Manager/page/Effective%20Planning%20and%20Use%20of%20IBM%20Tivoli%20Storage%20Manager%20V6%20Deduplication



Could you maybe please answer the following questions:
- are you using server side or client side dedup or both (percentage)?
- the 95 TB you stated here: Is this what your TB-lic reports, your 
occupancy (logical_mb) tells you, the storage pool states (in %) or what 
you see on disk? The last one is for sure higher, as it also includes the 
pending volumes for let's say 7 days of reuse dealy. It would be 
interesting, what numbers you have there, because this is the only value 
that counts for sizing.
- how happy are you with the 4TB disks? I also plan to use them, as my 
daily ingest is quite low as yours, so I don't see a problem. Expecially 
with client side dedup I think this won't matter that much...
- do you use client side dedup for DB-(DB2, Oracle, ...) Backups?
- how many objects have you stored in primary- and copypools? (select 
sum(num_files) from occupancy)

In my case I also plan a "cache" filepool with smaller 10k disks for 
backups which need higher performance in writing the data to TSM. Those 
backups will be server side deduped and migrated to the big 4TB disk 
filepool

some information about my system:
~200 TB native data (Occupancy)
daily ingest: ~3,5 TB / day
530.000.000 objects (primary + one copy)

Regards,
Alex




Von:Matthew McGeary 
An: ADSM-L@VM.MARIST.EDU, 
Datum:  05.03.2014 16:21
Betreff:Re: [ADSM-L] [Pool] Using Dedup with TSM : What kind of 
Hardware ?
Gesendet von:   "ADSM: Dist Stor Manager" 



I know this is a bit of a necro-reply, but I just saw this question and 
thought I'd discuss our config

- Total data in dedup pools (Native/Deduped)
We have a single deduplicated primary storage pool that is currently in 
the ~95 TB range.  Our copypool resides on LTO4 and occupies ~228TB
- Total data ingested daily (Native, server side/Deduped, client side)
Our 90-day daily average intake is 3.3 TB.  It can peak up to 8TB during 
our monthly cold backup of production Oracle data.
- Size of your DB
The DB fluctuates between 1.7 and 2TB presently, depending on reorg state.
- Do you backup your STG to Tape ?
Yes, as mentioned above.
- Disk subsystem for DB ?
V7000 SSD in RAID5. 
- Disk subsystem for Active Log ?
Our active logs are on a tiering pool and archive logs are on NL-SAS
- Opinion on that disk subsystem ? Enough, too few ?

A little more detail on our disk configuration:
1 V7000 with 4 drawers.  One is a mix of SSD and 15k SAS.  Another is pure 



SSD and the remaining two are 3TB NL-SAS.
1 DCS3700 populated with 36 3TB NL-SAS and 24 4TB NL-SAS.
Our primary storage resides in an extent pool that spans the DCS3700 
NL-SAS and the V7000 NL-SAS.  Both use RAID6.
The TSM server itself lives on a P740 and is configured to use all 
available resources on that system, so 16 POWER7 cores a

Antwort: Re: [ADSM-L] [Pool] Using Dedup with TSM : What kind of Hardware ?

[Alexander Heindl]

Hi Matthew,

I was quite happy when I read your message, because your system (size) 
seems to be very similar to mine with just one difference: your's is 
allready deduplicated.
A lot of numbers really fit my system, so yours gives me a glue, what I 
need to size it, and: it confirms the numbers I calculated whith this 
document (which is highly recommended ro read!):
https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/Tivoli%20Storage%20Manager/page/Effective%20Planning%20and%20Use%20of%20IBM%20Tivoli%20Storage%20Manager%20V6%20Deduplication

Could you maybe please answer the following questions:
- are you using server side or client side dedup or both (percentage)?
- the 95 TB you stated here: Is this what your TB-lic reports, your 
occupancy (logical_mb) tells you, the storage pool states (in %) or what 
you see on disk? The last one is for sure higher, as it also includes the 
pending volumes for let's say 7 days of reuse dealy. It would be 
interesting, what numbers you have there, because this is the only value 
that counts for sizing.
- how happy are you with the 4TB disks? I also plan to use them, as my 
daily ingest is quite low as yours, so I don't see a problem. Expecially 
with client side dedup I think this won't matter that much...
- do you use client side dedup for DB-(DB2, Oracle, ...) Backups?
- how many objects have you stored in primary- and copypools? (select 
sum(num_files) from occupancy)

In my case I also plan a "cache" filepool with smaller 10k disks for 
backups which need higher performance in writing the data to TSM. Those 
backups will be server side deduped and migrated to the big 4TB disk 
filepool

some information about my system:
~200 TB native data (Occupancy)
daily ingest: ~3,5 TB / day
530.000.000 objects (primary + one copy)

Regards,
Alex




Von:Matthew McGeary 
An: ADSM-L@VM.MARIST.EDU, 
Datum:  05.03.2014 16:21
Betreff:Re: [ADSM-L] [Pool] Using Dedup with TSM : What kind of 
Hardware ?
Gesendet von:   "ADSM: Dist Stor Manager" 



I know this is a bit of a necro-reply, but I just saw this question and 
thought I'd discuss our config

- Total data in dedup pools (Native/Deduped)
We have a single deduplicated primary storage pool that is currently in 
the ~95 TB range.  Our copypool resides on LTO4 and occupies ~228TB
- Total data ingested daily (Native, server side/Deduped, client side)
Our 90-day daily average intake is 3.3 TB.  It can peak up to 8TB during 
our monthly cold backup of production Oracle data.
- Size of your DB
The DB fluctuates between 1.7 and 2TB presently, depending on reorg state.
- Do you backup your STG to Tape ?
Yes, as mentioned above.
- Disk subsystem for DB ?
V7000 SSD in RAID5. 
- Disk subsystem for Active Log ?
Our active logs are on a tiering pool and archive logs are on NL-SAS
- Opinion on that disk subsystem ? Enough, too few ?

A little more detail on our disk configuration:
1 V7000 with 4 drawers.  One is a mix of SSD and 15k SAS.  Another is pure 

SSD and the remaining two are 3TB NL-SAS.
1 DCS3700 populated with 36 3TB NL-SAS and 24 4TB NL-SAS.
Our primary storage resides in an extent pool that spans the DCS3700 
NL-SAS and the V7000 NL-SAS.  Both use RAID6.
The TSM server itself lives on a P740 and is configured to use all 
available resources on that system, so 16 POWER7 cores at 3.6 GHz and 120 
GB of RAM.  We use VIOS for NPIV storage and networking, which takes up 
the remainder of the RAM and steals CPU cycles when necessary.

Overall this system has managed data intake growth in excess of 50% 
year-over-year and database growth of 400%  The DCS3700 in particular is a 

champ: great value for money.  We originally went with V7000 because it 
was pitched to us with compression for the storage pools in mind. 
Unfortunately, this was a bad fit due to the inherent (but poorly 
documented at the time) performance penalties that the IBM compression 
solution has for sequential workloads.  Other than this shortcoming, the 
v7000 has been a good fit for TSM and has handled everything we've thrown 
at it.

Matthew McGeary
Technical Specialist
PotashCorp - Saskatoon
306.933.8921



From:   Erwann Simon 
To: ADSM-L@VM.MARIST.EDU
Date:   01/28/2014 11:09 PM
Subject:[ADSM-L] [Pool] Using Dedup with TSM : What kind of 
Hardware ?
Sent by:"ADSM: Dist Stor Manager" 



Hi,

I'm wondering what kind of hardware you are using if you're using TSM 
Dedup facilities (client and/or server) ?

Can you fill the following fields :
- Total data in dedup pools (Native/Deduped)
- Total data ingested daily (Native, server side/Deduped, client side)
- Size of your DB
- Do you backup your STG to Tape ?
- Disk subsystem for DB ?
- Disk subsystem for Active Log ?
- Opinion on that disk subsystem ? Enough, too few ?

Here's an example from one of my customers
- Total data in dedup pools (Native/Deduped) : a bit less than 10 TB 
(logical_mb), 21,5 TB (reporting_mb)
- Total data ingested daily (Native, serve

Antwort: Re: [ADSM-L] Dedup Question

[Alexander Heindl]

Hi,

Regarding Client-side Dedup:
this then would have impact to a dedup cache on client-side. It should be 
disabled or the data be sent directly to the bigger, slower pool, isn't 
it?

Regards,
Alex



Von:Erwann Simon 
An: ADSM-L@VM.MARIST.EDU, 
Datum:  18.02.2014 11:58
Betreff:Re: [ADSM-L] Dedup Question
Gesendet von:   "ADSM: Dist Stor Manager" 



Hi Alex,

If deduplicated data are moved or copied from a deduplication enabled 
storage pool to anoter deduplication enabled storage pool, only the unique 
missing chunks are moved or copied.

During client side deduplication, chunks are only evaluated against just 
the target pool.

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

- Mail original -
De: "Alexander Heindl" 
A: ADSM-L@VM.MARIST.EDU
Envoyé: Mardi 18 Février 2014 10:45:10
Objet: [ADSM-L] Dedup Question

Hi,

I have questions regarding Client- and Serverside Deduplication.

If I have 2 primary pools (file dedup of course), where the smaller and
faster is the target for clients and the bigger and slower is the next
pool for it, how does deduplication behave?:
Clients that don't use client-side dedup: Sends all data, of course. That
data is deduplicated on Serverside, and migrated later to the bigger,
slower pool. Is the data rehydrated during migration, or will it just move
the missing chunks?
Clients that use client-side dedup: Are the necessary chunks to send are
measured against all or just the target pool? Because in the target pool
(smaller, faster) is just a small part of the client's data..
If I moreover copy all data to a dedup pool: would then the data be
rehydrated?

Regards,
Alex

Dedup Question

[Alexander Heindl]

Hi,

I have questions regarding Client- and Serverside Deduplication.

If I have 2 primary pools (file dedup of course), where the smaller and
faster is the target for clients and the bigger and slower is the next
pool for it, how does deduplication behave?:
Clients that don't use client-side dedup: Sends all data, of course. That
data is deduplicated on Serverside, and migrated later to the bigger,
slower pool. Is the data rehydrated during migration, or will it just move
the missing chunks?
Clients that use client-side dedup: Are the necessary chunks to send are
measured against all or just the target pool? Because in the target pool
(smaller, faster) is just a small part of the client's data..
If I moreover copy all data to a dedup pool: would then the data be
rehydrated?

Regards,
Alex

Antwort: [ADSM-L] Data Protection for Lotus Domino

[Alexander Heindl]

Hi,

just use the "SESSIONS" parameter in domdsm.cfg
in my experience it behaves like this:
the number used, is the number of databases wich are backed up in a bunch.
after completion of the last db it take the next block..

maybe also have a look at the following:
http://adsm.org/forum/showthread.php?24839-Performance-Tuning-TDP-domino
http://www-01.ibm.com/support/docview.wss?uid=swg21194688

Regards,
Alex



Von:"Loon, EJ van - SPLXM" 
An: ADSM-L@VM.MARIST.EDU,
Datum:  12.08.2013 13:51
Betreff:[ADSM-L] Data Protection for Lotus Domino
Gesendet von:   "ADSM: Dist Stor Manager" 



Hi all!

We are currently migrating part of our company from Netbackup to TSM.
They currently backup their Lotus Domino servers to tape (through the
SAN) by using Netbackup for Lotus Notes and they achieve an average
throughput around 10 Mb/sec. This performance is acceptable for the
customer. It's achieved because Netbackup is able to use multiple backup
streams.

We installed Data Protection for Lotus Domino and we see an average
throughput of less than 1 Mb/sec. Tracing showed that the client is
mostly waiting for the Domino server. My guess is that we can achieve 10
Mb/sec too if we were able to use some kind of parallelism with TDP, but
I cannot find a way to do this, other than backing up each database
individually at the same time... Not very convenient.

Does anybody have some tips to boost TDP performance in some way?

Thank you very much for any help in advance!

Kind regards,

Eric van Loon

AF/KLM Storage Engineering




For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee only. If
you are not the addressee, you are notified that no part of the e-mail or
any attachment may be disclosed, copied or distributed, and that any other
action related to this e-mail or attachment is strictly prohibited, and
may be unlawful. If you have received this e-mail by error, please notify
the sender immediately by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission
of this e-mail or any attachments, nor responsible for any delay in
receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered
number 33014286




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] replication issue tsm 6.3.0

[Alexander Heindl]

Hi,

same at my site...
some nodes currently never finish (although they did in the past).

I have a PMR open at IBM and it seems to have to do with "invalid links"
in the storage pool on the target.
I bet you're using dedupe pools, isn't it?

in an second case I have the opposite situation. source has invalid links,
so my replication fails, but without this error and no other messages...

Regards,
Alex




Von:Ray Carlson 
An: ADSM-L@VM.MARIST.EDU
Datum:  02.05.2012 17:58
Betreff:Re: [ADSM-L] replication issue tsm 6.3.0
Gesendet von:   "ADSM: Dist Stor Manager" 



Tim,

I have been fighting this problem for several months now.  IBM is looking
at it, but haven't come up with a solution.

Ray

On May 2, 2012, at 10:39 AM, Tim Brown wrote:

> Error during nodegroup replication, but I cant see any errors on the
target server
>
>
>
>   ANR1815W Check target server for storage problems
during
>
>  replication of node MINERVA, PERSEUS, SILVANUS,
THESEUS,
>
>  POKUCMS2, POKXPR1, POKSESAP1, POKOSVMS1,
POKXPRSAT2,
>
>  CRONUS, POKVERINTDB, POKVERINTREC, POKVERINTARC.
>
>  (SESSION: 51623, PROCESS: 709)
>
>
>
> Rerun of replicate works
>
>
>
> Thanks,
>
>
>
> Tim Brown
> Supervisor Computer Operations
>
> Central Hudson Gas & Electric
> 284 South Ave
> Poughkeepsie, NY 12601
> Email:   tbr...@cenhud.com << <
mailto:tbr...@cenhud.com> mailto:tbr...@cenhud.com>>
> Phone: 845-486-5643
> Fax: 845-486-5921
> Cell: 845-235-4255
>
>
>
>
> "This message contains confidential information and is only for the
intended recipient. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message
to the intended recipient, please notify the sender immediately by
replying to this note and deleting all copies and attachments."




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: [ADSM-L] Question about Tsm replication on V6.3

[Alexander Heindl]

you need to use "remove replnode xxx" on both servers.

Regards,
Alex Heindl



Von:Robert Ouzen 
An: ADSM-L@VM.MARIST.EDU
Datum:  16.04.2012 08:32
Betreff:[ADSM-L] Question about Tsm replication on V6.3
Gesendet von:   "ADSM: Dist Stor Manager" 



Hi

I have just test the new feature on TSM server 6.3 "Tsm Replication" on my 
test environment , works fine very pleased ?

A little question when trying to delete the nodename who was replicated on 
the  target server , I always get that ii can't be remove still in 
replicate status

I update the node on both side( Source an target) with replstate=disabled

I also set replserver with none parameter to reset it on the source server
I reset crossdefine off on both side (Source, Target)

But still can't remove the node on the target server !

Regards Robert




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] Antwort: [ADSM-L] Antwort: [ADSM-L] dedup question

[Alexander Heindl]

thanks so far.

if you would have two pools dedup in hierarchy (one points to the next)
and client backs up with dedup=yes, would it dedup "all" pools the client
occupies or just to data that is in the first pool (bound to mgmtclass)?

Thanks!
Alexander Heindl



Von:Steven Langdale 
An: ADSM-L@VM.MARIST.EDU
Datum:  10.04.2012 14:03
Betreff:Re: [ADSM-L] Antwort: [ADSM-L] Antwort: [ADSM-L] dedup
question
Gesendet von:   "ADSM: Dist Stor Manager" 



> dedupe of pool 1 should not affect pool 2 or 3 and vice versa. so that
in
> case of a restore of a node, only one pool is needed. not the others
> because a chunk is stored there.
> so dedup of a chunk within a pool is ok, but not across all pools.
>
> Dedupe is not across pools.  Even if all 3 pools are deduped, it is done
within the storagepool.

Steven




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: [ADSM-L] Antwort: [ADSM-L] dedup question

[Alexander Heindl]

Hi,

Thanks so far, but now I'm confused... :-)

hope we are talking about the same:
what I want is the following example:

let's say 3 pools with dedup enabled.
serveral nodes backup - some to pool 1, some to 2 and some to 3.

dedupe of pool 1 should not affect pool 2 or 3 and vice versa. so that in 
case of a restore of a node, only one pool is needed. not the others 
because a chunk is stored there.
so dedup of a chunk within a pool is ok, but not across all pools.

and, would that work with client-dedup too?

Thanks,
Alexander Heindl



Von:Ullrich Mänz 
An: ADSM-L@VM.MARIST.EDU
Datum:  10.04.2012 11:29
Betreff:[ADSM-L] Antwort: [ADSM-L] dedup question
Gesendet von:   "ADSM: Dist Stor Manager" 



Alexander,

you can limit dedup on several pools. First, you need to update all 
stgpools with identifyprocess=0.
Next, for each stgpool you want to have dedup working, you need to run 
command "identify duplicates  numpr=1".
For best performance, turn off deduplication before running a "reclaim 
stg" or doing backups by turning off dedup processes using command 
"identify duplicates  numpr=". That can be scheduled by 
administrative commands.

Mit freundlichen Grüßen / best regards

Ullrich Mänz
Data Center Services

FRITZ & MACZIOL Software und Computervertrieb GmbH
Ludwig Str. 180D, 63067 Offenbach, Germany

Mobil   +49 170 7678 434
Fax:   +49 69 3801 3500 10
Web:   http://www.fum.de

Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936
Geschäftsführer: Heribert Fritz, Frank Haines
Inhaber: Imtech N.V., Gouda, Niederlande

Wir bieten herstellerneutrale Cloud- und Software-as-a-Service (SaaS) 
Beratung.



Von:Alexander Heindl 
An: ADSM-L@VM.MARIST.EDU
Datum:  10.04.2012 11:06
Betreff:[ADSM-L] dedup question
Gesendet von:   "ADSM: Dist Stor Manager" 



Hi, 

If I have several pools with dedup enabled, normally it dedupes accross 
all pools. 
Can I limit that to dedup only within each pool? 

thx, 
Alexander Heindl




smime.p7s
Description: S/MIME Cryptographic Signature

dedup question

[Alexander Heindl]

Hi,

If I have several pools with dedup enabled, normally it dedupes accross
all pools.
Can I limit that to dedup only within each pool?

thx,
Alexander Heindl

smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] Tsm Node replication on Version 6.3

[Alexander Heindl]

I'm using it productive...

my reccomendations:
expire inventory right before replication to reduce the amount of data to 
replicate.
and to prevent ressource waiter timeouts: do not backup and replicate a 
node at the same time.
best practice: backup, expire, replication
to do so, I created an "expire and replicate" admin schedule which 
reschedules to "now+5 minutes" as long as backup is still running.

if you have a weak line and you need it during day for business, consider 
canceling replication.
somtimes this can take a while (up to hours for weak lines). a PMR is open 
for that.

last thing to know about: it is no replacement for a copypool. I'd call it 
an "addon" to disaster capabilities which allows you to "instantly" access 
data of a node, like some did it with daily "export node" in the past.

Regards,
Alexander Heindl




Von:Erwann Simon 
An: ADSM-L@VM.MARIST.EDU
Datum:  04.04.2012 19:45
Betreff:Re: [ADSM-L] Tsm Node replication on Version 6.3
Gesendet von:   "ADSM: Dist Stor Manager" 



Hi Robert,

Did you attend these STE sessions last week :
http://www-01.ibm.com/support/docview.wss?uid=swg27024234

I'm not using Node replication in production right now but I'm considering 
to use it soon. 

I Think there is still missing some features such as being able to restore 
a failed volume of the source server from the target server. The idea 
behind is to avoid backing up stgs and just replicating nodes...

- Mail original -
De: "Robert Ouzen" 
À: ADSM-L@VM.MARIST.EDU
Envoyé: Mercredi 4 Avril 2012 14:10:18
Objet: [ADSM-L] Tsm Node replication on Version 6.3

Hi to all

I implant in my environment test the new feature on version 6.3 "TSM Node 
Replication" . The installation , configuration done without errors and 
made some test successfully !

Just wonder if someone is already work in production and can share some 
tips , recommendations ?..

T.I.A Regards

Robert Ouzen
Haifa University
Israel




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: [ADSM-L] replicate with file storage pool

[Alexander Heindl]

Hi,

you maybe activated collocation. if your clients do not belong to a
collocation group and your pool is activated for, it will collocate.

btw. I'd reduce the "maxsess" parameter for replication to reduce the
amount of volumes "touched", but depends on NW-Speed and your performance
needs.

Regards,
Alex



Von:Tim Brown 
An: ADSM-L@VM.MARIST.EDU
Datum:  03.02.2012 15:38
Betreff:[ADSM-L] replicate with file storage pool
Gesendet von:   "ADSM: Dist Stor Manager" 



We are testing 6.3 replication, the file disk pools devclass has
maxcapacity of 20GB and maxscr=50



The first replicate created 10 .bfs files all, all less then 6% used and
all filling/rw



The second created 26 additional .bfs files all, all less then 6% used
except for 1 at 22% and all filling/rw



Question: Why doesn't 2nd replicate add to previous 10 bfs and then only
create a new 20gb bfs when those

others are full/rw



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the
intended recipient. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message
to the intended recipient, please notify the sender immediately by
replying to this note and deleting all copies and attachments.




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?'copystgpool=[yadda]'

[Alexander Heindl]

yes, I mean 'copystgpool=[yadda]'.
well, I experienced this myself within a PMR.
the problem is the "data movement".
it's not the same, and therefore the pool is removed from the list of
copypools.
sadly have no more detailed information on this, maybe ask IBM...

I'm using nonblocked pools myself as a Content Manager target.

Regards, Alex



Von:"Allen S. Rout" 
An: ADSM-L@VM.MARIST.EDU
Datum:  04.01.2012 20:45
Betreff:Re: [ADSM-L] Antwort: Re: [ADSM-L] Sources of discrepancy
between FILE volume size on disk and reported space?
Gesendet von:   "ADSM: Dist Stor Manager" 



On 01/04/2012 09:17 AM, Alexander Heindl wrote:
> use a nonblocked pool
> (you cannot change this setting - you'll need to move all data)
>
> consider some disadvantages of nonblocked data, e.g. no autocopy with
> "blocked" pools...
>

Could you hit that with a little more detail?  When you say 'autocopy',
I think 'copystgpool=[yadda]'.  But nonblock is specifically allowed for
copystgpool sources.  I don't use copystgpool, but it's of interest
nonetheless.


- Allen S. Rout




smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] Sources of discrepancy between FILE volume size on disk and reported space?

[Alexander Heindl]

use a nonblocked pool
(you cannot change this setting - you'll need to move all data)

consider some disadvantages of nonblocked data, e.g. no autocopy with
"blocked" pools...

Regards,
Alex




Von:"Allen S. Rout" 
An: ADSM-L@VM.MARIST.EDU
Datum:  04.01.2012 15:04
Betreff:Re: [ADSM-L] Sources of discrepancy between FILE volume
size on disk and reported space?
Gesendet von:   "ADSM: Dist Stor Manager" 



On 01/04/2012 08:01 AM, Underdown,John William wrote:
> i have the same issue with our document-imaging backups. this is due to
> zillions of itty-bitty files being backed up, see below. btw, the
> TXNGROUPMAX option only applies to files being backed up, not moved or
> reclaimed.  [...]

Sounds like this could very well be my problem.  Thanks!

Shame I can't fix it for extant data.  I might not be able to fix it at
all:  if the content managment system sends just a page, or just a
packet of metadata, the txngroupmax will be irrelevant:  transaction
size = 1. :P


- Allen S. Rout




smime.p7s
Description: S/MIME Cryptographic Signature

confused about deduprequiresbackup

[Alexander Heindl]

Hi,

I'm a bit confused about this option.
when I set it to no, reclamation on my primary dedup filepool works
when set to yes, not. although all data is copied to a copypool.
reclamaion on copypool works in both situations...

could it have to do with the fact that the copypool is also file device
(on a share) with deduplication activated?

Regards,
Alex Heindl

smime.p7s
Description: S/MIME Cryptographic Signature

Questions according deduplication

[Alexander Heindl]

Hi,

some questions according deduplication:

1.) when a client backups deduped to a small, but fast filepool (for daily
amount), and the rest resides in the successor pool, is it deduped all
over the machine, or just for that small pool?

2.) when migrating from one Filepool to the other (both dedup), is the
data inflated? Moreover, if already "identified" duplicates in that pool,
are those migrated, or jumped above?

3.) Implied Qestions: Does Deduplication happen only within a pool, or
across all Filepools?

The reason why not having just one pool is, that the second one could be
on "cheaper" disk, which are maybe not "mirrored SAN".

Best Regards,
Alexander Heindl

smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] Antwort: Re: [ADSM-L] Reduce DB in 6.2.2.2

[Alexander Heindl]

Hi Dave,

Thanks, as deletion of data will be finished in summer, I'll wait for that 
to do so
growth: no, not rapidly, it' just continuously growing (never shrinking).

maybe I'm trying Amos's tip, just backup/restore DB.
Offlline is ok, as long it can be achieved in a weekend.

Best Regards,
Alex

______ 
Ing. Alexander Heindl

Generali IT-Solutions GmbH
WIs

Kratochwjlestraße 4, 1220 Wien
Telefon: +43 (0)1 53401-13160
Fax: +43 1 532 09 49 3160
E-Mail: alexander.hei...@generali.at

http://www.generali.at

Generali IT-Solutions GmbH, Sitz in Wien
registriert beim Handelsgericht Wien unter FN 215738 m
DVR-Nr.: 266. 
Die Gesellschaft gehört zur Unternehmensgruppe der 
Assicurazioni Generali S.p.A., Triest, eingetragen im 
Versicherungsgruppenregister der ISVAP unter der 
Nummer 026.
__ 




Von:Dave Canan 
An: ADSM-L@VM.MARIST.EDU
Datum:  04.02.2011 20:23
Betreff:Re: [ADSM-L] Antwort: Re: [ADSM-L] Reduce DB in 6.2.2.2
Gesendet von:   "ADSM: Dist Stor Manager" 



Alex, you should contact TSM support for this. Because of these DB2 APARs 
I
mentioned that are currently open, doing a reorg of the DB and indicies 
does
not usually reduce the DB size. There are ways to do this, but they 
involve
taking TSM down and running db2 commands to export the tables, drop them,
and then re-import them. (that's not exactly the correct terminology, but
that's essentially what we're doing.) They have scripts that they can
provide here. It could just be the case of a few tables that need to have
the scripts run against them.

Are you also seeing rapid growth here in your DB?

On Fri, Feb 4, 2011 at 12:17 AM, Alexander Heindl <
alexander.hei...@generali.at> wrote:

> Hi Dave,
>
> My problem is shrinking. I did not experience performance issues or
> unexpected db growth so far and I know now, that 6.2.3.0 will address 
some
> reorg enhancements (Thanks to Joerg Pohlmann).
> To be honest, I don't know the difference between table and index  reorg 
so
> far as I have less experience with DB2 (just what I need to know for 
TSM).
> The goal is to reduce the size of my db, as I'm sure it could shrink
> because of deleting serveral filespaces (yesterday nealy 10%).
> If I have a look at my db history graph, db never decreased ( could send
> you a jpg)
>
> Best Regards,
> Alex
>
> __
> Ing. Alexander Heindl
>
> Generali IT-Solutions GmbH
> WIs
>
> Kratochwjlestraße 4, 1220 Wien
> Telefon: +43 (0)1 53401-13160
> Fax: +43 1 532 09 49 3160
> E-Mail: *alexander.hei...@generali.at* 
> *
> **http://www.generali.at* <http://www.generali.at/>
>
> Generali IT-Solutions GmbH, Sitz in Wien
> registriert beim Handelsgericht Wien unter FN 215738 m
> DVR-Nr.: 266.
> Die Gesellschaft gehört zur Unternehmensgruppe der
> Assicurazioni Generali S.p.A., Triest, eingetragen im
> Versicherungsgruppenregister der ISVAP unter der
> Nummer 026.
> __
>
>
>
>
> Von:Dave Canan 
> An:ADSM-L@VM.MARIST.EDU
> Datum:03.02.2011 18:21
> Betreff:Re: [ADSM-L] Reduce DB in 6.2.2.2
> Gesendet von:"ADSM: Dist Stor Manager" 
> --
>
>
>
> Alex, is the issue here that the database is not shrinking or is this a
> question about reorgs? There are currently several APARs against the DB2
> V9.7 that will not allow the DB to be reduced when reorgs occur. These 
will
> be addressed in a future service level of TSM and DB2. If you have
> questions
> about enabling index reorgs, you should contact TSM support for 
assistance.
> There are several things to be aware of before index reorgs are enabled, 
so
> PLEASE contact them first.
>
> Also, if you'd like we could arrange a call here to discuss this 
further. I
> realize the time differences involved, but we could arrange something. 
Let
> me know.
>
> Dave Canan
> IBM Advanced Technical Support
> ddcananATUSDOTIBMDOTCOM
> 916-723-2410
>
>
>
> On Thu, Feb 3, 2011 at 3:32 AM, Alexander Heindl <
> alexander.hei...@generali.at> wrote:
>
> > Hi,
> >
> > I have a TSM-Server instance with a 188 GB Database:
> > Space Used by Database(MB): 188,032
> >
> > Although deleting several (big) filespaces which are not needed 
anymore,
> > database ist not shrinking. I thought with 6.1 (an 6.2) this is done
> > automatically?
> >
> > Best Regards,
> > Alex
> >
> > __
> > Ing. Alexander Heindl
> >
> > Generali IT-Solutions GmbH
> > WIs
> >
> > Kratochwjlestraße 4, 1220 W

Antwort: Re: [ADSM-L] Reduce DB in 6.2.2.2

[Alexander Heindl]

Hi Dave,

My problem is shrinking. I did not experience performance issues or 
unexpected db growth so far and I know now, that 6.2.3.0 will address some 
reorg enhancements (Thanks to Joerg Pohlmann).
To be honest, I don't know the difference between table and index  reorg 
so far as I have less experience with DB2 (just what I need to know for 
TSM).
The goal is to reduce the size of my db, as I'm sure it could shrink 
because of deleting serveral filespaces (yesterday nealy 10%).
If I have a look at my db history graph, db never decreased ( could send 
you a jpg)

Best Regards,
Alex

______ 
Ing. Alexander Heindl

Generali IT-Solutions GmbH
WIs

Kratochwjlestraße 4, 1220 Wien
Telefon: +43 (0)1 53401-13160
Fax: +43 1 532 09 49 3160
E-Mail: alexander.hei...@generali.at

http://www.generali.at

Generali IT-Solutions GmbH, Sitz in Wien
registriert beim Handelsgericht Wien unter FN 215738 m
DVR-Nr.: 266. 
Die Gesellschaft gehört zur Unternehmensgruppe der 
Assicurazioni Generali S.p.A., Triest, eingetragen im 
Versicherungsgruppenregister der ISVAP unter der 
Nummer 026.
__ 




Von:Dave Canan 
An: ADSM-L@VM.MARIST.EDU
Datum:  03.02.2011 18:21
Betreff:Re: [ADSM-L] Reduce DB in 6.2.2.2
Gesendet von:   "ADSM: Dist Stor Manager" 



Alex, is the issue here that the database is not shrinking or is this a
question about reorgs? There are currently several APARs against the DB2
V9.7 that will not allow the DB to be reduced when reorgs occur. These 
will
be addressed in a future service level of TSM and DB2. If you have 
questions
about enabling index reorgs, you should contact TSM support for 
assistance.
There are several things to be aware of before index reorgs are enabled, 
so
PLEASE contact them first.

Also, if you'd like we could arrange a call here to discuss this further. 
I
realize the time differences involved, but we could arrange something. Let
me know.

Dave Canan
IBM Advanced Technical Support
ddcananATUSDOTIBMDOTCOM
916-723-2410



On Thu, Feb 3, 2011 at 3:32 AM, Alexander Heindl <
alexander.hei...@generali.at> wrote:

> Hi,
>
> I have a TSM-Server instance with a 188 GB Database:
> Space Used by Database(MB): 188,032
>
> Although deleting several (big) filespaces which are not needed anymore,
> database ist not shrinking. I thought with 6.1 (an 6.2) this is done
> automatically?
>
> Best Regards,
> Alex
>
> __
> Ing. Alexander Heindl
>
> Generali IT-Solutions GmbH
> WIs
>
> Kratochwjlestraße 4, 1220 Wien
> Telefon: +43 (0)1 53401-13160
> Fax: +43 1 532 09 49 3160
> E-Mail: *alexander.hei...@generali.at* 
> *
> **http://www.generali.at* <http://www.generali.at/>
>
> Generali IT-Solutions GmbH, Sitz in Wien
> registriert beim Handelsgericht Wien unter FN 215738 m
> DVR-Nr.: 266.
> Die Gesellschaft gehört zur Unternehmensgruppe der
> Assicurazioni Generali S.p.A., Triest, eingetragen im
> Versicherungsgruppenregister der ISVAP unter der
> Nummer 026.
> __
>
>




smime.p7s
Description: S/MIME Cryptographic Signature

Reduce DB in 6.2.2.2

[Alexander Heindl]

Hi,

I have a TSM-Server instance with a 188 GB Database:
Space Used by Database(MB): 188,032

Although deleting several (big) filespaces which are not needed anymore, 
database ist not shrinking. I thought with 6.1 (an 6.2) this is done 
automatically?

Best Regards,
Alex

__ 
Ing. Alexander Heindl

Generali IT-Solutions GmbH
WIs

Kratochwjlestraße 4, 1220 Wien
Telefon: +43 (0)1 53401-13160
Fax: +43 1 532 09 49 3160
E-Mail: alexander.hei...@generali.at

http://www.generali.at

Generali IT-Solutions GmbH, Sitz in Wien
registriert beim Handelsgericht Wien unter FN 215738 m
DVR-Nr.: 266. 
Die Gesellschaft gehört zur Unternehmensgruppe der 
Assicurazioni Generali S.p.A., Triest, eingetragen im 
Versicherungsgruppenregister der ISVAP unter der 
Nummer 026.
__ 



smime.p7s
Description: S/MIME Cryptographic Signature

Antwort: Re: [ADSM-L] LTO-5 Experience?

[Alexander Heindl]

We are using two Quantum (former ADIC) Scalar i6000 Libraries with 8 HP 
drives each, since May 2010.
Before that I had 6 IBM LTO3 each in i2000. The libraries remained, just 
were upgraded to i6000.
In the beginning we had some small troubles which were library, driver or 
firmware specific, I suspect.
Currently I'm using Firmware I3AZ for my drives and it seems to be stable.
I'm quite happy with it.

The biggest problem was maybe, that it was an early step, where I had to 
migrate TSM to version 6.2, which was brand new too...

Best Regard,
Alex

______ 
Ing. Alexander Heindl

Generali IT-Solutions GmbH
WIs

Kratochwjlestraße 4, 1220 Wien
Telefon: +43 (0)1 53401-13160
Fax: +43 1 532 09 49 3160
E-Mail: alexander.hei...@generali.at

http://www.generali.at

Generali IT-Solutions GmbH, Sitz in Wien
registriert beim Handelsgericht Wien unter FN 215738 m
DVR-Nr.: 266. 
Die Gesellschaft gehört zur Unternehmensgruppe der 
Assicurazioni Generali S.p.A., Triest, eingetragen im 
Versicherungsgruppenregister der ISVAP unter der 
Nummer 026.
__ 


smime.p7s
Description: S/MIME Cryptographic Signature

AUTO: Alexander Heindl/IT/IM/EAG/AT ist außer Haus. (Rückkehr am 27.12.2010)

[Alexander Heindl]

Ich bin bis 27.12.2010 abwesend.

Gerne werde ich Ihre Nachricht nach meiner Rückkehr beantworten.

Alexander Heindl


Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht  "Re: [ADSM-L] 
Bind server instance to a specific IP instead of all interfaces" gesendet am 
22.12.2010 17:54:05.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese 
Person abwesend ist.

TSM Fastback Server x64

[Alexander Heindl]

Hi,

TSM Fastback Server supports only x86 on Windows.
Is there a plan for a x64 version?


Best Regards,
Alexander Heindl


smime.p7s
Description: S/MIME Cryptographic Signature

AUTO: Alexander Heindl/IT/IM/EAG/AT ist außer Haus. (Rückkehr am 30.11.2010)

[Alexander Heindl]

Ich bin bis 30.11.2010 abwesend.

Gerne werde ich Ihre Nachricht nach meiner Rückkehr beantworten.

Alexander Heindl


Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht  "[ADSM-L] TSM 
5.4 and 6.2 on the same box" gesendet am 28.11.2010 08:42:02.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese 
Person abwesend ist.

AUTO: Alexander Heindl/IT/IM/EAG/AT ist außer Haus. (Rückkehr am 27.10.2010)

[Alexander Heindl]

Ich bin bis 27.10.2010 abwesend.

Gerne werde ich Ihre Nachricht nach meiner Rückkehr beantworten.

Alexander Heindl


Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht  "Re: [ADSM-L] 
Lousy performance on new 6.2.1.1 server with SAN/FILEDEVCLASS storage" gesendet 
am 22.10.2010 03:35:20.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese 
Person abwesend ist.

AUTO: Alexander Heindl/IT/IM/EAG/AT ist außer Haus. (Rückkehr am 07.10.2010)

[Alexander Heindl]

Ich bin bis 07.10.2010 abwesend.

Gerne werde ich Ihre Nachricht nach meiner Rückkehr beantworten.

Alexander Heindl


Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht  "[ADSM-L] TSM 
5.4 Training Material" gesendet am 06.10.2010 14:49:11.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese 
Person abwesend ist.