Re: TS4300 configuration

[Martin Janosik]

Hi,

/dev directory is dynamically built so it's not needed to create directory 
manually, it should get populated once you load kernel module

> When you run the lin_tape kernel module, it creates special files in the /dev 
> directory

Adding persistent naming + all  stop/unload/load/start steps are described in 
User's Guide (page 54) 'Persistent Naming Support'
https://www.ibm.com/support/pages/system/files/inline-files/$FILE/GC27-2130-23_0.pdf

Martin Janosik


-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Loon, Eric 
van (ITOP DI) - KLM
Sent: piatok 23. decembra 2022 15:18
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: [ADSM-L] TS4300 configuration

Hi Martin!

Thanks for the link!
I've done some more searching online and I found some documentation about 
enabling the following option:
options lin_tape alternate_pathing=1
So I created a /etc/modprobe.d/lin_tape.conf file and added this option to it, 
along with the persistent naming option:
options lin_tape persistent_n_device=1
I also created the /etc/udev/rules.d/98-lin_tape.rules file with all the drives 
in it. I stopped and unloaded lin_tape, reloaded the rules with udevadm control 
--reload-rules and loaded and started lin_tape. I was expecting to see the 
devices created, but I still can't find a /dev/lin_tape/by-id directory. I 
don't have to create this directory manually, do I?
Thanks again for your help!

Kind regards,
Eric van Loon
Air France/KLM Core Infra

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Martin Janosik
Sent: vrijdag 23 december 2022 15:04
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TS4300 configuration

Hi Eric,

I'm not sure it's possible to selectively remove /dev/IBMchangerX devices.
I would follow 
https://www.ibm.com/docs/en/ts4300-tape-library?topic=tape-taking-devices-offline-completing-maintenance
  to completely stop lintaped as it should remove all IBMtape/IBMchanger and 
then proceed with removal of generic tape devices

lsscsi and find the H:B:T:L for each Tape Device.
Then, for each H:B:T:L do:
echo 1 > /sys/bus/scsi/devices/H:B:T:L/delete

Reconfigure control paths in library (, rescan_scsi just to make sure) and 
start lintaped.

Martin Janosik

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Loon, Eric 
van (ITOP DI) - KLM
Sent: piatok 23. decembra 2022 11:23
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] [ADSM-L] TS4300 configuration

Hi guys,

I'm connecting a TS4300 to my SP server. The library I defined contains 6 drive 
and I selected all drives as control path. This however creates six 
/dev/IBMchanger devices. So before I correct my mistake and update the library 
definition, I like to remove /dev/IBMchanger1 to 5 first. What is the proper 
way to remove these library devices from a Linux host?
Thanks for any help in advance!

Kind regards,
Eric van Loon
Core Infra

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


Unless stated otherwise above:
Kyndryl Česká republika, spol. s r. o.
Sídlo: V Parku 2294/4, Chodov, 148 00  Praha 4,
IČ: 096 28 886
Zapsaná v obchodním rejstříku, vedeném Městským soudem v Praze (oddíl C, vložka 
339277) Registered address: V Parku, 2294/4, Chodov, 148 00 Prague 4 Company 
ID: 096 28 886 Registered in the Commercial Register maintained by the 
Municipal Court in Prague (Part C, Entry 339277

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, a

Re: TS4300 configuration

[Martin Janosik]

Hi Eric,

I'm not sure it's possible to selectively remove /dev/IBMchangerX devices.
I would follow 
https://www.ibm.com/docs/en/ts4300-tape-library?topic=tape-taking-devices-offline-completing-maintenance
 to completely stop lintaped as it should remove all IBMtape/IBMchanger and 
then proceed with removal of generic tape devices

lsscsi and find the H:B:T:L for each Tape Device.
Then, for each H:B:T:L do:
echo 1 > /sys/bus/scsi/devices/H:B:T:L/delete

Reconfigure control paths in library (, rescan_scsi just to make sure) and 
start lintaped.

Martin Janosik

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Loon, Eric 
van (ITOP DI) - KLM
Sent: piatok 23. decembra 2022 11:23
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] [ADSM-L] TS4300 configuration

Hi guys,

I'm connecting a TS4300 to my SP server. The library I defined contains 6 drive 
and I selected all drives as control path. This however creates six 
/dev/IBMchanger devices. So before I correct my mistake and update the library 
definition, I like to remove /dev/IBMchanger1 to 5 first. What is the proper 
way to remove these library devices from a Linux host?
Thanks for any help in advance!

Kind regards,
Eric van Loon
Core Infra

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


Unless stated otherwise above:
Kyndryl Česká republika, spol. s r. o.
Sídlo: V Parku 2294/4, Chodov, 148 00  Praha 4,
IČ: 096 28 886
Zapsaná v obchodním rejstříku, vedeném Městským soudem v Praze (oddíl C, vložka 
339277)
Registered address: V Parku, 2294/4, Chodov, 148 00 Prague 4
Company ID: 096 28 886
Registered in the Commercial Register maintained by the Municipal Court in 
Prague (Part C, Entry 339277

Re: SQL query to identify all nodegroup members

[Martin Janosik]

Hi Eric,

Table 'nodes' has column 'nodegroup' so just use
select node_name from nodes where nodegroup='specific-large-nodegroup'

It's not possible to memorize the database schema so I always use these 2:
# to get list of available tables
select tabname from syscat.tables
# to see what colums are present in that table
select colname from syscat.columns where tabname='NODES'

Easiest is to query for a single object from table using 'fetch...'
select * from nodes fetch first 1 row only
however it is useless  if you run it against an empty table:
Protect: SP01>select * from COLLOCGROUP
ANR2034E SELECT: No match found using this criteria.
ANS8001I Return code 11.
In that case use syscat.columns.

Martin Janosik

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Loon, Eric 
van (ITOP DI) - KLM
Sent: piatok 12. augusta 2022 9:24
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] [ADSM-L] SQL query to identify all nodegroup members

Hi everybody,

I'm trying to create a SQL query to identify all nodegroup members for a 
specific nodegroup. The problem is that a select node_name from nodegroup 
returns only the first 2048 characters, so for large nodegroups, the output is 
incomplete...
Does anybody know a solution for this issue? Thanks in advance!

Kind regards,
Eric van Loon
Core Infra

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


