Re: How to backup Exchange full using multiple concurrent sessions

[Tian Miao Liu]

Hi,

It should be fine to run the parallel backup on different databases
that are not on the same LUN/volumes.
For your problem, RC 418 means TSM API error, please check
dsmerror.log under baclient directory to see if there is any error
messages. Also you can contact support for help.

Best regards.
Tian Miao Liu


"ADSM: Dist Stor Manager"  wrote on 04/27/2016
08:58:20 AM:

> From: "Schaub, Steve" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 04/27/2016 09:01 AM
> Subject: [ADSM-L] How to backup Exchange full using multiple
> concurrent sessions
> Sent by: "ADSM: Dist Stor Manager" 
>
> TDP 6.4.1, moving to 7.1.4 very soon.
>
> We are having some single-stream throughput issues and while I wait
> for that resolution, I need to find a way to shrink my full Exchange
> database backup runtimes.
> So far, I have not found anything easy built in, for example the "/
> stripes=x" parm I can use for SQL Server.
> Barring that, testing scripting logic to run multiple concurrent
> databases has been problematic.
>
> I keep seeing this error, making me think the CAD is somehow
> limiting me from running multiple command line specific backups of
> different databases?
> Both CAD and the Remote Client Agent are installed & running.
>
> "ANS2619S The Client Acceptor Daemon was unable to start the Remote
> Client Agent."
>
> Using this command in powershell:
> & .\TDPEXCC BACKUP $myDatabase FULL /SkipIntegrityCheck /
> DAGNode=EXCHANGE2010 /BackupMethod=VSS /BackupDestination=TSM /
> LogFile=$myTsmSchedLog
>
> Looks like the first one in works, the one that tries to run next
> gets a rc=418
>
> What am I missing?
>
> Steve Schaub
> Systems Engineer II, Backup/Recovery
> Blue Cross Blue Shield of Tennessee
> 423-535-6574 (desk)
> 423-785-7347 (cell)
>
>
>
--

> Please see the following link for the BlueCross BlueShield of
> Tennessee E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm
>

Re: TSM Client upgrade on AIX

[Andrew Raibeck]

Hi Pam,

During incremental backup, the peak memory utilization usually occurs when
the client is processing the directory with the largest number of files. In
this case, unless your machine has only 8 MB of RAM ;-) I do not see how
~15K objects could cause memory to be exhausted. It doesn't pass the "sniff
test".

Regarding the 6.4 error where you see the return code 11: This most likely
corresponds to errno EAGAIN, which means there were insufficient system
resources to create a new thread. This is not an insufficient memory issue,
but some other system resource.

A shot in the dark, but... by any chance is the AIX system configured to
use 64 KB page sizes? I ask because of this AIX APAR which *might* be a
match:

http://www.ibm.com/support/docview.wss?uid=isg1IZ27457

(See the Comments section of the APAR to match the acutal 6.1 maintenance
level.)

Best regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-27
15:56:42:

> From: "Pagnotta, Pamela (CONTR)" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-27 15:59
> Subject: Re: TSM Client upgrade on AIX
> Sent by: "ADSM: Dist Stor Manager" 
>
> Andy,
>
> Here is the top few entries from the select statement. From what I
> can tell, none of the filesystems have more than 200K objects on this
client.
>
> FILESPACE_NAME: /gridfs
>HL_NAME: /oraem/Oracle/admin/emrep/adump/
>  TOTAL_OBJECTS: 15551
>
> FILESPACE_NAME: /gridfs
>HL_NAME: /oraem/Oracle/middleware/oms/sysman/archives/emgc/
> deployments/GCDomain/emgc.ear/em.war/cabo/jsLibs/resources/
>  TOTAL_OBJECTS: 2473
>
> FILESPACE_NAME: /gridfs
>HL_NAME: /oraem/Oracle/middleware/logs/
>  TOTAL_OBJECTS: 2344
>
> Since moving back to version 6.4.2.0 there is a new message
>
> 04/27/16   02:33:22 ANS0361I DIAG: Thread creation failed; rc=11.
> 04/27/16   02:33:24 ANS1999E Incremental processing of '/usr' stopped.
>
> The only Technote I can find that is close to this message and rc is
> TSM server related on a Linux system.  Is there anywhere where these
> diagnostic return codes are defined for TSM administrators?
>
> I have moved this backup to a quieter time of the night to see if
> that helps at all.
>
> I will open a ticket for this new error tomorrow.
>
> Thank you,
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office: 301-903-5508
> Mobile: 301-335-8177
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Andrew Raibeck
> Sent: Wednesday, April 27, 2016 2:19 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] TSM Client upgrade on AIX
>
> Hi Pam,
>
> Do any of the file systems happen to have directories that contain large
> numbers of files (say, more than a million)? You could try running this
> SELECT statement from an administrative command line client to assess
this.
> Make sure to the node name RAIBECK with your node name (in all upper
case):
>
> select filespace_name, hl_name, count(*) as total_objects from backups
> where node_name='RAIBECK' and state='ACTIVE_VERSION' group by
> filespace_name, hl_name order by 3 desc
>
> You can cancel the output after the first few lines. What you are looking
> for is the top of the list, which would show you which file system and
> directory has the largest number of files. How many objects are there?
>
> If there are millions of files involved, it could be that memory is being
> exhausted (how much memory is available on this system?); though I would
> normally expect a proper "out of memory" message, rather than the more
> cryptic message you are seeing. In the past, I have heard customers say
> that this occurs after upgrading the client, but what really happened was
> that the number of files in the directory was growing continuously, and
> eventually the backup could not allocate enough memory; and the upgrade
> just happened to roughly coincide with the onset of the issue. I cannot
say
> whether this is possible in your situation, but I am just sharing some of
> my past experiences with this issue.
>
> From which client version and bit-architecture did you upgrade to 7.1? I
> see you put 6.4 on as a "workaround", but what was the original version?
> Earlier client versions did see an increase in memory usage when the
> clients were changed from 32-bit to 64-bit, as 64-bit software tends to
use
> more memory (pointer variables are 8 bytes rather than 4 bytes, and that
is
> one chief contributor). But no suc

