Re: internal server error detected

[Billaudeau, Pierre]

Hi Eric,
Is the Max Mount point high enough on the node definition ? If 
concurrent QVIPNBDORA01_02-ORC sessions run at the same time.


Pierre Billaudeau
Administrateur de stockage
Livraison des infra serveurs



-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Loon, 
Eric van (ITOPT3) - KLM
Envoyé : 31 janvier 2017 09:48
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] internal server error detected

Hi Sasa (and all others who responded)!
The issue seems to be on the Storage Agent side, all other clients and the 
server itself operate normally. So no errors are seen in the DB2 log.
The STA was stopped and started, but to no avail. Everything was working fine 
on this client until this morning...
On the server all drives and paths are online. The paths defined for the STA 
are also online. We have 1300 scratch tapes available in the library... I'm 
lost.
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sasa 
Drnjevic
Sent: dinsdag 31 januari 2017 14:03
To: ADSM-L@VM.MARIST.EDU
Subject: Re: internal server error detected

This log is almost always helpful:

/home/instance_owner/sqllib/db2dump/db2diag.0.log

Or it could be rotated into db2diag.n.log in the same directory.

Regards,

--
Sasa Drnjevic
www.srce.unizg.hr




On 31.1.2017. 13:56, Loon, Eric van (ITOPT3) - KLM wrote:
> Hi guys!
> I have an Oracle client which backup failed with the following error in the 
> tdpoerror.log:
>
> 01/31/2017 09:08:35 ANS0278S The transaction will be aborted.
> 01/31/2017 09:08:35 ANS0278S The transaction will be aborted.
> 01/31/2017 09:08:35 TID<19506> ==> ANS0278S (RC157)  The transaction will be 
> aborted.
> 01/31/2017 09:08:35 ANS1312E Server media mount not possible
> 01/31/2017 09:08:35 ANS1312E Server media mount not possible
> 1/31/2017 09:08:35 TID<19506> ==> ANS1312E (RC12)   Server media mount not 
> possible
>
> The TSM server shows the following error:
>
> 01/31/2017 09:08:32 ANR0530W Transaction failed for session 9302740 for node 
> QVIPNBDORA01_02-ORC (TDPO Linux86-64) - internal server error detected. 
> (SESSION: 9302740)
> 01/31/2017 09:08:35 ANR0525W (Session: 7358241, Origin: QVIPNBDORA01)  
> Transaction failed for session 277695 for node QVIPNBDORA01_02-ORC (TDPO 
> Linux86-64) - storage media inaccessible. (SESSION: 7358241)
>
> The Oracle client is backing up through a storage agent and the 'internal 
> server error' seems to cause the scratch tape mount to fail which results in 
> the 'storage media inaccessible' message. Does anybody have an idea where to 
> look for the cause of the 'internal server error'?
> 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
> 
>

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: client restore got ANS4035W - files unavailable

[Billaudeau, Pierre]

Hi Rick,
This could be caused by a client-server version problem :
http://www-01.ibm.com/support/docview.wss?uid=swg1IT15117

Pierre Billaudeau
Administrateur de stockage
Livraison des infra serveurs




-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Rhodes, Richard L.
Envoyé : 13 janvier 2017 09:17
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] client restore got ANS4035W - files unavailable

Hi,

Last night a DBA tried to do a restore of some files.  He get returned

  01/12/17   22:01:07 ANS4035W File 'xxx' currently unavailable on server.

The client data is on tape.
The tape drives and library are handled by a separate dedicated library manager 
instance.

I see:
  on tsm server
 the client restore session
 the sessions to the library mgr instance (I think)
  on lib mgr
 the session which I believe would be for the mount (I think)  on tsm server
 ANS4025 errors for all files for the restore

Nowhere is there any indication of WHY the files are unavailable.
Nowhere is there any indication of what volume(s) were trying to be used.

I checked:
  there were tape drives free in the library
  all tape volumes are read/write or read-only
  no tape errors or hdwr errors


Q)  Any thoughts on why the files would be unavailable?
Q)  How can you tell specific volumes are needed for a client restore?

The only thing I can think of is that the volumes are unavailable, but I can't 
figure out what volumes it wanted to use.

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.

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: Reg: datamover sessions hung for tsm/ve backups

[Billaudeau, Pierre]

We had a similar situation and we resolved it by halting and restarting TSM 
server. TSM/VE were taking longer and longer to complete and some Datamovers 
were hanging.

Pierre Billaudeau
SAQ

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Tom 
Alverson
Envoyé : 5 juillet 2016 09:40
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Reg: datamover sessions hung for tsm/ve backups

Does anyone have a resolution for this yet?  I have a PMR open with a level
2 tech and so far all he has said was to update VMware tools to 10.0.9.   I
did that on the datamovers which did not help at all.  I am trying to get our 
VM team to update the VM's but that is a very slow process since they
would all need to be rebooted.   Last night half of our datamovers crashed
with this error.

On Wed, Apr 6, 2016 at 10:33 AM, Tom Alverson 
wrote:

> I am getting this error on three different TSM for VE VBS servers today.
> Waiting 60 minutes for each VM is causing the schedule to run into the
> next days schedule (the job runs for over 24 hours).  I have to stop
> and restart the service to snap it out of this mode and hope the next backup 
> runs OK.
>
> Tom
>
>
> On Sun, Mar 27, 2016 at 4:45 AM, Srikanth Kola23 
> wrote:
>
>> Hi Team,
>>
>> I am facing tsm/ve backups hung  over some couple of weeks which is
>> requiring manual intervention to reboot the datamover server then
>> only I am able to get the backup sessions running fine.
>>
>> share your experience and fixes if any you come across for this issue
>>
>> tsm/ve version 7140
>> platform windows 2012
>> tsm server version  7.1.4.100
>>
>> I do not find any errors in error log for the hungs when we had
>> traces enabled so disabled them then the error log saying as below
>> error.VE_POK11DM3.log 
>> 03/26/2016 22:29:37 ANS1717E A VMware vStorage web service task failed.
>> 03/26/2016 23:07:17 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>> 03/26/2016 23:07:17 ANS0361I DIAG: Waiting up to another 360
>> milliseconds to process a request to VddkFullVMCloseVMDKs for vm
>> 'pokcsmeta01'.
>> 03/26/2016 23:07:24 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>> 03/26/2016 23:07:24 ANS0361I DIAG: Waiting up to another 360
>> milliseconds to process a request to VddkFullVMOpenCloseSingleVMDK
>> for vm 'POKCBSAPAP62'.
>> 03/26/2016 23:27:58 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>> 03/26/2016 23:27:58 ANS0361I DIAG: Waiting up to another 360
>> milliseconds to process a request to VddkFullVMCloseVMDKs for vm
>> 'pokcsmetvm01'.
>> 03/26/2016 23:28:20 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>> 03/26/2016 23:28:20 ANS0361I DIAG: Waiting up to another 360
>> milliseconds to process a request to VddkFullVMOpenCloseSingleVMDK
>> for vm 'pokcdmetvm01'.
>> 03/26/2016 23:28:25 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>> 03/26/2016 23:28:25 ANS0361I DIAG: Waiting up to another 360
>> milliseconds to process a request to VddkFullVMOpenCloseSingleVMDK
>> for vm 'POKCDSAPAP31'.
>> 03/26/2016 23:29:37 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>> 03/26/2016 23:29:37 ANS0361I DIAG: Waiting up to another 360
>> milliseconds to process a request to VddkFullVMCloseVMDKs for vm
>> 'pokctcvs01'.
>> 03/27/2016 00:07:17 ANS0361I DIAG: The VDDK Utility Thread may be
>> hung processing another request.
>>
>> Thanks & Regards,
>>
>> *Srikanth kola*
>> Backup & Recovery
>> IBMIndiaPvt Ltd, Bangalore
>> Mobile: +91 9885473450
>>
>
>

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: DP Exchange Mailbox Restore

[Billaudeau, Pierre]

Yes , I realize those restores can only be done one at the time. The PMR I 
opened also confirms that.

Thanks Del

Pierre

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Del 
Hoobler
Envoyé : 14 mars 2016 17:53
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] DP Exchange Mailbox Restore

