Re: multiple directories an archive

[Juan Manuel Lopez Azañon]

Try this way :
dsmc archive -subdir=yes "f:\sys\user\administ\*" "f:\sys\user\adpessoa\*"
It should works fine.



Por favor, responda a "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Enviado por:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Destinatarios:[EMAIL PROTECTED]
CC:
Asunto:multiple directories an archive


Hi,

I would like to execute an archive in multiple directories and I setup the
object as f:\sys\user\administ\*' 'f:\sys\user\adpessoa\*but as
you can see I received a RC=12. Please what is wrong ?

Thanks a lot !!!



18-09-2003 16:27:13

18-09-2003 16:27:13 Schedule Name: S_TEST_01
18-09-2003 16:27:13 Action:Archive
18-09-2003 16:27:13 Objects:   f:\sys\usuario\administ\*'
'f:\sys\usuario\adpessoa\*
18-09-2003 16:27:13 Options:   -subdir=yes
18-09-2003 16:27:13 Server Window Start:   16:26:00 on 18-09-2003
18-09-2003 16:27:13

18-09-2003 16:27:13 Command will be executed in 1 minute.
18-09-2003 16:27:13
Time remaining until execution:
Executing scheduled command now.
18-09-2003 16:28:13 Node Name: IPBR21
18-09-2003 16:28:13 Session established with server TSMSERVER1: Windows
18-09-2003 16:28:13   Server Version 5, Release 1, Level 5.0
18-09-2003 16:28:13   Server date/time: 18-09-2003 16:28:11  Last access:
18-09-2003 16:27:11

18-09-2003 16:28:13 --- SCHEDULEREC OBJECT BEGIN S_TEST_01 18-09-2003
16:26:00
18-09-2003 16:28:13 Archive function invoked.

18-09-2003 16:28:15 ANS1898I * Processed   500 files *
18-09-2003 16:28:16 ANS1898I * Processed 1,000 files *
18-09-2003 16:28:18 ANS1898I * Processed 1,500 files *
18-09-2003 16:28:20 ANS1898I * Processed 2,000 files *
18-09-2003 16:28:22 ANS1898I * Processed 2,500 files *
18-09-2003 16:28:25 ANS1898I * Processed 3,000 files *
18-09-2003 16:28:27 ANS1898I * Processed 3,500 files *
18-09-2003 16:28:29 ANS1898I * Processed 4,000 files *
18-09-2003 16:28:32 ANS1898I * Processed 4,500 files *
18-09-2003 16:28:34 ANS1898I * Processed 5,000 files *
18-09-2003 16:28:36 ANS1898I * Processed 5,500 files *
18-09-2003 16:28:37   0 \\ipbr21\f$\sys [Sent]
18-09-2003 16:28:37   0 \\ipbr21\f$\sys\usuario [Sent]
18-09-2003 16:28:37   0 \\ipbr21\f$\sys\usuario\administ
[Sent]
18-09-2003 16:28:37 ANS1092E No files matching search criteria were found
18-09-2003 16:28:37 ANS1803E Archive processing of
'\\ipbr21\f$\sys\usuario\administ\*'' finished with failures.

18-09-2003 16:28:38 --- SCHEDULEREC STATUS BEGIN
18-09-2003 16:28:38 Total number of objects inspected:5,977
18-09-2003 16:28:38 Total number of objects archived: 0
18-09-2003 16:28:38 Total number of objects updated:  0
18-09-2003 16:28:38 Total number of objects rebound:  0
18-09-2003 16:28:38 Total number of objects deleted:  0
18-09-2003 16:28:38 Total number of objects expired:  0
18-09-2003 16:28:38 Total number of objects failed:   0
18-09-2003 16:28:38 Total number of bytes transferred: 0  B
18-09-2003 16:28:38 Data transfer time:0.00 sec
18-09-2003 16:28:38 Network data transfer rate:0.00 KB/sec
18-09-2003 16:28:38 Aggregate data transfer rate:  0.00 KB/sec
18-09-2003 16:28:38 Objects compressed by:0%
18-09-2003 16:28:38 Elapsed processing time:   00:00:25
18-09-2003 16:28:38 --- SCHEDULEREC STATUS END
18-09-2003 16:28:38 --- SCHEDULEREC OBJECT END S_IPBR21_01 18-09-2003
16:26:00
18-09-2003 16:28:38 ANS1512E Scheduled event 'S_TEST_01' failed.  Return
code = 12.
18-09-2003 16:28:38 Sending results for scheduled event 'S_IPBR21_01'.
18-09-2003 16:28:38 Results sent to server for scheduled event
'S_IPBR21_01'.

Re: multiple directories an archive

[Juan Manuel Lopez Azañon]

If that does not work, you need to create a executable file ( cmd ) on
client machine and on it put the line I told you in the other message.


Por favor, responda a "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Enviado por:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Destinatarios:[EMAIL PROTECTED]
CC:
Asunto:multiple directories an archive


Hi,

I would like to execute an archive in multiple directories and I setup the
object as f:\sys\user\administ\*' 'f:\sys\user\adpessoa\*but as
you can see I received a RC=12. Please what is wrong ?

Thanks a lot !!!



18-09-2003 16:27:13

18-09-2003 16:27:13 Schedule Name: S_TEST_01
18-09-2003 16:27:13 Action:Archive
18-09-2003 16:27:13 Objects:   f:\sys\usuario\administ\*'
'f:\sys\usuario\adpessoa\*
18-09-2003 16:27:13 Options:   -subdir=yes
18-09-2003 16:27:13 Server Window Start:   16:26:00 on 18-09-2003
18-09-2003 16:27:13

18-09-2003 16:27:13 Command will be executed in 1 minute.
18-09-2003 16:27:13
Time remaining until execution:
Executing scheduled command now.
18-09-2003 16:28:13 Node Name: IPBR21
18-09-2003 16:28:13 Session established with server TSMSERVER1: Windows
18-09-2003 16:28:13   Server Version 5, Release 1, Level 5.0
18-09-2003 16:28:13   Server date/time: 18-09-2003 16:28:11  Last access:
18-09-2003 16:27:11

18-09-2003 16:28:13 --- SCHEDULEREC OBJECT BEGIN S_TEST_01 18-09-2003
16:26:00
18-09-2003 16:28:13 Archive function invoked.

18-09-2003 16:28:15 ANS1898I * Processed   500 files *
18-09-2003 16:28:16 ANS1898I * Processed 1,000 files *
18-09-2003 16:28:18 ANS1898I * Processed 1,500 files *
18-09-2003 16:28:20 ANS1898I * Processed 2,000 files *
18-09-2003 16:28:22 ANS1898I * Processed 2,500 files *
18-09-2003 16:28:25 ANS1898I * Processed 3,000 files *
18-09-2003 16:28:27 ANS1898I * Processed 3,500 files *
18-09-2003 16:28:29 ANS1898I * Processed 4,000 files *
18-09-2003 16:28:32 ANS1898I * Processed 4,500 files *
18-09-2003 16:28:34 ANS1898I * Processed 5,000 files *
18-09-2003 16:28:36 ANS1898I * Processed 5,500 files *
18-09-2003 16:28:37   0 \\ipbr21\f$\sys [Sent]
18-09-2003 16:28:37   0 \\ipbr21\f$\sys\usuario [Sent]
18-09-2003 16:28:37   0 \\ipbr21\f$\sys\usuario\administ
[Sent]
18-09-2003 16:28:37 ANS1092E No files matching search criteria were found
18-09-2003 16:28:37 ANS1803E Archive processing of
'\\ipbr21\f$\sys\usuario\administ\*'' finished with failures.

18-09-2003 16:28:38 --- SCHEDULEREC STATUS BEGIN
18-09-2003 16:28:38 Total number of objects inspected:5,977
18-09-2003 16:28:38 Total number of objects archived: 0
18-09-2003 16:28:38 Total number of objects updated:  0
18-09-2003 16:28:38 Total number of objects rebound:  0
18-09-2003 16:28:38 Total number of objects deleted:  0
18-09-2003 16:28:38 Total number of objects expired:  0
18-09-2003 16:28:38 Total number of objects failed:   0
18-09-2003 16:28:38 Total number of bytes transferred: 0  B
18-09-2003 16:28:38 Data transfer time:0.00 sec
18-09-2003 16:28:38 Network data transfer rate:0.00 KB/sec
18-09-2003 16:28:38 Aggregate data transfer rate:  0.00 KB/sec
18-09-2003 16:28:38 Objects compressed by:0%
18-09-2003 16:28:38 Elapsed processing time:   00:00:25
18-09-2003 16:28:38 --- SCHEDULEREC STATUS END
18-09-2003 16:28:38 --- SCHEDULEREC OBJECT END S_IPBR21_01 18-09-2003
16:26:00
18-09-2003 16:28:38 ANS1512E Scheduled event 'S_TEST_01' failed.  Return
code = 12.
18-09-2003 16:28:38 Sending results for scheduled event 'S_IPBR21_01'.
18-09-2003 16:28:38 Results sent to server for scheduled event
'S_IPBR21_01'.

TDP Error

[Nazeer Parak]

Hi
 i wonder if anyone could possibly tell me what is causing this specific error and /or 
what i can do to rectify it: 
 
 
i am running tdp for nt oracle 
with base tsm 4.2.0 and tdp 3.2.01
 
when running either an online or offline database backup i get the following error:
 