Re: TSM Client upgrade on AIX

[Pagnotta, Pamela (CONTR)]

Andy,

Here is the top few entries from the select statement. From what I can tell, 
none of the filesystems have more than 200K objects on this client. 

FILESPACE_NAME: /gridfs
   HL_NAME: /oraem/Oracle/admin/emrep/adump/
 TOTAL_OBJECTS: 15551

FILESPACE_NAME: /gridfs
   HL_NAME: 
/oraem/Oracle/middleware/oms/sysman/archives/emgc/deployments/GCDomain/emgc.ear/em.war/cabo/jsLibs/resources/
 TOTAL_OBJECTS: 2473

FILESPACE_NAME: /gridfs
   HL_NAME: /oraem/Oracle/middleware/logs/
 TOTAL_OBJECTS: 2344

Since moving back to version 6.4.2.0 there is a new message

04/27/16   02:33:22 ANS0361I DIAG: Thread creation failed; rc=11.
04/27/16   02:33:24 ANS1999E Incremental processing of '/usr' stopped.

The only Technote I can find that is close to this message and rc is TSM server 
related on a Linux system.  Is there anywhere where these diagnostic return 
codes are defined for TSM administrators?

I have moved this backup to a quieter time of the night to see if that helps at 
all.

I will open a ticket for this new error tomorrow. 

Thank you,

Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew 
Raibeck
Sent: Wednesday, April 27, 2016 2:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Client upgrade on AIX

Hi Pam,

Do any of the file systems happen to have directories that contain large
numbers of files (say, more than a million)? You could try running this
SELECT statement from an administrative command line client to assess this.
Make sure to the node name RAIBECK with your node name (in all upper case):

select filespace_name, hl_name, count(*) as total_objects from backups
where node_name='RAIBECK' and state='ACTIVE_VERSION' group by
filespace_name, hl_name order by 3 desc

You can cancel the output after the first few lines. What you are looking
for is the top of the list, which would show you which file system and
directory has the largest number of files. How many objects are there?

If there are millions of files involved, it could be that memory is being
exhausted (how much memory is available on this system?); though I would
normally expect a proper "out of memory" message, rather than the more
cryptic message you are seeing. In the past, I have heard customers say
that this occurs after upgrading the client, but what really happened was
that the number of files in the directory was growing continuously, and
eventually the backup could not allocate enough memory; and the upgrade
just happened to roughly coincide with the onset of the issue. I cannot say
whether this is possible in your situation, but I am just sharing some of
my past experiences with this issue.

>From which client version and bit-architecture did you upgrade to 7.1? I
see you put 6.4 on as a "workaround", but what was the original version?
Earlier client versions did see an increase in memory usage when the
clients were changed from 32-bit to 64-bit, as 64-bit software tends to use
more memory (pointer variables are 8 bytes rather than 4 bytes, and that is
one chief contributor). But no such change occurred from 6.4 to 7.1, so why
memory would be exhausted in 7.1 but not 6.4, I have no immediate idea.

If the affected machine does not really have any directories with huge
numbers of files, then this could be something else... I would invite you
to reopen your PMR, let me know, and I will have it escalated to our Level
2 support for further investigation. As I mentioned earlier, the cryptic
calloc() error does not seem right.

Best regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-27
13:15:50:

> From: "Pagnotta, Pamela (CONTR)" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-27 13:17
> Subject: Re: Re: TSM Client upgrade on AIX
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi Dave,
>
> Thank you for the information. I, of course, could not get the
> person assigned to my ticket to even acknowledge that this might be
> due to some different memory requirements for the newer TSM clients.
> The only response I received was that we just must not have enough
> memory on our system to do the backup despite being told that there
> was no issue with an older client.
>
> Pam
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office

Re: TSM Server 7.1.4 woes

[Andrew Raibeck]

Follow-up:

Can you put the QUIET option in the client options file, then try the
restore again? This is without upgrading the client software.

Let me know if this enables a successful restore from tape.

Best regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-27
12:54:02:

> From: Andrew Raibeck/Hartford/IBM@IBMUS
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-27 12:57
> Subject: Re: TSM Server 7.1.4 woes
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi Michael,
>
> I am looking further into this, but have you tried the latest 6.1 client
> level? I tested 6.1.0.0, and I get the same error you do (backing up to
LTO
> tape). I tried the restore with 6.1.5.0 and it was successful.
>
> server: 7.1.4 on AIX
> client: 6.1.0.0 on Windows 7 (backup and first restore test)
> client: 6.1.5.0 on Windows 7 (restore of file backed up with 6.1.0.0 was
> successful)
>
> Regards,
>
> Andy
>
>


>
> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
>
> IBM Tivoli Storage Manager links:
> Product support:
>
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

>
> Online documentation:
>
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

>
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager"  wrote on 2016-04-27
> 09:43:00:
>
> > From: Michael Prix 
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2016-04-27 09:44
> > Subject: Re: TSM Server 7.1.4 woes
> > Sent by: "ADSM: Dist Stor Manager" 
> >
> > Hello Andrew,
> >
> >   yes, you are correct ANS4035W ist the correct message.
> > As of your suggestions, we did some backups and restores and found out
> that
> > this error only appears if the object resides on tape. It doesn't
matter
> if
> > tape is primary, copy or nextstoragepool.
> >
> > This error appears on Windows, Linux (x and p) and AIX clients up to
and
> > including Client Version 6.1.x.y (other OS and Versions still testing)
> working
> > with Linux (x and p), AIX and Windows servers.
> >
> > ANE4035W reported in Actlog.
> >
> > --
> > Michael PrixOn Mi, 2016-04-27 at 08:38 -0400, Andrew Raibeck wrote:
> > > And another question:
> > >
> > > I think the message is on the client, ANS4035W (not ANR4035W)? When
the
> > > problem occurs, are there any messages displayed in the server
activity
> log
> > > that would seem to correspond with this issue?
> > >
> > > Andy
> > >
> > >
>