Unless stated otherwise above:
Kyndryl Česká republika, spol. s r. o.
Sídlo: V Parku 2294/4, Chodov, 148 00  Praha 4,
IČ: 096 28 886
Zapsaná v obchodním rejstříku, vedeném Městským soudem v Praze (oddíl C, vložka 
339277)
Registered address: V Parku, 2294/4, Chodov, 148 00 Prague 4
Company ID: 096 28 886
Registered in the Commercial Register maintained by the Municipal Court in 
Prague (Part C, Entry 339277

Re: Files not rebinding as expected

[Martin Janosik]

Hi Eric,

The folder was backed up on 13/7 under management class with longest retention 
(BA7Y_L) since no DIRMC was configured.
During backup on 14/7 folder was already removed from the server so the object 
was only inactivated.
Rebinding of MC only occurs for existing files/folders.
You most probably added DIRMC option *after* 14/July.

If an existing folder was backed up with new DIRMC (BA14_L) option, also all 
previous versions of the folder were rebound from BA7Y_L to BA14_L. If you 
delete such folder, its inactive version will be stored under BA14_L.

Martin Janosik

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Loon, Eric 
van (ITOP DI) - KLM
Sent: pondelok 8. augusta 2022 14:40
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: [ADSM-L] Files not rebinding as expected

Hi Andy,

I changed the includes accordingly, so the clopset now looks like this:

DIRMC0 No BA14_L
INCLEXCL 1 No include.backup 
d:\...\* BA14_L
INCLEXCL 2 No include.backup 
c:\...\* BA14_L
INCLEXCL 3 No INCLUDE.BACKUP 
d:\MSP\...\* BA7Y_L
INCLEXCL 4 No INCLUDE.BACKUP 
d:\FTPDATA\sapdw\...\* BA7Y_L
INCLEXCL 5 No INCLUDE.BACKUP 
d:\FTPDATA\workathome\...\* BA7Y_L

The includes 1 to 5 seem to be working OK now, the only strange thing I can't 
explain is why several (but certainly not all) inactive directories on the C: 
drive are now bound to BA7Y_L too:

> select * from backups where node_name='YS0023SA' and 
> object_id=3771909693

  NODE_NAME: YS0023SA
 FILESPACE_NAME: \\ys0023sa\c$
   FILESPACE_ID: 2
  STATE: INACTIVE_VERSION
   TYPE: DIR
HL_NAME: \PROGRAMDATA\MICROSOFT\WINDOWS\WER\REPORTQUEUE\
LL_NAME: 
NONCRITICAL_MICROSOFTEDGEUPD_CD9A261DDE7F7CA3A975FAD1C617B3157C4755__D3238B06
  OBJECT_ID: 3771909693
BACKUP_DATE: 2022-07-13 23:19:26.00
DEACTIVATE_DATE: 2022-07-14 22:45:18.00
  OWNER:
 CLASS_NAME: BA7Y_L
ACTUAL_SIZE: 659

Thanks for your help!

Kind regards,
Eric van Loon
Air France/KLM Core Infra

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Andrew Raibeck
Sent: woensdag 3 augustus 2022 22:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Files not rebinding as expected

Hi Erik,

Looking at your option set INCLEXCL statements, at least part of the binding 
problem looks to be the sequence of statements:

  INCLEXCL 0 Yes INCLUDE.BACKUP d:\MSP\...\*.* BA7Y_L
  INCLEXCL 1 Yes INCLUDE.BACKUP d:\FTPDATA\sapdw\...\*.* BA7Y_L
  INCLEXCL 2 Yes INCLUDE.BACKUP d:\FTPDATA\workathome\...\*.* BA7Y_L
  INCLEXCL 3 Yes include.backup d:\...\*.* BA14_L
  INCLEXCL 4 Yes include.backup c:\...\*.* BA14_L

(note: The FORCE option is ignored for INCLEXCL.)

The above include-exclude statements are processed from the bottom up, the same 
as if you put them in your dsm.opt file. For example, a file such as 
"D:\FTPDATA\sapdw\somefile.txt" matches the pattern "d:\...\*.*", so it is 
bound to BA14_L. You can fix this by resequencing the INCLEXCL options in the 
client option set. For example:

  update clientopt mpsserver inclexcl 0 5
  update clientopt mpsserver inclexcl 1 6
  update clientopt mpsserver inclexcl 2 7

Thus the new sequence is:

  include.backup d:\...\*.* BA14_L
  include.backup c:\...\*.* BA14_L
  INCLUDE.BACKUP d:\MSP\...\*.* BA7Y_L
  INCLUDE.BACKUP d:\FTPDATA\sapdw\...\*.* BA7Y_L
  INCLUDE.BACKUP d:\FTPDATA\workathome\...\*.* BA7Y_L

Note that if you run "dsmc query inclexcl", the include-exclude list is 
displayed in inverted order (don't ask me why...), so patterns closer to the 
top of the displayed list are matched first.

One more observation: The "*.*" pattern means "match any file name with a dot ( 
. ) character in the name. Thus files with no extension, though not so common 
on Windows, do not match the "*.*" pattern. In general, it is best to use "*" 
to refer to any file name... unless you really mean to include only files that 
have a dot in the name.

To augment this comment from Josh-Daniel Davis:

> * Directories always are bound to the longest retention management class 
> unless you use DIRMC to override it.

Specifically, it is the management class with the longest RETONLY setting. If 
more than one management class has the same (highest) RETONLY setting, then the 
management class name that is last in ascending sort order is the default 
DIRMC. For example, if you have two management classes named DISK and TAPE, and 
they both have the same highest RETONLY setting of all the management classes, 
then the default DIRMC is TAPE. 

You probably are not doing this, but I will mention it anyway, for 
completeness: When 

Re: Files not rebinding as expected

[Martin Janosik]

Hi Eric,

from my observation updating node to new policy domain is instantaneous no 
matter how many files are stored under the node. There is no way that during 
this instant operation files are re-bound from no-more-existing-in-new-domain 
management class to new domain's default management class. That would explains 
question #3.

Also:
> if a user changes the binding in an include statement, then instead of
> running a full incremental backup, only selective or incremental-by-date 
> backups
> are performed, then only active versions will be rebound, while inactive 
> versions
> will remain bound to the original management class.

If you run anything else than full incremental (in this case `dsmc incr C: D:`) 
then only newly backed up files are stored under new management class

Expire inventory goes through all inactive files and if their MC matches with 
the MC defined in the policy domain, it expires data accordingly.
If there is no matching MC present, objects will expire based on default 
management class (or grace retention period).

Is the destination by any chance a directory pool? I *think* that deduped 
objects (=those referenced by multiple backup versions) are not necessarily 
re-bound.

Martin Janosik

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Loon, Eric 
van (ITOP DI) - KLM
Sent: utorok 2. augusta 2022 12:42
To: ADSM-L@VM.MARIST.EDU
Subject: [EXTERNAL] Re: [ADSM-L] Files not rebinding as expected

Hi Skylar,

Yes, this node is backed up every day...

Kind regards,
Eric van Loon
Core Infra

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Skylar 
Thompson
Sent: maandag 1 augustus 2022 17:43
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Files not rebinding as expected

Hi Eric,

Have you run an incremental backup yet? You'll need to do that in order to get 
active versions rebound to the management classes in the nodes include/exclude 
rules.

Inactive versions will stay bound to their old management class but, in the 
event of a domain change, I think will use either a management class with the 
same name in the new domain/policyset, or the domain default management class 
if that management class doesn't exist. I'm not sure how that would be reported 
with SQL or QUERY BACKUP, though.

On Mon, Aug 01, 2022 at 11:51:08AM +, Loon, Eric van (ITOP DI) - KLM wrote:
> Hi everybody,
>
> I have a node called YS0023SA, which uses domain MPS_7_YEARS and client 
> option set MPSSERVER. I listed all policy details down below.
> I issued a select * from backups for this node and for some reason, all files 
> are either bound to mgmtclass DEFAULT, bound to BA14_L (which is the 
> default), or to TOC, which doesn't even exist in this domain (it does exist 
> in the node's previous domain).
> Can anybody explain:
>
>   1.  Why are files using both DEFAULT and BA14_L?
>   2.  Why is the include.backup for the other mgmtclass BA7Y_L in the 
> cloptset not working?
>   3.  Why are some files (active and inactive files) still bound to a 
> management class from the previous domain?
> Thanks for any help in advance!
>
> Kind regards,
> Eric van Loon
>
>
>
> Domain MPS_7_YEARS:
>   Policy Domain Name: MPS_7_YEARS
> Activated Policy Set: MPS_7_YEARS
> Activation Date/Time: 19-07-2022 12:04:05
>Days Since Activation: 13
> Activated Default Mgmt Class: BA14_L
>   Number of Registered Nodes: 1
>  Description: Domain for MPS server Backup 
> Retention (Grace Period): 14 Archive Retention (Grace Period): 14
>   Last Update by (administrator): 
>Last Update Date/Time: 19-07-2022 12:04:05
> Managing profile:
>  Changes Pending: No
>Active Data Pool List:
>  Domain Type: Standard
>
> Policy set MPS_7_YEARS:
> PolicyPolicyDefault   Description  Last Update by  Last 
> Upda- Managing profile  Changes
> DomainSet Name  Mgmt   (administrator) te 
> Date/T-   Pending
> NameClass ime
> Name
> - - -  --- 
> --  --
> MPS_7_YE- ACTIVEBA14_LPolicy set for MPS   
> 19-07-202-  No
> ARS   server   2 
> 11:46:-
>
> 26
>
> MGMTClasses:
> PolicyPolicyMgmt  DefaultDescription
> DomainSet Name  Class Mgmt Clas-
> NameName

Re: Operations Center 8.1.4 - Client Package Download using Proxy

[Martin Janosik]

Hello,
have you considered some kind of transparent TCP-to-proxy redirection, i.e.
redsocks?
I have not tested is personally but I bookmarked it in the past - I thought
it could be helpful one day (today?)

Martin J.

"ADSM: Dist Stor Manager"  wrote on 2018-03-06
10:34:13:

> From: Uwe Schreiber 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2018-03-06 10:36
> Subject: Re: [ADSM-L] Operations Center 8.1.4 - Client Package
> Download using Proxy
> Sent by: "ADSM: Dist Stor Manager" 
>
> I did a test by setting the Java options for the instance user, and
> restarted the instance.
>
> As well i set the Java options for usage by the OPC.
>
> -> unchanged situation -> download of packages is failing.
>
> Not the OC which is downloading the software packages.
> The "Deploy Package Manager" (integrated in the dsmserv binary?)
> triggers the download / refresh / etc. of the software packages.
>
> I did not see any other java processes than the OPC GUI when the
> message "ANR3753I The client update packages manager is started. /
> ANR3756I A refresh of client update packeges was started."
>
> So I assume dsmserv does not start any Java based sub-processes for
> downloading the software packages.
>
> Uwe
>
> On Tue, 2018-03-06 at 11:07 +0300, Efim wrote:
> > Why not to configure a transparent proxy for this traffic?
> >
> > Assuming that the hub participates in the download of packages, by
> > default Java does not use a system proxy.
> > You can try to use option Djava.net.useSystemProxies = true in the
> > environment settings for the user, on behalf of which the hub starts
> > .
> > it will looks like export IBM_JAVA_OPTIONS="-Dmysysprop1=tcpip
> > -Dmysysprop2=wait -Xdisablejavadump"
> > I found example in https://www.ibm.com/support/knowledgecenter/en/SSM
> > KFH/com.ibm.apmaas.doc/install/config_forwardproxy_dc.htm
> > but it uses jvm.options file.
> >
> > Efim
> >
> >
> > > 6 марта 2018 г., в 10:39, Uwe Schreiber  > > E> написал(а):
> > >
> > > Hello Efim,
> > >
> > > thank you for your response.
> > >
> > > I already had a try using the local catalog.
> > > This did not bypass the direct download from IBM.
> > >
> > > From my point of view, the local catalog gives you the possibility
> > > to
> > > create your own package repository.
> > > Therefor you have to build a http server where you store the
> > > package
> > > for a download by the OC hub instance.
> > > In addition you have to modify the local catalog.json file to point
> > > to
> > > the right package locations on your own http server.
> > >
> > > Of course i could setup my own http server and build a local
> > > repository.
> > > But this would increase the complexity, etc.
> > >
> > > Uwe
> > >
> > >
> > > On Tue, 2018-03-06 at 09:25 +0300, Efim wrote:
> > > > Hi
> > > > you can try to configure local catalog. it will bypass using
> > > > proxy:
> > > >
> > > > setopt clientdeployuselocalcatalog yes
> > > > create dir: //deployconfig/
> > > > run (you can add it to the cron): curl -o / > > > dir>/deployconfig/catalog.json https://public.dhe.ibm.com/storage
> > > > /tiv
> > > > oli-storage-management/catalog/client/catalog.json
> > > >
> > > > Efim
> > > >
> > > >
> > > >
> > > > > 6 марта 2018 г., в 0:32, Uwe Schreiber  > > > > E.DE
> > > > > > написал(а):
> > > > >
> > > > > I'am searching a solution for deploying client updates using
> > > > > Operations
> > > > > Center 8.1.4.
> > > > >
> > > > > My OC hub (is spoke as well) is not able to connect direct to
> > > > > https://urldefense.proofpoint.com/v2/url?
> u=https-3A__p=DwIFaQ=jf_iaSHvJObTbx-
> siA1ZOg=H5e_B7Ka5iXApV9NLO3a6LPjgmGzpTrVrSapqmyEY0E=TCER6L5E-
>
e0Od-1y1NcsjYk6dr2uwz7GBhdESLV4VP0=KfrP7fY71S9D98_YhAxk99uk4IhkHCZZ6h7jnd9iQgM=

> > > > > ublic.dhe.ibm.com/...
> > > > > I have to use a proxy configuration to enable that
> > > > > communication.
> > > > >
> > > > > So I configured the variables http_proxy / https_proxy with the
> > > > > according proxy informations for the instance user within the
> > > > > RHEL
> > > > > 7.4
> > > > > operating System.
> > > > >
> > > > > Testing using "curl" and "wget" works as expected when trying
> > > > > to
> > > > > download an deployment package.
> > > > >
> > > > > For forcing the instance to do a software package refresh I
> > > > > restarted
> > > > > the instance, but I still got the error
> > > > >
> > > > > ANR3763E An error occurred while the catalog file used for
> > > > > client
> > > > > updates was downloading from
> > > > > https://public.dhe.ibm.com/storage/tivoli-storage-management/ca
> > > > > talo
> > > > > g/cl
> > > > > ient/catalog.json.
> > > > >
> > > > > After restarting the instance a "tcpdump" was showing packets
> > > > > to
> > > > > "public.dhe.ibm.com" using https.
> > > > > The tcpdump tool stops to show such packets as soon as I get
> > > > > the
> > > > > above
> > > > > message within 

Re: Why is is dedup cache file not excluded by default ?

[Martin Janosik]

Hello,

your presumtion doesn't seems accurate to me (Windows, Linux, AIX clients,
mostly v7.1):