BKI0027I: Internal error:   ***  E:\cvmann\dev\xint\control\ctrl_task.cpp:749: 
XINT_CTRL_Task::handle_native(XINT_LOG_Message*): caught RW exception: [INDEXERR] 
Illegal Index (0) for collection or string with 0 elements
 
 the backup then continues but does not process all objects and obviously terminates 
with errors. 
any assistance would be greatly appreciated.
 
has anybody else received a similar error?
 
regards  
 
Nazeer Parak 
Systems Engineer
Arivia.kom 
 
* Phone:   800-5273 
* Cell:   084-447-7771
 E-Mail:    [EMAIL PROTECTED]


NOTICE: Please note that this eMail, and the contents thereof, is subject to the 
standard arivia.kom email disclaimer which may be found at:  
http://www.arivia.co.za/disclaimer.htm.  If you cannot access the disclaimer through 
the URL attached, and you wish to receive a copy thereof, please send an eMail to 
[EMAIL PROTECTED] or call (011) 233-0800. You will receive the disclaimer by return 
email or fax.

Antwort: Re: Antwort: How to move your TSM server recovery logs?

[Markus Veit]

Hi,
Version 5.1.7.1, 12 GB is still valid, does that change with 5.2? If it does,
maybe I should read the manual :-))

Mit freundlichen Grüßen / Best Regards

Markus Veit




   
   
   
An: [EMAIL PROTECTED]
Kopie: 
Thema:   Re: Antwort: How to move your 
TSM server recovery logs?
   
  [EMAIL PROTECTED]   
  Received :  18.09.2003   
  18:17
  Bitte antworten an "ADSM:
  Dist Stor Manager"   
   
   




It´s depends of your TSM Server versionWhat is your ?


Por favor, responda a "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Enviado por:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Destinatarios:[EMAIL PROTECTED]
CC:
Asunto:Antwort: How to move your TSM server recovery logs?


Hi,
how big is your recovery log? It should't be bigger than 12 GB because
than you
wouldn't be able to increase the size of it.

Now lets say it is 6GB, just define a new logvolume on the new drive,
def logvol  F=6000  (in MB)
now issue
extend log 6000
now you just need to delete your old log volume
del logvol 'old_volume'

define extra log volumes on the new drive and extend it.
You could also do it in smaller chunks, but the rule is:
max reduction of the whole logsize can not be smaller than the logvolume
to be
deleted

Mit freundlichen Grüßen / Best Regards

Markus Veit







An: [EMAIL PROTECTED]
Kopie:
Thema:   How to move your TSM server recovery logs?

[EMAIL PROTECTED]
Received :  18.09.2003
17:34
Bitte antworten an "ADSM:
Dist Stor Manager"






Environ:

W2K server 5.1.6.3

I need to move my recovery logs to another drive to increase their size.

I have looked in the W2K Admin Guide for a procedure, but failed to find
one.

Does anyone have a procedure to move your recovery logs?

Here is what I was thinking of doing:


1) Halt TSM server.

2) Use the DSMSERV FORMAT utility to define new recovery logs on the new
drive.

3) Restart the TSM server.

Is it this simple or am I missing something?

TIA.

Ken Sedlacek
AIX/TSM/UNIX Administrator
[EMAIL PROTECTED]

IBM Certified Specialist: RS/6000 AIX v4.3 Support
IBM Certified Specialist: RS/6000 SP & PSSP 3
Tivoli Certified Consultant - Tivoli Storage Manager v4.1

Does TSM support Network Load Balanced (NLB) clients

[Mastrangelo, Ralph]

We need to back up some Microsoft Network Load Balanced (NLB) clients
(as opposed to Microsoft Cluster Service clustered clients) running
Microsoft SQL. Does either TSM V4.2 or V5.x support this? 

If needed, here's a link (http://tinyurl.com/nusf) to an article,
"Windows clustering: Microsoft Cluster Service or network load
balancing," which discusses the difference between NLB and Clustering.

Thanks for your help

Ralph

upgrade dubs

[Juan Manuel Lopez Azañon]

Hi all.
I will upgrade my tsm server to 4.2 next week so I have one 3.7 client and
I do not know if it will go on working with the new tsm version.
Could anybody help me ?
Thanks.
Juanma.

Re: DB2 high speed SP switch backups dead slow

[Muthyam Reddy]

** High Priority **

Hi Travis,
bunch of thanks for ur kind responce .Yesterday changed couple of parameter in sys 
file at client and I could finish my backup 3 hrs which is 14 before.i could'nt belive 
that.
still I need tune few things in tcp/ip and high speed switch.


thanks again.

best regards
/muthyam



>>> Travis Zong <[EMAIL PROTECTED]> 09/15/03 11:22AM >>>



Muthyam,

We got the same problem since our TSM migrated to 5.1.5. After one month's
work, I made the following changes on TSM DB2 Client, and fixed the problem. I
think TCPWINDOWSIZE is the critical factor. Both server and clients were 2048
in our environment. Good luck!!

Travis

FROM:
LARGECOMMBUFFERSYES
TCPWINDOWSIZE   2048
TCPBUFFSIZE 64

TO:
LARGECOMMBUFFERSNO
TCPWINDOWSIZE   128
TCPBUFFSIZE 32
TCPNODELAY  YES



This electronic mail transmission contains information from Joy Mining Machinery
which is confidential, and is intended only for the use of the proper addressee.
If you are not the intended recipient, please notify us immediately at the return
address on this transmission, or by telephone at (724) 779-4500, and delete
this message and any attachments from your system.  Unauthorized use, copying,
disclosing, distributing, or taking any action in reliance on the contents of
this transmission is strictly prohibited and may be unlawful.

<>

Managed Systems for SAN files needed

[Shawn Price]

Hello all,
 I was preparing to setup Lan-free on my new 5.1 server and found that my CD
is physically bad and I cannot access the files that I need (belive me, I've
tried it in every machine in sight.) Does anyone have any idea where I can
find the filesets that I need? I'm just looking for the stuff in the
/usr/sys/inst.images directory. I've called my distributor and asked for a
media refresh, but it won't be here until Monday.

Thanks in advance for your help... Btw the Full name and numbers on the CD
are "IBM Tivoli Storage Manager for Storage Area Networks Managed Systems
for SAN" v.5.1.5  LCD7-0426-01 C23PWIE



Shawn

Re: upgrade dubs

[Vazquez Vegas, Sergio]

Sure.

I'm sure your 3.7 client will go on working normally with your 4.2
TSM Server.

Hope this can help!

Sergio Vázquez Vegas
Administración TSM
*: 104688 - 912134688
*: [EMAIL PROTECTED]