>
> > >
> > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> > >
> > > IBM Tivoli Storage Manager links:
> > > Product support:
> > >
>
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manag

>
> > > er
> > >
> > > Online documentation:
> > >
>
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.htm

>
> > > l
> > >
> > > Product Wiki:
> > >
>
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storag

>
> > > e%20Manager
> > >
> > > "ADSM: Dist Stor Manager"  wrote on 2016-04-27
> > > 08:36:23:
> > >
> > > > From: Andrew Raibeck/Hartford/IBM@IBMUS
> > > > To: ADSM-L@VM.MARIST.EDU
> > > > Date: 2016-04-27 08:37
> > > > Subject: Re: TSM Server 7.1.4 woes
> > > > Sent by: "ADSM: Dist Stor Manager" 
> > > >
> > > > Hello Michael,
> > > >
> > > > On what type of media does the backup data reside? Does this
restore
> > > issue
> > > > occur when the data is on:
> > > >
> > > > * Disk (random access, device class DISK)
> > > > * Disk (sequential, device class FILE)
> > > > * Tape (a tape device class)
> > > > * Next generation storage pool
> > > >
> > > > What type (operating system, e.g., Windows, AIX, Linux) of clients
do
> you
> > > > know to be affected?
> > > >
> > > > Best regards,
> > > >
> > > > Andy
> > > >
> > > >
> > >
>


>
> > >
> > > >
> > > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> > > >
> > > > IBM Tivoli Storage Manager links:
> > > > Product support:
> > > >
> > >
>
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manag

>
> > > er
> > >
> > > >
> > > > Online documentation:
> > > >
> > >
>
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.htm

>
> > > l
> > >
> > > >
> > > > Product Wiki:
> > > >
https://www.ibm.com/developerwork

Re: TSM Client upgrade on AIX

[Andrew Raibeck]

Hi Pam,

Do any of the file systems happen to have directories that contain large
numbers of files (say, more than a million)? You could try running this
SELECT statement from an administrative command line client to assess this.
Make sure to the node name RAIBECK with your node name (in all upper case):

select filespace_name, hl_name, count(*) as total_objects from backups
where node_name='RAIBECK' and state='ACTIVE_VERSION' group by
filespace_name, hl_name order by 3 desc

You can cancel the output after the first few lines. What you are looking
for is the top of the list, which would show you which file system and
directory has the largest number of files. How many objects are there?

If there are millions of files involved, it could be that memory is being
exhausted (how much memory is available on this system?); though I would
normally expect a proper "out of memory" message, rather than the more
cryptic message you are seeing. In the past, I have heard customers say
that this occurs after upgrading the client, but what really happened was
that the number of files in the directory was growing continuously, and
eventually the backup could not allocate enough memory; and the upgrade
just happened to roughly coincide with the onset of the issue. I cannot say
whether this is possible in your situation, but I am just sharing some of
my past experiences with this issue.

>From which client version and bit-architecture did you upgrade to 7.1? I
see you put 6.4 on as a "workaround", but what was the original version?
Earlier client versions did see an increase in memory usage when the
clients were changed from 32-bit to 64-bit, as 64-bit software tends to use
more memory (pointer variables are 8 bytes rather than 4 bytes, and that is
one chief contributor). But no such change occurred from 6.4 to 7.1, so why
memory would be exhausted in 7.1 but not 6.4, I have no immediate idea.

If the affected machine does not really have any directories with huge
numbers of files, then this could be something else... I would invite you
to reopen your PMR, let me know, and I will have it escalated to our Level
2 support for further investigation. As I mentioned earlier, the cryptic
calloc() error does not seem right.

Best regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-27
13:15:50:

> From: "Pagnotta, Pamela (CONTR)" 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-27 13:17
> Subject: Re: Re: TSM Client upgrade on AIX
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hi Dave,
>
> Thank you for the information. I, of course, could not get the
> person assigned to my ticket to even acknowledge that this might be
> due to some different memory requirements for the newer TSM clients.
> The only response I received was that we just must not have enough
> memory on our system to do the backup despite being told that there
> was no issue with an older client.
>
> Pam
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office: 301-903-5508
> Mobile: 301-335-8177
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of David Bronder
> Sent: Wednesday, April 27, 2016 12:56 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Re: TSM Client upgrade on AIX
>
> This isn't really helpful for your specific situation, Pam (I don't think
> I've had the specific errors you've seen).  But I have noticed (with much
> dismay) that the 7.x clients for AIX have required significantly more
memory
> than earlier versions.  I have clients with 1+ million files in a
filesystem
> that had no problems with 6.x and earlier clients, but consistently
required
> huge data ulimits after upgrading to 7.x (and would fail, often
completely
> silently, if the ulimit wasn't high enough).
>
> I don't know what IBM did with the 7.x clients to make them so
memory-greedy
> compared to earlier versions.  Maybe the client-side dedupe support or
> something, though I'm not using those newer features currently, so I
would
> hope that wouldn't be a factor.  Then again, I would hope IBM would
realize
> that setting the data ulimit to unlimited isn't really a best practice
and
> that having successful backups shouldn't require risking breaking
services on
> the systems those backups are protecting.  ()
>
> So far, I've gotten by with a non-unlimited ulimit, but it seems like I
do
> have to keep raising it with each new 7.x client release...
>
> =Dave
>
>
> 

Re: TSM Server 7.1.4 woes

[Zoltan Forray]

All this talk about server upgrade woes has me concerned, especially since
I am heading to 7.1.5  with my 6.3.5 servers.  Being a university, we have
quite a few boxes that can't/wont upgrade (Solaris 5.8 running 5.3.6.6
client,  old linux/2.4 kernel running 5.5 client, Solaris boxes running
Notes/Domino with 6.1.3 client/TDP - being twilighted, quite a few linux
x32 boxes running 6.2 client).  Thanks goodness the IRIX boxes running the
4.x client finally went away!