This is not possible concurrently using the same Exchange Server.
You would need to perform the concurrent restore on a different Exchange Server 
or do them sequentially.


Thank you,

Del

---

"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 03/14/2016
07:42:46 AM:

> From: "Billaudeau, Pierre" <p.billaud...@saq.qc.ca>
> To: ADSM-L@VM.MARIST.EDU
> Date: 03/14/2016 07:43 AM
> Subject: DP Exchange Mailbox Restore
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
>
> Hi,
> I know it is possible to restore multiple mailboxes
> at the same time (within the same GUI interface command) but is it
> possible to restore one specific mailbox at different dates
> simultaneously (or at least conccurently). I tested two restores of
> the same mailbox at 2 different dates and the second restore rapidly
> failed. Looks like one cannot run 2 simultaneous restores from the
> same Exchange DB (TSMRDB). Anyone has a solution to bypass this
limitation ?
>
> Thanks,
> Pierre Billaudeau
> Administrateur de stockage
> Livraison des infra serveurs
> Tél : 514-254-6000 poste 6559
>
>
> --

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

DP Exchange Mailbox Restore

[Billaudeau, Pierre]

Hi,
I know it is possible to restore multiple mailboxes at the same 
time (within the same GUI interface command) but is it possible to restore one 
specific mailbox at different dates simultaneously (or at least conccurently). 
I tested two restores of the same mailbox at 2 different dates and the second 
restore rapidly failed. Looks like one cannot run 2 simultaneous restores from 
the same Exchange DB (TSMRDB). Anyone has a solution to bypass this limitation ?

Thanks,
Pierre Billaudeau
Administrateur de stockage
Livraison des infra serveurs
Tél : 514-254-6000 poste 6559


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: Bring back TSM Administrator's Guide

[Billaudeau, Pierre]

I fully agree !!!

Pierre Billaudeau
Admin stockage
SAQ

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Roger 
Deschner
Envoyé : 11 décembre 2015 20:39
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Bring back TSM Administrator's Guide

A great book is gone. The TSM Administrator's Guide has been obsoleted as of 
v7.1.3. Its priceless collection of how-to information has been scattered to 
the winds, which basically means it is lost. A pity, because this book had been 
a model of complete, well-organized, documentation.

The "Solution Guides" are suitable only for planning a new TSM installation, 
and do not address existing TSM sites. Furthermore, they are much too narrow, 
and do not cover real-world existing TSM customers.
For instance, we use a blended disk and tape solution (D2D2D2T) to create a 
good working compromise between faster restore and storage cost.

Following links to topics in the online Information Center is a haphazard 
process at best, which is never repeatable. There is no Index or Table of 
Contents for the online doc - so you cannot even see what information is there. 
Unless you actually log in, there is no way to even leave a "trail of 
breadcrumbs". Browser bookmarks are useless here, due to IBM's habit of 
changing URLs frequently. This is an extremely inefficient use of my time in 
finding out how to do something in TSM.

Search is not an acceptable replacement for good organization. Search is 
necessary, but it cannot stand alone.

Building a "collection" is not an answer to this requirement. It still lacks a 
coherent Index or Table of Contents, so once my collection gets sizeable, it is 
also unuseable. And with each successive version, I will be required to rebuild 
my collection from scratch all over again.

Despite the fact that it had become fairly large, I humbly ask that the 
Administrator's Guide be published again, as a single PDF, in v7.1.4.

Roger Deschner  University of Illinois at Chicago rog...@uic.edu
==I have not lost my mind -- it is backed up on tape somewhere.=

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: TDP4VE: How to delete old backups of excluded volumes

[Billaudeau, Pierre]

Hi Andreas,
If your setup is like ours : One node which correspond to your Vcenter 
and 1 filespace per VM , you don't have the granularity to delete a specific 
drive within the filespace (1 per VM). You will have to wait expiration of 
older versions before you see some benefits in space usage.

Pierre

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Francisco Javier
Envoyé : 9 octobre 2015 10:37
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TDP4VE: How to delete old backups of excluded volumes

Use delete filespace ...

best regards =)


2015-10-09 7:10 GMT-05:00 Andreas Boesler :

> Hello,
>
> environment is windows with tsm 7.1.1.100
>
> We do backups of vmware systems (IFIncremental). Now we want to
> exclude some disks/volumes (D:, E:).
> We also want to delete the old backups of this volumes to get free
> space in the file device.
> How to delete old backups of excluded vmware volumes?
> Are there any tips or experience?
>
> Thanks for your help.
>
> Andreas
>

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

[Billaudeau, Pierre]

Hi Tom,
It looks like you are not connecting to the Vcenter. You can reset your 
Vcenter user password and try again.


Pierre Billaudeau
Administrateur de stockage
Livraison des infra serveurs
SAQ

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Tom 
Alverson
Envoyé : 28 juillet 2015 13:28
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

I had a backup issue with one particular VM (ANS9921E and ANS9919E) which I 
thought might be fixed (per a KB article) by upgrading the BACLIENT from
7.1.1.0 to 7.1.2.2.  Not only did this not fix the issue but now when I run the 
GUI and click the + to expand the list of VM's to back up I get this
error:

ANS1403E Error loading a required library: vixDiskLib.dll, Win32 rc=126 DLL
   and
ANS9266E Failure initializing virtual machine environment.  Can not find 
vcbMounter.exe command RC=-303

So next I upgraded TSM for VE from 7.1.1.0 to 7.1.2.0 but I still get the same 
error.  I searched the entire disk for vcbMounter.exe but could not find it.  I 
then searched the entire disk of a different VBS server that was still working 
and did not find that command either.  Does anyone know how to resolve this?  I 
asked someone on our backup team to open a ticket with IBM but I would like to 
fix what I have broken quickly if possible before a ton of backup failure 
tickets are created tonight when this backup does not work.

Tom

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

[Billaudeau, Pierre]

Hi ,
After upgrading to VSPhere 6.0, we had to upgrade TSm client from 7.1.1 
to 7.1.2 and also have those 3 patches installed on VSPhere 6.0:

2116126
2116127
2116129

They all are related to backup and CBT operations.

Pierre

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Gee, 
Norman
Envoyé : 28 juillet 2015 13:52
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

I have just upgraded one of my servers from 7.1.1 to 7.1.2.2 because of the 
support needed for VSphere 6.0 and I am experiencing some of the same problems. 
I have open a PMR with IBM on this.  I was attempting the backups manually with 
Dsmc -asnode=datacenter Backup vm a -vmbackuptype=fullvm It appears to backup 
but does not.  It gave messages that hinted it did backup, but no statistical 
messages.

I also try
Dsmc -nodename=datacenter
Backup vm a -vmbackuptype=fullvm
It does backup, but this is not the correct way.

I am waiting for IBM for an answer on this.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tom 
Alverson
Sent: Tuesday, July 28, 2015 10:41 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Upgrading BACLIENT to 7.1.2.2 broke TSM for VE ???

I saw that article and already had tried that.  I think I may have fixed it.  I 
found in swg21580462 a hint that you may need to do a custom install of the 
BACLIENT and enable the VMWare Backup Tools option to fix the issue.  In 
7.1.2.2 there is nothing called VMware Backup Tools but there was another 
VMware option that was not enabled and now that I have added that feature I am 
able to expand the list of VM's to backup in the GUI.  I will try a backup next 
and hopefully it will work (any maybe even fix my original problem)

Thanks for your input!

Tom

On Tue, Jul 28, 2015 at 1:34 PM, Billaudeau, Pierre p.billaud...@saq.qc.ca
wrote:

 Hi Tom,
 It looks like you are not connecting to the Vcenter. You can
 reset your Vcenter user password and try again.


 Pierre Billaudeau
 Administrateur de stockage
 Livraison des infra serveurs
 SAQ

 -Message d'origine-
 De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part
 de Tom Alverson Envoyé : 28 juillet 2015 13:28 À :
 ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Upgrading BACLIENT to 7.1.2.2
 broke TSM for VE ???

 I had a backup issue with one particular VM (ANS9921E and ANS9919E)
 which I thought might be fixed (per a KB article) by upgrading the
 BACLIENT from
 7.1.1.0 to 7.1.2.2.  Not only did this not fix the issue but now when
 I run the GUI and click the + to expand the list of VM's to back up I
 get this
 error:

 ANS1403E Error loading a required library: vixDiskLib.dll, Win32 rc=126 DLL