-Mensaje original-
De: Juan Manuel Lopez Azañon [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 19 de septiembre de 2003 14:49
Para: [EMAIL PROTECTED]
Asunto: upgrade dubs


Hi all.
I will upgrade my tsm server to 4.2 next week so I have one 3.7 client and
I do not know if it will go on working with the new tsm version.
Could anybody help me ?
Thanks.
Juanma.

Este mensaje de correo electrónico y sus documentos adjuntos están dirigidos
EXCLUSIVAMENTE a los destinatarios especificados. La información contenida
puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente
refleja la opinión de ENDESA. Si usted recibe este mensaje por ERROR, por
favor comuníqueselo inmediatamente al remitente y  ELIMÍNELO ya que usted
NO ESTA AUTORIZADO al uso, revelación, distribución, impresión o copia de
toda o alguna parte de la información contenida. Gracias. 

This e-mail message and any attached files are intended SOLELY for the
addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY
PRIVILEGED  information and may not necessarily represent the opinion of
ENDESA. If you receive this message in ERROR, please immediately notify the
sender and DELETE it since you ARE NOT AUTHORIZED  to use, disclose,
distribute, print or copy all or part of the contained information. Thank
you.  

Re: Managed Systems for SAN files needed

[Bill Smoldt]

ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance/server/v5r
1/
ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance/storage-ag
ent/v5r1/

Bill Smoldt
STORServer, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Shawn Price
Sent: Friday, September 19, 2003 8:02 AM
To: [EMAIL PROTECTED]
Subject: Managed Systems for SAN files needed


Hello all,
 I was preparing to setup Lan-free on my new 5.1 server and found that my CD
is physically bad and I cannot access the files that I need (belive me, I've
tried it in every machine in sight.) Does anyone have any idea where I can
find the filesets that I need? I'm just looking for the stuff in the
/usr/sys/inst.images directory. I've called my distributor and asked for a
media refresh, but it won't be here until Monday.

Thanks in advance for your help... Btw the Full name and numbers on the CD
are "IBM Tivoli Storage Manager for Storage Area Networks Managed Systems
for SAN" v.5.1.5  LCD7-0426-01 C23PWIE



Shawn

Tape Verification

[Joe Pendergast]

I need to write the procedures for tape verification and wish some
guidance:
(Background info:  AIX 4.3.3 running TSM 4.2.1 on LTO libraries).

1. How do you verify your permanent offsite tapes are still valid (Audit
Volume or other)?
2. How often do you verify those tapes?
3. How long will most LTO tapes take to do an Audit Volume?
4. What other tools are available verify a TSM tape is valid?
5. What is the best tool to use to verify that a "backupset" is still
valid?

Thanks for your responses.

Re: TDP for Domino Executables won't run

[Debi Randolph]

No.  We are using Trend Micro for Virus Protection.
And No to Terminal Services.   I access the console via Dameware or DSVIEW,
I have the problem with either method.   But Terminal Services may be on
this server for others to use.

I'll see if I can find any hits in the Knowledge Database.

Thanks,
Deb Randolph





  Seema Gururaj
  <[EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  COM> cc:
  Sent by: "ADSM:  Subject:  Re: TDP for Domino 
Executables won't run
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  09/18/2003 06:28
  PM
  Please respond to
  "ADSM: Dist Stor
  Manager"






Hi Debi,
Do you have the GroupShield anti virus software running on your machine?
Or are you trying to run TDP for Domino via Terminal services. There are
some known problems with running Domino server and Groupshield.
You can also search IBM Knowledge Database to see if the problem you are
seeing is documented. To
access this go to:
http://www.ibm.com/support/search
Enter the keyword TDP for Domino and you should see some relevant
articles.
Regards,
-Seema

===
Seema Gururaj
TDP/TSM Development
Tivoli Software/IBM






Debi Randolph <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/18/2003 01:53 PM
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:TDP for Domino Executables won't run



Hi List,

new day, new issue

The executable for the GUI and the executable for the Command Line of TDP
for Domino will not start on two of my clients.
It acts like it's starting, and then it just goes away.   It never paints
the screen or anything on the GUI.   On the command line one, it takes me
out to a dos prompt in the right directory, but it's not logged into
Tivoli, it's just a normal dos command line from the server.

So what do you do?

I tried rebooting the servers, no luck.
I tried to reinstall the TDP with the Repair option.No luck.
I copied the executables from a working server over to a non-working
server, no luck.
There are no errors reported in the Tivoli logs.
There are no errors reported in the NT Event logs.


We're running two TSM servers, one TDP client problem on each server.

We have :

Server 1 is:  Windows 2000, SP3, TSM V5.1.7.0

Server 2 is:   Windows 2003, TSM V5.2.1.0

Both clients are Windows 2000, SP3, TDP V5.1.5


I have other TDP Clients working on both servers.


I guess I could try to un-install and reinstall, but it requires a few
reboots and too much down time for our customers.
I don't want to go thru all that if there is an easier way, and maybe that
won't work any way.

Any suggestions?


Deb Randolph














***N O T I C E***
The information contained in this e-mail, and in any accompanying
documents, may constitute confidential and/or legally privileged
information.  The information is intended only for use by the
designated recipient.  If you are not the intended recipient (or
responsible for the delivery of the message to the intended
recipient), you are hereby notified that any dissemination,
distribution, copying, or other use of, or taking of any action in
reliance on this e-mail is strictly prohibited.  If you have received
this e-mail communication in error, please notify the sender
immediately and delete the message from your system.
***



***N O T I C E***
The information contained in this e-mail, and in any accompanying
documents, may constitute confidential and/or legally privileged
information.  The information is intended only for use by the
designated recipient.  If you are not the intended recipient (or
responsible for the delivery of the message to the intended
recipient), you are hereby notified that any dissemination,
distribution, copying, or other use of, or taking of any action in
reliance on this e-mail is strictly prohibited.  If you have received
this e-mail communication in error, please notify the sender
immediately and delete the message from your system.
***





***N O T I C E***
The information contained in this e-mail, and in any accompanying
documents, may constitute confidential and/or legally privileged
information.  The information is intended only for use by the
designated recipient.  If you are not the intended recipient (or
responsible for the delivery of the message to the intended
recipient), you are hereby notified that any dissemination,
distribution, copying, or other use of, or taking of any action in
reliance on this e-

Re: Saving data on a defective cartridge

[Prather, Wanda]

That's insane.
Sounds like the best bet for cost savings would be to focus on elimiating
some upper management!!!

-Original Message-
From: Wholey, Joseph (IDS DM&DS) [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 1:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


A "little" off the subject, and I already heard Richard Simms view on not
having a second copy...  but what are most shops doing with respect to a
second copy.
I'm in a pretty large shop and upper management, in a cost savings effort,
wants us to turn off the creation of a second tape copy.  I'm not too
comfortable with the idea.  What are "your" thoughts?

-Original Message-
From: Coats, Jack [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 12:38 PM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


Try doing a move data to get the data off of the tape.  If I find I am
starting to have problems I usually do a:

update vol VOLUMENAME acc=reado
move data VOLUMENAME

This should move all data that is recoverable from the volume to another
volume in the same storage pool.  I then eject the offending volume and
check it for apparent physical issues.  Then the part I hate:

delete vol VOLUMENAME discarddata=yes

Sometimes I am able to re-label the volume and use it again.  But
typically it gets moved to a less critical use, returned to the vendor
for a new tape [my preferred method], or degaused and distroyed by
a certified vendor [least preferred, paying to have it thrown away].

If anyone has a better method, please let me know! ... JC

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 11:24 AM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


Hello,
I forgot to mention that because of lack of resources I can't afford a
copypool for the backup files. I have one for the archives.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Juan Manuel Lopez Azanon
> Sent: Thursday, September 18, 2003 6:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Saving data on a defective cartridge
>
>
> Disaster recovery management: Restore it from outside volumes from copy
> stgpool
>

Re: Tape Verification

[Tom Kauffman]

I've only got a few tapes that fall into the 'permanent' offsite category --
commonstore archives of SAP extracts being kept seven years for legal
reasons. Everything else is backups (continuous reclaim) or 21-day archives
(some reclaim before the time is up, others sit off-site for 21 days and
come back empty).

For the commonstore archives, I do the occasional audit volume fix=no for
the *on-site* copy and then do reclaim or move data for the off-site volume.
If I have a problem with the local version, I'll bring in the off-site copy
and rebuild the local tape (but I haven't hit that yet). My intent is to
never bring back an off-site tape with data on it unless I need it to
rebuild a local tape.

Can't help you on backupsets -- I have yet to figure out a meaningful use
for them here.

But, in line with your question -- what can I do to verify that my TSM
database backup tape is readable/useable BEFORE it comes out of the library
to go off-site? This is, to my thinking, the single biggest hole in the
entire TSM functionality; I want to be able to validate that backup OR write
multiple concurrent identical backups WITHIN TSM.

Tom Kauffman
NIBCO, Inc

-Original Message-
From: Joe Pendergast [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 10:29 AM
To: [EMAIL PROTECTED]
Subject: Tape Verification


I need to write the procedures for tape verification and wish some
guidance:
(Background info:  AIX 4.3.3 running TSM 4.2.1 on LTO libraries).

1. How do you verify your permanent offsite tapes are still valid (Audit
Volume or other)?
2. How often do you verify those tapes?
3. How long will most LTO tapes take to do an Audit Volume?
4. What other tools are available verify a TSM tape is valid?
5. What is the best tool to use to verify that a "backupset" is still
valid?

Thanks for your responses.
CONFIDENTIALITY NOTICE:  This e-mail and any attachments are for the exclusive and 
confidential use of the intended recipient.  If you are not the intended recipient, 
please do not read, distribute or take action in reliance upon this message. If you 
have received this in error, please notify us immediately by return e-mail and 
promptly delete this message and its attachments from your computer system. We do not 
waive attorney-client or work product privilege by the transmission of this message.

AIX first timer.

[Brian L. Nick]

Hi everyone.

 Well now we are planning to move our TSM server from OS/390 to AIX here is
our AIX config.

 TSM 5.2

 AIX 5.2

 ACSLS 6.1.1

My question relates to tape drives. I was able to get the Library, Drives
and paths defined to that I think are correct parameters using ACSLS I have
exported data from my OS/390 TSM server and I am attempting to import the
data into the AIX server that is when i received the following error
message:

ANR0796E IMPORT NODE: Error encountered in accessing data
storage - insufficient number of mount points
available
for removable media.

 The thing is I think that I have the mountpoints that I need for this here
are the detailed list of the LIbrary, Drives, Device class. I am unable to
reach serarch.adsm.org so I thouhgt that I'd ask the questions to the gang.
Any help is appreciated.

 Q library:

  Library Name: ACSLIB
  Library Type: ACSLS
ACS Id: 0
  Private Category:
  Scratch Category:
  External Manager:
Shared: No
   LanFree:
ObeyMountRetention:
   Primary Library Manager:
   WWN:
 Serial Number:
 AutoLabel:
Last Update by (administrator): TECBLN
 Last Update Date/Time: 09/19/03 13:05:43


 Q DRIVE:


Library Name: ACSLIB
  Drive Name: DRIVE01
 Device Type: GENERICTAPE
 On-Line: Yes
Read Formats:
   Write Formats:
 ACS DriveId: 0,0,10,0
 Drive State: UNKNOWN
Allocated to:
 WWN:
   Serial Number:
  Last Update by (administrator): TECBLN
   Last Update Date/Time: 09/19/03 12:16:17
Cleaning Frequency (Gigabytes/ASNEEDED/NONE):

Library Name: ACSLIB
  Drive Name: DRIVE02
 Device Type: GENERICTAPE
 On-Line: Yes
Read Formats:
   Write Formats:
 ACS DriveId: 0,0,10,1
 Drive State: UNKNOWN
Allocated to:
 WWN:
   Serial Number:
  Last Update by (administrator): TECBLN
   Last Update Date/Time: 09/18/03 13:53:14
Cleaning Frequency (Gigabytes/ASNEEDED/NONE):

Library Name: ACSLIB
  Drive Name: DRIVE03
 Device Type: GENERICTAPE
 On-Line: Yes
Read Formats:
   Write Formats:
 ACS DriveId: 0,0,10,2
 Drive State: UNKNOWN
Allocated to:
 WWN:
   Serial Number:
  Last Update by (administrator): TECBLN
   Last Update Date/Time: 09/18/03 13:53:25
Cleaning Frequency (Gigabytes/ASNEEDED/NONE):


Q DEVC:

  Device Class Name: 9840
 Device Access Strategy: Sequential
Storage Pool Count: 1
   Device Type: ECARTRIDGE
Format: 9840
 Est/Max Capacity (MB):
   Mount Limit: DRIVES
  Mount Wait (min): 60
 Mount Retention (min): 60
  Label Prefix: TSMDMZ
   Library: ACSLIB
 Directory:
   Server Name:
  Retry Period:
Retry Interval:
Shared:
Last Update by (administrator): TECBLN
 Last Update Date/Time: 09/19/03 09:09:35






Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900

E-MAIL:  [EMAIL PROTECTED]
PHONE:   (860)403-2281



*** 
CONFIDENTIAL: This communication, including attachments, is intended only for the 
exclusive use of addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, you are hereby notified that you 
have received this document in error, and any use, review, copying, disclosure, 
dissemination or distribution is strictly prohibited. If you are not the intended 
recipie

TSM and DR

[Gerald Wichmann]

Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a database
recovery. If that DB was created back in January and it's now March, isn't
there a potential for objects getting expired the first time you start the
TSM server? E.g. when the TSM server is started it typically performs an
expire inventory as part of that sequence. I would imagine that now that
it's 2 months later, would it therefore start expiring objects that you
probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server (or
perhaps even before recovering the DB) to ensure expire inventory doesn't
ruin your recovery? I recall there being an option in dsmserv.opt that
allows you to turn off automatic expire inventory. That seems like a good
idea.. but what if there was an admin schedule that runs expire inventory
back then and you happen to start the recovery while in the schedule's
window?

I think you can see what I'm getting at with all this. I want to make sure
all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.

Re: TSM and DR

[Steve Schaub]

If someone has not taken a TSM DB backup for 3 months, they weren't
really serious about DR in the first place.

Steve Schaub
Systems Engineer
Haworth, Inc
616-393-1457 (desk)
616-412-0544 (numeric page)
[EMAIL PROTECTED] (text page)
WWJWMTD


-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a
database recovery. If that DB was created back in January and it's now
March, isn't there a potential for objects getting expired the first
time you start the TSM server? E.g. when the TSM server is started it
typically performs an expire inventory as part of that sequence. I would
imagine that now that it's 2 months later, would it therefore start
expiring objects that you probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server
(or perhaps even before recovering the DB) to ensure expire inventory
doesn't ruin your recovery? I recall there being an option in
dsmserv.opt that allows you to turn off automatic expire inventory. That
seems like a good idea.. but what if there was an admin schedule that
runs expire inventory back then and you happen to start the recovery
while in the schedule's window?

I think you can see what I'm getting at with all this. I want to make
sure all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital
Safe(tm) service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is privileged, confidential or exempt from disclosure
under applicable law.  If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited.  If you have received this communication in error, please
notify the sender immediately by telephone or directly reply to the
original message(s) sent.  Thank you.

Re: TSM and DR

[Bill Fitzgerald]

very true. 

we do a DB backup every day after all the copying and migration is done. 



>>> [EMAIL PROTECTED] 09/19/03 01:28PM >>>
If someone has not taken a TSM DB backup for 3 months, they weren't
really serious about DR in the first place.

Steve Schaub
Systems Engineer
Haworth, Inc
616-393-1457 (desk)
616-412-0544 (numeric page)
[EMAIL PROTECTED] (text page)
WWJWMTD


-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED] 
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a
database recovery. If that DB was created back in January and it's now
March, isn't there a potential for objects getting expired the first
time you start the TSM server? E.g. when the TSM server is started it
typically performs an expire inventory as part of that sequence. I would
imagine that now that it's 2 months later, would it therefore start
expiring objects that you probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server
(or perhaps even before recovering the DB) to ensure expire inventory
doesn't ruin your recovery? I recall there being an option in
dsmserv.opt that allows you to turn off automatic expire inventory. That
seems like a good idea.. but what if there was an admin schedule that
runs expire inventory back then and you happen to start the recovery
while in the schedule's window?

I think you can see what I'm getting at with all this. I want to make
sure all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital
Safe(tm) service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is privileged, confidential or exempt from disclosure
under applicable law.  If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited.  If you have received this communication in error, please
notify the sender immediately by telephone or directly reply to the
original message(s) sent.  Thank you.

Re: TSM and DR

[Reiss David IT751 (ext-CDI)]

I would agree, if you haven't gotten a Dbbackup in months... then, you
aren't serious about DR, or even day to day backups really.

But to answer the expire question...  set the ExpInterval option in the
dsmserv.opt file to 0, or do "setopt ExpInterval 0" from the command line.


David N. Reiss  407-736-3912
TSM Support Engineer
[EMAIL PROTECTED]
...one of God's own prototypes -- a high-powered mutant of some kind who was
never even considered for mass production. He was too weird to live and too
rare to die.

-Original Message-
From: Steve Schaub [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:29 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR


If someone has not taken a TSM DB backup for 3 months, they weren't
really serious about DR in the first place.

Steve Schaub
Systems Engineer
Haworth, Inc
616-393-1457 (desk)
616-412-0544 (numeric page)
[EMAIL PROTECTED] (text page)
WWJWMTD


-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a
database recovery. If that DB was created back in January and it's now
March, isn't there a potential for objects getting expired the first
time you start the TSM server? E.g. when the TSM server is started it
typically performs an expire inventory as part of that sequence. I would
imagine that now that it's 2 months later, would it therefore start
expiring objects that you probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server
(or perhaps even before recovering the DB) to ensure expire inventory
doesn't ruin your recovery? I recall there being an option in
dsmserv.opt that allows you to turn off automatic expire inventory. That
seems like a good idea.. but what if there was an admin schedule that
runs expire inventory back then and you happen to start the recovery
while in the schedule's window?

I think you can see what I'm getting at with all this. I want to make
sure all my bases are covered..

Re: TSM and DR

[Tom Kauffman]

Um -- if your DB backup is that old, yuo've got other REAL problems in your
D/R environment or specifications.

Our requirement (set by the executive board) is to recover, within 48 hours
of the incident, to within 24 hours of the start of outage. If your database
backup is that old, it implies that anything done in the last three months
is of no value . . .

Tom Kauffman
NIBCO, Inc

-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 12:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a database
recovery. If that DB was created back in January and it's now March, isn't
there a potential for objects getting expired the first time you start the
TSM server? E.g. when the TSM server is started it typically performs an
expire inventory as part of that sequence. I would imagine that now that
it's 2 months later, would it therefore start expiring objects that you
probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server (or
perhaps even before recovering the DB) to ensure expire inventory doesn't
ruin your recovery? I recall there being an option in dsmserv.opt that
allows you to turn off automatic expire inventory. That seems like a good
idea.. but what if there was an admin schedule that runs expire inventory
back then and you happen to start the recovery while in the schedule's
window?

I think you can see what I'm getting at with all this. I want to make sure
all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.
CONFIDENTIALITY NOTICE:  This e-mail and any attachments are for the exclusive and 
confidential use of the intended recipient.  If you are not the intended recipient, 
please do not read, distribute or take action in reliance upon this message. If you 
have received this in error, please notify us immediately by return e-mail and 
promptly delete this message and its attachments from your computer system. We do not 
waive attorney-client or work product privilege by the transmission of this message.

Re: TSM and DR

[Ray Baughman]

One other thing to consider.  Does the data still reside on the tapes today
that it resided on one month ago?  With tape reclamation taking place, and
tapes being reused.  The tape which contained data in a storage pool one
month ago, may contain data from another storage pool today.


Ray Baughman
TSM & Engineering Systems Administrator
National Machinery LLC
Phone 419-443-2257
Fax 419-443-2376
Email [EMAIL PROTECTED]


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Gerald Wichmann
> Sent: Friday, September 19, 2003 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: TSM and DR
>
>
> Say for a moment you're faced with recovering a TSM server in a DR
> situation. You have your DB backup and copypool tapes and perform
> a database
> recovery. If that DB was created back in January and it's now March, isn't
> there a potential for objects getting expired the first time you start the
> TSM server? E.g. when the TSM server is started it typically performs an
> expire inventory as part of that sequence. I would imagine that now that
> it's 2 months later, would it therefore start expiring objects that you
> probably don't want to have expired?
>
> If not, why not?
> If so, whats the appropriate step to take before starting the TSM
> server (or
> perhaps even before recovering the DB) to ensure expire inventory doesn't
> ruin your recovery? I recall there being an option in dsmserv.opt that
> allows you to turn off automatic expire inventory. That seems like a good
> idea.. but what if there was an admin schedule that runs expire inventory
> back then and you happen to start the recovery while in the schedule's
> window?
>
> I think you can see what I'm getting at with all this. I want to make sure
> all my bases are covered..
>
>
> This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
> service.  For more information, visit us at www.zantaz.com.
> IMPORTANT: This electronic mail message is intended only for the
> use of the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential or exempt from disclosure under
> applicable
> law.  If the reader of this message is not the intended recipient, or the
> employee or agent responsible for delivering this message to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited.  If you
> have received
> this communication in error, please notify the sender immediately by
> telephone or directly reply to the original message(s) sent.  Thank you.
>

Re: TSM and DR

[Prather, Wanda]

I agree with prior comments that you should have tapes available for DR that
are more current than 3 months back.

However, in MOST cases, even if expiration runs it probably won't cause
problems; TSM is NEVER going to be expiring the ACTIVE files associated with
a node.  And in MOST cases for DR, you are trying to get your client
machines restored to the latest possible level.

Now where you get in trouble, is if you let the client run a new BACKUP,
before you have restored everything you need.  When the client runs, it will
flag any files not on the hard drive as being expired, and that may have
side effects you don't want.

So I would say in a DR situation you should turn off your client schedules.




-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a database
recovery. If that DB was created back in January and it's now March, isn't
there a potential for objects getting expired the first time you start the
TSM server? E.g. when the TSM server is started it typically performs an
expire inventory as part of that sequence. I would imagine that now that
it's 2 months later, would it therefore start expiring objects that you
probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server (or
perhaps even before recovering the DB) to ensure expire inventory doesn't
ruin your recovery? I recall there being an option in dsmserv.opt that
allows you to turn off automatic expire inventory. That seems like a good
idea.. but what if there was an admin schedule that runs expire inventory
back then and you happen to start the recovery while in the schedule's
window?

I think you can see what I'm getting at with all this. I want to make sure
all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.

Tivoli Packet sizes..

[Peter Ford]

I am trying to get some networking information in order to tune the through-put on our 
firewalls that handle TSM backup traffic.  I vaguely remember seeing an option to tune 
the packet size, but I thought I would throw this out to the list for comment.  

How big are typical TSM packet size?  Is there an option to set this size?  What is 
the maximum size for a TSM packet?

thanks in advance.
Peter


Stentor, Inc.
 [EMAIL PROTECTED]  
 http://www.stentor.com

Re: TSM and DR

[Andrew Raibeck]

This is what the REUSEDELAY sequential media storage pool option is for.

Of course, as others have already noted, hopefully your last database
backup is a lot more recent than a month ago. You should be doing TSM
database backups on a regular basis, ideally once a day.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Ray Baughman <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/19/2003 10:51
Please respond to "ADSM: Dist Stor Manager"

To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM and DR


One other thing to consider.  Does the data still reside on the tapes
today
that it resided on one month ago?  With tape reclamation taking place, and
tapes being reused.  The tape which contained data in a storage pool one
month ago, may contain data from another storage pool today.


Ray Baughman
TSM & Engineering Systems Administrator
National Machinery LLC
Phone 419-443-2257
Fax 419-443-2376
Email [EMAIL PROTECTED]


> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Gerald Wichmann
> Sent: Friday, September 19, 2003 1:19 PM
> To: [EMAIL PROTECTED]
> Subject: TSM and DR
>
>
> Say for a moment you're faced with recovering a TSM server in a DR
> situation. You have your DB backup and copypool tapes and perform
> a database
> recovery. If that DB was created back in January and it's now March,
isn't
> there a potential for objects getting expired the first time you start
the
> TSM server? E.g. when the TSM server is started it typically performs an
> expire inventory as part of that sequence. I would imagine that now that
> it's 2 months later, would it therefore start expiring objects that you
> probably don't want to have expired?
>
> If not, why not?
> If so, whats the appropriate step to take before starting the TSM
> server (or
> perhaps even before recovering the DB) to ensure expire inventory
doesn't
> ruin your recovery? I recall there being an option in dsmserv.opt that
> allows you to turn off automatic expire inventory. That seems like a
good
> idea.. but what if there was an admin schedule that runs expire
inventory
> back then and you happen to start the recovery while in the schedule's
> window?
>
> I think you can see what I'm getting at with all this. I want to make
sure
> all my bases are covered..
>
>
> This e-mail has been captured and archived by the ZANTAZ Digital
Safe(tm)
> service.  For more information, visit us at www.zantaz.com.
> IMPORTANT: This electronic mail message is intended only for the
> use of the
> individual or entity to which it is addressed and may contain
information
> that is privileged, confidential or exempt from disclosure under
> applicable
> law.  If the reader of this message is not the intended recipient, or
the
> employee or agent responsible for delivering this message to the
intended
> recipient, you are hereby notified that any dissemination, distribution
or
> copying of this communication is strictly prohibited.  If you
> have received
> this communication in error, please notify the sender immediately by
> telephone or directly reply to the original message(s) sent.  Thank you.
>

Re: Saving data on a defective cartridge

[Paul Zarnowski]

We have had success doing exactly what Doug suggests below.  Sometimes it
requires deleting more than one file.
First, try doing a move data.  Keep doing a Q PROC to see how many files
(if any) the MOVE DATA succeeds in moving.  Oft times, the bad file is not
the first on the tape.  THis is because of file aggregation.  When MOVE
DATA aborts, it backs out the move of all the files in the aggregation.
Then, do a Q CONTENT COUNT=nn, where "nn" is the number of files
successfully moved by MOVE DATA + 1.  This will tell you the filename.
Then do what Doug suggests - find a way to purge this file from TSM.  We
did what Doug suggests, which is to backup the same file enough times that
the copy of the file mapping the bad spot on tape expires.  Once this
happens, try it all again.  There may be more than one file mapping onto
the bad spot.
It would be much easier of TSM handled this more gracefully.

Or, use copy storage pools.

Or, if you're using DLT, use something else.  We've had good luck with LTO.

..Paul

At 10:38 AM 9/18/2003 -0700, Doug Thorneycroft wrote:
If the move fails at the same spot each time, and audit vol f=y
doesn't help, then you might try using q content to see what the first
few files are. Then backup these same files enough times for the copies
on the tape to expire. This might allow a move to skip over the bad spot.
The next step is to beg management for enough blank cartridges to set up
a copy pool.
Doug Thorneycroft
County Sanitation Districts of Los Angeles County
(562) 699-7411 Ext. 1058
FAX (562) 699-6756
[EMAIL PROTECTED]


--
Paul Zarnowski Ph: 607-255-4757
719 Rhodes Hall, Cornell UniversityFx: 607-255-8521
Ithaca, NY 14853-3801  Em: [EMAIL PROTECTED]

Re: Tivoli Packet sizes..

[Richard Sims]

>I am trying to get some networking information in order to tune the
>through-put on our firewalls that handle TSM backup traffic.  I vaguely
>remember seeing an option to tune the packet size, but I thought I would
>throw this out to the list for comment.

If the context is TCP/IP, then it may be mean much...
TCP/IP has architecturally limited MTU sizes, where the standard Ethernet MTU
size is 1500.  Jumbo Frames with gige boost that to 9000, but from what I've
read Jumbo Frames is non-standard.  And you may be cut down anyway by the Path
MTU Discovery.  Larger packets need to be subdivided to be transmitted, then be
reassembled at their destination, in the right order, after receiving all.
Enforcing smaller packets via TCPNodelay may get data out faster, but that may
mean more packets...and each packet makes for a CPU interrupt, and CPU
interrupts can be a big impairment on host performance.

  Richard Sims, BU

Re: TSM and DR

[Gerald Wichmann]

You guys are reading into the question WAY more then need be =). It was a
scenario question and all time lines were made up to drive home the point of
what I was trying to get at, and that's the potential for expire inventory
to expire data you maybe don't want expired. Even if your turn around for a
true disaster is supposedly 48 hours, I would imagine you'd still be
interested in what the question was getting at (if nothing else, just to be
aware of how TSM works if it was a concern).

Also it's a good point that you'd probably only be interested in ACTIVE
files when recovering your environment but none the less, humor me and
assume you're also interested in ensuring no INACTIVE version is lost. In
that case what can one do to ensure no data is expired AT ALL? The only
thing I can think of is to ensure expire inventory never runs. The
dsmserv.opt entry would help prevent that prior to recovering the database
but what about any admin schedules that might've been defined? Is it
possible to disable client and admin scheduling without first starting TSM?

Gerald

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR

I agree with prior comments that you should have tapes available for DR that
are more current than 3 months back.

However, in MOST cases, even if expiration runs it probably won't cause
problems; TSM is NEVER going to be expiring the ACTIVE files associated with
a node.  And in MOST cases for DR, you are trying to get your client
machines restored to the latest possible level.

Now where you get in trouble, is if you let the client run a new BACKUP,
before you have restored everything you need.  When the client runs, it will
flag any files not on the hard drive as being expired, and that may have
side effects you don't want.

So I would say in a DR situation you should turn off your client schedules.




-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a database
recovery. If that DB was created back in January and it's now March, isn't
there a potential for objects getting expired the first time you start the
TSM server? E.g. when the TSM server is started it typically performs an
expire inventory as part of that sequence. I would imagine that now that
it's 2 months later, would it therefore start expiring objects that you
probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server (or
perhaps even before recovering the DB) to ensure expire inventory doesn't
ruin your recovery? I recall there being an option in dsmserv.opt that
allows you to turn off automatic expire inventory. That seems like a good
idea.. but what if there was an admin schedule that runs expire inventory
back then and you happen to start the recovery while in the schedule's
window?

I think you can see what I'm getting at with all this. I want to make sure
all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communication in error, please notify the sender immediately by
telephone or directly reply to the original message(s) sent.  Thank you.

Re: HBA's for backup SAP ?

[Richard Rhodes]

What kind of LAN?

You must match the speed you can read the date from the source disk drives,
the speed
the data can be sent across the lan,  and the write speed of the tape
drives.

We run  LTO I drives to backup our SAP systems.  We use SAn attached disk
and SAN
attached LTO drives.  We are able to spin 4 LTO I drives  at 30MB/s (total
of 120MB/s throughput) .
We use drive compression and get about a 4-to-1 compression ratio (+400GB
per tape).  Note,
we use HP Omniback for this, not TSM.

How much data can you push from the source system to the TSM server via the
LAN?  If it's a
10/100 ethernet, then you won't even get 1 LTO drives worth of speed
(10MB/s).  If the LAN is
GE, then you might be able to get 2 LTO drives spinning (60MB/s).  I
suppose it's
possible to get 3 spinning (90MB/s), but I've never seen a GE connection
run that fast sending
real data.   I don't see how you expect to keep 4 drives spinning.

If you can get the drives spinning at full speed, then you probably should
only attach 2 drives per
FC adapter.

The worse thing you can do is run lots of drives but starve them for data.






  Juan Jose Reale
  <[EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  OM>  cc:   (bcc: Richard L. 
Rhodes/OE/FirstEnergy)
  Sent by: "ADSM:  Subject:  HBA's for backup SAP ?
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  09/18/2003 05:55
  PM
  Please respond to
  "ADSM: Dist Stor
  Manager"






 Hi everybody!

Some of you know how many HBA's (Fibre Channel Bus Adapter 1000
Gb/s) we should get for backup SAP via LAN.  We have four drives LTO I
(3584) and are running TSM 4.2.2.10 on AIX and TSM Client on Window 2000.
We are not using SAN.

Big thank.  I very much look forward to hearing from you.
Regards.
Juan R.
System Administrator.


This email has been scanned for all viruses by the MessageLabs service.






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

Re: TSM and DR

[Richard Sims]

>...Is it
>possible to disable client and admin scheduling without first starting TSM?

DISABLESCheds   Server option to specify whether
administrative and client schedules are
disabled during an TSM server recovery
scenario.  Syntax:
 DISABLESCheds Yes | No
Default:  No

  Richard Sims, BU

Re: Managed Systems for SAN files needed

[David Longo]

Did you try cleaning the CD?  Not the drive but the CD?  May be obvious
large or small smudges or boulders on it.  I had a big problem once.  30 
seconds of cleaning solved it.


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 09/19/03 10:01AM >>>
Hello all,
 I was preparing to setup Lan-free on my new 5.1 server and found that my CD
is physically bad and I cannot access the files that I need (belive me, I've
tried it in every machine in sight.) Does anyone have any idea where I can
find the filesets that I need? I'm just looking for the stuff in the
/usr/sys/inst.images directory. I've called my distributor and asked for a
media refresh, but it won't be here until Monday.

Thanks in advance for your help... Btw the Full name and numbers on the CD
are "IBM Tivoli Storage Manager for Storage Area Networks Managed Systems
for SAN" v.5.1.5  LCD7-0426-01 C23PWIE



Shawn

##
This message is for the named person's use only.  It may 
contain confidential, proprietary, or legally privileged 
information.  No confidentiality or privilege is waived or 
lost by any mistransmission.  If you receive this message 
in error, please immediately delete it and all copies of it 
from your system, destroy any hard copies of it, and notify 
the sender.  You must not, directly or indirectly, use, 
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of 
a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.
##

Copypool Reclamation

[Mark Bertrand]

How does Copypool reclamation work? I mean, the tapes are offsite, so is all
of the reclamation done within the database?

When I start the copypool reclamation with an "upd stg copypool reclaim=50"
it tells me what tapes it is going to perform reclamation on. Everything is
OK, those tapes are offsite and my tapepool tapes are onsite ( I run a
tapepool reclamation separate). I always understood that the process took
place in the database and didn't actual need the tapes directly. This
morning I noticed an anr1081i.
09/19/2003 09:05:05 ANR1040I Space reclamation started for volume xxxACRLx,
storage pool COPYPOOL (process number 745).
09/19/2003 09:08:14 ANR1081W Space reclamation terminated for volume
xxxACRLx - storage media inaccessible.
Help on anr1081w shows that the tape was unavailable to mount, server waits
and retries again, no user response.
Do I have to checkin all tapes on the list for every copypool reclamation
process everyday? Have I been doing it wrong for the last couple of years?
I have read the technical guide and information guide redbooks but neither
had much detail on the subject. I did find out one thing that brings up
another question, to start reclamation, the technical guide state to use a
number between 99 and 50 percent, why cutoff at 50% I have been running at
40% and at times have used 30%? Will the system recognize numbers lower than
50?
OK last question on reclamation, is my goal to have the tapes listed with q
vol that have a status of full to have as close to 100% utilized as I can
get them to take full advantage of my library?
I appreciate any help you can give to help me understand reclamation better,
even if it is to direct me to another publication that has the details on
this subject. I also tried search.adsm.org but could not get to it this
morning.
System TSM Server 5.1.6.3 with DRM, Win 2K. 3584 Library
Thanks,
Mark Bertrand

Re: Tivoli Packet sizes..

[Peter Ford]

> -Original Message-
> From: Richard Sims [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 19, 2003 11:25 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Tivoli Packet sizes..
> 
> 
> If the context is TCP/IP, then it may be mean much...
> TCP/IP has architecturally limited MTU sizes, where the 
> standard Ethernet MTU
> size is 1500.  Jumbo Frames with gige boost that to 9000, but 
> from what I've
> read Jumbo Frames is non-standard.  And you may be cut down 
> anyway by the Path
> MTU Discovery.  Larger packets need to be subdivided to be 
> transmitted, then be
> reassembled at their destination, in the right order, after 
> receiving all.

We really need as large a packet size as possible.  Will TSM send the at the largest 
possible MTU by default?  As you pointed out Richard, we want to pack as much data 
into the fewest number of packets to increase throughput.  

Thanks.
Peter

Re: Copypool Reclamation

[Ford, Phillip]

Copytape reclamation generally uses copytapes if they are in the library and
not offsite.  If they are offsite then reclaim uses the primary tapes.  I
have seen your problem if the primary tape is marked unavailable for some
reason or is taken out of the library.  It can also fail if the primary tape
has a corrupted file that can not be used.  I set reclaim to 45.  If I can
take two tape and write one then I gain a scratch.  Generally we are tight
on the number of scratches.  I have gone lower but we just end up beating
our selves to death.


--
Phillip Ford
Senior Software Specialist
Corporate Computer Center
Schering-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
[EMAIL PROTECTED]





-Original Message-
From: Mark Bertrand [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:58 PM
To: [EMAIL PROTECTED]
Subject: Copypool Reclamation


How does Copypool reclamation work? I mean, the tapes are offsite, so is all
of the reclamation done within the database?

When I start the copypool reclamation with an "upd stg copypool reclaim=50"
it tells me what tapes it is going to perform reclamation on. Everything is
OK, those tapes are offsite and my tapepool tapes are onsite ( I run a
tapepool reclamation separate). I always understood that the process took
place in the database and didn't actual need the tapes directly. This
morning I noticed an anr1081i. 09/19/2003 09:05:05 ANR1040I Space
reclamation started for volume xxxACRLx, storage pool COPYPOOL (process
number 745). 09/19/2003 09:08:14 ANR1081W Space reclamation terminated for
volume xxxACRLx - storage media inaccessible. Help on anr1081w shows that
the tape was unavailable to mount, server waits and retries again, no user
response. Do I have to checkin all tapes on the list for every copypool
reclamation process everyday? Have I been doing it wrong for the last couple
of years? I have read the technical guide and information guide redbooks but
neither had much detail on the subject. I did find out one thing that brings
up another question, to start reclamation, the technical guide state to use
a number between 99 and 50 percent, why cutoff at 50% I have been running at
40% and at times have used 30%? Will the system recognize numbers lower than
50? OK last question on reclamation, is my goal to have the tapes listed
with q vol that have a status of full to have as close to 100% utilized as I
can get them to take full advantage of my library? I appreciate any help you
can give to help me understand reclamation better, even if it is to direct
me to another publication that has the details on this subject. I also tried
search.adsm.org but could not get to it this morning. System TSM Server
5.1.6.3 with DRM, Win 2K. 3584 Library Thanks, Mark Bertrand


*
This message and any attachments are solely for the intended recipient. If you are not 
the intended recipient, disclosure, copying, use or distribution of the information 
included in this message is prohibited -- Please immediately and permanently delete.

Re: Tivoli Packet sizes..

[Richard Sims]

>We really need as large a packet size as possible.  Will TSM send the at
>the largest possible MTU by default?  As you pointed out Richard, we
>want to pack as much data into the fewest number of packets to increase
>throughput.

Peter - Try for gigabit ethernet with Jumbo Frames for optimal throughput.

For most data in fewest packets, then compressed data is the thing,
either having previously been compressed on the client or per TSM
compression at send time.

There is also Adaptive Differencing (a.k.a "adaptive sub-file backup"),
which may be applicable, which reduces transmission requirements.

  Richard Sims, BU

Tape Library Capacity Increase Help.

[Curt Watts]

Howdy,

  I managed to increase the capacity of our IBM 3583 tape library from
18 LTO tapes to 54 LTO tapes but now the question arises, how do I get
TSM (4.2.3.2) to recognize the increase in the Tape Pool.  My fear is
that because the tape pool has been set up with the estimation of only
18 tapes, I'm going to have to create a new tape pool with the new size
and move the data over.
  I'm pretty sure the tape library is functional from the hardware side
of things because I'm able to manually move tapes from the I/O port into
the new tape cartidges.  The reason behind my question is that when
trying to checkin more than 18 tapes, I'm getting a "Library is Full"
from TSM.

Thanks & Regards

Curt Watts

___
Curt Watts
Network Analyst, Capilano College
[EMAIL PROTECTED]

Re: TSM and DR

[Tom Kauffman]

Well -- The first step in our recovery scenario (after starting the newly
restored TSM server) deletes all administrative schedules. The second step
is to kill any running processes (usually an expire inventory :-). But -
since our TSM database goes off with the data tapes every day, it is in sync
with them; expire inventory won't cost us anything, providing we haven't
done any client backups of non-restored clients yet.

Now, FWIW, we don't do bare-metal Windows restores -- we reload and restore
the application data only; and the vast majority of our mandatory recovery
data is in the form of archives with a given retention -- mostly 21 day.
Loosing the oldest day or so of the archive is not an issue. Not being able
to recover the most current archive IS an issue. I can see where there would
be differences if we were backing up and recovering desktops (and I'm SO
glad I don't need to :-)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:27 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR


You guys are reading into the question WAY more then need be =). It was a
scenario question and all time lines were made up to drive home the point of
what I was trying to get at, and that's the potential for expire inventory
to expire data you maybe don't want expired. Even if your turn around for a
true disaster is supposedly 48 hours, I would imagine you'd still be
interested in what the question was getting at (if nothing else, just to be
aware of how TSM works if it was a concern).

Also it's a good point that you'd probably only be interested in ACTIVE
files when recovering your environment but none the less, humor me and
assume you're also interested in ensuring no INACTIVE version is lost. In
that case what can one do to ensure no data is expired AT ALL? The only
thing I can think of is to ensure expire inventory never runs. The
dsmserv.opt entry would help prevent that prior to recovering the database
but what about any admin schedules that might've been defined? Is it
possible to disable client and admin scheduling without first starting TSM?

Gerald

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR

I agree with prior comments that you should have tapes available for DR that
are more current than 3 months back.

However, in MOST cases, even if expiration runs it probably won't cause
problems; TSM is NEVER going to be expiring the ACTIVE files associated with
a node.  And in MOST cases for DR, you are trying to get your client
machines restored to the latest possible level.

Now where you get in trouble, is if you let the client run a new BACKUP,
before you have restored everything you need.  When the client runs, it will
flag any files not on the hard drive as being expired, and that may have
side effects you don't want.

So I would say in a DR situation you should turn off your client schedules.




-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a database
recovery. If that DB was created back in January and it's now March, isn't
there a potential for objects getting expired the first time you start the
TSM server? E.g. when the TSM server is started it typically performs an
expire inventory as part of that sequence. I would imagine that now that
it's 2 months later, would it therefore start expiring objects that you
probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server (or
perhaps even before recovering the DB) to ensure expire inventory doesn't
ruin your recovery? I recall there being an option in dsmserv.opt that
allows you to turn off automatic expire inventory. That seems like a good
idea.. but what if there was an admin schedule that runs expire inventory
back then and you happen to start the recovery while in the schedule's
window?

I think you can see what I'm getting at with all this. I want to make sure
all my bases are covered..


This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm)
service.  For more information, visit us at www.zantaz.com.
IMPORTANT: This electronic mail message is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law.  If the reader of this message is not the intended recipient, or the
employee or agent responsible for delivering this message to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If you have received
this communi

Re: Tape Library Capacity Increase Help.

[David Longo]

Did you halt and restart TSM after the Library was upgraded?
You need to do that so TSM picks up new configf of library.

You then need to immediately run an
"audit library blah checklabel=barcode"  to synchronize inventory,
before doing any tape operations.


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 09/19/03 03:13PM >>>
Howdy,

  I managed to increase the capacity of our IBM 3583 tape library from
18 LTO tapes to 54 LTO tapes but now the question arises, how do I get
TSM (4.2.3.2) to recognize the increase in the Tape Pool.  My fear is
that because the tape pool has been set up with the estimation of only
18 tapes, I'm going to have to create a new tape pool with the new size
and move the data over.
  I'm pretty sure the tape library is functional from the hardware side
of things because I'm able to manually move tapes from the I/O port into
the new tape cartidges.  The reason behind my question is that when
trying to checkin more than 18 tapes, I'm getting a "Library is Full"
from TSM.

Thanks & Regards

Curt Watts

___
Curt Watts
Network Analyst, Capilano College
[EMAIL PROTECTED]

##
This message is for the named person's use only.  It may 
contain confidential, proprietary, or legally privileged 
information.  No confidentiality or privilege is waived or 
lost by any mistransmission.  If you receive this message 
in error, please immediately delete it and all copies of it 
from your system, destroy any hard copies of it, and notify 
the sender.  You must not, directly or indirectly, use, 
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of 
a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.
##

Re: Tape Library Capacity Increase Help.

[Hart, Charles]

This may be too simple of an answer, but just increase the Max Scratch of the stgpool.

-Original Message-
From: Curt Watts [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 2:13 PM
To: [EMAIL PROTECTED]
Subject: Tape Library Capacity Increase Help.


Howdy,

  I managed to increase the capacity of our IBM 3583 tape library from
18 LTO tapes to 54 LTO tapes but now the question arises, how do I get
TSM (4.2.3.2) to recognize the increase in the Tape Pool.  My fear is
that because the tape pool has been set up with the estimation of only
18 tapes, I'm going to have to create a new tape pool with the new size
and move the data over.
  I'm pretty sure the tape library is functional from the hardware side
of things because I'm able to manually move tapes from the I/O port into
the new tape cartidges.  The reason behind my question is that when
trying to checkin more than 18 tapes, I'm getting a "Library is Full"
from TSM.

Thanks & Regards

Curt Watts

___
Curt Watts
Network Analyst, Capilano College
[EMAIL PROTECTED]

TDPOSYNC returns Backup Sets even if they are present in the RMAN catalog

[Mike Angels]

Hi all,

I'm trying to use TDPOSYNC utility to delete all TSM entries no more present in the 
RMAN catalog.
As described in the manuals, TDPOSYNC should present, for the deletion, only the 
Backup Sets no more catalogued in RMAN catalog.
Instead the utility presents all Backup Sets, even if they are still in the RMAN 
catalog.

For example with the following command

tdposync syncdb
Catalog 1 User Name: rman
Catalog 1 Password: rman
Catalog 1 Connect String: europr
>From Date (mm/dd/yy): 09/01/03
To Date (mm/dd/yy): 09/01/03

give me the following Backup Sets:


   Backup DateSizeBackup Name
---
 1. |  09/01/0316:05:58   15.00MB /adsmorc//TTSM/503597152/33
 2. |  09/01/0316:05:52   41.00MB /adsmorc//TTSM/503597151/33
 3. |  09/01/0316:05:442,048.00KB /adsmorc//TTSM/503597143/33
 4. |  09/01/0316:05:443,072.00KB /adsmorc//TTSM/503597143/33
 5. |  09/01/0316:00:51   41.00MB /adsmorc//TTSM/503596850/33
 6. |  09/01/0316:00:51   20.00MB /adsmorc//TTSM/503596848/33
|

Those Backup Sets should be, as report by the manual, files that exist on Tivoli 
Storage Manager but not on RMAN

but the RMAN command

list backup;

say that those Backup Sets are still in the RMAN catalog with AVAILABLE status as 
shown below for one of them:


List of Backup Sets
Key Recid  Stamp  LV Set Stamp  Set Count  Completion Time
--- -- -- -- -- -- --
20034   329503596857  0  503596848  33101-SEP-03

List of Backup Pieces
Key Pc# Cp# Status  Completion TimePiece Name
--- --- --- --- -- 
20037   1   1   AVAILABLE   01-SEP-03  TTSM/503596848/331/1

List of Datafiles Included
File Name  LV Type Ckp SCNCkp Time
 - --  -- -
2/DATI_TTSM/oracle/data/rbs01.dbf  0  Full 36090  01-SEP-03
3/DATI_TTSM/oracle/data/users01.dbf0  Full 36090  01-SEP-03
4/DATI_TTSM/oracle/data/temp01.dbf 0  Full 36090  01-SEP-03

Is someone else using the TDPOSYNC utility?
Has someone else any idea about this behavior?

Thanks,

Mike

Re: TSM and DR

[Bill Smoldt]

Gerald,

When I've restored an old database, I've always had to use the ACCEPT DATE
command to get everything running again.  This also happens if I leave a TSM
server shut down for a month and then try to bring it up (as when I teach a
class once a month).

>From the Admin Reference Manual:

In addition, if the server detects an invalid date or time, server sessions
become disabled (as if the DISABLE SESSIONS command had been issued).
Expiration, migration, reclamation, and volume history deletion operations
are not able to continue processing.

An invalid time is considered to be:
Earlier than the server installation date and time.
More than one hour earlier than the last time the date was checked.
More than 30 days later than the last time the date was checked.

So in your example of restoring a database from January, expiration would
not run.

I hope it helps you sleep better this weekend anyway.

Bill Smoldt
STORServer, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Tom Kauffman
Sent: Friday, September 19, 2003 1:29 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR


Well -- The first step in our recovery scenario (after starting the newly
restored TSM server) deletes all administrative schedules. The second step
is to kill any running processes (usually an expire inventory :-). But -
since our TSM database goes off with the data tapes every day, it is in sync
with them; expire inventory won't cost us anything, providing we haven't
done any client backups of non-restored clients yet.

Now, FWIW, we don't do bare-metal Windows restores -- we reload and restore
the application data only; and the vast majority of our mandatory recovery
data is in the form of archives with a given retention -- mostly 21 day.
Loosing the oldest day or so of the archive is not an issue. Not being able
to recover the most current archive IS an issue. I can see where there would
be differences if we were backing up and recovering desktops (and I'm SO
glad I don't need to :-)

Tom Kauffman
NIBCO, Inc

-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:27 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR


You guys are reading into the question WAY more then need be =). It was a
scenario question and all time lines were made up to drive home the point of
what I was trying to get at, and that's the potential for expire inventory
to expire data you maybe don't want expired. Even if your turn around for a
true disaster is supposedly 48 hours, I would imagine you'd still be
interested in what the question was getting at (if nothing else, just to be
aware of how TSM works if it was a concern).

Also it's a good point that you'd probably only be interested in ACTIVE
files when recovering your environment but none the less, humor me and
assume you're also interested in ensuring no INACTIVE version is lost. In
that case what can one do to ensure no data is expired AT ALL? The only
thing I can think of is to ensure expire inventory never runs. The
dsmserv.opt entry would help prevent that prior to recovering the database
but what about any admin schedules that might've been defined? Is it
possible to disable client and admin scheduling without first starting TSM?

Gerald

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM and DR

I agree with prior comments that you should have tapes available for DR that
are more current than 3 months back.

However, in MOST cases, even if expiration runs it probably won't cause
problems; TSM is NEVER going to be expiring the ACTIVE files associated with
a node.  And in MOST cases for DR, you are trying to get your client
machines restored to the latest possible level.

Now where you get in trouble, is if you let the client run a new BACKUP,
before you have restored everything you need.  When the client runs, it will
flag any files not on the hard drive as being expired, and that may have
side effects you don't want.

So I would say in a DR situation you should turn off your client schedules.




-Original Message-
From: Gerald Wichmann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2003 1:19 PM
To: [EMAIL PROTECTED]
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a database
recovery. If that DB was created back in January and it's now March, isn't
there a potential for objects getting expired the first time you start the
TSM server? E.g. when the TSM server is started it typically performs an
expire inventory as part of that sequence. I would imagine that now that
it's 2 months later, would it therefore start expiring objects that you
probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the

Re: Saving data on a defective cartridge

[Bill Smoldt]

Good call, Wanda.

Joseph, please post the email addresses and home phone numbers of your upper
management here so we can help you convince them.  Or print our our
responses and anonymously put them in your manager's in box.

Bill

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Prather, Wanda
Sent: Friday, September 19, 2003 9:45 AM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


That's insane.
Sounds like the best bet for cost savings would be to focus on elimiating
some upper management!!!

-Original Message-
From: Wholey, Joseph (IDS DM&DS) [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 1:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


A "little" off the subject, and I already heard Richard Simms view on not
having a second copy...  but what are most shops doing with respect to a
second copy.
I'm in a pretty large shop and upper management, in a cost savings effort,
wants us to turn off the creation of a second tape copy.  I'm not too
comfortable with the idea.  What are "your" thoughts?

-Original Message-
From: Coats, Jack [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 12:38 PM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


Try doing a move data to get the data off of the tape.  If I find I am
starting to have problems I usually do a:

update vol VOLUMENAME acc=reado
move data VOLUMENAME

This should move all data that is recoverable from the volume to another
volume in the same storage pool.  I then eject the offending volume and
check it for apparent physical issues.  Then the part I hate:

delete vol VOLUMENAME discarddata=yes

Sometimes I am able to re-label the volume and use it again.  But
typically it gets moved to a less critical use, returned to the vendor
for a new tape [my preferred method], or degaused and distroyed by
a certified vendor [least preferred, paying to have it thrown away].

If anyone has a better method, please let me know! ... JC

-Original Message-
From: Gerhard Rentschler [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 11:24 AM
To: [EMAIL PROTECTED]
Subject: Re: Saving data on a defective cartridge


Hello,
I forgot to mention that because of lack of resources I can't afford a
copypool for the backup files. I have one for the archives.
Best regards
Gerhard

---
Gerhard Rentschleremail:[EMAIL PROTECTED]
Regional Computing Center tel.   ++49/711/685 5806
University of Stuttgart   fax:   ++49/711/682357
Allmandring 30a
D 70550
Stuttgart
Germany



> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> Juan Manuel Lopez Azanon
> Sent: Thursday, September 18, 2003 6:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Saving data on a defective cartridge
>
>
> Disaster recovery management: Restore it from outside volumes from copy
> stgpool
>

tsm win2k silent install

[Tim Brown]

i am trying a silent install with tsm 5.2 on win 2k, the 5.1 code readme file
had this command

dsmcutil  install /name:"TSM Central Scheduler Service" /node:NODE /password:PASS 
/autostart:yes /MACHine:nODE /CLIENTDIR:"c:\program files\tivoli\tsm\baclient"

the 5.2 readme does not

has anybody been able to install 5.2 on win2k silently

Tim Brown
Systems Specialist
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Phone: 845-486-5643
Fax: 845-486-5921

Re: Tape Library Capacity Increase Help.

[Curt Watts]

Well, I managed to get it up and running.  Good suggestion on the halt
and restart - completely slipped my mind to restart the box.  It did
however take a full restart of the server (not just restarting the
service) in order for it to pick up the new config.  As well, I had to
reenable the Managed Library license as the config had changed from the
previous one.

Oh, I had already increased the Max Scratch variable to accommodate.

Cheers,
  Curt

___
Curt Watts
Network Analyst, Capilano College
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 19/09/2003 12:32:07 pm >>>
Did you halt and restart TSM after the Library was upgraded?
You need to do that so TSM picks up new configf of library.

You then need to immediately run an
"audit library blah checklabel=barcode"  to synchronize inventory,
before doing any tape operations.


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 09/19/03 03:13PM >>>
Howdy,

  I managed to increase the capacity of our IBM 3583 tape library from
18 LTO tapes to 54 LTO tapes but now the question arises, how do I get
TSM (4.2.3.2) to recognize the increase in the Tape Pool.  My fear is
that because the tape pool has been set up with the estimation of only
18 tapes, I'm going to have to create a new tape pool with the new
size
and move the data over.
  I'm pretty sure the tape library is functional from the hardware
side
of things because I'm able to manually move tapes from the I/O port
into
the new tape cartidges.  The reason behind my question is that when
trying to checkin more than 18 tapes, I'm getting a "Library is Full"
from TSM.

Thanks & Regards

Curt Watts

___
Curt Watts
Network Analyst, Capilano College
[EMAIL PROTECTED]

##
This message is for the named person's use only.  It may
contain confidential, proprietary, or legally privileged
information.  No confidentiality or privilege is waived or
lost by any mistransmission.  If you receive this message
in error, please immediately delete it and all copies of it
from your system, destroy any hard copies of it, and notify
the sender.  You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of
a particular entity;  and (2) the sender is authorized by
the entity to give such views or opinions.
##

TCP/IP NAME TCP/IP ADDRESS

Need a little assistance on this.
I issue "q node f=d" from the server side for a NODE_A, I get a TCP/IP NAME and TCP/IP 
ADDRESS that are incorrect (say NODE_B).
At some point I may have connected virtually w/ the TCP/IP NAME (NODE_B) that I'm 
seeing, but even after I connect from the local host, NODE_A, the  TCP/IP NAME and 
TCP/IP ADDRESS still reflect
NODE_B's information.
I've seen this on a few instances.  What drew this to my attention is the fact that I 
had 8 sessions started for one archive on NODE_A and no "resource" definition in the 
dsm.sys.  When I checked the
dsm.sys on NODE_B, lo and behold, resource utilization is set to 10.  What am I 
missing?

Server Platform Z/os  running TSM Server v5,1,6.1
NODE_A Client Platform Sun2.8 running BAclient TSMv4,2,2.1
NODE_B Client Platform Sun2.8 running BAclient TSMv4,2,1.0

Any help would be greatly appreciated.  thx.

TSM managed services

Can anyone share some info on TSM managed services to address a Unix memory leak.  
i.e. have dsmcad start scheduler prior to backup and stop it after backup.  My 
understanding is that the memory leak
is actually a short coming of the Unix operating system architecture.  Apparently the 
scheduler aquires memory and does not release it.  Who recommends managed services?  
I'd like to hear.  thx.

Re: TSM managed services

[David Longo]

My only Unix here is AIX, have about 3 dozen.  Only use
dsmcad on one AIX system that has 10 million files (no typo).
Without it paging space would grow over days.

Also use it on most Novell file servers that have near 1 million
files more or less.  Makes them more stable.


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 09/19/03 10:17PM >>>
Can anyone share some info on TSM managed services to address a Unix memory leak.  
i.e. have dsmcad start scheduler prior to backup and stop it after backup.  My 
understanding is that the memory leak
is actually a short coming of the Unix operating system architecture.  Apparently the 
scheduler aquires memory and does not release it.  Who recommends managed services?  
I'd like to hear.  thx.

##
This message is for the named person's use only.  It may 
contain confidential, proprietary, or legally privileged 
information.  No confidentiality or privilege is waived or 
lost by any mistransmission.  If you receive this message 
in error, please immediately delete it and all copies of it 
from your system, destroy any hard copies of it, and notify 
the sender.  You must not, directly or indirectly, use, 
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of 
a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.
##