tsm> q inclexc
*** FILE INCLUDE/EXCLUDE ***
Mode Function  Pattern (match from top down)  Source File
 - -- -
No exclude filespace statements defined.
Excl Directory /.../.TsmCacheDir  TSM
Include Snapshot Retry
TSM500*/opt/tivoli/tsm/client/ba/bin/dsm.sys
No DFS include/exclude statements defined.

Any directory .TsmCacheDir is excluded by software itself

Martin J.

"ADSM: Dist Stor Manager"  wrote on 2018-02-26
07:40:18:

> From: Stefan Folkerts 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2018-02-26 07:42
> Subject: Re: [ADSM-L] Why is is dedup cache file not excluded by
default ?
> Sent by: "ADSM: Dist Stor Manager" 
>
> For as far as I know nothing is excluded by the code itself and I think
> this is a policy thing.
>
> Since you can install the software in different locations and you can use
> different names for different files (ie log files) IBM can never be 100%
> sure that the file it is hardcoded to exclude is the file we think it is.
> There is always that chance. It would have to be hardcoded as a sort of
> dynamic exclude like "I will exclude this is cache file that I am
currently
> actually using during the each backup".
>
> On Sat, Feb 24, 2018 at 5:26 PM, Erwann SIMON 
wrote:
>
> > Hi Rick,
> >
> > Yes, this is what I always do. But I was wondering why it's not
excluded
> > by the code itself.
> >
> > --
> > Best regards / Cordialement / مع تحياتي
> > Erwann SIMON
> >
> > - Mail original -
> > De: "Rick Adamson" 
> > À: ADSM-L@VM.MARIST.EDU
> > Envoyé: Vendredi 23 Février 2018 12:31:17
> > Objet: Re: [ADSM-L] Why is is dedup cache file not excluded by
default ?
> >
> > Erwann,
> > I have client option sets defined on the server that I use to globally
> > exclude it from all file level backups.
> >
> > -Rick Adamson
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Of
> > Erwann SIMON
> > Sent: Friday, February 23, 2018 1:14 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: [ADSM-L] Why is is dedup cache file not excluded by default ?
> >
> > * This email originated outside of the organization. Use caution when
> > opening attachments or clicking links. *
> >
> > --
> > Hi all,
> >
> > I'm wondering why the dedup cache file
(TSMDEDUPDB_servernamenodename.DB,
> > located in the dedupcachepath directory) is not excluded by default ?
> > I generally exclude it because it causes somes retries and do think
that
> > there's no need to back it up. But I may be wrong.
> > So, must we really back it up ? And why ?
> >
> > --
> > Best regards / Cordialement / مع تحياتي
> > Erwann SIMON
> >
> > **CONFIDENTIALITY NOTICE** This electronic message contains information
> > from Southeastern Grocers, LLC and is intended only for the use of the
> > addressee. This message may contain information that is privileged,
> > confidential and/or exempt from disclosure under applicable Law. This
> > message may not be read, used, distributed, forwarded, reproduced or
stored
> > by any other than the intended recipient. If you are not the intended
> > recipient, please delete and notify the sender
> >
>

Re: TSM 8.1.1 on Linux crash

[Martin Janosik]

Hello there,

errno 16 usually corresponds to 'device busy'. I have observed this error
mostly on systems with shared library (shared=yes) and with storage agents
that had some problems to communicate with TSM server.
Are you facing the issue only on a single tape drive, or all? Are they
zoned by any chance also to other systems, i.e. 2nd cluster node?
Can you send few lines from actlog related to the drive with error before
failure occured?

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 2018-01-09
17:58:09:

> From: Remco Post 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2018-01-09 17:59
> Subject: [ADSM-L] TSM 8.1.1 on Linux crash
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi All,
>
> over here we have a few TSM servers on Linux (RHEL 7.4) TSM 8.1.1.
> 021 (to be upgraded to .100 soon) and we see something new that we
> never saw on AIX. If for some reason a tape gets left in a drive
> (IBM 3592) the only way to get the drive working again in to reboot
> the drive. Until then TSM is unable to open the drive (error 16).
> Unfortunately we seem to be able to reliably cause severe issues in
> TSM by rebooting a tapedrive:
>
> kernel: NMI watchdog: BUG: soft lockup - CPU#6 stuck for 22s!
[dsmserv:6021]
>
> The only way out is to reboot the entire server.
>
> We never had such issues with TSM on AIX… is this something Linux-
> specific that we can hang TSM in non-interuptable routines (kernel
> space) by simply rebooting a tape drive?
>
> --
>
>  Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.p...@plcs.nl
> +31 6 248 21 622
>

Re: UNSUBSCRIBE

[Martin Janosik]

Dear ALL,

you are doing it wrong. If you are missing initial instructions of ADSM-L,
then here is how to unsubscribe:

You may leave the list at any  time by sending a "SIGNOFF ADSM-L" command
to lists...@vm.marist.edu (or LISTSERV@MARIST.BITNET).

Martin Janosik

Re: rebinding objects for API client archives

[Martin Janosik]

Hello,

during execution of expiration process on TSM/SP server each backed
up/archived object is processed, currently active backup/archive copy group
retention (versions and/or days) is applied.
Based on result if object is eligible for deletion, it is deleted;
otherwise object is kept until next expiration process.
Unfortunately you cannot rebind mgmt class of archived objects. So if you
now change retention of copy groups, it will apply from now on for all
existing and new objects.

If you change the retention, you can check the deletion date via 'dsmc
query archive -detail /path/to/api/file'
Bye

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 2017-09-20
14:18:41:

> From: "Rhodes, Richard L." 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2017-09-20 14:20
> Subject: [ADSM-L] rebinding objects for API client archives
> Sent by: "ADSM: Dist Stor Manager" 
>
> We have a TSM instance that is dedicated to "applications".  These
> are applications that use the API client to store some kind of
> object in TSM.  An example is IBM Content Manager.  Nodes are in
> domains with a default Mgt Class with 7 years retention, and store
> their data as Archives, although one application uses Backups.
>
> We received a legal hold request to keep some of this data for 12 years.
>
> It's my understanding that you cannot rebind archive data.  That is,
> changing the MgtClass will do nothing to keep this data longer.
>
> Do we have to change the Mgt Class and have the users retrieve/re-
> archive the data?
>
>
> Is this correct?  Thoughts?
>
> Thoughts?
>
> Rick
>
--

>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
> the reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are
> hereby notified that you have received this document in error and
> that any review, dissemination, distribution, or copying of this
> message is strictly prohibited. If you have received this
> communication in error, please notify us immediately, and delete the
> original message.

Re: How to prevent leading spaces in SQL output

[Martin Janosik]

Hi Eric,

'-tab' does the magic:
[~]$ dsmadmc -tab -se=TSM -id=admin -pa=admin -dataonly=yes "SELECT CAST
(float(used_space_mb)*100/total_space_mb AS DECIMAL(4,2)) FROM log"
0.98

[~]$ dsmadmc -se=TSM -id=admin -pa=admin -dataonly=yes "SELECT CAST(float
(used_space_mb)*100/total_space_mb AS DECIMAL(4,2)) FROM log"
      0.98

Bye

Martin Janosik

"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/25/2017
10:01:51 AM:

> From: "Loon, Eric van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> To: ADSM-L@VM.MARIST.EDU
> Date: 01/25/2017 10:06 AM
> Subject: [ADSM-L] How to prevent leading spaces in SQL output
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Hi TSM-ers!
> I'm executing the following command in a script:
>
> /usr/bin/dsmadmc -se=$INSTANCE -id=$ID -password=$PASSWORD -
> dataonly=yes "SELECT CAST(float(used_space_mb)*100/total_space_mb AS
> DECIMAL(4,2)) FROM log"
>
> The result is this (without quotes):
>
> '  0.49'
>
> I'm looking for a way to remove the leading spaces, so the output is
> just '0.49'. I know I can do it in the script itself, but I'm just
> wondering if there is a way to remove all formatting through the SQL
> statement itself.
> Thanks for any help in advance!
> Kind regards,
> Eric van Loon
> Air France/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
> 
>

Re: ISP 81 Discontinued functions

[Martin Janosik]

I'm also a bit nervous and curoius at the same time about discontinued
functions, namely:
Online system state restores - You can no longer restore the system state
on a system that is online. Instead, use the Automated System Recovery
(ASR) based recovery method to restore the system state in offline Windows
Preinstallation Environment (PE) mode.
and
The following operating systems are no longer supported by the
backup-archive client:
Linux on Power Systems™ (big endian). You can still use the IBM Spectrum
Protect API on Linux on Power Systems (big endian).

What is the idea behind "to be competive with x86 platform and get
compativility certification for SAP HANA with Linux on Power platform (Big
Endian)" (ref.
https://blogs.saphana.com/2015/08/21/announcing-general-availability-of-sap-hana-on-ibm-power-systems/
) and then 1.5 year later drop support of BAclient for OS"?

We deployed 10+ big SAP HANA on Power8 instances last year, and now we will
be getting "not supported" for new releases?

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 12/09/2016
02:45:34 PM:

> From: Chavdar Cholev 
> To: ADSM-L@VM.MARIST.EDU
> Date: 12/09/2016 02:47 PM
> Subject: [ADSM-L] ISP 81 Discontinued functions
> Sent by: "ADSM: Dist Stor Manager" 
>
> Does some one check discontinued functions in new version...
> especially part of no VM backup as standard function in BA client
> It is not good at all. TDP for Virtual environment for hyper-V creats
diff
> hdds (.avhdx)
> and my customers will not be happy with this, because you have to merge
> these file,
> when you need to expand .vhdx disk for example 
>
> :(
> Regards
> Cahvdar
>

Re: LVM Snapshot failed..

[Martin Janosik]

Hello,

you need to be able to create LVM snapshot manually, I tested it for you on
one our server (SUSE11):

srv-db01:~ # lvcreate -L1G --snapshot -n
LVbackup /dev/mapper/vg00-lv_opt_tivoli_cit
  Logical volume "LVbackup" created

srv-db01:~ # lvdisplay
.
  --- Logical volume ---
  LV Name/dev/vg00/LVbackup
  VG Namevg00
  LV UUIDLcG3Lu-rq0z-GR36-ozaq-crcP-Ye9x-v2jrqZ
  LV Write Accessread/write
  LV Creation host, time tep500-db01, 2016-11-28 14:34:01 +0100
  LV snapshot status active destination for /dev/vg00/lv_opt_tivoli_cit
  LV Status  available
  # open 0
  LV Size1.00 GiB
  Current LE 256
  COW-table size 1.00 GiB
  COW-table LE   256
  Allocated to snapshot  0.00%
  Snapshot chunk size4.00 KiB
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 1024
  Block device   253:70
...

srv-db01:~ # mkdir /LVbackup

srv-db01:~ # mount /dev/vg00/LVbackup /LVbackup

srv-db01:~ # df -h /LVbackup
Filesystem Size  Used Avail Use% Mounted on
/dev/mapper/vg00-LVbackup 1008M   62M  895M   7% /LVbackup

srv-db01:~ # ls /LVbackup
bin  cache_data  CIT_files  config  install  lost+found  properties

srv-db01:~ # umount /LVbackup

srv-db01:~ # lvremove /dev/vg00/LVbackup
Do you really want to remove active logical volume LVbackup? [y/n]: y
  Logical volume "LVbackup" successfully removed

Your error states that you don't have enough free space in volume group
'mongo_byg_pribuild'.
Did you create logical volume db_snap manualy? Was it created by dsmc's
invocation and not cleaned afterwards?

You should be able to use lvextend/lvreduce commands to change size of
snapshot LV as per manual pages of lvcreate (man lvcreate):
-s, --snapshot OriginalLogicalVolume{Name|Path}
The snapshot with the specified size does not need the same amount of
storage the origin has. In a typical scenario, 15-20% might be enough.  In
case the snapshot runs out of storage, use lvextend(8) to  grow  it.
Shrinking  a snapshot  is  supported  by lvreduce(8) as well.

Bye

Martin J.

"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 11/28/2016
01:42:08 PM:

> From: Bo Nielsen <boa...@dtu.dk>
> To: ADSM-L@VM.MARIST.EDU
> Date: 11/28/2016 01:43 PM
> Subject: Re: [ADSM-L] LVM Snapshot failed..
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Hi Martin,
>
> Can you tell me how I extend the LVG. I have tried, but it's not right.
>
> DF cmd:
> /dev/mapper/mongo_byg_pribuild-mongo   2113638320  399284 2016587488
> 1% /mnt/mongo
> /dev/mapper/mongo_byg_pribuild-db_snap 2113638320   81944 2006166220
> 1% /mnt/mongo_db_snap
>
> From LVDISPLAY:
> --- Logical volume ---
>   LV Path/dev/mongo_byg_pribuild/mongo
>   LV Namemongo
>   VG Namemongo_byg_pribuild
>   LV UUIDIiRkjV-qGSf-TBIq-989F-zGIK-iHt4-jzSZsd
>   LV Write Accessread/write
>   LV Creation host, time byg-pribuild, 2016-11-02 15:15:33 +0100
>   LV snapshot status source of
>  db_snap [active]
>   LV Status  available
>   # open 1
>   LV Size2.00 TiB
>   Current LE 524286
>   Segments   2
>   Allocation inherit
>   Read ahead sectors auto
>   - currently set to 8192
>   Block device   253:2
>
>   --- Logical volume ---
>   LV Path/dev/mongo_byg_pribuild/db_snap
>   LV Namedb_snap
>   VG Namemongo_byg_pribuild
>   LV UUIDfYGMil-2p3q-i33u-tdPV-gghC-pOFT-xNUR3Q
>   LV Write Accessread/write
>   LV Creation host, time byg-pribuild, 2016-11-28 12:51:22 +0100
>   LV snapshot status active destination for mongo
>   LV Status  available
>   # open 1
>   LV Size2.00 TiB
>   Current LE 524286
>   COW-table size 2.00 TiB
>   COW-table LE   524287
>   Allocated to snapshot  1.58%
>   Snapshot chunk size4.00 KiB
>   Segments   1
>   Allocation inherit
>   Read ahead sectors auto
>   - currently set to 8192
>   Block device   253:5
>
> I'm not strong in Linux. So pls help or guide me in the right way.
> Thanks
>
> Bo Nielsen
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Martin Janosik
> Sent: 15. november 2016 12:38
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] LVM Snapshot failed..
>
> Hi,
> check amount of free space in volume group mongo_byg_pribui