and
 ANS9266E Failure initializing virtual machine environment.  Can not
 find vcbMounter.exe command RC=-303

 So next I upgraded TSM for VE from 7.1.1.0 to 7.1.2.0 but I still get
 the same error.  I searched the entire disk for vcbMounter.exe but
 could not find it.  I then searched the entire disk of a different VBS
 server that was still working and did not find that command either.
 Does anyone know how to resolve this?  I asked someone on our backup
 team to open a ticket with IBM but I would like to fix what I have
 broken quickly if possible before a ton of backup failure tickets are
 created tonight when this backup does not work.

 Tom

 --


 Information confidentielle : Le présent message, ainsi que tout
 fichier qui y est joint, est envoyé à l'intention exclusive de son ou
 de ses destinataires; il est de nature confidentielle et peut
 constituer une information privilégiée. Nous avertissons toute
 personne autre que le destinataire prévu que tout examen,
 réacheminement, impression, copie, distribution ou autre utilisation
 de ce message et de tout fichier qui y est joint est strictement
 interdit, à moins d'avoir obtenu le consentement du destinataire. Si
 vous n'êtes pas le destinataire prévu, veuillez en aviser
 immédiatement l'expéditeur par retour de courriel et supprimer ce message et 
 tout document joint de votre système. Merci.


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: How to tell what VM's are running backup in TSM for VE 7.1?

[Billaudeau, Pierre]

Hi Steve,
As for what has completed, you can run this script (adapt date and 
time):
select SUB_ENTITY,DATE(START_TIME) as DATE,TIME(START_TIME) as 
START,TIME(END_TIME) as END,ENTITY as DataMover,AS_ENTITY as 
DataCenter,AFFECTED as NB_VMDK,BYTES/1048576 as MB,SUCCESSFUL from 
SUMMARY_EXTENDED where ACTIVITY='BACKUP' and ACTIVITY_DETAILS='VMware' and 
SUCCESSFUL='YES' AND START_TIME between '2015-04-23 06:00:35' and '2015-04-24 
06:00:34' order by start_time

Pierre Billaudeau
Administrateur stockage
Équipe livraison des infrastructures serveurs



-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Schaub, Steve
Envoyé : 23 avril 2015 16:22
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] How to tell what VM's are running backup in TSM for VE 7.1?

Running into some issues troubleshooting VE backups and hopefully I just don't 
know where to look.
I came in this morning and was surprised to find that one of my datamovers was 
still running a schedule.
There were 2 sessions in TSM, but of course they were using the datacenter name 
so I had no idea what was running, or what was still waiting to run.
So what do I use to gain visibility into a running VE schedule?
I want to know:

1.   What is running

2.   What has completed

3.   What is waiting to run
I tried deciphering it from dsmsched.log, but gave up looking for those needles 
in that haystack.
I also went to the VE web UI hoping reports/recent tasks would help, but 
nothing showed up there.
Surely there is some easy way to do this simple task that I have overlooked in 
the manual?

Steve Schaub
Systems Engineer II, Backup/Recovery
Blue Cross Blue Shield of Tennessee

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

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit, à moins 
d'avoir obtenu le consentement du destinataire. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et supprimer ce message et tout document joint de votre système. Merci.

Re: Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager EXTREMELY slow

[Billaudeau, Pierre]

Hi John,
I had a similar situation with Exchange 2010 TSM DP backups and the 
reason was the VM  had been Vmotioned from one ESX to another. Lan speed went 
from 1Gbs to 100Gbs. You might want to check this.

Pierre Billaudeau
Administrateur stockage

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Jeanne 
Bruno
Envoyé : 23 février 2015 15:43
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager 
EXTREMELY slow

Hello.  we skip integrity check as well.  Backups stored on a DS3512 device

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of John 
Keyes
Sent: Monday, February 23, 2015 2:47 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager 
EXTREMELY slow

Thank you Chavdar Cholev and Jeanne Bruno for sharing. I forgot to tell, we do 
skip the integrity check, and there are only passive Databases on the server.
Are your backups going to TSM server or to a local storage? Im interested 
either way.

Best Regards,
John



Gesendet: Montag, 23. Februar 2015 um 20:20 Uhr
Von: Chavdar Cholev chavdar.cho...@gmail.com
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: [ADSM-L] Exchange Backup with Flashcopy Manager EXTREMELY slow We 
have ~ 2TB full exchange backup and it takes ~ 20 hours. There is exch db 
consistency check before backup which takes considerable amount of time.
It can be switched off... but it is not recommnded

On Monday, 23 February 2015, John Keyes ra...@gmx.net wrote:

 Hello fellow TSM Admins!

 I'm struggling with Exchange Backup which over the course of the last
 few Days (mainly since the last full backup this weekend) takes about
 3-4 times as long as before.
 We have Exchange 2013 DAG with 48 Databases and a dedicaded VM to do
 the Backups (Flashcopy Manager 4.1.1, Backupdestination=local, on an
 IBM V7000 Storage).
 Right now even an incremental backup of 1 database takes ~12 minutes,
 but the volume is only 30GB big and has only 5GB (5000 x 1MB Files) on
 it. Two weeks ago this would only take 3 Minutes.
 A Full backup takes about half an hour (so I couldn't even complete a
 full backup for every database in one day). I also tried to
 full-backup the same database twice right after one another, with no 
 difference.

 This can hardly be normal, can it? Has anyone had the same problems
 and maybe could point me in the right direction?
 Also it would be great if anyone could share how much time their
 backups take...

 Best regards,
 John


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: TSM Tape utilization Issue...

[Billaudeau, Pierre]

Maybe it has something to do with your devclass definition (Device Class Name: 
DEVCLASS) . How did you define DEVCLASS ?

Pierre Billaudeau
SAQ, Montreal,qc,cdn

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Grigori Solonovitch
Envoyé : 21 janvier 2015 07:06
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TSM Tape utilization Issue...

Try to move data volume if number of volumes is not big.

Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, 
www.ahliunited.com.kw


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Kiran
Sent: 21 01 2015 1:59 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Tape utilization Issue...

WE have kept QUIET in dsm.opt and how to go about this issue.

Regards,
Kiran M



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann 
SIMON
Sent: Wednesday, January 21, 2015 4:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Tape utilization Issue...

Ok, so I suspect uncommited data due to retries during archive. Check your 
client log files (if not in QUIET).

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

- Mail original -
De: Kiran ki...@dqentertainment.com
À: ADSM-L@VM.MARIST.EDU
Envoyé: Mercredi 21 Janvier 2015 11:50:00
Objet: Re: [ADSM-L] TSM Tape utilization Issue...

Yes. Archive tape directly.



Regards,
Kiran M

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann 
SIMON
Sent: Wednesday, January 21, 2015 4:17 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Tape utilization Issue...

Hello,

Are you backing up (or archiving in this cas) to tape directly ?

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

- Mail original -
De: Kiran ki...@dqentertainment.com
À: ADSM-L@VM.MARIST.EDU
Envoyé: Mercredi 21 Janvier 2015 11:44:42
Objet: Re: [ADSM-L] TSM Tape utilization Issue...

No, Not so. Not only this tape we have some tapes of same sort.

I mentioned only a sample


Regards,
Kiran M


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Grigori Solonovitch
Sent: Wednesday, January 21, 2015 4:13 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Tape utilization Issue...

Maybe delete archive data?

Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, 
www.ahliunited.com.kw


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Kiran
Sent: 21 01 2015 1:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Tape utilization Issue...

We don't have expiration  for ARCHIVE data. We have set Retain Version=No limit 
.


Regards,
Kiran M

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Grigori Solonovitch
Sent: Wednesday, January 21, 2015 4:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Tape utilization Issue...

Most possible some data has been expired from last write 01/06/2015 22:27:18 
and reclamation process not started yet due to volume usage 72.9%.

Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, 
www.ahliunited.com.kw

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Kiran
Sent: 21 01 2015 1:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Tape utilization Issue...