So how concerned should I be?

On Tue, Apr 26, 2016 at 11:19 AM, Michael Prix 
wrote:

> Yes. Where it is possible to upgrade.
>
> --
> Michael PrixOn Di, 2016-04-26 at 15:03 +, Rhodes, Richard L. wrote:
> > Were you able to restore files after upgrading a client to a supported
> > version?
> >
> > Rick
> >
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> > Michael Prix
> > Sent: Tuesday, April 26, 2016 7:04 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: TSM Server 7.1.4 woes
> >
> > Hello all,
> >
> >   it is well known that older clients are out of support, but still
> continue
> > to work with the capabilities they were designed for.
> > Now I and some colleagues of mine upgraded customers to TSM 7.1.4 and
> 7.1.5,
> > with client-versions ranging from 5.5 to 7.1, and all of a sudden all
> > clients
> > <=6.1 can still backup to the server, but aren't any longer able to
> > restore/retrieve files. ANR4035W is reported.
> > While this might not be a situation where one could get support from
> IBM, it
> > is still a new situation as we as old *SMers are used to the fact that
> old
> > clients remain useable after an upgrade.
> >
> > --
> > Michael Prix
> >
> >
> > -
> > 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.
>



--
*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: Re: TSM Client upgrade on AIX

[Pagnotta, Pamela (CONTR)]

Hi Dave,

Thank you for the information. I, of course, could not get the person assigned 
to my ticket to even acknowledge that this might be due to some different 
memory requirements for the newer TSM clients. The only response I received was 
that we just must not have enough memory on our system to do the backup despite 
being told that there was no issue with an older client.

Pam

Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David 
Bronder
Sent: Wednesday, April 27, 2016 12:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Re: TSM Client upgrade on AIX

This isn't really helpful for your specific situation, Pam (I don't think
I've had the specific errors you've seen).  But I have noticed (with much
dismay) that the 7.x clients for AIX have required significantly more memory
than earlier versions.  I have clients with 1+ million files in a filesystem
that had no problems with 6.x and earlier clients, but consistently required
huge data ulimits after upgrading to 7.x (and would fail, often completely
silently, if the ulimit wasn't high enough).

I don't know what IBM did with the 7.x clients to make them so memory-greedy
compared to earlier versions.  Maybe the client-side dedupe support or
something, though I'm not using those newer features currently, so I would
hope that wouldn't be a factor.  Then again, I would hope IBM would realize
that setting the data ulimit to unlimited isn't really a best practice and
that having successful backups shouldn't require risking breaking services on
the systems those backups are protecting.  ()

So far, I've gotten by with a non-unlimited ulimit, but it seems like I do
have to keep raising it with each new 7.x client release...

=Dave


On 04/27/2016 09:09 AM, Pagnotta, Pamela (CONTR) wrote:
> Hi Matthew,
>
> Yes, the root user ulimits is set to unlimited on all the AIX servers.
>
> Regards,
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office: 301-903-5508
> Mobile: 301-335-8177
>
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Matthew McGeary
> Sent: Wednesday, April 27, 2016 9:56 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] TSM Client upgrade on AIX
>
> Good morning Pam,
>
> We encountered errors backing up filesystems with large numbers of files 
> until we set the root user ulimits to unlimited.  That fixed the problem but 
> can have other consequences, obviously.  Do you know if your AIX admin tried 
> changing the ulimits?
>
> Regards,
> __
>
> Matthew McGeary
> Senior Technical Specialist - Infrastructure
> PotashCorp
> T: (306) 933-8921
> www.potashcorp.com
>
> From:"Pagnotta, Pamela (CONTR)" 
> To:ADSM-L@VM.MARIST.EDU
> Date:04/27/2016 07:47 AM
> Subject:[ADSM-L] TSM Client upgrade on AIX
> Sent by:"ADSM: Dist Stor Manager" 
>
> 
>
>
>
> Hello,
>
> Recently one of our AIX administrators upgraded the TSM client to 7.1.4.4 on 
> her servers. Many of them started receiving errors like
>
> calloc() failed: Size 31496 File ../mem/mempool.cpp Line 1092
>
> I looked this up and the indication is that the AIX server could not supply 
> enough memory to TSM to complete the backup. We opened a ticket and were told 
> to try memoryefficientbackup with diskcachemethod. This did not fix the issue.
>
> In frustration the administrator reinstalled a TSM client version of 6.4.2.0 
> and is no longer experiencing the memory problems.
>
> Any thoughts?
>
> Thank you,
>
> Pam
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office: 301-903-5508
> Mobile: 301-335-8177
>

--
Hello World.David Bronder - Systems Architect
Segmentation Fault  ITS-EI, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm.   david-bron...@uiowa.edu

Re: Re: TSM Client upgrade on AIX

[David Bronder]