Re: LVM Snapshot failed..

[Martin Janosik]

Hi,
check amount of free space in volume group mongo_byg_pribuild. Free space
in volume group is used to create snapshot of existing logical volume.
Test if you can create snapshot manually (using linux commmands) before
investigating - some instructions can be found on
http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html
Bye

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 11/15/2016
11:43:58 AM:

> From: Bo Nielsen 
> To: ADSM-L@VM.MARIST.EDU
> Date: 11/15/2016 11:46 AM
> Subject: [ADSM-L] LVM Snapshot failed..
> Sent by: "ADSM: Dist Stor Manager" 
>
> I'm not expert in Linux. I try to do a LVM snapshot on Linux (CentOS
> Linux release 7.2.1511).
>
> I get this error:
>
> 1/15/2016 11:12:16 ANS5250E An unexpected error was encountered.
>TSM function name : DSnapshotProvider::startSnapshot():
>TSM function  : File descriptor 3 (/opt/tivoli/tsm/client/ba/
> bin/dsmopt.lock) leaked on lvcreate invocation. Parent PID 31371: /bin/sh
> File descriptor 7 (/opt/tivoli/tsm/client/ba/bin/dsmopt.lock) leaked
> on lvcreate invocation. Parent PID 31371: /bin/sh
> File descriptor 9 (/opt/tivoli/tsm/client/ba/bin/dsmopt.lock) leaked
> on lvcreate invocation. Parent PID 31371: /bin/sh
>   Volume group "mongo_byg_pribuild" has insufficient free space (0
> extents): 26215 required.
>
>TSM return code   : 5
>TSM file  : DSnapshotProvider.cpp (648)
> 11/15/2016 11:12:16 ANS1259E The image snapshot operation failed.
> Diagnostic text: tsmStartSnapshot.
> 11/15/2016 11:12:16 ANS8103W A command  was not successful.
>command   : /sbin/lvremove -f /dev/mongo_byg_pribuild/
> tsmsnapshot_date_11_15_2016_time_11.12.16 1>/dev/null
>TSM function name : DSnapshotProvider::deleteSnapshot():
>error output  : File descriptor 3 (/opt/tivoli/tsm/client/ba/
> bin/dsmopt.lock) leaked on lvremove invocation. Parent PID 31374: /bin/sh
> File descriptor 7 (/opt/tivoli/tsm/client/ba/bin/dsmopt.lock) leaked
> on lvremove invocation. Parent PID 31374: /bin/sh
> File descriptor 9 (/opt/tivoli/tsm/client/ba/bin/dsmopt.lock) leaked
> on lvremove invocation. Parent PID 31374: /bin/sh
>   Failed to find logical volume "mongo_byg_pribuild/
> tsmsnapshot_date_11_15_2016_time_11.12.16"
>
>return code   : 5
>TSM file  : DSnapshotProvider.cpp (840)
> 11/15/2016 11:12:17 ANS1228E Sending of object '/mnt/mongo' failed.
> 11/15/2016 11:12:17 ANS1258E The image snapshot operation failed.
>
> 11/15/2016 11:12:17 ANS1813E Image Backup processing of '/mnt/mongo'
> finished with failures.
>
> TSM client vers.: 7.1.4.0
>
> Used command:
> dsmc backup image /mnt/mongo -snapshotproviderimage=LINUX_LVM -
> SNAPSHOTCACHESIZE=10
>
> lvdisplay:
>
> --- Logical volume ---
>   LV Path/dev/mongo_byg_pribuild/mongo
>   LV Namemongo
>   VG Namemongo_byg_pribuild
>   LV UUIDIiRkjV-qGSf-TBIq-989F-zGIK-iHt4-jzSZsd
>   LV Write Accessread/write
>   LV Creation host, time byg-pribuild, 2016-11-02 15:15:33 +0100
>   LV Status  available
>   # open 1
>   LV Size1024.00 GiB
>   Current LE 262143
>   Segments   1
>   Allocation inherit
>   Read ahead sectors auto
>   - currently set to 8192
>   Block device   253:2
>
> /dev/mapper/mongo_byg_pribuild-mongo  1008G  366M  957G   1% /mnt/mongo
>
> What do I missed or is it impossible ???
> We expect the DB is growth to 2 Tb, therefor the snapshot technology.
>
> Regards
>
> Bo Nielsen
>
>
> IT Service
>
>
>
> Technical University of Denmark
>
> IT Service
>
> Frederiksborgvej 399
>
> Building 109
>
> DK - 4000 Roskilde
>
> Denmark
>
> Mobil +45 2337 0271
>
> boa...@dtu.dk
>

Re: Making use of two NICs

[Martin Janosik]

Hi Paul,

if you want to automatically load balance incoming traffic from clients you
need to configure both NICs in aggregate link mode (802.3ad) as well as
network switch must be able to support this feature and be configured -
there will be one IP address accessible via both network links, max
throughput will be 2x 1GBps.
If you don't have switch with support of 802.3ad you can "manually" load
balance.  Each NIC will have own IP and you need to modity dsm.opt/dsm.sys
files on client servers to point to new IP address.  This will limit max
throughput to 1GBps (or whatever speed you have) on each NIC.

Bye

"ADSM: Dist Stor Manager"  wrote on 09/14/2016
06:34:21 AM:

> From: Paul_Dudley 
> To: ADSM-L@VM.MARIST.EDU
> Date: 09/14/2016 06:36 AM
> Subject: [ADSM-L] Making use of two NICs
> Sent by: "ADSM: Dist Stor Manager" 
>
> We have TSM v6.3 running on an IBM x3650 M4 server with Windows
> 2008. The server has a second un-used NIC.
>
> If we configure and connect the second NIC, is it possible to make
> use of it so that TSM network traffic (ie: backups) could be spread
> across the two NICs?
>
>
>
>
>
> Thanks & Regards
>
> Paul
>
>
>
>
>
> Paul Dudley
>
> IT Operations
>
> ANL Container Line
>
> pdud...@anl.com.au
>
>
>
>
>
>
>
>
> ANL DISCLAIMER
>
> This e-mail and any file attached is confidential, and intended
> solely to the named add
> ressees. Any unauthorised dissemination or use is strictly
> prohibited. If you received
> this e-mail in error, please immediately notify the sender by return
> e-mail from your s
> ystem. Please do not copy, use or make reference to it for any
> purpose, or disclose its
>  contents to any person.
>

Re: SAP Hana deduplication savings in directory stgpool

[Martin Janosik]