Hi , My TSM is not utilizing tape 100%, its making tape FULL state before it is 
100% utilized. Check below is the newly assigned tape to TSM. But still its 
showing  Pct. Reclaimable Space: 27.1. Why??





This is LTO5 Media.



Volume Name: 000184L5

 Storage Pool Name: ARCHIVE

 Device Class Name: DEVCLASS

Estimated Capacity: 1.6 T

   Scaled Capacity Applied:

  Pct Util: 72.9

 Volume Status: Full

Access: Read/Write

Pct. Reclaimable Space: 27.1

   Scratch Volume?: No

   In Error State?: No

  Number of Writable Sides: 1

   Number of Times Mounted: 30

 Write Pass Number: 1

 Approx. Date Last Written: 01/06/2015 22:27:18

Approx. Date Last Read: 01/08/2015 21:26:55

   Date Became Pending:

Number of Write Errors: 0

 Number of Read Errors: 0

   Volume Location:

Volume is MVS Lanfree Capable : No

Last Update by (administrator): XXX

 Last Update Date/Time: 12/22/2014 16:16:15

  Begin Reclaim Period:

End Reclaim Period:

  Drive Encryption Key Manager: None

   Logical Block Protected: No



Regards,

Kiran M



Disclaimer: http://www.dqentertainment.com/e-mail_disclaimer.html


Please consider the environment before printing this Email.



CONFIDENTIALITY AND WAIVER: The information contained 

Re: breaking up tsm for ve backups into different nodes

[Billaudeau, Pierre]

Hi David,
Your primary storagepool has to be Collocate=filespace and I guess the 
target too if you want multiple threads.


Pierre Billaudeau
Administrateur stockage
Équipe livraison des infrastructures serveurs




-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de David 
Ehresman
Envoyé : 16 décembre 2014 15:31
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] breaking up tsm for ve backups into different nodes

Update stg STOAGEPOOL_NAME   MIGPRocess=XXX  where XXX is how many threads you 
want for your migration process.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, 
Gary
Sent: Tuesday, December 16, 2014 3:04 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] breaking up tsm for ve backups into different nodes

We are backing up our vmware environment (approximately 110 vms), using tsm for 
ve 6.4.2 tsmserver 6.2.5 under redhat 6.1.

The backup destination is disk.  Trouble is all data is owned by the datacenter 
node; consequently, migration has only one stream.

I do not currently have enough tape drives to run directly to tape.
Is there a solution I have missed?

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: TSM server appears to hang

[Billaudeau, Pierre]

Hi ,
AIX 6.1 TL6 and up and AIX 7.1 TL3 and up are known to bring those kind 
of problems :

http://www-01.ibm.com/support/docview.wss?uid=swg21587513

Pierre Billaudeau

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Matthew McGeary
Envoyé : 16 juillet 2014 20:19
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TSM server appears to hang

We're having the exact same problem, have been for quite a few months now.
 It occurred on 6.3.4.100 and 7.1.  Running on AIX 6.1 TL7 SP6 hosted on a 
P740.  It gets so bad on ours that I'll have to halt the dsmserv process, 
perform a db2stop force and then restart TSM.  Because it happens at random 
times and is totally infrequent, I've written a quick and dirty script to make 
sure that TSM is running and to do the shutdown/restart if the non-responsive 
behaviour kicks in again.

I don't have a solution for you but we've been all the way up the developer 
chain without much success.  What hardware are you running your server on?

Matthew McGeary
Technical Specialist
PotashCorp - Saskatoon
306.933.8921



From:   Rhodes, Richard L. rrho...@firstenergycorp.com
To: ADSM-L@VM.MARIST.EDU
Date:   07/16/2014 09:08 AM
Subject:[ADSM-L] TSM server appears to hang
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Hi Everyone,

The past couple of days we're had a strange problem with one of our TSM 
instances (v6.2.5).  At times it appears to hang.

Last night (and the previous night) it had many servers that got a dozen or 
more sessions.  This is really strange!  This morning as I was looking at this, 
cmds like q vol and q stgpool hang - no response!  Commands like q node 
and q proc work.  The server was doing very little I/O.
All of a sudden the hung cmds all ran through and the server I/O jumped to 
200-400MB/s.  Something was locking I/O.  I think the many sessions are clients 
that retry because the server is not responding.

In the TSM actlog there are no unusual messages about the time it un-stuck.  
The only strange entry in the actlog is a ANRD with
lockwait error early the previous evening.There are no AIX errors.

Any thought?

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.

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: TSM server appears to hang

[Billaudeau, Pierre]

Hi Rick,
From my experience, I had problem with an Expire inventory process (was 
hanging on a very large node in term of items  13 millions  )  that froze TSM 
but it was on 6.1 version. Also, REORG can use a lot of resources an impact TSM.

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Rhodes, Richard L.
Envoyé : 16 juillet 2014 11:08
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TSM server appears to hang

Hi Everyone,

The past couple of days we're had a strange problem with one of our TSM 
instances (v6.2.5).  At times it appears to hang.

Last night (and the previous night) it had many servers that got a dozen or 
more sessions.  This is really strange!  This morning as I was looking at this, 
cmds like q vol and q stgpool hang - no response!  Commands like q node 
and q proc work.  The server was doing very little I/O.  All of a sudden the 
hung cmds all ran through and the server I/O jumped to 200-400MB/s.  Something 
was locking I/O.  I think the many sessions are clients that retry because the 
server is not responding.

In the TSM actlog there are no unusual messages about the time it un-stuck.  
The only strange entry in the actlog is a ANRD with lockwait error early 
the previous evening.There are no AIX errors.

Any thought?

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.

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Drives stays IN USE after Library downtime

[Billaudeau, Pierre]

Hi Bjoern,
I had a similar problem recently on a physical library (tape showing 
dismounting on the library manager and IDLE on the library client). I had to 
stop/start the library client instance to solve the problem.


Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Nachtwey, Bjoern
Envoyé : 30 juin 2014 15:28
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Drives stays IN USE after Library downtime

Dear All,

after an error at one of our libraries (Quantum i6000, robotics became offline, 
we did a reboot instead of driving to the remote location to re-enable it) the 
library manager still shows one tape in a drive beeing IN USE.
but neither the library client who should own this tape / drive at the momten 
nor the library itself reports the same:
for the libclient the tape is not mounted for the library the drive is empty

I tried to do an library audit, this fails immediatly