This isn't really helpful for your specific situation, Pam (I don't think
I've had the specific errors you've seen).  But I have noticed (with much
dismay) that the 7.x clients for AIX have required significantly more memory
than earlier versions.  I have clients with 1+ million files in a filesystem
that had no problems with 6.x and earlier clients, but consistently required
huge data ulimits after upgrading to 7.x (and would fail, often completely
silently, if the ulimit wasn't high enough).

I don't know what IBM did with the 7.x clients to make them so memory-greedy
compared to earlier versions.  Maybe the client-side dedupe support or
something, though I'm not using those newer features currently, so I would
hope that wouldn't be a factor.  Then again, I would hope IBM would realize
that setting the data ulimit to unlimited isn't really a best practice and
that having successful backups shouldn't require risking breaking services on
the systems those backups are protecting.  ()

So far, I've gotten by with a non-unlimited ulimit, but it seems like I do
have to keep raising it with each new 7.x client release...

=Dave


On 04/27/2016 09:09 AM, Pagnotta, Pamela (CONTR) wrote:
> Hi Matthew,
>
> Yes, the root user ulimits is set to unlimited on all the AIX servers.
>
> Regards,
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office: 301-903-5508
> Mobile: 301-335-8177
>
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Matthew McGeary
> Sent: Wednesday, April 27, 2016 9:56 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] TSM Client upgrade on AIX
>
> Good morning Pam,
>
> We encountered errors backing up filesystems with large numbers of files 
> until we set the root user ulimits to unlimited.  That fixed the problem but 
> can have other consequences, obviously.  Do you know if your AIX admin tried 
> changing the ulimits?
>
> Regards,
> __
>
> Matthew McGeary
> Senior Technical Specialist - Infrastructure
> PotashCorp
> T: (306) 933-8921
> www.potashcorp.com
>
> From:"Pagnotta, Pamela (CONTR)" 
> To:ADSM-L@VM.MARIST.EDU
> Date:04/27/2016 07:47 AM
> Subject:[ADSM-L] TSM Client upgrade on AIX
> Sent by:"ADSM: Dist Stor Manager" 
>
> 
>
>
>
> Hello,
>
> Recently one of our AIX administrators upgraded the TSM client to 7.1.4.4 on 
> her servers. Many of them started receiving errors like
>
> calloc() failed: Size 31496 File ../mem/mempool.cpp Line 1092
>
> I looked this up and the indication is that the AIX server could not supply 
> enough memory to TSM to complete the backup. We opened a ticket and were told 
> to try memoryefficientbackup with diskcachemethod. This did not fix the issue.
>
> In frustration the administrator reinstalled a TSM client version of 6.4.2.0 
> and is no longer experiencing the memory problems.
>
> Any thoughts?
>
> Thank you,
>
> Pam
>
> Pam Pagnotta
> Sr. System Engineer
> Criterion Systems, Inc./ActioNet
> Contractor to US. Department of Energy
> Office of the CIO/IM-622
> Office: 301-903-5508
> Mobile: 301-335-8177
>

--
Hello World.David Bronder - Systems Architect
Segmentation Fault  ITS-EI, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm.   david-bron...@uiowa.edu

Re: TSM Server 7.1.4 woes

[Andrew Raibeck]

Hi Michael,

I am looking further into this, but have you tried the latest 6.1 client
level? I tested 6.1.0.0, and I get the same error you do (backing up to LTO
tape). I tried the restore with 6.1.5.0 and it was successful.

server: 7.1.4 on AIX
client: 6.1.0.0 on Windows 7 (backup and first restore test)
client: 6.1.5.0 on Windows 7 (restore of file backed up with 6.1.0.0 was
successful)

Regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-27
09:43:00:

> From: Michael Prix 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-27 09:44
> Subject: Re: TSM Server 7.1.4 woes
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hello Andrew,
>
>   yes, you are correct ANS4035W ist the correct message.
> As of your suggestions, we did some backups and restores and found out
that
> this error only appears if the object resides on tape. It doesn't matter
if
> tape is primary, copy or nextstoragepool.
>
> This error appears on Windows, Linux (x and p) and AIX clients up to and
> including Client Version 6.1.x.y (other OS and Versions still testing)
working
> with Linux (x and p), AIX and Windows servers.
>
> ANE4035W reported in Actlog.
>
> --
> Michael PrixOn Mi, 2016-04-27 at 08:38 -0400, Andrew Raibeck wrote:
> > And another question:
> >
> > I think the message is on the client, ANS4035W (not ANR4035W)? When the
> > problem occurs, are there any messages displayed in the server activity
log
> > that would seem to correspond with this issue?
> >
> > Andy
> >
> >


> >
> > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> >
> > IBM Tivoli Storage Manager links:
> > Product support:
> >
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manag

> > er
> >
> > Online documentation:
> >
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.htm

> > l
> >
> > Product Wiki:
> >
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storag

> > e%20Manager
> >
> > "ADSM: Dist Stor Manager"  wrote on 2016-04-27
> > 08:36:23:
> >
> > > From: Andrew Raibeck/Hartford/IBM@IBMUS
> > > To: ADSM-L@VM.MARIST.EDU
> > > Date: 2016-04-27 08:37
> > > Subject: Re: TSM Server 7.1.4 woes
> > > Sent by: "ADSM: Dist Stor Manager" 
> > >
> > > Hello Michael,
> > >
> > > On what type of media does the backup data reside? Does this restore
> > issue
> > > occur when the data is on:
> > >
> > > * Disk (random access, device class DISK)
> > > * Disk (sequential, device class FILE)
> > > * Tape (a tape device class)
> > > * Next generation storage pool
> > >
> > > What type (operating system, e.g., Windows, AIX, Linux) of clients do
you
> > > know to be affected?
> > >
> > > Best regards,
> > >
> > > Andy
> > >
> > >
> >


> >
> > >
> > > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> > >
> > > IBM Tivoli Storage Manager links:
> > > Product support:
> > >
> >
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manag

> > er
> >
> > >
> > > Online documentation:
> > >
> >
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.htm

> > l
> >
> > >
> > > Product Wiki:
> > > https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> > > 20Storage%20Manager
> > >
> > > "ADSM: Dist Stor Manager"  wrote on 2016-04-26
> > > 07:03:38:
> > >
> > > > From: Michael Prix 
> > > > To: ADSM-L@VM.MARIST.EDU
> > > > Date: 2016-04-26 07:04
> > > > Subject: TSM Server 7.1.4 woes
> > > > Sent by: "ADSM: Dist Stor Manager" 
> > > >
> > > > Hello all,
> > > >
> > > >   it is well known that older clients are out of support, but still
> > > continue
> > > > to work with the capabilities they were designed for.
> > > > Now I and some colleagues of mine upgraded customers to TSM 7.1.4
and
> > > 7.1.5,
> > > > with client-versions ranging from 5.5 to 7.1, and all of a sudden
all
> > > clients
> > > > <=6.1 can still backup to the server, but aren't any longer able to
> > > > restore/retrieve files. ANR4035W is reported.
> > > > While this might not be a situation where one could get support
from
> > IBM,
> > > it
> > > > is still a new situation as we as old *SMers are used to the fact
that
> > > old
> > > > clients remain useable after an upgrade.
> > > >
> > > > --
> > > > Michael Prix
> > > >
> > >
>