pped to TSM:
>
> ANR0951I Session 708064 for node   processed 1 files by using
> inline data deduplication or compression, or both. The number of original
> bytes was 18,483,972.
> Inline data deduplication reduced the data by 126,899 bytes and inline
> compression reduced the data by 0 bytes.
>
>
> 09/12/2016 00:20:25  ANR0951I Session 695360 for node 
>   processed 1 files by using inline data
> deduplication or compression, or both. The number of original bytes was
> 797,085,373,292. Inline data deduplication reduced the
>   data by 0 bytes and inline compression reduced
> the data by 0 bytes.  (SESSION: 695360)
>
> And even if compression was enabled in the HANA database itself I would
> assume to see some compression in the dedup process (small but not zero)
>
>
> Dedup stats for said node
>  Date/Time: 09/09/2016 14:07:06
>  Storage Pool Name: TSP3
>  Node Name: 
> Filespace Name: /tdpmux
>   FSID: 2
>   Type: Arch
>  Total Data Protected (MB): 3,490,805
>  Total Space Used (MB): 3,405,573
> Total Space Saved (MB): 85,232
>Total Saving Percentage: 2.44
>  Deduplication Savings: 89,372,414,238
>   Deduplication Percentage: 2.44
>  Non-Deduplicated Extent Count: 4,651
> Non-Deduplicated Extent Space Used: 1,832,923
>Unique Extent Count: 5,460,237
>   Unique Extent Space Used: 3,551,809,145,807
>Shared Extent Count: 205,396
>   Shared Extent Data Protected: 108,563,366,200
>   Shared Extent Space Used: 18,488,232,525
>Compression Savings: 0
> Compression Percentage: 0.00
>Compressed Extent Count: 0
>  Uncompressed Extent count: 5,670,284
>
>
>
> I am yet to try to enable compression on the stgpool since we just
upgraded
> to 7.1.6.
>
>
>
>
> *Arni Snorri Eggertsson*
> +45 40 80 70 31 <+45+40+80+70+31>  | ar...@gormur.com  |
http://gormur.com
> | Skype: arnieggertsson
> <http://dk.linkedin.com/in/arnieggertsson>
>
> On Wed, Sep 7, 2016 at 10:20 AM, Martin Janosik
<martin.jano...@cz.ibm.com>
> wrote:
>
> > Hello all,
> >
> > is anyone storing SAP HANA backups (using Data Protection for ERP) in
> > directory storage pools?
> > What are deduplication savings in your environment?
> >
> > In our environment we see only 40% savings (35%-50%), comparing to
> > predicted dedup savings 1:9 (this ratio is currently valid for backups
of
> > TDP4ERP Oracle, MS SQL, Oracle, ...).
> > This completely messes up the initial capacity planning :(
> >
> > tsm: PRYTSM1>q dedupstats DEDUPPOOL_REPL SAP_PEP f=d
> >
> >  Date/Time: 09/02/2016 21:01:00
> >  Storage Pool Name: DEDUPPOOL_REPL
> >  Node Name: SAP_PEP
> > Filespace Name: /tdpmux
> >   FSID: 2
> >   Type: Arch
> >  Total Data Protected (MB): 27,045,165
> >  Total Space Used (MB): 16,228,576
> > Total Space Saved (MB): 10,816,588
> >Total Saving Percentage: 39.99
> >  Deduplication Savings: 1,699,912,761,679
> >   Deduplication Percentage: 5.99
> >  Non-Deduplicated Extent Count: 8,414
> > Non-Deduplicated Extent Space Used: 3,329,503
> >Unique Extent Count: 15,846,440
> >   Unique Extent Space Used: 26,082,116,838,846
> >Shared Extent Count: 7,340,821
> >   Shared Extent Data Protected: 2,276,790,425,670
> >   Shared Extent Space Used: 574,756,400,378
> >Compression Savings: 9,642,102,240,318
> > Compression Percentage: 36.17
> >Compressed Extent Count: 21,757,839
> >  Uncompressed Extent count: 1,437,836
> >
> > Thank you in advance.
> >
> > Kind regards
> > Martin Janosik
> >
>

Re: Win silent install by MSI files

[Martin Janosik]

Hi Rick,

in past I succeeded with this:
unzip the exe installation package and

ECHO Detecting architecture...
SET OSbit=x64
reg query "HKLM\System\CurrentControlSet\Control\Session Manager
\Environment" /v PROCESSOR_ARCHITECTURE | find /i "x86" > NUL && SET
OSbit=x86
SET localRepository=C:\tsm_images
SET component=TSM
SET API=
IF %OSbit% EQU x64 SET API=64
...
REM You need to make sure that all prerequisite packages are installed
REM i.e.
REM START /wait vcredist_x64.exe /quiet /norestart
REM START /wait wusa.exe Windows6.1-KB2703425-x64.msu /quiet /norestart
...
ECHO %component% Starting installation
START /wait msiexec /i "IBM Tivoli Storage Manager Client.msi"
RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1 INSTALLDIR="%installPath%"
ADDLOCAL="BackupArchiveGUI,BackupArchiveWeb,Api%API%Runtime,AdministrativeCmd"
 TRANSFORMS=1033.mst /qn /l*v
"%localRepository%\%component%_install_log.txt"
SET RC=%ERRORLEVEL%
ECHO %component% Installation ended with RC=%RC%

You can also create "default" dsm.opt file and store it in installation
package in correct path.

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 09/08/2016
12:58:13 PM:

> From: "Rhodes, Richard L." 
> To: ADSM-L@VM.MARIST.EDU
> Date: 09/08/2016 12:59 PM
> Subject: [ADSM-L] Win silent install by MSI files
> Sent by: "ADSM: Dist Stor Manager" 
>
> One of our Win admins asked:
>
> >Do you know if IBM offers or has available a configuration wizard
> >that we can use to setup custom MSI files to install Tivoli 7.1.4
> remote to all
> >our servers?
>
> I didn't find anything from some quick googling.
> I know a silent install is supported, but I'm not sure how that
> relates to MSI files.
>
>
> Any thoughts are welcome!
>
> Thanks
>
> Rick
>
>
>
>
>
>
> -
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
> the reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are
> hereby notified that you have received this document in error and
> that any review, dissemination, distribution, or copying of this
> message is strictly prohibited. If you have received this
> communication in error, please notify us immediately, and delete the
> original message.
>

SAP Hana deduplication savings in directory stgpool

[Martin Janosik]

Hello all,

is anyone storing SAP HANA backups (using Data Protection for ERP) in
directory storage pools?
What are deduplication savings in your environment?

In our environment we see only 40% savings (35%-50%), comparing to
predicted dedup savings 1:9 (this ratio is currently valid for backups of
TDP4ERP Oracle, MS SQL, Oracle, ...).
This completely messes up the initial capacity planning :(

tsm: PRYTSM1>q dedupstats DEDUPPOOL_REPL SAP_PEP f=d

 Date/Time: 09/02/2016 21:01:00
 Storage Pool Name: DEDUPPOOL_REPL
 Node Name: SAP_PEP
Filespace Name: /tdpmux
  FSID: 2
  Type: Arch
 Total Data Protected (MB): 27,045,165
 Total Space Used (MB): 16,228,576
Total Space Saved (MB): 10,816,588
   Total Saving Percentage: 39.99
 Deduplication Savings: 1,699,912,761,679
  Deduplication Percentage: 5.99
 Non-Deduplicated Extent Count: 8,414
Non-Deduplicated Extent Space Used: 3,329,503
   Unique Extent Count: 15,846,440
  Unique Extent Space Used: 26,082,116,838,846
   Shared Extent Count: 7,340,821
  Shared Extent Data Protected: 2,276,790,425,670
  Shared Extent Space Used: 574,756,400,378
   Compression Savings: 9,642,102,240,318
Compression Percentage: 36.17
   Compressed Extent Count: 21,757,839
 Uncompressed Extent count: 1,437,836

Thank you in advance.

Kind regards
Martin Janosik

Re: Data Protection for Oracle 5.5.2 + 7.1.4 API

[Martin Janosik]

Hi Zoltan,

have you tried to delete all orphaned objects in one run? I had similar
issue recently, can't remember exact ANS/RC code. But try to split objects
to smaller group (250 was working for me on one server, 2000 on another),
and delete object in smaller bunches.
+1:250
O

Bye

Martin J.

"ADSM: Dist Stor Manager"  wrote on 03/17/2016
09:03:16 PM:

> From: Zoltan Forray 
> To: ADSM-L@VM.MARIST.EDU
> Date: 03/17/2016 09:05 PM
> Subject: Re: [ADSM-L] Data Protection for Oracle 5.5.2 + 7.1.4 API
> Sent by: "ADSM: Dist Stor Manager" 
>
> Unfortunately, you are right.  I only see 11 + 12, which is where we are.
>
> On Thu, Mar 17, 2016 at 3:33 PM, Stefan Folkerts

> wrote:
>
> > I don't think the 7.1.3 TDP supports Oracle 10.
> > I think this is 11 and 12 only.
> >
> > On Thu, Mar 17, 2016 at 5:53 PM, Zoltan Forray  wrote:
> >
> > > Why not upgrade the TSM TDP for Oracle to 7.1.3?  This combination
(TSM
> > > client 7.1.4.4 + TDP 7.1.3.0) is what we are running.
> > >
> > > On Thu, Mar 17, 2016 at 12:03 PM, Loon, EJ van (ITOPT3) - KLM <
> > > eric-van.l...@klm.com> wrote:
> > >
> > > > Hi guys!
> > > > I have an issue with one of my Oracle customers. They have several
> > RedHat
> > > > 5.8 servers (with Oracle 10) which had TSM 5.5 running, along with
TDP
> > > for
> > > > Oracle 5.5.2.
> > > > Since the OS support the new 7.1.4 client, they upgraded the BA and
API
> > > > client to 7.1.4. Since that moment they can no longer delete
obsolete
> > > > backup objects. In TDPOSYSNC you see the list of obsolete objects,
but
> > as
> > > > soon as you try to delete them it returns the following error:
> > > >
> > > > ANS0246E (RC2070) Issue dsmEndTxn and then begin a new transaction
> > > session.
> > > >
> > > > The TDP for Oracle 5.5.2 requirement list states "A Tivoli Storage
> > > Manager
> > > > API V5.5, or later", so technically it should be compatible...
> > > > Does anybody else ran into this issue before? And if so, how did
you
> > > solve
> > > > it? I know I could have them downgrade the BA and API client again,
but
> > > > then I also have to find a way to force a full back up on the BA
> > > client...
> > > > Thanks for any help in advance!
> > > > Kind regards,
> > > > Eric van Loon
> > > > Air France/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
> > > > 
> > > >
> > >
> > >
> > >
> > > --
> > > *Zoltan Forray*
> > > TSM Software & Hardware Administrator
> > > Xymon Monitor Administrator
> > > VMware Administrator (in training)
> > > 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://infosecurity.vcu.edu/phishing.html
> > >
> >
>
>
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Xymon Monitor Administrator
> VMware Administrator (in training)
> 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://infosecurity.vcu.edu/phishing.html
>

Re: RFE - DEACTIVATE FS

[Martin Janosik]

Hi Yann,

it seems the proposed functionality can be already achieved via command
DECOMMISSION VM while specifying FSID. Here is a real-word test:

Server Version 7, Release 1, Level 3.0 @AIX

tsm: TSM_2>q fi SERVERA

Node Name   Filespace   FSID Platform Filespace Is
Filesp-Capacity   Pct
Name  Type  ace
Unico-  Util

de?
--- ---   -
-- --- -
SERVERA /  1 Linux86  EXT2
No4,925 MB  52.7
SERVERA /home  2 Linux86  EXT2
No   32,127 MB   8.5

tsm: TSM_2>decommission vm SERVERA 2 nametype=fsid
ANR3392W DECOMMISSION VM: This command will decommission the specified
virtual machine. The active files that belong to the virtual machine will
be inactivated, and the file space of the
virtual machine will be automatically deleted after its all the files are
expired.

Do you wish to proceed? (Yes (Y)/No (N)) y
ANR3394I Process 3634 was started to decommission virtual machine 2 on node
SERVERA.
ANS8003I Process number 3634 started.

tsm: TSM_2>q act s=3634
01/25/2016 07:50:43 ANR0984I Process 3634 for DECOMMISSION VM started
in the BACKGROUND at 07:50:43. (SESSION: 2898529, PROCESS: 3634)
01/25/2016 07:50:43 ANR3394I Process 3634 was started to decommission
virtual machine 2 on node SERVERA. (SESSION: 2898529, PROCESS: 3634)
01/25/2016 07:51:25 ANR0987I Process 3634 for DECOMMISSION VM running
in the BACKGROUND processed 69,547 items with a completion state of SUCCESS
at 07:51:25. (SESSION: 2898529, PROCESS: 3634)

tsm: TSM_2>select state, count(*) from backups where node_name='SERVERA'
and FILESPACE_ID=2 group by state

STATE   Unnamed[2]
- 
INACTIVE_VERSION 69547

Bye

M. Janosik

"ADSM: Dist Stor Manager"  wrote on 01/25/2016
01:33:03 PM:

> From: "Meunier, Yann" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 01/25/2016 01:34 PM
> Subject: [ADSM-L] RFE - DEACTIVATE FS
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi,
>
> I’ve just post a new RFE : https://www.ibm.com/developerworks/rfe/
> execute?use_case=viewRfe_ID=82944
> What do you think about ?
>
> Best Regards,
> Yann MEUNIER
>
>
>
>
> Ce message et toutes les pièces jointes (ci-après le « message »)
> sont confidentiels et établis à l’intention exclusive de ses
> destinataires. Toute utilisation de ce message non conforme à sa
> destination, toute diffusion ou toute publication, totale ou
> partielle, est interdite, sauf autorisation expresse. Si vous
> recevez ce message par erreur, merci de le détruire sans en
> conserver de copie et d’en avertir immédiatement l’expéditeur.
> Internet ne permettant pas de garantir l’intégrité de ce message, la
> Caisse des Dépôts et Consignations décline toute responsabilité au
> titre de ce message s’il a été modifié, altéré, déformé ou falsifié.
> Par ailleurs et malgré toutes les précautions prises pour éviter la
> présence de virus dans nos envois, nous vous recommandons de
> prendre, de votre côté, les mesures permettant d'assurer la non-
> introduction de virus dans votre système informatique.
>
> This email message and any attachments (“the email”) are
> confidential and intended only for the recipient(s) indicated. If
> you are not an intended recipient, please be advised that any use,
> dissemination, forwarding or copying of this email whatsoever is
> prohibited without prior written consent of Caisse des Depots et
> Consignations. If you have received this email in error, please
> delete it without saving a copy and notify the sender immediately.
> Internet emails are not necessarily secure, and Caisse des Depots et
> Consignations declines responsibility for any changes that may have
> been made to this email after it was sent. While we take all
> reasonable precautions to ensure that viruses are not transmitted
> via emails, we recommend that you take your own measures to prevent
> viruses from entering your computer system.
>

LTO-5 Compression ratio

[Martin Janosik]

Hello all,

I'm looking for an advice or hint with following situation:
On one TSM server I'm observing weird (pretty high) compression ratio on
most of tapes. I wonder if it is possible to replicate this "success" to
other TSM server(s) with same/similar configuration, but I'm clueless on
where to start.

Volume Name Storage poolDevice ClassEstimated Capacity
Pct. UtilizationStatus
CO0250L5SPT_ORA DEVCLPR62   8.7 T   34.4Full
CO0273L5SPT_ORA DEVCLPR62   8.3 T   48.1Full
CO0091L5SPT_ORA DEVCLPR62   7.6 T   58.6Full
CO0308L5SPT_DB2 DEVCLPR62   7.1 T   60.4Full
CO0316L5SPT_DB2 DEVCLPR62   6.8 T   77  Full
CO0232L5SPT_DB2 DEVCLPR62   6.5 T   64.7Full
CO0056L5SPT_DB2 DEVCLPR62   6.4 T   84.7Full
CO0244L5SPT_DB2 DEVCLPR62   6.4 T   81.3Full
CO0026L5SPT_DB2 DEVCLPR62   6.1 T   90.2Full
CO0127L5SPT_DB2 DEVCLPR62   6.0 T   38  Full
CO0325L5SPT_SAP DEVCLPR62   6.0 T   61.9Full
CO0061L5SPT_DB2 DEVCLPR62   5.9 T   97.3Full
CO0228L5SPT_SAP DEVCLPR62   5.9 T   59.4Full
CO0071L5SPT_SAP DEVCLPR62   5.8 T   89.7Full
CO0189L5SPT_SAP DEVCLPR62   5.8 T   90  Full
CO0205L5SPT_SAP DEVCLPR62   5.8 T   90.2Full
CO0221L5SPT_SAP DEVCLPR62   5.8 T   66.1Full
CO0376L5SPT_SAP DEVCLPR62   5.8 T   99.9Full
CO0404L5SPT_SAP DEVCLPR62   5.8 T   90.2Full
CO0306L5SPT_SAP DEVCLPR62   5.7 T   86.5Full
CO0078L5SPT_SAP DEVCLPR62   5.6 T   71.9Full
CO0285L5SPT_SAP DEVCLPR62   5.6 T   93.4Full

Previous output is sorted by capacity, listed only Full tapes because for
those capacity is confirmed as real. Compression ratio is up to 5.8:1,
Stored data are Oracle/DB2/SAP Oracle, full backups and logs. One exception
is storage pool SPT_DB2 which holds backups of "directories" (someone
forgot to set up correctly DIRMC).
Tapes are created by "migration from disk stgpool" or by "clients directly
writing on tapes", there is no LAN-Free, compression is disabled on client
servers.
We use IBM TS1050 (ULT3580-TD5) tape drives in TS3500 library with mixed
firmware E6Q6 and  D8D4 attached via 8Gb/s TAN(SAN) network.

Any idea or suggestion is welcomed.

Thank you
M. Janosik

Re: TDP for SAP issue

[Martin Janosik]

Hi Eric,

during API initialization some libraries are loaded even if they are not
used at all - ie ssl libraries can be loaded even though SSL is not used
for client-server connection. This same applies also to encryption
libraries. By default AES128 encryption library is attempted.
But some older TDP applications are not happy if it tries to load AES128
encryption library that was installed as part of newer TSM API. In this
case you need to fallback to DES56 encryption library (even if you do not
intent to use them).

Bye

Martin J.

"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/10/2015
09:05:05 AM:

> From: "Loon, EJ van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> To: ADSM-L@VM.MARIST.EDU
> Date: 12/10/2015 09:06 AM
> Subject: Re: [ADSM-L] TDP for SAP issue
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Hi Martin!
> Like I specified in my mail, I do not want to use encryption at all!
> Encryption is killing for deduplication. But it's a bug that the TDP
> 6.2 client requires encryption to be switched on before it's working
> with the 7.1 API...
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Martin Janosik
> Sent: woensdag 9 december 2015 16:59
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: TDP for SAP issue
>
> Hello,
>
> by specifying 'ENCRYPTIONType DES56' in dsm.sys stanza you are just
> overwriting default value that is 'ENCRYPTIONType AES128'.
> If you want to enable encryption for your customer's backup, you
> need to specify it explicitly - via 'include.encrypt /.../*' in your
> include/exclude list or client option set.
> Have a look on
> http://www-304.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/
> com.ibm.itsm.client.develop.doc/c_encryp_transp.html
>
>
> Martin J.
>
> "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/09/2015
> 03:00:36 PM:
>
> > From: "Loon, EJ van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 12/09/2015 03:02 PM
> > Subject: [ADSM-L] TDP for SAP issue
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
> >
> > Hi guys!
> > One of my customers has an issue on his TDP for SAP clients. They are
> > using TDP for SAP 6.2 and recently we upgraded all TSM clients to 7.1.
> > This caused the TDP clients to fail with the following error:
> >
> > ANS1463E (RC5801) Unexpected error in cryptography library.
> >
> > In the API error log:
> >
> > 11/02/15 14:27:04 ANS1467E ICC routine ICC_SetValue
> > (ICC_FIPS_APPROVED_MODE) returned: majRC = 2, minRC = 2, desc =
> > 'Invalid data value: icclib.c:921'.
> >
> > We do not use any encryption, but as soon as the customer adds the
> > line ENCRYPTIONTYPE DES56 to the dsm.sys, the backup works! So that's
> > what he did, but now I have an issue, because encryption is killing
> > for the deduplication on the backend Data Domain...
> > IBM won't help me with this bug because TDP for SAP 6.2 is out of
> > support. The customer does not want to upgrade to TDP for SAP 7.1.3
> > yet because they need to validate this version first.
> > I could downgrade the BA/API client to 6.2, but then I have to force a
> > full back up again for the BA client, because restoring 7.1 data with
> > a 6.2 client will most likely not work. So I was hoping to find some
> > work-around. Is it maybe possible to somehow install the 6.2 API next
> > to the 7.1 API? In that case I need to figure out how to make the TDP
> > client use this API version only...
> > 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

Re: TDP for SAP issue

[Martin Janosik]

Hello Eric,

if you start dsmc and look up help for 'encryptiontype' parameter, will
find exactly this info which state AES128 is default value.

Syntax

   .-AES128-.
>>-ENCRYPTIONType--++--><
   '-DES56--'

Parameters

AES128
   AES 128-bit data encryption. AES 128-bit data encryption provides a
   stronger form of data encryption than DES 56-bit data encryption.
   This is the default.

DES56
   DES 56-bit data encryption.

Hope that helps

Martin J.

"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/10/2015
11:28:27 AM:

> From: "Loon, EJ van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> To: ADSM-L@VM.MARIST.EDU
> Date: 12/10/2015 11:29 AM
> Subject: Re: [ADSM-L] TDP for SAP issue
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Hi Martin!
> You stated " By default AES128 encryption library is attempted". Is
> that true? By default there is no ENCRYPTIONTYPE parameter in the
> dsm.sys which means no encryption at all.
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Martin Janosik
> Sent: donderdag 10 december 2015 10:46
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: TDP for SAP issue
>
> Hi Eric,
>
> during API initialization some libraries are loaded even if they are
> not used at all - ie ssl libraries can be loaded even though SSL is
> not used for client-server connection. This same applies also to
> encryption libraries. By default AES128 encryption library is attempted.
> But some older TDP applications are not happy if it tries to load
> AES128 encryption library that was installed as part of newer TSM
> API. In this case you need to fallback to DES56 encryption library
> (even if you do not intent to use them).
>
> Bye
>
> Martin J.
>
> "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/10/2015
> 09:05:05 AM:
>
> > From: "Loon, EJ van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 12/10/2015 09:06 AM
> > Subject: Re: [ADSM-L] TDP for SAP issue Sent by: "ADSM: Dist Stor
> > Manager" <ADSM-L@VM.MARIST.EDU>
> >
> > Hi Martin!
> > Like I specified in my mail, I do not want to use encryption at all!
> > Encryption is killing for deduplication. But it's a bug that the TDP
> > 6.2 client requires encryption to be switched on before it's working
> > with the 7.1 API...
> > Kind regards,
> > Eric van Loon
> > AF/KLM Storage Engineering
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
> > Of Martin Janosik
> > Sent: woensdag 9 december 2015 16:59
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: TDP for SAP issue
> >
> > Hello,
> >
> > by specifying 'ENCRYPTIONType DES56' in dsm.sys stanza you are just
> > overwriting default value that is 'ENCRYPTIONType AES128'.
> > If you want to enable encryption for your customer's backup, you need
> > to specify it explicitly - via 'include.encrypt /.../*' in your
> > include/exclude list or client option set.
> > Have a look on
> > http://www-304.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/
> > com.ibm.itsm.client.develop.doc/c_encryp_transp.html
> >
> >
> > Martin J.
> >
> > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/09/2015
> > 03:00:36 PM:
> >
> > > From: "Loon, EJ van (ITOPT3) - KLM" <eric-van.l...@klm.com>
> > > To: ADSM-L@VM.MARIST.EDU
> > > Date: 12/09/2015 03:02 PM
> > > Subject: [ADSM-L] TDP for SAP issue
> > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
> > >
> > > Hi guys!
> > > One of my customers has an issue on his TDP for SAP clients. They
> > > are using TDP for SAP 6.2 and recently we upgraded all TSM clients to
7.1.
> > > This caused the TDP clients to fail with the following error:
> > >
> > > ANS1463E (RC5801) Unexpected error in cryptography library.
> > >
> > > In the API error log:
> > >
> > > 11/02/15 14:27:04 ANS1467E ICC routine ICC_SetValue
> > > (ICC_FIPS_APPROVED_MODE) returned: majRC = 2, minRC = 2, desc =
> > > 'Invalid data value: icclib.c:921'.
> > >
> > > We do not use any encryption, but as soon as the customer adds the
> > > line ENCRYPTIONTYPE DES56 to the dsm.sys, the backup works! So

Re: TDP for SAP issue

[Martin Janosik]

Hello,

by specifying 'ENCRYPTIONType DES56' in dsm.sys stanza you are just
overwriting default value that is 'ENCRYPTIONType AES128'.
If you want to enable encryption for your customer's backup, you need to
specify it explicitly - via 'include.encrypt /.../*' in your
include/exclude list or client option set.
Have a look on
http://www-304.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.develop.doc/c_encryp_transp.html


Martin J.

"ADSM: Dist Stor Manager"  wrote on 12/09/2015
03:00:36 PM:

> From: "Loon, EJ van (ITOPT3) - KLM" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 12/09/2015 03:02 PM
> Subject: [ADSM-L] TDP for SAP issue
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi guys!
> One of my customers has an issue on his TDP for SAP clients. They
> are using TDP for SAP 6.2 and recently we upgraded all TSM clients
> to 7.1. This caused the TDP clients to fail with the following error:
>
> ANS1463E (RC5801) Unexpected error in cryptography library.
>
> In the API error log:
>
> 11/02/15 14:27:04 ANS1467E ICC routine ICC_SetValue
> (ICC_FIPS_APPROVED_MODE) returned: majRC = 2, minRC = 2, desc =
> 'Invalid data value: icclib.c:921'.
>
> We do not use any encryption, but as soon as the customer adds the
> line ENCRYPTIONTYPE DES56 to the dsm.sys, the backup works! So
> that's what he did, but now I have an issue, because encryption is
> killing for the deduplication on the backend Data Domain...
> IBM won't help me with this bug because TDP for SAP 6.2 is out of
> support. The customer does not want to upgrade to TDP for SAP 7.1.3
> yet because they need to validate this version first.
> I could downgrade the BA/API client to 6.2, but then I have to force
> a full back up again for the BA client, because restoring 7.1 data
> with a 6.2 client will most likely not work. So I was hoping to find
> some work-around. Is it maybe possible to somehow install the 6.2
> API next to the 7.1 API? In that case I need to figure out how to
> make the TDP client use this API version only...
> 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
> 
>