then i restartet first the library manager instance later the whole physical 
server, the libmanager stiil reports the drive IN USE with the tape, even if 
there no session from the library client :-(

starting a library audit then, took much longer, I canceled this after about 
three hours dismount vol does not work either

Any idea what to do?

a little bit off-topic: an IBM 3584 can do an internal inventory run, does 
anyone know something similar for the i6k?

Thanks in advance  best regards,
Bjørn


Bjørn Nachtweymailto:bjoern.nacht...@gwdg.de
Arbeitsgruppe IT-Infrastruktur   Tel. +49 551 201-2181
- G W D G  Gesellschaft 
für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 
Göttingen
E-Mail: g...@gwdg.de   Tel.:   +49 (0)551 201-1510
URL:http://www.gwdg.de Fax:+49 (0)551 201-2150
Geschäftsführer:Prof. Dr. Ramin Yahyapour
Aufsichtsratsvorsitzender:  Dipl.-Kfm. Markus Hoppe
Sitz der Gesellschaft:  Göttingen
Registergericht:Göttingen  Handelsregister-Nr. B 598

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Enabling Encryption in TS3500/E06 Drives

[Billaudeau, Pierre]

Hi Zoltan,
Is the drive encryption enabled at the OS level. On E05 drives, I had 
to update our AIX server drive definition:
chdev  -l 'rmt6' -a wrt_encryption='on'
I did not have to change anything to our new E07 drive, I guess they 
were set OK.

Pierre Billaudeau
SAQ
Montreal

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Zoltan 
Forray
Envoyé : 3 septembre 2013 11:15
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Enabling Encryption in TS3500/E06 Drives

Well, contrary to the response I received about this being as simple as 
changing the devclass value, I can not get encryption to work.

I changed the devclass to  DRIVEENCRYPTION=ON and the first attempt to write a 
new tape fails with:

9/3/2013 9:59:03 AM ANR8985E The drive 7876475
(/dev/lin_tape/by-serial/07876475) in library TS3500-COPY is using an 
encryption method that is incompatible with the current server settings.

So, I figured I would check the hardware settings of the TS1130 -E06 drives.  
They were all set to NO ENCRYPTION.  I changed this to APPLICATION and figured 
that would take care of it. No such luck.  Same errors.

Tried resetting/cycling the drives - still nothing.

Tried taking all drives and paths offline, figuring this might reset/retrieve 
the new drive setting - still nothing - same errors.

Is there some library (TS3500) setting that may be blocking this?

So, what I am missing?




On Tue, Aug 20, 2013 at 12:34 PM, Zoltan Forray zfor...@vcu.edu wrote:

 Well, the saga is coming to a conclusion and I am going to active
 encryption of offsite tapes, via AME/TSM.

 Is there anything more I need to do besides update the DEVCLASS to
 DRIVEENCRYPTION=ALLOW on all of my TSM servers?

 When I check the drive details via the TS3500 interface, is says
 encryption is disabled?  Do I need to go to each drive and enable it?

 --
 *Zoltan Forray*
 TSM Software  Hardware Administrator
 Virginia Commonwealth University
 UCC/Office of Technology Services
 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
Virginia Commonwealth University
UCC/Office of Technology Services
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

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Implementing Encryption

[Billaudeau, Pierre]

Hi Zoltan,
We used TSM encryption (Application base on AIX TSM servers) and here 
are the steps we had to implement:

1. On  TSM server :
 Update DEVCLASS 3592CLASS2 drivee=on

2. On  AIX :
chdev  -l 'rmt6' -a wrt_encryption='on'
chdev  -l 'rmt13' -a wrt_encryption='on'
chdev  -l 'rmt14' -a wrt_encryption='on'

('on' replaces the value 'custom')

3. Change at the  hardware level  :
Enable Application at the drive level :

CE Drv Options
Drive encryption
Method config
Application

Pierre Billaudeau

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Zoltan 
Forray
Envoyé : 4 avril 2013 09:41
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Implementing Encryption

I know this sounds strange, but we need to implement encryption on our
TS1130 tapes.

Never having done this, I need some help/suggestions/war-stories/etc on how to 
basically turn encryption on.  Is there a quick-and-dirty book on the subject?

I understand the first thing would be to change the devclass for the tape 
drives to encryption=yes for ALL of my servers (currently, 2 of 7 are library 
managers).

Then I saw something about EKM to manage the keys.  Is this also implemented on 
all TSM servers?

--
*Zoltan Forray*
TSM Software  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
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

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Latest Linux/X86 32 bit client

[Billaudeau, Pierre]

Hi,
From what I see on TSM FTP download site, Linux/X86 32 bit 
client are not available from version 6.3 and 6.4 . Is it correct that the 
latest  TSM Linux client for 32bit OS is 6.2.2 ?
Thanks
Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Latest Linux/X86 32 bit client

[Billaudeau, Pierre]

I just downloaded 6.2.4.4 .

Thanks a lot

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Zoltan 
Forray
Envoyé : 18 février 2013 13:48
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Latest Linux/X86 32 bit client

Correction - for latest patches, 6.2.4.4 Linux client is latest

2013/2/18 Zoltan Forray zfor...@vcu.edu

 Actually, 6.2.4 is the latest.


 2013/2/18 Remco Post r.p...@plcs.nl

 On 18 feb. 2013, at 19:42, Billaudeau, Pierre
 p.billaud...@saq.qc.ca
 wrote:

  Hi,
 From what I see on TSM FTP download site, Linux/X86
  32
 bit client are not available from version 6.3 and 6.4 . Is it correct
 that the latest  TSM Linux client for 32bit OS is 6.2.2 ?

 yes.

  Thanks
  Pierre Billaudeau
  Analyste en stockage
  Livraison des Infrastructures Serveurs Société des Alcools du
  Québec
  514-254-6000 x 6559
 
 
  --
 
 
  Information confidentielle : Le présent message, ainsi que tout
  fichier
 qui y est joint, est envoyé à l'intention exclusive de son ou de ses
 destinataires; il est de nature confidentielle et peut constituer une
 information privilégiée. Nous avertissons toute personne autre que le
 destinataire prévu que tout examen, réacheminement, impression,
 copie, distribution ou autre utilisation de ce message et de tout
 fichier qui y est joint est strictement interdit. Si vous n'êtes pas
 le destinataire prévu, veuillez en aviser immédiatement l'expéditeur
 par retour de courriel et supprimer ce message et tout document joint de 
 votre système. Merci.

 --

 Met vriendelijke groeten/Kind regards,

 Remco Post
 r.p...@plcs.nl
 +31 6 24821622




 --
 *Zoltan Forray*
 TSM Software  Hardware Administrator
 Virginia Commonwealth University
 UCC/Office of Technology Services
 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
Virginia Commonwealth University
UCC/Office of Technology Services
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

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: TDP SQL 6.4

[Billaudeau, Pierre]

Hi Robert,
When you have 2 different backups or 2 different SQL databases on a 
server, you can create 2 icons pointing to your optionfiles (in this case they 
are on different drives). You need both the optionfiles and the configfile:
Eg:
C:\Program Files\Tivoli\TSM\TDPSql\tdpsql.exe 
/configfile=g:\tsm\tdpsql\tdpsql.cfg /tsmoptfile=g:\tsm\tdpsql\dsm.opt

C:\Program Files\Tivoli\TSM\TDPSql\tdpsql.exe 
/configfile=e:\tsm\tdpsql\tdpsql.cfg /tsmoptfile=e:\tsm\tdpsql\dsm.opt


Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Robert 
Ouzen
Envoyé : 7 février 2013 04:59
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TDP SQL 6.4

Hello

I implanted the new TDP for SQL version 6.4 in our environment without any 
problems , working fine ...

I need now to create another dsm.opt for DRM named DRM.opt , from the 
tdpsqlc.exe (command line) I succeed to run commands.

But how to load the GUI (dashboard) when I loaded it I got only the node form 
the dsm.opt , I need to load  the node from the DRM.opt to make restore  etc 
etc  ?

T.I.A  Regards

Robert

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Reclamation of Virtual Tapes

[Billaudeau, Pierre]

I noticed a serious performance drop when our backup primary tapes to copypool 
runs at night (VTL Quantum DXi8500 to TS1140 tapes). The throughput of backups 
to VTL drops when the DXi rehydrates the deduplicated/compressed virtual 
tapes. I can imagine the reclamation process does the same thing. There is a 
need to adjust maintanance schedules to avoid the situation.

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Schneider, Jim
Envoyé : 27 décembre 2012 11:18
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Reclamation of Virtual Tapes

Our primary (and only) storage is a Data Domain.  Be careful when reclaiming 
virtual tapes.  It works perfectly but servers backing up to the Data Domain 
have their bandwidth throughput drop from 85% to 5% during reclamation.  This 
was determined by watching Windows Task Manager network utilization with 
reclamation running and then cancelled.

Our reclamation threshold is set at 95% and runs for about 20 minutes.  The SQL 
storage pool that holds 1.1 TB files is set at 99% to effectively prevent 
reclamation.  We had a bad weekend where reclamation started Friday at 5 PM and 
was 60% complete Monday morning before being cancelled.  All of those weekend 
backups were slowed and the database backup ran 5 hours instead of 1.75 hours.

Don't make my mistakes!

Jim Schneider

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Ehresman,David E.
Sent: Tuesday, December 18, 2012 2:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Reclamation of Virtual Tapes

We reclaim our virtual tapes.  They have the same waste patterns as physical 
tape and are certainly as expensive.

David

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, 
Gary
Sent: Tuesday, December 18, 2012 2:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Reclamation of Virtual Tapes

Sounds like someone set the reclaim storage pool on the virtual tape pool to 
the physical tape pool.

I know of no reason why not to reclaim virtual tapes.

Wish I had one to play with.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Welton, Charles
Sent: Tuesday, December 18, 2012 11:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Reclamation of Virtual Tapes

Hello:

We have a TSM instance that uses virtual tapes as our primary backup data pool. 
 The data on the virtual tapes are eventually migrated to tape.  We are 
currently down to 3 virtual scratch tapes and 6 physical scratch tapes.  I 
noticed that we are not running any reclamation processes on our virtual tape 
pool.  It seems we have a hand-full of under-utilized virtual tapes.  I went 
ahead and ran a manual reclamation on the virtual tape pool and I noticed the 
output tape pool is a physical tape.  I assumed that the virtual tape would 
reclaim to another virtual tape.  Is that not the case?

Could there be a reason why reclamation shouldn't be ran on a virtual tape pool?

Thank you...


Charles

This email contains information which may be PROPRIETARY IN NATURE OR OTHERWISE 
PROTECTED BY LAW FROM DISCLOSURE and is intended only for the use of the 
addresses(s) named above.  If you have received this email in error, please 
contact the sender immediately.

**
Information contained in this e-mail message and in any attachments thereto is 
confidential. If you are not the intended recipient, please destroy this 
message, delete any copies held on your systems, notify the sender immediately, 
and refrain from using or disclosing all or any part of its content to any 
other person.

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: TDP for Domino on Linux keeps telling me API not installed

[Billaudeau, Pierre]

Michael,
I ran into a similar problem with TDP for Exchange 5.2.1.1 (to 
reproduce a problem in Lab). I had to uninstall, the TSM baclient 6.3 and 
install TSM 5.4.1.4 in order to get the TSM API installed. I guess you will 
need to go back to a version 5 baclient.

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Michael Roesch
Envoyé : 31 juillet 2012 05:09
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TDP for Domino on Linux keeps telling me API not installed

Hi all,

I'm trying to install TDP for Domino 5.5.3 on Linux openSuSE 12.1 x64. I 
already installed the BA client version 6.3.0.15 and also installed the TSM API.
The problem is, when I run the TDP installer, it tells me The Tivoli Storage 
Manager Client API v5.5.1 or higher is not installed.

Any ideas where the problem could be?

Thanks in advance

Regards,
Michael Roesch

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Deployment Engine Failed to initialize

[Billaudeau, Pierre]

Now, I guess that means with 6.1.3.3 installed since 2010, I can't see the 
light even going to 6.2 or 6.3 with tablespace in db2 9.5 format. A fellow DBA 
suggested that if the 6.1.3.3 database was really migrated to 6.2 db2 9.7 , 
tablespace could  be converted to 9.7 format. Do I really want to go into that 
??? No, I am seriously thinking about starting a brand new TSM server with 6.3 
and let 6.1 die...   Thanks for all this info.


Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559



-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Zoltan 
Forray/AC/VCU
Envoyé : 28 février 2012 09:39
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Deployment Engine Failed to initialize

WOW - such harsh words about 6.1 !   I don't agree..my main production
6.x system is 6.1.5.10 with no issues.  At least it hasn't had this wacky, 
problem my other 6.2.x servers have had with a DB backup randomly, 
intermittently failing with no discernible reason(note, there are docs that 
say you really need to be at least at 6.1.4.1 to resolve some big problems, 
especially with reorgs)


Zoltan Forray
TSM Software  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
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



From:   Prather, Wanda wprat...@icfi.com
To: ADSM-L@VM.MARIST.EDU
Date:   02/28/2012 05:57 AM
Subject:Re: [ADSM-L] Deployment Engine Failed to initialize
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



What Remco said.
Nothing Good will Happen on 6.1.
I finally got a production system stable on 6.1.3 by disabling reorgs, but that 
was Windows.
I wouldn't even think of doing it on Linux.

W

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco 
Post
Sent: Monday, February 27, 2012 5:10 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deployment Engine Failed to initialize

Hi,

do not use TSM server 6.1, not even if you have no other options. 6.1 does not 
even begin to approach alpha quality software. IBM should never have shipped 
it. I can't think of a single good reason to install 6.1. Go with
6.2.3 or newer or 6.3 something.



On 27 feb. 2012, at 22:57, George Huebschman wrote:

 We are getting the Deployment Engine Failed to Initialize when
 running ./install.bin for TSM Server 6.1 on a clean new RHEL server.
 I see lots of noise out here about this error, in and out of the TSM
world.

 (We have another TSM installation of TSM 6.3 on a VM  that isn't even
 QA as such, just a practice install.) Documetation specifies that
 there be 2GB available in the home directory.
 We only have 1.6 GB, BUT so does the successful 6.3 install.
 We had the error on the first and subsequent 3 attempts to run the
 install.  We did not find any .lock or .lck files.
 I am told that SELINUX is set to permissive.

 Except for the home directory, the other space guidelines were met.
 The install is being done as root.

 Looking at the TSM related posts about this issue, I didn't notice any
 for releases after 6.1.
 Is that because I didn't look hard enough?  Or, was documentation
 improved, or was a bug fixed?
 Should I talk someone into 6.2 to get past this?

 Most of my experience has been with 5.* I have read the install guide
 (most of it) for 6.2, which is what I thought we were installing.  Do
 I need to step back in documentation?


 --
 George Huebschman

 When you have a choice, spend money where you would prefer to work if
 you had NO choice.

--
Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Disk storage pool 100% utilized but NOT cached

[Billaudeau, Pierre]

Hi Zoltan,
Is it possible you had a very large (or several) backup running using 
the remaining 66% (over 4 tb) of your backup pool ? Current backups freezes 
backup data space on the disk pool so it is not eligible for migration.

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Zoltan 
Forray/AC/VCU
Envoyé : 13 septembre 2011 10:23
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Disk storage pool 100% utilized but NOT cached

I think I know the answer to this question but figured it would be a good
question to ask,

This morning I was getting reports that backups were failing due to
backups not being able to get space in the disk stgpool.


When I did a Q STG, this is what I get:

9:25:34 AM   MOON : q stg
Storage  Device   EstimatedPctPct  High  Low  Next Stora-
Pool NameClass NameCapacity   Util   Migr   Mig  Mig  ge Pool
Pct  Pct
---  --  --  -  -    ---  ---
ARCHIVEPOOL  DISK 205 G0.30.390   70  TS1130
BACKUPPOOL   DISK   6,369 G  100.0   33.990   70  TS1130

Why would a disk storage pool be 100% Utilized and only 34% migratable
when I don't have Caching turned on?


Zoltan Forray
TSM Software  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
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

--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Probleme with TS3200 and Redhat

[Billaudeau, Pierre]

Hi Grégory,
Did you run a checkin command to have your scratch tapes recognized by 
your TSM instance:

Checkin LIBVolume newlib??? SEARCH=Yes volrange=nn,nn Status=SCRATCH 
Checklabel=no devtype=devtype

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de molin 
gregory
Envoyé : 11 juillet 2011 12:41
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Probleme with TS3200 and Redhat

Hello,

I installed a new server, a new robot on a backup site.
TSM 6.1.4.3 - Redhat 5.4 - TS3200
The bands are visible in the robot and the console.
When I do a query drive I get the serial numbers and WWN.
When I did a query library I get no serial number but not the WWN.
No band is detected by an audit library checkl = bar / yes
If anyone has an idea, I'm interested


Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système.

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. 


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Expiration causes backups to hang

[Billaudeau, Pierre]

Hi Hans,
We are still having problem with the expiration on some filesystem node 
but instead of hanging, the DB is growing at an incredible pace then TSM 
crashes. This is with 6.1.3 and cancel expiration command would not respond. We 
identified some Windows 2008 servers (Systemstate filesystem) that was so big 
(14M entries) and excluded them from Expiration process. Expiration runs very 
fine since then and we were hoping 6.2.2 would solve the problem but from what 
you experience it does not look good.

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Hans 
Christian Riksheim
Envoyé : 13 avril 2011 04:18
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Expiration causes backups to hang

Hi,

anyone else have this problem? Running 6.2.2 on AIX 6.1. Submitting a PMR on
this in parallell.

When I say hang I mean a complete hang. All incoming backups stops. Traffic
is resumed when we cancel expiration.

Hans Chr.


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: TDP for Exchange (2010)

[Billaudeau, Pierre]

Hi Del,
I just tried this and I get this message:
C:\Program Files\Tivoli\TSM\TDPExchangeTDPEXCC QUERY EXCHANGE 
/EXCSERVER=CTELPME115.SAQ.QC.CA

IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 6, Release 1, Level 3.0
(C) Copyright IBM Corporation 1998, 2010. All rights reserved.

ACN0101E Invalid argument: QUERY EXCHANGE /EXCSERVER=CTELPME115.SAQ.QC.CA

You are right when you say there must be something particular in my 
environment. My PMR has been escalated to level 2.

Merci beaucoup,
Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Del 
Hoobler
Envoyé : 1 février 2011 09:23
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TDP for Exchange (2010)

Bonjour Pierre,

We have not seen this. One thing to try:

   TDPEXCC QUERY EXCHANGE /EXCSERVER=servername.domain

Other than that, there is no way to feed the domain name
into TSM. TSM will use the domain that the machine is in.
There must be something unique to your configuration.
Opening the PMR with IBM was a good way to proceed.


Merci,

Del



ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 01/31/2011
01:49:49 PM:

 From: Billaudeau, Pierre p.billaud...@saq.qc.ca
 To: ADSM-L@vm.marist.edu
 Date: 01/31/2011 01:51 PM
 Subject: TDP for Exchange (2010)
 Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu

 Hi,
 I get this message after installing TDP for Exchange
 Client on a Windows 2008 R2 64bit server. I can do a TDPEXCC QUERY
 TSM and QUERY TDP with no problem but when I do QUERY EXCHANGE I get
this :

 C:\Program Files\Tivoli\TSM\TDPExchangetdpexcc query exchange

 IBM Tivoli Storage Manager for Mail:
 Data Protection for Microsoft Exchange Server
 Version 6, Release 1, Level 2.0
 (C) Copyright IBM Corporation 1998, 2010. All rights reserved.

 Querying Exchange Server to gather component information, please
wait...

 Connecting to remote server failed with the following error message
 : The WSMan
 client cannot process the request. Proxy is not supported under
 HTTP transport.
  Change the transport to HTTPS and specify valid proxy information
 and try again
 . For more information, see the about_Remote_Troubleshooting Help
topic.

 This points to WINRM and when I do :

 C : WINRM id -r :servername  I get the same error :
 WSManFault
 Message = The WSMan client cannot process the request. Proxy is
 not supporte
 d under HTTP transport.  Change the transport to HTTPS and specify
 valid proxy i
 nformation and try again.

 Error number:  -2147024891 0x80070005
 Access is denied.

 When I add the domain (it works):
 C : WINRM id -r :servername.domain name
 IdentifyResponse
 ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
 ProductVendor = Microsoft Corporation
 ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0

 Using the domain name help for this WinRM command but I
 wonder how to pass this parameter to TSM. This problem appeared
 following implementing Exchange 2010 Sp1 update rollup 2 (from
 rollup 1). If anyone of you encountered and resolved this problem,
 I would really appreciate your help. I have a PMR opened at IBM too.

 Thanks,


 Pierre Billaudeau
 Analyste en stockage
 Livraison des Infrastructures Serveurs
 Société des Alcools du Québec
 514-254-6000 x 6559


 --


 Information confidentielle : Le présent message, ainsi que tout
 fichier qui y est joint, est envoyé à l'intention exclusive de son
 ou de ses destinataires; il est de nature confidentielle et peut
 constituer une information privilégiée. Nous avertissons toute
 personne autre que le destinataire prévu que tout examen,
 réacheminement, impression, copie, distribution ou autre
 utilisation de ce message et de tout fichier qui y est joint est
 strictement interdit. Si vous n'êtes pas le destinataire prévu,
 veuillez en aviser immédiatement l'expéditeur par retour de
 courriel et supprimer ce message et tout document joint de votre
 système. Merci.


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

TDP for Exchange (2010)

[Billaudeau, Pierre]

Hi,
I get this message after installing TDP for Exchange Client on a 
Windows 2008 R2 64bit server. I can do a TDPEXCC QUERY TSM and QUERY TDP with 
no problem but when I do QUERY EXCHANGE I get this :

C:\Program Files\Tivoli\TSM\TDPExchangetdpexcc query exchange

IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 6, Release 1, Level 2.0
(C) Copyright IBM Corporation 1998, 2010. All rights reserved.

Querying Exchange Server to gather component information, please wait...

Connecting to remote server failed with the following error message : The WSMan
client cannot process the request. Proxy is not supported under HTTP transport.
 Change the transport to HTTPS and specify valid proxy information and try again
. For more information, see the about_Remote_Troubleshooting Help topic.

This points to WINRM and when I do :

C : WINRM id -r :servername  I get the same error :
WSManFault
Message = The WSMan client cannot process the request. Proxy is not supporte
d under HTTP transport.  Change the transport to HTTPS and specify valid proxy i
nformation and try again.

Error number:  -2147024891 0x80070005
Access is denied.

When I add the domain (it works):
C : WINRM id -r :servername.domain name
IdentifyResponse
ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0

Using the domain name help for this WinRM command but I wonder how 
to pass this parameter to TSM. This problem appeared following implementing 
Exchange 2010 Sp1 update rollup 2 (from rollup 1). If anyone of you encountered 
and resolved this problem, I would really appreciate your help. I have a PMR 
opened at IBM too.

Thanks,


Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.

Re: Anybody seen this? 6.1.3.3 ADM14001C An unexpected and critical error has occurred: DBMarkedBad.

[Billaudeau, Pierre]

Hi Wanda,
TSM 6.1.2.0 crashed twice in our environment (AIX 6.1) but each time  
it was due to a process (expiration once and delete filespace the other time) 
that was working on a very large node (in term of number of files  6 
millions). TSM DB ran out of space and TSM crashed on a DB2 space exhausted 
error message. Restart went just fine and a lot of space was released. Your 
message is very different but I thought this could bring somtehing to the 
discussion. 

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de 
Prather, Wanda
Envoyé : 15 décembre 2010 18:56
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Anybody seen this? 6.1.3.3 ADM14001C An unexpected and 
critical error has occurred: DBMarkedBad.

Win2k3 TSM server 6.1.3.

Found my TSM server comatose.  Had stopped writing to actlog 12 hours ago.  Q 
session showed many sessions just sitting in RUN state, no processes, no tape 
mounts.  DB2 seems to have died out from underneath.

Nothing in the activity log, nothing in db2diag.log.  But found the messages 
messages below in the Windows event log.

Found one hit on DBMarkedBad :
http://www-01.ibm.com/support/docview.wss?rs=0q1=1426627uid=swg21426627loc=en_UScs=utf-8cc=uslang=en

But that refers to an SQL error initializing the TSM DB after this failure, and 
my TSM restarted just fine.
Also can run a DB backup without errors.
So I don't know if anything is actually bad, or not, or I have corruption in 
the DB.


Event log errors:
+++
ADM7518C  TSMDB1   marked bad.
 
12/14/2010  11:28:15 PM SERVER1 Error None  4 N/A   VDCTSM1 
2010-12-14-23.28.15.921000   Instance:SERVER1   Node:000
PID:2604(db2syscs.exe)   TID:6856   Appid:*LOCAL.SERVER1.101215034202
base sys utilities  sqeLocalDatabase::MarkDBBad Probe:10   Database:TSMDB1

ADM14001C  An unexpected and critical error has occurred: DBMarkedBad. The
instance may have been shutdown as a result. Automatic FODC (First 
Occurrence
Data Capture) has been invoked and diagnostic information has been recorded in
directory
C:\DOCUME~1\ALLUSE~1\APPLIC~1\IBM\DB2\DB2TSM1\SERVER1\FODC_DBMarkedBad_2010-12
-14-23.28.15.890001\. Please look in this directory for detailed evidence
about what happened and contact IBM support if necessary to diagnose the
problem.
 
12/14/2010  11:28:15 PM SERVER1 Error None  4 N/A   VDCTSM1 
2010-12-14-23.28.15.421000   Instance:SERVER1   Node:000
PID:2604(db2syscs.exe)   TID:6856   Appid:*LOCAL.SERVER1.101215034202
relation data serv  sqlrr_dump_ffdc Probe:200   Database:TSMDB1

ADM0001C  A severe error has occurred.  Examine the administration notification
log and contact IBM Support if necessary.

Wanda Prather  |  Senior Technical Specialist  | 
wprat...@icfi.commailto:wprat...@icfi.com  |  www.jasi.comwww.jasi.com%20
ICF Jacob  Sundstrom  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 
410.539.1135



___
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à 
l'intention exclusive de son ou de ses destinataires; il est de nature 
confidentielle et peut constituer une information privilégiée. Nous avertissons 
toute personne autre que le destinataire prévu que tout examen, réacheminement, 
impression, copie, distribution ou autre utilisation de ce message et de tout 
fichier qui y  est joint est strictement interdit. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et  supprimer ce message et tout document joint de votre système. 
Merci.

Expiration and Delete Filespace causing TSM DB to grow and crash

[Billaudeau, Pierre]

Hi TSMers,

Our TSM 6.1.3.3. has a Windows 2008 (R2 64bits) client node that 
contains over 14 millions files (95% being SystemState backup files) and when 
either the expiration process or a delete filespace command is run against it, 
TSM DB is growing at the rate of 1 gb/hour until DB2 DB gets a space exhausted 
message and TSM crashes. Of course we removed that node from the daily 
expiration process but we'd like to clean those entries from the DB before 
doing a DB2 REORG of some Index tables that became huge over the last year. By 
the way, under TSM 5.5, our TSM DB was 85gb (1 year ago) and it now reach over 
400gb (more than 50% being Index table fragmentation we were told by IBM). Any 
thoughts on how to get rid of those entries (Export node was not a success too 
but cause no DB increase) ? 

 

Pierre Billaudeau

Analyste en stockage

Livraison des Infrastructures Serveurs

Société des Alcools du Québec

514-254-6000 x 6559

 



___
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à 
l'intention exclusive de son ou de ses destinataires; il est de nature 
confidentielle et peut constituer une information privilégiée. Nous avertissons 
toute personne autre que le destinataire prévu que tout examen, réacheminement, 
impression, copie, distribution ou autre utilisation de ce message et de tout 
fichier qui y  est joint est strictement interdit. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et  supprimer ce message et tout document joint de votre système. 
Merci.

Re: Expiration and Delete Filespace causing TSM DB to grow and crash

[Billaudeau, Pierre]

Wanda   - Client is 6.1.3.0 and I am upgrading it right now to 6.2.1 .
Richard - Most of the backup data is collocated to 1-2 tapes. I will try the 
delete vol discard=yes .

Thanks for the help,

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de 
Prather, Wanda
Envoyé : 23 novembre 2010 15:40
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Expiration and Delete Filespace causing TSM DB to grow and 
crash

Also, have you upgraded your Win2K8 to 6.2.1?
That client version does true incremental backups of Win2K8, that is backing 
up only the system state files that have actually changed.  That should help 
with the problem over time.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of 
Richard Sims
Sent: Tuesday, November 23, 2010 2:46 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Expiration and Delete Filespace causing TSM DB to grow 
and crash

It is often the case that such backups are segregated on their own volumes, 
where that allows you to perform a Delete Volume to dispose of the stuff in a 
meta manner.

   Richard Sims



___
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à 
l'intention exclusive de son ou de ses destinataires; il est de nature 
confidentielle et peut constituer une information privilégiée. Nous avertissons 
toute personne autre que le destinataire prévu que tout examen, réacheminement, 
impression, copie, distribution ou autre utilisation de ce message et de tout 
fichier qui y  est joint est strictement interdit. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et  supprimer ce message et tout document joint de votre système. 
Merci.

DocAve TSM for Microsoft SharePoint

[Billaudeau, Pierre]

Hi,

Has anyone of you have TDP for SharePoint widely installed in your 
TSM environment ? I could only get feedback from 2008 experiences and it was 
not so positive. As our Microsoft Sharepoint is growing, we need a solution for 
TSM backup other then the TDP for SQL backup. So my question is do you consider 
TSM TDP DocAve for Microsoft SharePoint a good solution for SP backup ? 

 

Thanks,

Pierre Billaudeau

Analyste en stockage

Livraison des Infrastructures Serveurs

Société des Alcools du Québec

514-254-6000 x 6559

 



___
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à 
l'intention exclusive de son ou de ses destinataires; il est de nature 
confidentielle et peut constituer une information privilégiée. Nous avertissons 
toute personne autre que le destinataire prévu que tout examen, réacheminement, 
impression, copie, distribution ou autre utilisation de ce message et de tout 
fichier qui y  est joint est strictement interdit. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et  supprimer ce message et tout document joint de votre système. 
Merci.

Re: TSM 6 database space performance question

[Billaudeau, Pierre]

Hi John,
We are running TSM 6.1.3.3 on AIX 6.1 and we already increased TSM DB2 
Database space twice using the same Filesystem (directory). TSM documentation 
only mention the use of a new filesystem to increase the size of the DB using 
EXTEND DBSPACE new_filesystem . I don't think extending TSM DB across 2-3-4 
filesystem would spread the I/O more then using only one filesystem based on 
the fact that it is the number of disk your DB is spread across that will make 
the difference. Your LUNs need to be spread across different raid groups in 
order to provide the best performance. I really think one directory can be as 
efficient as 2 or 3.   

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de John 
D. Schneider
Envoyé : 11 mai 2010 16:21
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TSM 6 database space performance question

Greetings,
   I have a customer running TSM 6.1.3 on a Linux RedHat 5.4 server.
They are using high-performance SAN attached disk for the TSM database
and logs.  They have created the TSM database all in one directory under
one filesystem.  Recently then needed to add more space, and they carved
out a lun from another RAID group, and then added that lun to the
existing filesystem.  TSM shows that it now has the additional space,
but it is still all under one directory.
   In reading the Performance Guide and Admin Guide, they both recommend
spreading the data out over multiple directories, putting each directory
behind separate disks/luns.  This certainly makes sense to spread the
I/O out over multiple luns, and I get that.  But is there anything wrong
with the way my customer has done it?  They are using multiple luns from
different RAID groups, but they are all put together behind one
directory.  Is this going to become a problem as they add more and more
load to this instance?  If TSM has lots of separate directories and they
are across multiple luns, does TSM do it's database I/O differently?

Best Regards,

John D. Schneider
The Computer Coaching Community, LLC
Cell: (314) 750-8721



___
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à 
l'intention exclusive de son ou de ses destinataires; il est de nature 
confidentielle et peut constituer une information privilégiée. Nous avertissons 
toute personne autre que le destinataire prévu que tout examen, réacheminement, 
impression, copie, distribution ou autre utilisation de ce message et de tout 
fichier qui y  est joint est strictement interdit. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et  supprimer ce message et tout document joint de votre système. 
Merci.

TSM 6.1.2.1 to 6.1.3.3 (AIX 6.1)

[Billaudeau, Pierre]

Hi,

In order to resolve problems we have with the current version of 
TSM (6.1.2.1) :

-  Expiration fails on one large node (14Million entries for one 
filespace).

-  Database increase 1gb per day.

-  Retrieve file on WEB or GUI takes over 30 minutes to list files 
(once again for large node).

-  Incremental backup very slow for directories having over 5 million 
entries (Workaround was to run JBB).

 

IBM recommends to go from 6.1.2.1 to 6.1.3.0 and the to 6.1.3.3. Has anyone 
done a similar upgrade on a AIX server and any recommendation you can make is 
welcome. We plan to do this change this coming Monday.

 

Thanks

 

Pierre Billaudeau

Analyste en stockage

Livraison des Infrastructures Serveurs

Société des Alcools du Québec

514-254-6000 x 6559

 



___
Information confidentielle:
Le présent message, ainsi que tout fichier qui y est joint, est envoyé à 
l'intention exclusive de son ou de ses destinataires; il est de nature 
confidentielle et peut constituer une information privilégiée. Nous avertissons 
toute personne autre que le destinataire prévu que tout examen, réacheminement, 
impression, copie, distribution ou autre utilisation de ce message et de tout 
fichier qui y  est joint est strictement interdit. Si vous n'êtes pas le 
destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de 
courriel et  supprimer ce message et tout document joint de votre système. 
Merci.