Re: TSM Client upgrade on AIX

[Pagnotta, Pamela (CONTR)]

Hi Matthew,

Yes, the root user ulimits is set to unlimited on all the AIX servers.

Regards,

Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177

From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Matthew McGeary
Sent: Wednesday, April 27, 2016 9:56 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Client upgrade on AIX

Good morning Pam,

We encountered errors backing up filesystems with large numbers of files until 
we set the root user ulimits to unlimited.  That fixed the problem but can have 
other consequences, obviously.  Do you know if your AIX admin tried changing 
the ulimits?

Regards,
__

Matthew McGeary
Senior Technical Specialist - Infrastructure
PotashCorp
T: (306) 933-8921
www.potashcorp.com

From:"Pagnotta, Pamela (CONTR)" 
mailto:pamela.pagno...@hq.doe.gov>>
To:ADSM-L@VM.MARIST.EDU
Date:04/27/2016 07:47 AM
Subject:[ADSM-L] TSM Client upgrade on AIX
Sent by:"ADSM: Dist Stor Manager" 
mailto:ADSM-L@VM.MARIST.EDU>>





Hello,

Recently one of our AIX administrators upgraded the TSM client to 7.1.4.4 on 
her servers. Many of them started receiving errors like

calloc() failed: Size 31496 File ../mem/mempool.cpp Line 1092

I looked this up and the indication is that the AIX server could not supply 
enough memory to TSM to complete the backup. We opened a ticket and were told 
to try memoryefficientbackup with diskcachemethod. This did not fix the issue.

In frustration the administrator reinstalled a TSM client version of 6.4.2.0 
and is no longer experiencing the memory problems.

Any thoughts?

Thank you,

Pam

Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177

Re: TSM Client upgrade on AIX

[Matthew McGeary]

Good morning Pam,

We encountered errors backing up filesystems with large numbers of files
until we set the root user ulimits to unlimited.  That fixed the problem
but can have other consequences, obviously.  Do you know if your AIX admin
tried changing the ulimits?

Regards,
__
Matthew McGeary
Senior Technical Specialist - Infrastructure
PotashCorp
T: (306) 933-8921
www.potashcorp.com




From:   "Pagnotta, Pamela (CONTR)" 
To: ADSM-L@VM.MARIST.EDU
Date:   04/27/2016 07:47 AM
Subject:[ADSM-L] TSM Client upgrade on AIX
Sent by:"ADSM: Dist Stor Manager" 



Hello,

Recently one of our AIX administrators upgraded the TSM client to 7.1.4.4
on her servers. Many of them started receiving errors like

calloc() failed: Size 31496 File ../mem/mempool.cpp Line 1092

I looked this up and the indication is that the AIX server could not
supply enough memory to TSM to complete the backup. We opened a ticket and
were told to try memoryefficientbackup with diskcachemethod. This did not
fix the issue.

In frustration the administrator reinstalled a TSM client version of
6.4.2.0 and is no longer experiencing the memory problems.

Any thoughts?

Thank you,

Pam

Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177

TSM Client upgrade on AIX

[Pagnotta, Pamela (CONTR)]

Hello,

Recently one of our AIX administrators upgraded the TSM client to 7.1.4.4 on 
her servers. Many of them started receiving errors like

calloc() failed: Size 31496 File ../mem/mempool.cpp Line 1092

I looked this up and the indication is that the AIX server could not supply 
enough memory to TSM to complete the backup. We opened a ticket and were told 
to try memoryefficientbackup with diskcachemethod. This did not fix the issue.

In frustration the administrator reinstalled a TSM client version of 6.4.2.0 
and is no longer experiencing the memory problems.

Any thoughts?

Thank you,

Pam

Pam Pagnotta
Sr. System Engineer
Criterion Systems, Inc./ActioNet
Contractor to US. Department of Energy
Office of the CIO/IM-622
Office: 301-903-5508
Mobile: 301-335-8177

Re: TSM Server 7.1.4 woes

[Michael Prix]

Hello Andrew,

  yes, you are correct ANS4035W ist the correct message.
As of your suggestions, we did some backups and restores and found out that
this error only appears if the object resides on tape. It doesn't matter if
tape is primary, copy or nextstoragepool.

This error appears on Windows, Linux (x and p) and AIX clients up to and
including Client Version 6.1.x.y (other OS and Versions still testing) working
with Linux (x and p), AIX and Windows servers.

ANE4035W reported in Actlog.

-- 
Michael PrixOn Mi, 2016-04-27 at 08:38 -0400, Andrew Raibeck wrote:
> And another question:
> 
> I think the message is on the client, ANS4035W (not ANR4035W)? When the
> problem occurs, are there any messages displayed in the server activity log
> that would seem to correspond with this issue?
> 
> Andy
> 
> 
> 
> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> 
> IBM Tivoli Storage Manager links:
> Product support:
> https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manag
> er
> 
> Online documentation:
> http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.htm
> l
> 
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storag
> e%20Manager
> 
> "ADSM: Dist Stor Manager"  wrote on 2016-04-27
> 08:36:23:
> 
> > From: Andrew Raibeck/Hartford/IBM@IBMUS
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2016-04-27 08:37
> > Subject: Re: TSM Server 7.1.4 woes
> > Sent by: "ADSM: Dist Stor Manager" 
> > 
> > Hello Michael,
> > 
> > On what type of media does the backup data reside? Does this restore
> issue
> > occur when the data is on:
> > 
> > * Disk (random access, device class DISK)
> > * Disk (sequential, device class FILE)
> > * Tape (a tape device class)
> > * Next generation storage pool
> > 
> > What type (operating system, e.g., Windows, AIX, Linux) of clients do you
> > know to be affected?
> > 
> > Best regards,
> > 
> > Andy
> > 
> > 
> 
> 
> > 
> > Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> > 
> > IBM Tivoli Storage Manager links:
> > Product support:
> > 
> https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manag
> er
> 
> > 
> > Online documentation:
> > 
> http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.htm
> l
> 
> > 
> > Product Wiki:
> > https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> > 20Storage%20Manager
> > 
> > "ADSM: Dist Stor Manager"  wrote on 2016-04-26
> > 07:03:38:
> > 
> > > From: Michael Prix 
> > > To: ADSM-L@VM.MARIST.EDU
> > > Date: 2016-04-26 07:04
> > > Subject: TSM Server 7.1.4 woes
> > > Sent by: "ADSM: Dist Stor Manager" 
> > > 
> > > Hello all,
> > > 
> > >   it is well known that older clients are out of support, but still
> > continue
> > > to work with the capabilities they were designed for.
> > > Now I and some colleagues of mine upgraded customers to TSM 7.1.4 and
> > 7.1.5,
> > > with client-versions ranging from 5.5 to 7.1, and all of a sudden all
> > clients
> > > <=6.1 can still backup to the server, but aren't any longer able to
> > > restore/retrieve files. ANR4035W is reported.
> > > While this might not be a situation where one could get support from
> IBM,
> > it
> > > is still a new situation as we as old *SMers are used to the fact that
> > old
> > > clients remain useable after an upgrade.
> > > 
> > > --
> > > Michael Prix
> > > 
> > 

Re: Reg: tsm ba client autodeploy package 7.1.4.1

[Rick Adamson]

Agreed Neil !

-Rick Adamson


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Schofield, Neil (Storage & Middleware, Backup & Restore)
Sent: Tuesday, April 26, 2016 12:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Reg: tsm ba client autodeploy package 7.1.4.1

Srikanth

I complained about the very same thing last month:
https://urldefense.proofpoint.com/v2/url?u=https-3A__adsm.org_lists_html_ADSM-2DL_2016-2D03_msg8.html&d=CwIFAg&c=AzgFQeXLLKhxSQaoFCm29A&r=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxw&m=a9Hro2QaPc6EZZX8R9Z8uzzfU8latkfezbR7j2ZVOYw&s=XCSMeZuTRcYn71vmKaOqZxzhVH6vntm2J9T7Ir9Lx0A&e=
 

I've since discovered that IBM have indeed made the decision to no longer 
supply exported packages for interim fixes. If you're using auto-deployment 
then you need to find another mechanism for pushing out interim fixes because 
it now only works for fix packs. (But then if you've got such a mechanism, why 
bother with TSM auto-deployment in the first place?)

I've not given up hope that IBM will see how perverse this approach is and 
reverse its decision. The current client fix pack (7.1.4) was released in 
November and was followed by a flash in February which described how data loss 
could occur and recommended 7.1.4.1 be installed on vulnerable systems. How 
exactly did they think large shops were supposed to push that update out to 
affected systems? Maybe customers should wait for the 7.1.5 client? No, hang on 
- they skipped that one so we're currently waiting on 7.1.6 with its associated 
.EXP files.

I agree that there are good reasons why customers should think carefully before 
auto-deploying interim fixes. For what it's worth I think IBM should tell them 
the reasons, publish the exported packages anyway and give them the *choice* of 
being able to perform tightly targeted deployments where there is a requirement 
to do so.

Regards
Neil



Neil Schofield
Tivoli Storage Manager SME
Backup & Recovery | Storage & Middleware | Central Infrastructure Services | 
Infrastructure & Service Delivery | Group IT LLOYDS BANKING GROUP


Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. 
Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. 
Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England 
and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered 
Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. 
Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: 
Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. 
Telephone: 0345 603 1637

Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential 
Regulation Authority and regulated by the Financial Conduct Authority and 
Prudential Regulation Authority.

Cheltenham & Gloucester plc is authorised and regulated by the Financial 
Conduct Authority.

Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings 
is a division of Lloyds Bank plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in 
Scotland no. SC218813.

This e-mail (including any attachments) is private and confidential and may 
contain privileged material. If you have received this e-mail in error, please 
notify the sender and delete it (including any attachments) immediately. You 
must not copy, distribute, disclose or use any of the information in it or any 
attachments. Telephone calls may be monitored or recorded.

Re: Manual db2 online reorg for ver.6.3

[Del Hoobler]

The TSM 6.3 reorganization server option default values are appropriate 
most (but not all) of the time. In this environment the default values are 
not optimal and you should continue to use the current values for the 
reorganization server options.


Thank you,

Del




"ADSM: Dist Stor Manager"  wrote on 04/26/2016 
06:55:50 AM:

> From: Krzysztof Przygoda 
> To: ADSM-L@VM.MARIST.EDU
> Date: 04/26/2016 06:56 AM
> Subject: Re: Manual db2 online reorg for ver.6.3
> Sent by: "ADSM: Dist Stor Manager" 
> 
> Thank you Del for clarification.
> Now its getting strange after:
> "With Spectrum Protect server version 6.3, IBM does not recommend online 
index
> reorganization on
> 
BF_AGGREGATED_BITFILES,BF_BITFILE_EXTENTS,BACKUP_OBJECTS,ARCHIVE_OBJECTS"
> as I did it with success (and significant reduce of db and increase of
> overall performance) on several such servers.
> Could you elaborate more on why is such recommendation now? Previously I
> thought that those tables are disabled by default to make people aware 
of
> enabling them.
> Kind regards
> Krzysztof
> 
> 
> 2016-04-25 17:09 GMT+02:00 Del Hoobler :
> 
> > In
> >
http://www-01.ibm.com/support/docview.wss?uid=swg21683633#online_index
> > IBM was trying to discuss the improvements that have been made to the 
on
> > line index reorganization initiated by the Spectrum Protect server. It 
was
> > not IBM's intention to recommend that the above DB2 commands be 
executed
> > outside of the Spectrum Protect server. Except for some exceptional 
case
> > on line reorganization should only be initiated by the Spectrum 
Protect
> > server.
> >
> > For Spectrum Protect server version 6.3, IBM recommends upgrading to 
at
> > least version 6.3.5.000 which will allow the use of this server option
> >DISABLEREORGINDEX
> > the default value for DISABLEREORGINDEX is
> > 
BF_AGGREGATED_BITFILES,BF_BITFILE_EXTENTS,BACKUP_OBJECTS,ARCHIVE_OBJECTS
> >
> > With Spectrum Protect server version 6.3, IBM does not recommend on 
line
> > index reorganization on
> > 
BF_AGGREGATED_BITFILES,BF_BITFILE_EXTENTS,BACKUP_OBJECTS,ARCHIVE_OBJECTS
> >
> >
> > IBM will clarify the information and update the technote.
> >
> >
> >
> > Thank you,
> >
> > Del
> >
> > 
> >
> > "ADSM: Dist Stor Manager"  wrote on 04/25/2016
> > 06:34:58 AM:
> >
> > > From: Krzysztof Przygoda 
> > > To: ADSM-L@VM.MARIST.EDU
> > > Date: 04/25/2016 06:35 AM
> > > Subject: Re: Manual db2 online reorg for ver.6.3
> > > Sent by: "ADSM: Dist Stor Manager" 
> > >
> > > Anyone from IBM?
> > > Recently we raised PMR with such but support seems just to quote the
> > same
> > > docs...
> > > Kind regards
> > > Krzysztof
> > >
> > >
> > > 2016-04-22 10:11 GMT+02:00 Krzysztof Przygoda :
> > >
> > > > Hi
> > > > Just wondering if anyone tried with TSM ver 6.3  method described 
in
> > > > document related to ver 7.1
> > > > http://www-01.ibm.com/support/docview.wss?uid=swg21683633
> > > >
> > > > "*Online index reorganization*
> > > >
> > > > You can initiate online index reorganization by running a command 
with
> > the
> > > > following syntax:
> > > > db2 reorg indexes all for table  allow write access
> > > >
> > > > For example:
> > > > db2 reorg indexes all for table BF_AGGREGATED_BITFILES allow write
> > access
> > > >
> > > > "
> > > >
> > > > as that part is missing in previous document version:
> > > > http://www-01.ibm.com/support/docview.wss?uid=swg21452146
> > > >
> > > > Seems to be pure db2 thing and would be nice to be able to use
> > such...when
> > > > we don't want to start it as automatic.
> > > > Question is if TSM doing something more when initiating that for 
its
> > own
> > > > or if such manual run on db2 is anyhow harmful to tsm?
> > > >
> > > >
> > > > Kind regards
> > > > Krzysztof
> > > >
> > >
> >
> 

Re: TSM Server 7.1.4 woes

[Andrew Raibeck]

And another question:

I think the message is on the client, ANS4035W (not ANR4035W)? When the
problem occurs, are there any messages displayed in the server activity log
that would seem to correspond with this issue?

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-27
08:36:23:

> From: Andrew Raibeck/Hartford/IBM@IBMUS
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-27 08:37
> Subject: Re: TSM Server 7.1.4 woes
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hello Michael,
>
> On what type of media does the backup data reside? Does this restore
issue
> occur when the data is on:
>
> * Disk (random access, device class DISK)
> * Disk (sequential, device class FILE)
> * Tape (a tape device class)
> * Next generation storage pool
>
> What type (operating system, e.g., Windows, AIX, Linux) of clients do you
> know to be affected?
>
> Best regards,
>
> Andy
>
>


>
> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
>
> IBM Tivoli Storage Manager links:
> Product support:
>
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

>
> Online documentation:
>
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

>
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager"  wrote on 2016-04-26
> 07:03:38:
>
> > From: Michael Prix 
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2016-04-26 07:04
> > Subject: TSM Server 7.1.4 woes
> > Sent by: "ADSM: Dist Stor Manager" 
> >
> > Hello all,
> >
> >   it is well known that older clients are out of support, but still
> continue
> > to work with the capabilities they were designed for.
> > Now I and some colleagues of mine upgraded customers to TSM 7.1.4 and
> 7.1.5,
> > with client-versions ranging from 5.5 to 7.1, and all of a sudden all
> clients
> > <=6.1 can still backup to the server, but aren't any longer able to
> > restore/retrieve files. ANR4035W is reported.
> > While this might not be a situation where one could get support from
IBM,
> it
> > is still a new situation as we as old *SMers are used to the fact that
> old
> > clients remain useable after an upgrade.
> >
> > --
> > Michael Prix
> >
>

Re: TSM Server 7.1.4 woes

[Andrew Raibeck]

Hello Michael,

On what type of media does the backup data reside? Does this restore issue
occur when the data is on:

* Disk (random access, device class DISK)
* Disk (sequential, device class FILE)
* Tape (a tape device class)
* Next generation storage pool

What type (operating system, e.g., Windows, AIX, Linux) of clients do you
know to be affected?

Best regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2016-04-26
07:03:38:

> From: Michael Prix 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2016-04-26 07:04
> Subject: TSM Server 7.1.4 woes
> Sent by: "ADSM: Dist Stor Manager" 
>
> Hello all,
>
>   it is well known that older clients are out of support, but still
continue
> to work with the capabilities they were designed for.
> Now I and some colleagues of mine upgraded customers to TSM 7.1.4 and
7.1.5,
> with client-versions ranging from 5.5 to 7.1, and all of a sudden all
clients
> <=6.1 can still backup to the server, but aren't any longer able to
> restore/retrieve files. ANR4035W is reported.
> While this might not be a situation where one could get support from IBM,
it
> is still a new situation as we as old *SMers are used to the fact that
old
> clients remain useable after an upgrade.
>
> --
> Michael Prix
>