Re: Retrieving Associated Volumes from Off-Site

[Zlatko Krastev/ACIT]

I am just a beginner but what I read in the docs was that you have to do it
in REVERSE order!!!
Have a look at RedBook SG24-4877 "Tivoli Storage Management Concepts" (it
can be downloaded from http://www.redbooks.ibm.com).

At page 88 (p.110 in the PDF) you can read:
"   5.4.2 Reclamation of offsite volumes
Care must be taken in reclaiming offsite copy storage volumes. Tivoli
Storage Manager cannot physically move the data from one of these volumes
to another, because they are in a vault, not available in the library.
Tivoli Storage Manager manages reclamation for an offsite copy pool by
obtaining the active files from a primary storage pool or from an onsite
volume of a copy pool. These files are then written to a new volume in the
copy pool, and the database is updated. A message is then issued that an
offsite volume was reclaimed. The new volume will get moved to the offsite
location, and the offsite volumes, whose active data it has combined, will
be moved back to the scratch pool onsite, when the reuse delay parameter
has been satisfied. "

Thus first you have to reclaim volumes from primary pools data. Your copy
data will not be lost and all volumes (look below) will be reclaimed.
You will get the list of emptied volumes which on the phase two can be
retrieved back on-site. This must be done just after you are sure that new
copy volume(s) arrived off-site. Coming back you can take with you the
listed free/scratch volumes.

Remark: If an reclaimable volume contains just part of a file and the rest
is on another volume (which is your associated one). The file would be
reclaimed from both on a third volume (new copy vol) and now the second
volume usage can also drop below 5% (it will become 95% reclaimable). And
you will have another volume for reclamation.

Greetings
Zlatko Krastev
IT Consultant





Ruth Robertson <[EMAIL PROTECTED]> on 26.07.2001 22:08:47
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Retrieving Associated Volumes from Off-Site

My copy storage pool volumes go off-site.  Once a week, I start reclamation
for the off-site volumes: I list out volumes where percent reclaimable
space
>= 95, I retrieve those volumes from off-site, check them in, and set
reclamation to 95.  Works great...except for a few volumes that complain
about an associated volume before they'll be reclaimed.  The associated
volumes don't show up in the reclamation list, and are therefore not
retrieved from off-site.  How do I get the list of volumes associated with
those in the reclamation list?
Since I only receive the ADSM-L Digest, please email me directly.
Thanks!
Ruth Robertson, Unix Administrator
[EMAIL PROTECTED]

Re: Teaching others TSM

[Zlatko Krastev/ACIT]

IMHO training can provide you two things - a smooth start and someone more
experienced than you (to ask questions and to give you broad overview).
At the other side nothing can replace practical experience ("The experience
is proportional to the number of broken systems" :-)

So the answer is: do both.
And this is relevant not only to TSM.

Re: Admin changes in last 2 years? - Image backup

[Zlatko Krastev/ACIT]

Image backup is completely different than selective backup. This is offline
backup of raw device, i.e. RDBMS table space.




Any improvements with point in time backup/restores? I see an
"imagebackup", but from reading the description doesn't make much sense to
me. It reads pretty much like the same thing as a selective backup.

Re: Backup Scheduling

[Zlatko Krastev/ACIT]

The backup set IS exactly a snapshot. It makes a bundle of file copies and
does not track the separate files (the DB tracks them as parts of stgpools)
but tracks the entire bundle/backupset as a single object.
The backupset written to a media (tapes, CDs, etc.) can be used for "bare
metal/LAN-free" restore. So tracking of backupset gives you an idea when
you created that image. If it is recent enough you can restore the system
from media containing the backupset and later just restore newer files.
So this functions also as something similar to archive.





On Fri, 27 Jul 2001, Len Boyle wrote:

> In article <[EMAIL PROTECTED]>, Steve Harris
> <[EMAIL PROTECTED]> says:
> 2) If you need to keep a snap shot of data for a long time  without the
>need to keep the data in the tsm data look at the backupset
>function to snap a copy of the active fileset on a tape set that
>can be removed from the tsm server.


I just read the description for the backupset and I don't see how it can
be used as a snap shot. I didn't really understand from reading that what
is that the backupset is or does. In particular I don't see how it would
do what Len wrote above .. "keep a snap shot of data for a long time
without the need to keep the data in the tsm data". Does that mean that
the backupset is not tracked by the DB? It seems TSM remembers or tracks
the existance of the backupset since there is a parameter for that, but
what does that keep track of?

Thanks.

Re: TDP not using diskpool

[Zlatko Krastev/ACIT]

Check the destination storage pool in your copy group.
Are you using different node name for Backup/Archive client and for TDP ?
What is the TDP you are having problem with ?

I made backups successfully on disk with both TDP for Domino and TDP for
Informix.







Gisbert Schneider <[EMAIL PROTECTED]> on 27.07.2001 19:11:28
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TDP not using diskpool

Hello,

when we do a backup via the TDP, the backup goes not first to the
disk storage pool, but directly to tape. We have tried it with and without
caching files on the disk pool. No success. Has someone an idea what
the problem might be?

An other problem is that, when we set caching to NO, the value for PctUtil
never becomes zero. Can we force it and how?

Thanks,
Gisbert



__


   Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden
   koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche
   Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer
   die Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von
   rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben
   unberuehrt.

Re: Magstar 3570

[Zlatko Krastev/ACIT]

We run a nightly archive of 70 GB that is taking just over 8 hours
uncompressed.   In our Magstar 3570 we have two different tape drives.   My
question follows:   Is it possible to be running two different archives at
the same time to cut down the processing time?   If it is possible how
would
you go at it?


If you are able to allocate 50-70 GB of disk space I would recommend you to
create primary storage pool of type DISK and setup that its next storage
pool is the tape pool defined on 3570. Later set its migration thresholds
average low (for example HighMig=30 LowMig=0).
This must speed up your backup and probably you will finish faster than in
8 hours and migration processes will start for both drives moving data from
disk storage pool to tape.

Zlatko Krastev
IT Consultant

Re: TDP not using diskpool - IT IS BACKUP

[Zlatko Krastev/ACIT]

THIS IS NOT TRUE. Look at the report from TDP for Informix backup:

tsm: PUMBA.ACIT.BG>q cont /dev/rtsm_bk00

Node NameType Filespace  Client's Name for File
  Name
  --
--
PUMBA-API.ACIT.BGBkup /pumba_lo- /pumba_local/datadbs/ 0
   cal

tsm: PUMBA.ACIT.BG>q cont /dev/rtsm_bk01

Node NameType Filespace  Client's Name for File
  Name
  --
--
PUMBA-API.ACIT.BGBkup /pumba_lo- /pumba_local/rootdbs/ 0
   cal
PUMBA-API.ACIT.BGBkup /pumba_lo- /pumba_local/datadbs/ 0
   cal
PUMBA-API.ACIT.BGBkup /pumba_lo- /pumba_local/0/ 20
   cal






remember that TDP is not going to your server as a "backup" it is going as
an "archive" look at where the archives are pointed to in the management
class you've specified in your init.utl file...

Dwight

Re: Magstar 3570

[Zlatko Krastev/ACIT]

We run a nightly archive of 70 GB that is taking just over 8 hours
uncompressed.   In our Magstar 3570 we have two different tape drives.   My
question follows:   Is it possible to be running two different archives at
the same time to cut down the processing time?   If it is possible how
would
you go at it?


If you wish to do backup on two (or more drives) simultaneously just change
the MAXNUMMP parameter for the nodes you want to speed-up the backup. This
should allow you to write to many devices using single session.
Anyway I stay at my previous opinion that backup to disk (with server
migrating data to tape) has to be faster.

Zlatko Krastev
IT Consultant

Re: SUBFILE Technical Details?

[Zlatko Krastev/ACIT]

See redbook SG2-6110 "Tivoli Storage Manager Version 3.7.3 & 4.1: Technical
Guide" p.p. 20-39 (36-55 in pdf file).
You can obtain it from http://www.redbooks.ibm.com/
You can find there description of adaptive sub-file backup in detail.

Zlatko Krastev
IT Consultant





mrkirra2001 <[EMAIL PROTECTED]> on 31.07.2001 06:14:53
Please respond to mrkirra2001 <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:SUBFILE Techonical Details?

Is there anywhere that I can find the technical details on how SUBFILE
works? For example..
- what does it use the local cache for? - if I have 20GB of backup data,
how
does it use the 10MB cache area?
- what if I delete the local cache?
- does TSM always backup the differences, or is it smart enough to say this
difference file is 50% (for example) of the original so I'll back it all
up!
- does it do a full backup every now again anyway?
- should compression and subfile be used together?

It would be really nice to see all these questions and more answered in one
paper...

Regards

/gjs

Re: Bad tape

[Zlatko Krastev/ACIT]

David,

look for AUDIT VOLUME, RESTORE VOLUME and UPDATE VOLUME ACCESS=DESTROYED
commands. They can help you when the bad things already happened.
If you want to prevent or predict tape failure you can use private volumes
instead of scratch (yes, I know it's harder to maintain).
For private volumes there is useful info in Q VOL F=D output - "Write Pass
Number: ". And you can estimate how many times this particular cartridge
was used.
You have same data for scratch volumes BUT when the volume becomes empty
and returns to scratch status the counter is reset to 0 !!! So you cannot
rely on it.

Greetings
Zlatko Krastev
IT Consultant


Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Bad tape

Is there a procedure to replace the data on a tape that has went
bad? We use 3590 tapes on our AS/400 side and they are known to break the
tape or just become unusable for some reason.
We haven't had a bad tape on the PC side yet. We use a library that
has the tapepool tapes in it and have our copypool tapes in the vault. I
know it will happen one day and I need some way to replace the data that
was
on the unusable tape either from the library or from the vault.
Server is a WinNT4 running 4.1.3.
Thanks...

David Tyree
Microcomputer Specialist
South Georgia Medical Center
229.333.1155

Confidential Notice:  This e-mail message, including any attachments, is
for
the sole use of the intended recipient(s) and may contain confidential and
privileged information.  Any unauthorized review, use,  disclosure or
distribution is prohibited.  If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

Re: Volume out of sync

[Zlatko Krastev/ACIT]

AUDIT VOLUME helps to localize faulty files and to mark them in the
database. Afterwards you must perform RESTORE VOLUME or RESTORE STGPOOL to
bring the file back. AUD V does not perform the restore by itself but after
audit volume-by-volume you can perform one complete restore of the whole
storage pool.

Zlatko Krastev
IT Consultant





Sam Schrage <[EMAIL PROTECTED]> on 31.07.2001 01:22:45
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Volume out of sync

I have a volume that is out of sync.  I did a AUDIT VOLUME XX, and it
listed
all the errors.  The AUDIT ran successfully and did not list any damaged
files
but said that the were objects that need updating.  A typical error in the
ACTLOG was:

 07/30/01 09:36:14 ANR2337W Need to reset header size for object
4739469,
   verb type (93), from (0) to (248).
 07/30/01 09:36:15 ANR4131W Audit Volume found incorrect object
information
   for volume L00039: Node RSERVER01, Type SpaceMg,
File
   space /600_archive, File name
/TAC98/tac980062.tar.Z.
 07/30/01 09:36:15 ANR2337W Need to reset header size for object
4739470,
   verb type (93), from (0) to (248).

What should I try.AUDIT VOLUME L00039 FIX=YES,   or  RESTORE VOLUME
L00039  ?  ( I previewed the restore and have a list of tape that I'll need
from
the offsite vault.)  Will the AUDIT VOLUME pull infomation from the
database and
backup tape pools or will it still require copypool tapes?

Open to suggestions

Sam Schrage
TRW Systems
615-360-4716
[EMAIL PROTECTED]

Re: !!Backupsets and Raw Volumes!!

[Zlatko Krastev/ACIT]

The idea behind backupset is to have all files for quick restore after a
disaster - some are calling it "bare metal" restore.
After you finish restore of files (including *SM client) you can easily
continue with raw device restore to completely restore the whole data.
*SM server is unaware of data in your raw devices so it cannot recreate
them without additional knowledge (of physical allocation for example) and
cannot restore their contents together with file restore.

Zlatko Krastev
IT Consultant






Scott Thompson <[EMAIL PROTECTED]> on 31.07.2001 16:05:19
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:!!Backupsets and Raw Volumes!!

Hi,

question for you about backupsets

I am running a backupset every month on a system that backs up both normal
filesystems and raw partitions (using the dsmc backup image command).

Problem is that when i do:

tsm> q backupsetcontents nodename backupsetname

I can see a list of all my files but no mention of the raw partitions.
is this correct...

any ideas how I would go about checking that the raw partitions are
actually contained in the backupset and how to restore them???

Cheers
Scott Thompson



http://www.phoenixitgroup.com
**Internet Email Confidentiality Footer***

Phoenix IT Group Limited is registered in England and Wales under company
number 3476115.  Registered Office: Technology House, Hunsbury Hill Avenue,
Northampton, NN4 8QS

Opinions, conclusions and other information in this message that do not
relate to the official business of our firm shall be understood as neither
given nor endorsed by it.

No contracts may be concluded on behalf of our firm by means of email
communications.

Confidentiality: Confidential information may be contained in this message.
If you are not the recipient indicated (or responsible for delivery of the
message to such person), you may not take any action based on it, nor
should
you copy or show this to anyone; please reply to this email and highlight
the error to the sender, then delete the message from your system.

Monitoring of Messages: Please note that we reserve the right to monitor
and
intercept emails sent and received on our network.
Warning:  Internet email is not 100% secure. We ask you to understand and
observe this lack of security when emailing us. We do not accept
responsibility for changes made to this message after it was sent

Viruses: Although we have taken steps to ensure that this email and any
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus
free.

Re: Is TSM Ver. 4.2 a upgrade or maintenance release.

[Zlatko Krastev/ACIT]

Andy,

if a customer does have maintenance contract - first year after purchase
(of v4.1 in our case) or additionally paid for next years is he eligible to
receive last version (here 4.2) without additional fees?

Zlatko Krastev
IT Consultant






Andrew Raibeck <[EMAIL PROTECTED]> on 31.07.2001 22:33:30
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Is TSM Ver. 4.2 a upgrade or maintenance release.

TSM version numbers are composed of four period-delimited numbers. The
numbers, read from left to right, represent (in order):

- Version
- Release
- PTF
- Patch (fixtest) level

Thus version 4.1.2.19 can be read as, "Version 4, Release 1, PTF 2, patch
level 19".

Whenever the server version or release numbers change, we're talking about
a chargeable upgrade. Whenever the PTF or patch level changes, we're
talking about non-chargeable maintenance.

Most of the standard backup-archive clients are not chargeable, even for a
version or release upgrade (i.e. you can download, install, and use the
4.2 Windows client, even if you are still using the 4.1 server).

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
"The command line is your friend"





Doug Thorneycroft <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/31/2001 11:54
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Is TSM Ver. 4.2 a upgrade or maintenance release.



We are getting ready to upgrade our Window TSM server from
Ver 3.7.
When we purchased 3.7, we got the automatic upgrade to 4.1

Does anyone know if we can upgrade to 4.1, then apply the maintenance
release for Ver 4.2, or is 4.2 a new release requiring an upgrade fee?

Doug Thorneycroft
County Sanitation Districts of Los Angeles County
(562) 699-7411 Ext. 1058
FAX (562) 699-6756
[EMAIL PROTECTED]

Re: TSM quick questions

[Zlatko Krastev/ACIT]

1. Same data twice - I am not sure but as far as I know - NO! After first
backup you can make second copies (in copy pool, backup sets) but not at
the same time.
2. Under Notes/Domino - YES! In Notes/Domino each user's mail box is a
separate database which can be restored individually. If you use Notes
shared mail feature the answer will be NO - you can restore user's mail box
but if particular message was purged from shared mail database by Object
Collect task it was gone. You are restoring only a stub.
3. TSM itself is not capable to backup database logs and file groups. This
is done by Tivoli Data Protection products. So both are needed.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TSM quick questions

Quick ones:
- Is TSM able to backup the same data into more than one drive at the same
time (cloning)?
- Is TSM able to perform individual (per user) restore of mail boxes under
Notes or Exchange?
- Is TSM able to backup database transation LOGs and file groups?

Thanks in advance!

Regards,

Mauricio

Re: FC Device Driver on AIX

[Zlatko Krastev/ACIT]

As you read tivoli.tsm.devices.rte and tivoli.tsm.devices.fcprte are
mutualy exclusive filesets.
The reason is that the latter DOES CONTAIN all the files from the first
one. Thus you get both FC and SCSI attachments. All singing, all dancing.
BUT BE CAREFULL for the order:
1. install tivoli.tsm.devices.fcprte,
2. remove tivoli.tsm.devices.rte,
3. force install again tivoli.tsm.devices.fcprte to get back removed files.
If you try to remove first tivoli.tsm.devices.rte fileset you get deleted
all your devices and will have to re-create them. Not a disaster but more
work :-)
This raises the question:
Why Tivoli packaged the FCP support with SCSI support instead of making
tivoli.tsm.devices.fcp (FCP only fileset) dependant on
tivoli.tsm.devices.rte?
Maybe to be coherent with other platforms. But for them we do not have the
need to do the three step process (do we?).

Zlatko Krastev
IT Consultant






"Joshua S. Bassi" <[EMAIL PROTECTED]> on 02.08.2001 22:14:44
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:FC Device Driver on AIX

All,

I know the AIX TSM SCSI and Fibre Channel device drivers
cannot coexist on the same server.  Here is my question,
if I have both 3590 SCSI attached (which I don't believe
uses the TSM SCSI driver), STK DLT SCSI based drives
(which does use the SCSI driver) and I am now installing
3590 drives on a Fibre Channel SAN (which requires the
FC driver) how does this all work?

If I uninstall the SCSI driver and install the FC driver
will my DLT drives still be usable?  If not should I use
the TSM SCSI driver only?


--
Joshua S. Bassi
Independent Consultant
IBM Certified - AIX/HACMP, SAN, Shark
Tivoli Certified Consultant- ADSM/TSM
Cell (408)&(831) 332-4006
[EMAIL PROTECTED]

Re: Enterprise Solution.

[Zlatko Krastev/ACIT]

Yury,

These tasks can be done with other Tivoli products.
TSM v3.7 and beyond is successor of former IBM ADSM (v3.1 and below) 
product and this list is for both. The products cover backup and archiving 
of data.
The tasks you want to perform can be done with Tivoli Inventory and Tivoli 
Software Distribution products.
If you wish we can discuss them outside this particular list or look at 
Tivoli web site. Of course you can simply contact closest IBM/Tivoli sales 
people.

Zlatko Krastev
IT Consultant






Yury Us <[EMAIL PROTECTED]> on 02.08.2001 15:19:03
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Re: Enterprise Solution.

Do I need to install some additional software for that? 
Is there some books that explain how to set up everything?
The only information I was able to get is how to set up inter-server
communication, and that works ok.

-Original Message-
From: Angela Hughes [mailto:[EMAIL PROTECTED]]
Sent: 13 ÉÀÌÑ 2001 Ç. 21:51
To: [EMAIL PROTECTED]
Subject: Re: Enterprise Solution.


Yury US,
Yes, I've done it for IBM internally and externally
and it can be done w/TSM.
Thanks,
Angela
--- Yury Us <[EMAIL PROTECTED]> wrote:
> Hi everybody,
> Currently we use ADSM for back up only, but there
> are some other components,
> so I am trying to get information about those
> components too and need a good
> advice.
>
> SUTUATION: We have few overseas locations in
> different countries, where
> development is taking place.
>
> So this is a very important task monitoring the
> software installed on all
> PC, servicepacks installed on every single PC, to
> make the possible
> transition from overseas computers here in
> headquarters.
>
> Another important task is deployment and
> installation the software to the
> clients. Sometimes it is a hundred PC on client
> site.
>
> Third task is to produce the servisepacks and deploy
> them to client.
>
> Next very important task is keeping track about what
> the client has.
>
> QUESTION: Does anybody has experience with Tivoli
> that covers the listed
> above issues?
> Documentation claims that all that software exists
> already. If there are
> people who think that using that software is a smart
> choice I would
> appreciate the answer.
>
> Yuriy Us.


 
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: Thoughts on really old clients and newer servers...

[Zlatko Krastev/ACIT]

You have at least three options:
1. Brute force attack - make a statement or even block those nodes from
using the server.
2. Install Tivoli Software Distribution product and perform clients upgrade
by yourself (will it be easier? :-)
3. have a beer and leave as it is.

Zlatko Krastev
IT Consultant





"Cook, Dwight E" <[EMAIL PROTECTED]> on 01.08.2001 17:49:28
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Thoughts on really old clients and newer servers...

My problem is the vast number of support groups across client machines...
getting them to do things :-/

Yes, I know looking at the support matrix we currently see things such as a
TSM 4.1 server works with TSM 3.7, 4.1, & 4.2 clients.

I'm thinking about the making a statement that I can NOT allow old clients
that aren't in the current support matrix to back up to my TSM Servers.

mainly to force folks into putting upgraded clients on their boxes but also
to keep those old clients from (in some unseen way) smoke'n my servers.

Thoughts ?

Any Tivoli folks want to touch this ?

Dwight

Re: Backup Strategy

[Zlatko Krastev/ACIT]

Jon,

you are doing things well. But you did not pointed how much is your backup
data to see is this a problem or not. But to fill several libraries in 4
1/2 hours is good job and I think there is no any problems.
Normally the backup of clients to primary pools (!) must finish within the
backup window (usually during the night). Rest of the time is available for
migration, backup of primary pools to copy pools, etc. There is nothing to
be concerned, just a matter of proper scripts.
If the speed is still unsatisfactory you can install additional drive(s) in
the library(ies).
Also companies grow so grows their data and this also is normal. You can
add more slots is the libraries are upgradeable and there is room to
upgrade. Or additional library can be bought (together with drives it will
give you also the speed). Or even throw all existing ones away and buy huge
new one :-)
All this is not your problem - it's a problem for your purchasing
department.

Zlatko Krastev
IT Consultant






"Martin, Jon R." <[EMAIL PROTECTED]> on 01.08.2001 18:15:58
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Backup Strategy

Hello,

Currently our backup strategy for the TSM Servers is as follows on
a
daily basis.

1. Backup 'diskpool' to 'copypool'
2. Backup 'tapepool' to 'copypool'
3. Full back up of DB

From what I understand this is the most bullet proof method.
However we are at edge of our tape libraries capacity and the 3 steps above
are taking about 4 1/2 hours to complete each day.

Is anyone using a strategy that would reduce both the amount of
time
and possibly the number of volumes needed for these administrative tasks.

Thanks,

Jon Martin

Re: *** TSM CHANGES DOMINO SERVER DATE FORMAT ***

[Zlatko Krastev/ACIT]

Have you tried to invoke the command with "-date 2" or set dateformat
option in dsm.opt??

Zlatko Krastev
IT Consultant






Luciano Ariceto <[EMAIL PROTECTED]> on 02.08.2001 22:49:48
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:*** TSM CHANGES DOMINO SERVER DATE FORMAT ***

Hi All !!!

I need a little help to solve a problem as follow :

Daily when the  backup process is started using the AGENTLN (*) for  LOTUS
NOTES
the  DOMINO server date format is changed from dd/mm/ (my regional
settings) to mm/dd/.
To solve this after  the backup finished we need to shutdown the DOMINO
server and restart it.

(*) %LN_DIR%\dsmnotes incr e:\notes\data - subdir=yes

P.S. If I type the command above the date format keeps unchanged. (I
suppose the scheduler changes this)

the server configurations are :
NT 4 sp6a
Domino/Notes 4.5.5
TSM Version 4, Release 1, Level

Any ideas ??

Thanks a lot !

Re: 3rd copy of dbvol on other Volumegroup

[Zlatko Krastev/ACIT]

Are you made your existing copies using LVM, i.e. each TSM DB volume is on
LVM logical volume with two copies?
If you make DB volume mirrors using TSM then there is no problem to go
beyond VG boundaries.
If you imagine the raw device(s) (of the LVM lv) are partitions, DBVOL is a
logical partition and the DB is a logical volume the things become very
similar (maybe even parts of the code are reused :) :

LVM physical partition  ->  basic storage element
Raw device (for dbvol)  /

LVM LV's logical partition  ->  may have up to three copies
DB volume (for TSM DB)  /   for redundancy

LVM logical volume (data)   ->  requested data content
Database (all volumes)  /

Each TSM DB volume can have up to three copies. But is is YOUR
responsibility to ensure that each DB volume has mirrors. LVM creates PP
copies altogether. TSM DB volumes are mirrored one by one. And you can
create for example two copies for one volume and three copies for another
volume. Or even have one mirrored but the next not (who is so silly to do
such things is a different question ;-)
I've just tested and successfully created two lv's - one is rootvg and
another in newly created tsmvg and made a mirrored TSM DB volume using
them.


Zlatko Krastev
IT Consultant






Pothula S Paparao <[EMAIL PROTECTED]> on 03.08.2001 12:42:09
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:3rd copy of dbvol on other Volumegroup

Hi all,
Im having 2 dbvolume copies on same VG called tsmvg. Im intrsted in keeping
the third copy of the DBvol in rootvg instead in TSMvg . My view in this is
to recover latest dbvolume from rootvg incase of  TSMvg corruption.
Can i keep 3rd copy on rootvg. if so, please let me know the steps involed.

Help in this regard is highly appriciated.
THanks and regards
sreekumar.

Re: allocating disk volumes on RAID5 array

[Zlatko Krastev/ACIT]

> ... I rather NOT use RAID-5 for TSM disk pool volumes... Why pay the penalty
for calc & writing parity when you don't expect to read it more than
once?!? This data is so transient (in general, it exists for less than 48
hours)
it's not worth sacrificing ANY performance -- we really want to get the
backups AND migration done as quickly as possible, right?  These days, I
recommend RAID-0, striping without parity, if any at all; ...

Don,
on this list several people have had problems when something happened
before they completed daily BACKUP STGPOOL. If you define volumes over
RAID 0 array and only one disk fails you will lose many hundred GBs of
client backups. For some sites this might not be important and backups can
be restarted or wait for the next day's backup. But for others it can be
not possible. It is all about SLA you have.
And lets just imagine a situation - quaterly results are archived with
-deletefiles option and you RAID-0 drops a disk before primary pool backup

This is an imaginary situation but you can find more realistic one.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: allocating disk volumes on RAID5 array

Wanda has identified the critical choices;  there is no single, right
answer
because the performance factors intersect at different points for nearly
every situation -- if only because most sites are at different points
along
the evolutionary development of IT infrastructure, different sized disks
for
RAID, different RAID technologies (ESS vs. EMC vs. native/local drives,
etc.), and different performance ranges for a given TSM server box.

And it does matter how you decide to carve up your disk pool resources.
Just
as different tape capacities & technology will influence your choices for
how tape pools are configured, variety in the type and capacity AND number
of channels accessing a set of disks will dictate the kind of performance
you can achieve.  So, if you think your TSM server system can handle 25
(50
in today's terms) sessions concurrently, then you measure the disk I/O
performance choices against that level of concurrency.  Most folks (these
days) disregard the effect of distributing many logical (TSM) volumes over
some number of physical volumes;  increasing the number of logical volumes
per physical gets that many concurrent writes queued to the device.  The
more of each, the more sessions can be sustained without waiting for
"mount-point".

I rather NOT use RAID-5 for TSM disk pool volumes... Why pay the penalty
for
calc & writing parity when you don't expect to read it more than once?!?
This data is so transient (in general, it exists for less than 48 hours)
it's not worth sacrificing ANY performance -- we really want to get the
backups AND migration done as quickly as possible, right?  These days, I
recommend RAID-0, striping without parity, if any at all;  on most
moderate
sized Unix machines, no striping at all, and as many smaller drives as can
be handled -- these days that translates to 36 or 72 GB drives, fill the
drive bays, get as much SCSI separation as possible... do the math on
dividing each physical drive into some 7-10 logical drives.  For RAID
anything, Gianluca's 7 or 8 physical drives per RAID config is a good
high-end count.


Don France
Technical Architect -- Tivoli Certified Consultant
San Jose, Ca
(408) 257-3037
mailto:[EMAIL PROTECTED]

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gerald Wichmann
Sent: Tuesday, May 28, 2002 3:30 PM
To: [EMAIL PROTECTED]
Subject: Re: allocating disk volumes on RAID5 array


That's more along the lines of what kind of info I'm digging for - but
doesn't quite address how one goes about coming up with a number or size.
There may not be a "right" or "single" answer however you must admit there
is a generalized "right" answer. Consider for example that while RAID-5
arrays can vary in the # of disks assigned and size of them, there is a
generalized rule of thumb as Cordiali pointed out. Too few or too many
disks
in your RAID-5 array and you can have performance implications. There's a
sort of sweet spot for creating RAID-5 arrays and keeping that in mind
there
should also be a similar sweet spot in how many volumes one might want to
assign. All in all though I still wonder if it really matters a whole
lot..
Whether you have 1 write going on or 10, you're still striping across the
array and I question whether you'd really see much difference one way or
another. Might be an interesting thing to try various variants of..

Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)

-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 2:38 PM
To

Re: opinion on AIT vs LTO and 3570 tape technology?

[Zlatko Krastev/ACIT]

--> ... in these days where disk space is not much more expensive than tape space.

I would disagree on part. LTO is sligthly better than disks when measured
in TB/sq.m. but does not require those many kVAs disks need. Disks require
about 30W/drive + some extra for controllers, etc. Also this electricity
transforms into heat. So you need initial investment for big UPSes and
conditioners and they also have to be counted for floorspace. EMC
Symmetrix or IBM ESS require 20-30kVA UPS and also corresponding
batteries.
Thus again - it depends.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: opinion on AIT vs LTO and 3570 tape technology?

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Lisa Cabanas
> I had briefly thought about HSM, but the enormous number of files and
> directories makes it sound like a really bad idea to me.  Any thoughts?

The HSM issue is not a matter of the number of files and directories, but
rather an issue of frequency of access. If the files are generated and
then
rarely accessed, HSM would make sense, given if the following is true:

1. The customer is *really* tight on disk space, and
2. The files are infrequently accessed, but need to be immediately
available.

HSM is a more complex issue if you're dealing with Windows client boxes.
You'll have to look at a solution like OTG DiskXtender for non-UNIX
clients.

HSM actually doesn't make a lot of sense, in these days where disk space
is
not much more expensive than tape space.

--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
Certified AIX system engineer
MSCE

Re: Moving data to a new storage pool, but still having volumes in old copy pool ...

[Zlatko Krastev/ACIT]

Arnaud,

Yes, you have doubled your copypool copies. And yes, you know the answer -
you can delete safely volumes from "old" copy pool if it was used to
backup ONLY primaryA pool. WARNING: if you have backed up more than one
primary pool chain (!) to same copy pool and only one chain is backed to
another copy pool you *cannot* safely delete volumes from copyA unless all
pool chains have backups to other copy pools!
What you have done is equivalent to "backup stg stgpoolA copypoolB". You
forgot that TSM does NOT treat backups, images, volumes, etc. It works
with (business) objects - be it file from BA, HSM client or whatever
application uses through API client.
An example - many of us use backup of the disk pool to copypool, migration
to tape and backup of primary tape pool. If it worked as you expected from
your pools it would do: backup from disk to copy pool, migration which
should delete just created backups from the copypool and re-creation of
backups but this time from tape pool to same copy pool ?!? Not so good
from both our point of view and ADSM/TSM developers'.
Bottom line: "backup stg primaryA copyB" means "create copy in pool copyB
for all objects found in pool primaryA which do not have copies in copyB
or their copies are older", i.e. incremental. Same if you backup a server
with two TSM client instances under different node names and expecting
expiration of file under one instance to initiate expiration under second
node name without full incremental performed in second instance.
TSM is very consistent in its ideology.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Moving data to a new storage pool, but still having volumes in 
old
copy pool ...

Hi *SM'ers !

Could someone give me an explanation on following topic : I had a storage
pool called stgpoolA, wich had copy made daily on a copy storage pool
called CopypoolA. For technical reasons I moved all data from stgpoolA to
a new primary stgpool called stgpoolB, wich is having daily copies on copy
storage pool CopypoolB.
I expected my copystgpool CopypoolA to be empty after having been moving
all original data to stgpoolB, due to the fact that this stgpool has a
daily copy to a CopypoolB, therefore making old copy storage pool data
obsolete. Problem is that several days after having completely transfering
primary pool data to my new stgpool, I still have volumes belonging the
old  copy storage pool. How is it possible ? Do I have doubled data in my
2 copy storage pools ? May I safely delete volumes belonging old copy
storage pool ?
Any help or explanation greatly appreciated ;-)
Thanks in advance.

Arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Backup retention period

[Zlatko Krastev/ACIT]

Ruksana,

there is no simple answer, it depends.
If you make two backups to a primary pool and just send one set of tapes
off-site it would expire.If you backup primary pool to copypool it is
same.
One method to retain "forever" first backup and expire next one (with
consequent ones) is to use two node names (with different policies) for
same box. The other method is to use archive instead of backup. Thus on
27-th you create archive with RETVer=NOLimit or very long retension and on
29-th you have regular incremental backup with retextra=92.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Backup retention period

Hi Zaltko,

Sorry to bother you again. I understood the concept of VEREXIST AND
RETEXTRA.

We have done a offlinebackup on 27th may and a online backup on 29th.For
me
the offline backup is the most imp one if I had to restore.

if I do the verexist=unlimit and retextra=92 will the inactive backups ie
the offline and the online which I have done ( I have done no backup since
thelast offline and online ) will stay there for the period mentioned.

is there anyway to let TSM know to hold the offline backup forever till I
ask it to delete so ..?

I appreciate any help from you.

With regards,



-Original Message-
From: Zlatko Krastev [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 28 May 2002 9:48
To: [EMAIL PROTECTED]
Subject: Re: Backup retention period


Ruksana,

the method TSM usilizes is "keep several copies, check to limits, if any
limit is reached delete oldest copy"
So if you have set 31 versions and perform backups weekly last version
would be 31 weeks old. But if you set at the same time versions to stay
for 31 days you will have no more than 5 (sixth would be more than 31 days
and would be "expired").
Most recent copy ("active" one) would stay forever until you delete the
file. At that time next pair of limits (VERDELETED and RETONLY) would take
care of the copies.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Backup retention period

Hi Zlatko,

Thanks for your quick response.
According to my TSM the copygroup setting has nolimit for this management
class but the utl file has MAX versions 31.
>From what you said ( my understanding is )  below if I don't do the backup
of this database it should stay forever as it has nolimit -but if I do
perform backup it will stay for next 31 days. Correct me if I'm wrong.

The link you sent me was very useful I will start reading it.

With regards,
Ruksana Siddiqui



-Original Message-
From: Zlatko Krastev [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 7:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Backup retention period


The backup would stay there undefinitely if the content does not change.
If it changes and a new backup is performed the copy you've just becomes
obsolete and according to copygroup settings will expire some day. To
ensure it would not be before three months have passed set
VEREXIST=NOLimit and RETExtra=92.
To become familiar with TSM (which is more evolved than competitive
products) I highly recommend you to have a look at nice redbook "Tivoli
Storage Management Concepts" - SG24-4877-02
(http://www.redbooks.ibm.com/). This would save you many headaches.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Backup retention period

Hi,

I just started working with TSM but can someone tell me how can I find the
retention period of the backup I have done.

I have done a particular backup and wanted to have it for atleast 3 months
-
is there anyway I tell TSM to hold it for 3 months or can I actually check
how long TSM was configured to hold the data.

Any help is highly appreciated.

With regards,
Ruksana Siddiqui



CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify AMCOR
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of AMCOR.

CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please noti

Re: LTO don't need clean up?

[Zlatko Krastev/ACIT]

If you read carefully library maintenance manual you would find that
library requires a cartridge with specific label (starting with CLNI, i.e.
CLNI39 is the one I've used last week) and performs cleaning
automatically. So set CLEANFREQ=NONE as Mark pointed. Those of you WITH
3584 may have overlooked that base frame is with 141-281 slots according
to IBM Announcement but capacity is 14-28TB, not 14.1-28.1. This is again
due to one slot occupied by cleaning cartridge for library automatic
cleaning.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:LTO don't need clean up?

Hi all,

one of LTO 3583 (2 drives) we take care of still didn't clean drives. It
is
operate from january 2002 and there is about 10-20 GB daily data flow
through each drive, 3-5 daily tape-mounts. Both drives are set to ASNEEDED
cleaning frequency, but no clean occured from january (!!), no dirty drive
signalized on display ... is it possible? LTO box is placed in climatized
dust-free environment, but .??? Has anyone some similar experience
with
LTO clean frequency?

Tom

Re: True statement???

[Zlatko Krastev/ACIT]

definitely NO (if you are not talking about NT v0.357 :)
You can have more interfaces limited by number of slots and maximum number
of particular adapter combinations supported by the HW
platform/drivers/OS.
TSM does not deal with SCSI direct but through OS and drivers. NT 4 does
not limit to only two buses (actually it treates IDE also as SCSI so in
desktop PC with SCSI adapter you already can have 3 interfaces).

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:True statement???

Is this a true statement?

"You can have multiple Tivoli SM servers but only two SCSI interfaces per
TSM NT server."


Kevin Fletcher

Re: server-to-server copy-pools

[Zlatko Krastev/ACIT]

Other server is related not to copy pool but to the device class. You have
only to define second pool over same devclass.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:server-to-server copy-pools

Hi all,

today we have two servers connected via server-to-server. Both server have
defined their copy-pool on the other server.
I would like to split the copy-pool into two different ones. Reason is to
run stg-pool-backups in more than one session parallel..
Does anybody know, if this is possible and how I can set up two different
copypools on a server, that are accessed via server-to-server connection
from one other server.

Thanks for any help

Christoph

Re: AW: server-to-server copy-pools

[Zlatko Krastev/ACIT]

Not exactly. Keep in mind that for target server the source one is just a 
node of type server. So it depends on domain settings source server node 
resides in to which primary pool virtual volumes go. And how many mount 
points you have there.
Also you may want more than one mount points in copy pools so generic 
formula for mount limit will not be count of copy pools but sum of desired 
mount points in pools. Look what Karel wrote.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:AW: server-to-server copy-pools

Thanks,

an additional question before setting up the configuration :
second copy-pool with same device-class means that the data physically go 
to
the same tape-pool on the other server, because it works with the default
management-class for that server ( where the pool name is defined). Is 
this
correct ? 
So the only additional config to make (beneath defining the second
copy-pool) is increasing the 'mount limit' in device-class 'server' on the
one side where copy-pool is defined to the number of copy-pools I define ?

Thanks
Christoph



> -----Ursprüngliche Nachricht-
> Von:  Zlatko Krastev/ACIT [SMTP:[EMAIL PROTECTED]]
> Gesendet am:  Mittwoch, 5. Juni 2002 07:47
> An:   [EMAIL PROTECTED]
> Betreff:  Re: server-to-server copy-pools
> 
> Other server is related not to copy pool but to the device class. You 
have
> only to define second pool over same devclass.
> 
> Zlatko Krastev
> IT Consultant
> 
> 
> 
> 
> Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> cc:
> 
> Subject:server-to-server copy-pools
> 
> Hi all,
> 
> today we have two servers connected via server-to-server. Both server 
have
> defined their copy-pool on the other server.
> I would like to split the copy-pool into two different ones. Reason is 
to
> run stg-pool-backups in more than one session parallel..
> Does anybody know, if this is possible and how I can set up two 
different
> copypools on a server, that are accessed via server-to-server connection
> from one other server.
> 
> Thanks for any help
> 
> Christoph

Re: tsm ftp server

[Zlatko Krastev/ACIT]

Burak,

the reason is that patches are released to fix specific problems (that's
why they are *patches*) and do not go through full testing procedure.
Whereas maintenance and rarely *some* patches get more testing and become
recommended and pointed by web site.
Think as ftp site holding all versions but web site pointing the last
*recommended* one.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:tsm ftp server

Hi Everybody,
Why is the following web site is always behind ftp servers? Does anybody
can
answer it?
All development stuff in IBM does good job and releases maintenances and
patches but
the web stuff does not need to update the htmls immediately. I am bored to
surf
inside the
ftp archive to find whether there is a new release or patch etc.
Regards,
Burak



http://www.tivoli.com/support/storage_mgr/adsercli.htm

Re: IBM 3584 L32 LTO configuration question

[Zlatko Krastev/ACIT]

Kevin,

you provoked many answers to wrong thread. So get an answer on this one as
well.
Facts about 3584:
- you can have HVD, LVD or FC drives or mix of them;
- you can have from 1 to 72 drives;
- you can use one or dual channel SCSI, integrated or on slot;
- you can connect drives one per bus, two or even more if not pay
attention to recommendations;
- you can access SCSI drives through SAN gateway (FC-SCSI);
- you can have direct attached FC drives (or SAN gates), connect through
hub or fabric;
- etc., etc. ...
Zillions of options and all are up to you. All (or nearly all) are working
and can serve you. Choose one which you think should fit to your needs and
then ask is it good. But there is no simple/short answer to your generic
question. And if you search list archives you can see many people's
configurations.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:IBM 3584 L32 LTO configuration question

I have an IBM 3584 L32 LTO library.  It has 4 drives.

I have it connected to an HP LH3 server running NT 4.0 and TSM 4.2.

I have 1 Symbios SYM22910 SCSI controller card with 2 channels connected
to
this library.  One channel is interfacing with two of the drives + the
library and the other channel is interfacing with the other two drives.

I'm interested in hearing what other IBM 3584 L32 LTO library users have
done to configure this library to their NT TSM servers.  I've been told
that
I can and cannot connect this LTO library in many other ways and I'm
interested in what others have *successfully* done.

Thanks in advance for all responses!

Kevin Fletcher
SSCI

Learn from the mistakes of others. You can't live long enough to make them
all yourself.

Re: Deleting a portion of a filespace

[Zlatko Krastev/ACIT]

Luke,

you can define virtual filespaces using VIRTUALMOUNTPOINT option. They
would become separate filespaces on TSM server's DB and you can use DELete
FIlespace command later.
The other possible approach is to re-bind *all* files from than directory
*before* deletetion to a class with verdeleted=0.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Deleting a portion of a filespace

Hi All,
Client version: 4.2.1.0
Client OS: Solaris 5.6
Server OS: Solaris 8
TSM Server Version: 4.2.1.15

We have a NFS mounted NetApp filer that retains their critical data.
The data is is library with a number of different subdirectories for
each project.  They require we keep all data forever until they specify
it may be deleted.  They've asked us to set up verexists  and
verdeleted .  Being TSM views the mount "/data" as one filespace,
I'm wondering if we can purge a portion of that filespace when they
approve it.  For example a subdirectory may be /data/mars02lib/...
After the project has been terminated they would like us to delete the
mars02lib but still retain all of the other libraries under /data.  Any
suggestions/advice would be highly appreciated.  Thanks!

Luke Dahl
NASA-Jet Propulsion Laboratory
818-354-7117

Re: TSM 4.2 possible IP problem

[Zlatko Krastev/ACIT]

octet 255 is broadcast only if network is class C, i.e. 192.0.0.0 -
223.255.255.255. Other case is when subnet mask is 24 bits - 255.255.255.0
But if he has subnet 10.0.10.0/22 for example (adresses 10.0.10.0 -
10.0.13.255) this is ordinary host address and this IS a bug.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: TSM 4.2 possible IP problem

Sean

the octet 255 is broadcast address, not to be used.   Two machine address
octets never to use are 0 and 255.
0 is ok for network octets but don't use 255.


Allan



"McNeill, Sean"
   cc:
Sent by: "ADSM:  Subject: TSM 4.2 possible
IP problem
Dist Stor Manager"
<[EMAIL PROTECTED]
EDU>


06/06/2002 07:27
AM
Please respond to
"ADSM: Dist Stor
Manager"






Does anyone know if the TSM server would have a problem with a client
attempting to connect via an IP address with the last octet being 255?  I
have a server that will not talk to the TSM server, it has been rebuilt
several times, I have tried several different client versions and still no
luck.  The only constant thru all of this is its IP address 10.0.11.255.

Any help would be appreciated





Sean McNeill

Windows Administrator

J.D. Edwards & Company

One Technology Way

Denver, CO 80237

303-334-5543 phone

720-635-0458 Cell

[EMAIL PROTECTED] 

Re: Can't do reclamation

[Zlatko Krastev/ACIT]

How many drives do you have in the library? Can you provide additional
info - output from Q LIBR, from Q DRI F=D and from Q DEV 3590CLASS2.
You do not have reclamation pool and if the number of drives is not enough
reclamation would not start.
Was it ever working?

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Can't do reclamation

Hi all,

Thanks for all reply. Here is the details of the storage pool that can't
perform
reclamatoin.

Volume Name   Storage  Device  EstimatedPct Volume
  Pool NameClass Name   Capacity   Util Status
(MB)
--- --
-  -  
FP0018FILE_PTPOOL  3590CLASS2   21,271.10.1 Full
FP0024FILE_PTPOOL  3590CLASS2   21,177.20.0 Full
FP0025FILE_PTPOOL  3590CLASS2   22,015.40.0 Full
FP0026FILE_PTPOOL  3590CLASS2   21,700.40.0 Full
FP0027FILE_PTPOOL  3590CLASS2   21,324.94.3 Full
FP0028FILE_PTPOOL  3590CLASS2   21,091.50.0 Full
FP0029FILE_PTPOOL  3590CLASS2   21,160.00.0 Full
FP0030FILE_PTPOOL  3590CLASS2   21,141.00.0 Full
FP0031FILE_PTPOOL  3590CLASS2   21,185.00.0 Full

The followin is the result of "q stgp file_ptpool f=d"

 Storage Pool Name: FILE_PTPOOL
   Storage Pool Type: Primary
   Device Class Name: 3590CLASS2
 Estimated Capacity (MB): 2,051,004,907,651.1
Pct Util: 0.0
Pct Migr: 0.0
 Pct Logical: 100.0
High Mig Pct: 99
 Low Mig Pct: 99
 Migration Delay: 0
  Migration Continue: Yes
 Migration Processes:
   Next Storage Pool:
Reclaim Storage Pool:
  Maximum Size Threshold: No Limit
  Access: Read/Write
 Description:
   Overflow Location:
   Cache Migrated Files?:
  Collocate?: No
   Reclamation Threshold: 80
 Maximum Scratch Volumes Allowed: 99,999,999
   Delay Period for Volume Reuse: 0 Day(s)
  Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
 Volume Being Migrated/Reclaimed:
  Last Update by (administrator): ADMIN
   Last Update Date/Time: 04/29/02 11:44:41


l've already tried to update thereclamation thershold to 50% but it still
no
reclaim process can be query.

Max







Gerald Wichmann <[EMAIL PROTECTED]> on 06/06/2002 12:37:17 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Max LH KWONG/LCSD/HKSARG)

Subject:  Re: Can't do reclamation



You'll need to provide more information then that.. be a lot more
specific.
Specifically why can't you perform reclamation? Did you configure a
reclamation pool? Is it a problem in the configuration of the reclamation
pool? I recommend posting some details/output about the storage pool
you're
trying to reclaim (q stg f=d) and the reclamation pool you have setup to
do
the reclamation. Also post output on any errors you're getting as to why
you
can't do it. The more info you provide the more likely someone can help
you.

Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)

-Original Message-
From: Max Kwong [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 04, 2002 9:47 PM
To: [EMAIL PROTECTED]
Subject: Can't do reclamation

Hi all,

l have a storage pool can't peform the reclamation. It just only can use
the
"move data" command to manually reclaim the tape. How can l solve this
problem?

Max

Re: Processing Time for incremental backup

[Zlatko Krastev/ACIT]

Look at the output of Q DB F=D. Is you cache hit ratio below 95%? What is
the type/speed of disks you use for DB volumes, Q DBV may sched some
light.
Check also the connection to those nodes - 10/100, Full/Half duplex
settings. Avoid auto-detect settings on both Ethernet adapters and switch.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Processing Time for incremental backup

Hi all,

I've a schedule incemental backup processing time is much more than the
others.
The followings is the details of the schedule result.

Normal Schedule Processing Time: 3 minutes

05/25/2002 04:56:57 --- SCHEDULEREC STATUS BEGIN
05/25/2002 04:56:57 Total number of objects inspected:  440,573
05/25/2002 04:56:57 Total number of objects backed up:0
05/25/2002 04:56:57 Total number of objects updated:  0
05/25/2002 04:56:57 Total number of objects rebound:  0
05/25/2002 04:56:57 Total number of objects deleted:  0
05/25/2002 04:56:57 Total number of objects expired:  0
05/25/2002 04:56:57 Total number of objects failed:   0
05/25/2002 04:56:57 Total number of bytes transferred:0 Bytes
05/25/2002 04:56:57 Data transfer time:0.00 sec
05/25/2002 04:56:57 Network data transfer rate:0.00 KB/sec
05/25/2002 04:56:57 Aggregate data transfer rate:  0.00 KB/sec
05/25/2002 04:56:58 Objects compressed by:0%
05/25/2002 04:56:58 Elapsed processing time:   00:03:46
05/25/2002 04:56:58 --- SCHEDULEREC STATUS END
05/25/2002 04:56:58 --- SCHEDULEREC OBJECT END MAP_INCR_BACKUP 05/25/2002
04:30:00
05/25/2002 04:56:58 Scheduled event 'MAP_INCR_BACKUP' completed
successfully.
05/25/2002 04:56:58 Sending results for scheduled event 'MAP_INCR_BACKUP'.
05/25/2002 04:56:58 Results sent to server for scheduled event
'MAP_INCR_BACKUP'.

Problem Schedule Processing Time: 5 Hrs

05/31/2002 03:11:31 ANS1898I * Processed   682,000 files *
05/31/2002 03:11:32 --- SCHEDULEREC STATUS BEGIN
05/31/2002 03:11:32 Total number of objects inspected:  682,460
05/31/2002 03:11:32 Total number of objects backed up:2
05/31/2002 03:11:32 Total number of objects updated:  0
05/31/2002 03:11:32 Total number of objects rebound:  0
05/31/2002 03:11:32 Total number of objects deleted:  0
05/31/2002 03:11:32 Total number of objects expired:  0
05/31/2002 03:11:32 Total number of objects failed:   0
05/31/2002 03:11:32 Total number of bytes transferred: 2.20 KB
05/31/2002 03:11:32 Data transfer time:0.00 sec
05/31/2002 03:11:32 Network data transfer rate:0.00 KB/sec
05/31/2002 03:11:32 Aggregate data transfer rate:  0.00 KB/sec
05/31/2002 03:11:32 Objects compressed by:   42%
05/31/2002 03:11:32 Elapsed processing time:   05:26:47
05/31/2002 03:11:32 --- SCHEDULEREC STATUS END
05/31/2002 03:11:32 --- SCHEDULEREC OBJECT END MF1_INCR_BACKUP 05/30/2002
21:25:00
05/31/2002 03:11:32 Scheduled event 'MF1_INCR_BACKUP' completed
successfully.
05/31/2002 03:11:32 Sending results for scheduled event 'MF1_INCR_BACKUP'.
05/31/2002 03:11:32 Results sent to server for scheduled event
'MF1_INCR_BACKUP'.

Two backup job using same policy domain. How can l solve this problem?

Regards,
Max

Re: Select statement (using events table)

[Zlatko Krastev/ACIT]

select schedule_name, status, result, reason -
from events -
where date(scheduled_start) <= current_date - cast(1 as interval day)

Zlatko Krastev
IT Consultant




Please respond to <[EMAIL PROTECTED]>
To: "'Zlatko Krastev/ACIT'" <[EMAIL PROTECTED]>
cc:

Subject:RE: Select statement (using events table)

Hi Zlatko,

So that's the trick...

I've trying to get the startdate set, using some example statements, but I
cannot get it done it seems. Here's what I tried:

select schedule_name,status,result,reason from events where
(scheduled_start - 1 day)

Well, that doesn't work :-( (obviously because the syntax isn't right :-)
).
Do you happen to know how that works?

Kind regards,

Rick



-Oorspronkelijk bericht-
Van: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]]
Verzonden: 6 juni 2002 14:56
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Select statement (using events table)


Rick,

the trick is that Tivoli decided for some reasons select from events to be
limited as is in Q EVENT. You need to specify WHERE clause.

Zlatko Krastev
IT Consultant




Please respond to [EMAIL PROTECTED]
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Select statement

Hi *SMers,

I've trying to figure something out using select-statements. I want to
know
what events did or didn't complete succesfully for, say, the last 24
hours.
I'm getting the results, but I only get the results since last midnight.
How
do I get the results from the last 24 hours.

This is what I have so far:

select schedule_name,scheduled_start,actual_start,result from events


Anyone here who can help?

Kind regards,

Rick Harderwijk
Systems Administrator
Factotum Media BV
Oosterengweg 44
1212 CN Hilversum
P.O. Box 335
1200 AH Hilversum
The Netherlands
Tel: +31-35-6881166
Fax: +31-35-6881199
E: [EMAIL PROTECTED]

Re: Réf. : Re: Select statement (using events table)

[Zlatko Krastev/ACIT]

Why it does not work? What error is returned and if it complains for 
syntax at which word?
To be sure it works I've tested it on TSM 3.7.0 for Win (being at customer 
site) but when I return to office I will test it on 4.1.4.1 for AIX (out 
test one) and on 4.2.1.15.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Réf. : Re: Select statement (using events table)

I can't seem to get a handle on this events table. The SQL you supplied 
isn't working on my server (4.1.3.0 on AIX). When I do a select with no 
dates in the where clause,
all I get is the admin scheds for the current day. Other than that, I 
can't get a thing. Is there something I'm missing??

Thanks

Guillaume Gilbert
CGI Canada




Zlatko Krastev/ACIT <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-07 
08:54:26

Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Envoyé par :   "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


Pour :[EMAIL PROTECTED]
cc :
Objet :   Re: Select statement (using events table)

select schedule_name, status, result, reason -
from events -
where date(scheduled_start) <= current_date - cast(1 as interval day)

Zlatko Krastev
IT Consultant




Please respond to <[EMAIL PROTECTED]>
To: "'Zlatko Krastev/ACIT'" <[EMAIL PROTECTED]>
cc:

Subject:RE: Select statement (using events table)

Hi Zlatko,

So that's the trick...

I've trying to get the startdate set, using some example statements, but I
cannot get it done it seems. Here's what I tried:

select schedule_name,status,result,reason from events where
(scheduled_start - 1 day)

Well, that doesn't work :-( (obviously because the syntax isn't right :-)
).
Do you happen to know how that works?

Kind regards,

Rick



-Oorspronkelijk bericht-
Van: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]]
Verzonden: 6 juni 2002 14:56
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Select statement (using events table)


Rick,

the trick is that Tivoli decided for some reasons select from events to be
limited as is in Q EVENT. You need to specify WHERE clause.

Zlatko Krastev
IT Consultant




Please respond to [EMAIL PROTECTED]
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Select statement

Hi *SMers,

I've trying to figure something out using select-statements. I want to
know
what events did or didn't complete succesfully for, say, the last 24
hours.
I'm getting the results, but I only get the results since last midnight.
How
do I get the results from the last 24 hours.

This is what I have so far:

select schedule_name,scheduled_start,actual_start,result from events


Anyone here who can help?

Kind regards,

Rick Harderwijk
Systems Administrator
Factotum Media BV
Oosterengweg 44
1212 CN Hilversum
P.O. Box 335
1200 AH Hilversum
The Netherlands
Tel: +31-35-6881166
Fax: +31-35-6881199
E: [EMAIL PROTECTED]

Re: tsm ftp server

[Zlatko Krastev/ACIT]

And because for clients for example patches sometimes come
one-after-another with rate 2/month.
If you feel comfortable to upgrade 100-200 nodes' clients just to have 2
weeks of "fun" and need either to upgrade again or to go back to a stable
version ...
Working with the bleeding edge of technology is not always fun :-)

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: tsm ftp server

So you probably don't want to install _all_ the patches. But if you want
to
know when a new patch comes out so you can look it over there are many
products that can monitor a web site for changes. I'm sure that at least
some of them could watch a tree on an ftp site that allows anonymous
access.

Have fun!

- kai.

-Original Message-
From: Zlatko Krastev/ACIT
To: [EMAIL PROTECTED]
Sent: 6/6/02 5:20 AM
Subject: Re: tsm ftp server

Burak,

the reason is that patches are released to fix specific problems (that's
why they are *patches*) and do not go through full testing procedure.
Whereas maintenance and rarely *some* patches get more testing and
become
recommended and pointed by web site.
Think as ftp site holding all versions but web site pointing the last
*recommended* one.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:tsm ftp server

Hi Everybody,
Why is the following web site is always behind ftp servers? Does anybody
can
answer it?
All development stuff in IBM does good job and releases maintenances and
patches but
the web stuff does not need to update the htmls immediately. I am bored
to
surf
inside the
ftp archive to find whether there is a new release or patch etc.
Regards,
Burak



http://www.tivoli.com/support/storage_mgr/adsercli.htm

Re: Migration Problem

[Zlatko Krastev/ACIT]

Gerald,

maybe you already found the problem but there can be a real situation
without any errors to force same behavior:
17.4% of the disk pool are free, i.e. 21 GB. And if the client attempts to
write 25 GB file it would go direct to next primary pool.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Migration Problem

TSM Server 4.2.2.0 on Solaris 2.8
TSM Client 5.1.0 on Linux 2.4

Test system.. primary disk pool filled up almost but not quite to hit the
hi
threshold of 90 that would start a migration.. yet I notice backups are
now
going to tape instead of the diskpool. What gives? Theres no Max size
threshold that would cause the files to go to tape due to size. Why are
the
backups going to tape instead of filling the disk pool up to it's hi of
90?
Weird..

tsm: SERVER1>q stg

Storage  Device   EstimatedPctPct  High  Low  Next Stora-
Pool NameClass NameCapacity   Util   Migr   Mig  Mig  ge Pool
   (MB) Pct  Pct
---  --  --  -  -    ---  ---
ARCHIVEPOOL  DISK   1,030.0   17.5   17.590   70
BACKUPPOOL   DISK 122,891.0   82.6   82.690   70  TAPEPOOL
SPACEMGPOOL  DISK   0.00.00.090   70
TAPEPOOL DC.LIB_TA-   350,000.07.9   40.090   70
  PE_1

tsm: SERVER1>q stg backuppool f=d

   Storage Pool Name: BACKUPPOOL
   Storage Pool Type: Primary
   Device Class Name: DISK
 Estimated Capacity (MB): 122,891.0
Pct Util: 82.6
Pct Migr: 82.6
 Pct Logical: 100.0
High Mig Pct: 90
 Low Mig Pct: 70
 Migration Delay: 0
  Migration Continue: Yes
 Migration Processes: 1
   Next Storage Pool: TAPEPOOL
Reclaim Storage Pool:
  Maximum Size Threshold: No Limit
  Access: Read/Write
 Description:
   Overflow Location:
   Cache Migrated Files?: No
   Collocate:
   Reclamation Threshold:
 Maximum Scratch Volumes Allowed:
   Delay Period for Volume Reuse:
  Migration in Progress?: Yes
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 110
Reclamation in Progress?:
 Volume Being Migrated/Reclaimed:
  Last Update by (administrator): ADMIN
   Last Update Date/Time: 06/07/02   01:42:37
Storage Pool Data Format: Native


tsm: SERVER1>

tsm: SERVER1>q sess f=d

  Sess Number: 317
 Comm. Method: Tcp/Ip
   Sess State: Run
Wait Time: 0 S
   Bytes Sent: 3.4 M
  Bytes Recvd: 107
Sess Type: Admin
 Platform: SUN SOLARIS
  Client Name: ADMIN
  Media Access Status:
User Name:
Date/Time First Data Sent:

  Sess Number: 12,105
 Comm. Method: Tcp/Ip
   Sess State: RecvW
Wait Time: 0 S
   Bytes Sent: 1.1 K
  Bytes Recvd: 3.7 G
Sess Type: Node
 Platform: Linux86
  Client Name: CYGNUS-PRI-10.0.172.5
  Media Access Status: Current output volume: LABEL.LIB_TAPE_1.4.
User Name:
Date/Time First Data Sent: 06/06/02   21:43:58

  Sess Number: 12,110
 Comm. Method: Tcp/Ip
   Sess State: RecvW
Wait Time: 0 S
   Bytes Sent: 489
  Bytes Recvd: 841.3 M
Sess Type: Node
 Platform: Linux86
  Client Name: CYGNUS-PRI-10.0.204.10
  Media Access Status: Current output volume: LABEL.LIB_TAPE_1.5.
User Name:
Date/Time First Data Sent: 06/06/02   22:47:14

  Sess Number: 12,113
 Comm. Method: Tcp/Ip
   Sess State: MediaW
Wait Time: 2.8 H
   Bytes Sent: 378
  Bytes Recvd: 16.1 M
Sess Type: Node
 Platform: Linux86
  Client Name: CYGNUS-PRI-10.0.172.6
  Media Access Status: Waiting for mount point in device class
more...   ( to continue, 'C' to cancel)

DC.LIB_TAPE_1 (10246 seconds).
User Name:
Date/Time First Data Sent: 06/06/02   22:53:52

  Sess Number: 12,140
 Comm. Method: Tcp/Ip
   Sess State: IdleW
Wait Time: 1.8 H
   Bytes Sent: 2.7 K
  Bytes Recvd: 1.0 K
Sess Type: Node
 Platform: Linux86
  Client Name: CYGNUS-PRI-10.0.204.8
  Media Access Status:
User Nam

Re: cleaning cart in IBM 3502-014 DLT lib

[Zlatko Krastev/ACIT]

Same as we had with 7337-306. Use 
checkin libv lb0.0.0.1 search=yes volrange=cln001,cln001
to cheat the TSM. Have in mind Mark's remark.

Zlatko Krastev
IT Consultant



Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:cleaning cart in IBM 3502-014 DLT lib

Dear colleagues,

could anyone give a suggestion how to checkin the cleaning cart in the 
a.m. lib? When I try to checkin libv lb0.0.0.1 cln001 checklabel=no I 
always get the same message: library is full. There is one empty slot from 

TSM point of view and it is physically occupied by CLN001 (I even tried 
when the lib was completely empty!).

Now I have to manually put this cart into library when a drive need 
cleaning, clean it from the lib panel and remove, because every checkin 
libv search=yes tries to load the cart into drive to read the label.

Your advice is very much appreciated.

Regards,
Anton Gubarkov.
IT Manager
SONY CIS
Tel. +7 095 258 7626
Fax +7 095 258 7650
My certificate can be obtained at ldap://koi8.sony.ru
ó Õ×ÁÖÅÎÉÅÍ,
áÎÔÏÎ ÷ÉËÔÏÒÏ×ÉÞ çÕÂÁÒØËÏ×
îÁÞÁÌØÎÉË ÏÔÄÅÌÁ áóõ
úáï óïîé óîç
ôÅÌ. +7 095 258 7626
æÁËÓ. +7 095 258 7650
íÏÊ X.509 ÓÅÒÔÉÆÉËÁÔ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÎÁ ldap://koi8.sony.ru

 

Re: Make Compression Client faster ??

[Zlatko Krastev/ACIT]

MAXNUMMP takes place for direct to tape operations. For disk you can have
more sessions but when disk pool gets full only maxnummp of them will
continue to write to tape.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Make Compression Client faster ??

Does it start multiple sessions as expected during a backup? As someone
else
already pointed out, this is tied to the # of filesystems you have and
you're only specifying /.. I believe you also need to make sure the node
(q
node f=d) has a MAXNUMP of 4 (default is 1) to get more then 1 data
session
running on a node.

Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)

-Original Message-
From: Grems [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 2:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Make Compression Client faster ??

this is my DSM.SYS

--
SErvername TSM_SERVER
   COMMmethod TCPip
   TCPPort1500
   TCPServeraddress   10.100.24.42

compression on
passwordaccess generate
resourceutilization 4
--

when i make a

root:>dsmc i / -sub=yes

omly one processeurs is use for compression, why ?



- Original Message -
From: "Gerald Wichmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 06, 2002 7:28 PM
Subject: Re: Make Compression Client faster ??


You sure the process is cpu bound and that it even matters? One would
think
the operation is more I/O bound..

Otherwise from redbook "using the ba client" try adjusting the
resourceutilization paramater:

Resourceutilization
Authorized User
The resourceutilization option regulates the level of resources the
Tivoli Storage Manager server and client can use during processing.
When you request a backup or archive, the client can use more than
one session to the server. The default is to use a maximum of two
sessions; one to query the server and one to send file data. The
client can use only one server session if you specify a
resourceutilization setting of 1. The client is also restricted to a
single session if a user who is not authorized invokes a UNIX client
with passwordaccess=generate specified.
A client can use more than the default number of sessions when
connecting to a server that is Version 3.7 or higher. For example,
resourceutilization=10 permits up to eight sessions with the server.
Multiple sessions may be used for querying the server and sending
file data.
Multiple query sessions are used when multiple file specifications
are used with a backup or archive command. For example, if you
enter:
inc filespaceA filespaceB
and you specified resourceutilization=5, the client may start a
second session to query files on file space B. Whether or not the
second session starts depends on how long it takes to query the
server about files backed up on file space A. The client may also try
to read data from the file system and send it to the server on
multiple sessions.
The following factors can affect the throughput of multiple sessions:
6 The server's ability to handle multiple client sessions. Is there
sufficient memory, multiple storage volumes, and CPU cycles to
increase backup throughput?
6 The client's ability to drive multiple sessions (sufficient CPU,
memory, etc.).
6 The configuration of the client storage subsystem. File systems
that are striped across multiple disks, using either software
striping or RAID-5 can better handle an increase in random read
requests than a single drive file system. Additionally, a single
drive file system may not see performance improvement if it
attempts to handle many random concurrent read requests.
6 Sufficient bandwidth in the network to support the increased
traffic.
Potentially undesirable aspects of running multiple sessions include:
6 The client could produce multiple accounting records.
6 The server may not start enough concurrent sessions. To avoid
this, the server maxsessions parameter must be reviewed and
possibly changed.
6 A query node command may not summarize client activity.
Note: The server can also define this option.

Also from another section:

Note: On occasion, the aggregate data transfer rate may be
higher than the network data transfer rate. This is because
the backup-archive client has multithreading capabilities.
When multiple threads run during backup, the data
transfer time represents the sum time from all threads
running. In this case, aggregate data transfer time is
mistakenly reported as higher. However, when running a
single thread, the aggregate data transfer rate should
always be reported as lower than the network data
transfer rate.



Regards,

Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)

-Original Message-
From: Grems [mailto:[EMAIL PROTE

Re: Directorie only

[Zlatko Krastev/ACIT]

AFAIK we still do not have the include.dir option :-)
But "exclude /.../*" left alone will do the trick.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Directorie only

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
William Rosette
>  I currently have a 3.1.0.8 TSM AIX SP node client (with
> 4.2.1 AIX) and
> want to back up a file system, but only the file structure.  I do not
need
> to back up the files.  For DR purposes, I need the file/directory
> structure.  I thought there was a parameter in the include for
directories
> only, but I am not sure if it is 3.1.0.8 compatible.  Any suggestions
are
> always welcome.

Aside from a desperate need to update both your TSM client *and* AIX OS
out
of unsupported levels ;o), you can add

exclude /.../*
include.dir /.../*

to your TSM client option file. I know the .dir extension was available in
3.7; I think it works in 3.1 as well. Of course, as with all unsupported
levels, YMMV.

--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
Certified AIX system engineer
MSCE

Re: TSM v4.1 clients NOT compatible with V5.1 server?

[Zlatko Krastev/ACIT]

you can have v4.1, v4.2 and v5.1 clients with v4.2 server and according to
Tivoli all those are working *and* supported configurations. So you can
upgrade your server to 4.2.x.x and everything ought to be fine.
As Don said unsupported does not automatically mean broken. For old/rare
OSes many are still using old v3.1 clients (the last available for my OS/2
is v3.7.2). Just IBM/Tivoli support will recommend you to upgrade before
calling them. Be aware that v4.1 also will go out of support end of the
month. The only reason which can force you to use v4.1 clients is
client/OS incompatibility. The latter is real, i.e. v4.2 client would not
work with Win95 and v5.1 would not with 95&98. But you cannot sign a
support contract with a maillist :-)

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TSM v4.1 clients NOT compatible with V5.1 server?

Hello all,
 If I am reading things correctly, all my v4.1 clients are NOT
compatible with V5.1 server.  Nor is a V5.1 client (where supported)
compatible with a V4.1.5 server.   Is this supposed to be a multi-step
upgrade?   Am I therefore supposed to tell management that the presence of
WIN95 laptops will stop our ability to upgrade to V5.1, (because they do
not
have a v4.2 client)  ?
http://www.tivoli.com/support/storage_mgr/compatibility.html

I am running v4.1.5 server on z/OS 1.1.   I have WINxx (all of them )
clients, AIX, SUN, Novell, and MAC clients mostly v4.1.  Has anyone gone
this route already or can tell me what migration path I can take?
Matt

Re: Password Experation Period

[Zlatko Krastev/ACIT]

default is 90 days.
If you set it to 0 you disable recycling of passwords and in long term are
vulnerable to password compromise.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Password Experation Period

Hi, TSMers,

If you do not specify or leave blank when registering a node, what will
be the default exp. period? Should I always enter some value for this
field using Web admin interface? I know that 0 means never expire the
password. Should I set all the node with this value?

Thanks for your help.



Jin Bae Chi (Gus)
Data Center
614-287-2496
614-287-5488 Fax
e-mail: [EMAIL PROTECTED]

Re: Anyone know what is up with ANR0197E

[Zlatko Krastev/ACIT]

No need to audit 3K volumes :-) Look for APAR IC33641 or search Tivoli KB for ANR0197E.
We had same problem not with tape but with file volume:
ANR8341I End-of-volume reached for FILE volume
C:\TIVOLI\TSM\STG_POOL\AF12.BFS.
ANR0195W Attempting to remove extraneous database entries for volume
C:\TIVOLI\TSM\STG_POOL\AF12.BFS.
ANRD asalloc.c(663): ThreadId<23> Volume
C:\TIVOLI\TSM\STG_POOL\AF12.BFS being accessed remotely - ending
repair attempt.
ANR0197E Removal of extraneous database entries for volume
C:\TIVOLI\TSM\STG_POOL\AF12.BFS failed due to contention with other
server processes or activities.
In our case the problem was last segment in the volume AF12.BFS while
the file continues in volume AF15.BFS which was in use by other
process.
Bottom line: fix for APAR IC32423 has to be *fixed* :-)
Oh, yes, it is TSM 4.2.1.15 on Win2k.

Zlatko Krastev
IT Consultant



Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Anyone know what is up with ANR0197E

Sorry,A q vol shows nothing out of the ordinary/ volumes in read-write
.


Volume Name: D03071
  Storage Pool Name: CDWOFFSITE
  Device Class Name: IBM3590
Estimated Capacity (MB): 67,159.6
   Pct Util: 100.0
  Volume Status: Full
 Access: Read/Write
 Pct. Reclaimable Space: 0.0
Scratch Volume?: No
In Error State?: No
   Number of Writable Sides: 1
Number of Times Mounted: 1
  Write Pass Number: 1
  Approx. Date Last Written: 05/13/02   17:30:35
 Approx. Date Last Read: 05/13/02   17:30:35
Date Became Pending:
 Number of Write Errors: 0
  Number of Read Errors: 0
Volume Location:
Last Update by (administrator): WILEYG
  Last Update Date/Time: 05/12/02   12:33:20

DO I NEED TO SEE AN OPTOMETRIST ?

The message happens usually when a backup stgpool is running or
reclamation.

Haven't  yet notcied it at DBbackup time, probably because my pager is
backed up from all the other messages I am getting.

I will see if it happens on a DBbackup volume today..

No command was issued, script checks actlog for anything out of the
ordinary(or what I haven't placed in the page_exclude list)

If auditing is the resolution, it will take weeks for that to complete on
3
thousand tapes.

Gabriel C. Wiley
ADSM/TSM Administrator
AIX Support
Phone 1-614-308-6709
Pager  1-877-489-2867
Fax  1-614-308-6637
Cell   1-740-972-6441

Siempre Hay Esperanza



|-+-->
| |   David Longo|
| |   |
| |   Sent by: "ADSM:|
| |   Dist Stor Manager" |
| |   <[EMAIL PROTECTED]|
| |   DU>|
| |  |
| |  |
| |   05/13/2002 08:22 PM|
| |   Please respond to  |
| |   "ADSM: Dist Stor   |
| |   Manager"   |
| |  |
|-+-->

>--|
  |   |
  |   To:   [EMAIL PROTECTED]  |
  |   cc:   |
  |   Subject:  Re: Anyone know what is up with ANR0197E |
  |   |
  |   |

>--|



I have 4.2.1.10 and message is not on my system or in messages pdf.
Did you try a q vol volname f=d or a content volname to see what
info if any about these available?

You didn't indicate whatb command you issued that gave the errors
listed.  Is a reclamation, backup DB or any other process involving
tape/disk/DB going on?  I would wait for quiet or cancel processes and
again.  May need to do audit volume to fix.

David Longo

>>> [EMAIL PROTECTED] 05/13/02 05:09PM >>>
I have checked in/out  and re-labeled these tapes 3-4 times, no message
available.

Does anyone know what this means and how to resolve?

05/13/02   16:40:43  ANR0197E Removal of extraneous database entries for
volume
   D03071 failed due to contention with other server
  processes or activities.
05/13/02   16:40:43  ANR0197E Removal of extraneous database entries for
volume
   D03072 failed due to contention with other server
  processes or activities.
05/13/02   17:03:43  ANR2017I Administrator WILEYG issued command:

Re: 3590 pricing (used)

[Zlatko Krastev/ACIT]

--> It'll be wierd when my 3494 is my "low-latency, low-capacity" storage
format.

Don't be afraid of this. Magstar is still not dead. Maybe you missed it
but last month's IBM news article was about 1 TB in 3590 not in LTO
cartridge :-)

Zlatko Krastev
IT Consultant



Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: 3590 pricing (used)

=> On Wed, 12 Jun 2002 17:06:10 -0400, Steve Schaub
<[EMAIL PROTECTED]> said:

> Has anyone purchased used 3590 equipment recently and would be willing
to
> share a reasonable ballpark dollar amount?  We are running out of room
in
> our 3494 and would like to start converting our S/390 over from 3490 to
> 3590.  What would be a good price for an A60 controller and four 3590E1A
or
> B1a (escon) drives?

> Alternately, if I sacrificed my 4) 3590E1A drives from TSM to the
Mainframe
> and bought a separate library for TSM, what would it take to replace
what I
> have (277-J, 218-K of which 119-K are offsite)?

Whatever you do, don't bother buying a new 3494.  Just expand what you've
got.
If you think about it, there's no way you can possibly save cash that way.

If you're willing to take the hit in seek time, then you could go for a
dumber
library: a 3584 with LTO drives will most definitely be fewer dollars per
TB,
fewer square feet of floor per TB, etc.  and the LTO physical standard has
absolutely tremendous upgrade paths.

But if you're sticking with the 3590s for a bit longer (which was our
call)
then just toss the new drives in the existing 3494.

The used market is pretty good.  Lots of folks who don't need the access
speed
are going LTO, so some 3590s are hitting the market.  It'll be wierd when
my
3494 is my "low-latency, low-capacity" storage format. :)

- Allen S. Rout

Re: ADSM 3.1 to 4.2.1 Migration

[Zlatko Krastev/ACIT]

Marc,

if you can afford little bit more time I would recommend you to test it
first to ensure it will run smoothly:
1. Get another box capable to run AIX 4.2.1 (it can be hard those days :-)
and put ADSM 3.1 on it.
2. Restore your TSM DB to this "new" box. Just the DB, there is no need to
attach to it any storage devices. And do not forget to disable schedules
in dsmserv.opt - your test server can try to contact several nodes in
prompted mode.
3. Perform OS and TSM upgrade.
4. Backup upgraded DB and restore it on new production server.
If all this completes successfully you can be sure real upgrade+migration
would be fine. And you will not be in a hurry.
There are no two ways to upgrade - I am sure you cannot put AIX 4.2.1 on
your brand new server :-) Yes, you can put ADSM 3.1 on AIX 4.3 and then
upgrade to TSM but better perform upgrade on the old box and only restore
the DB on the new server. If you are not confident in the success of the
migration perform the upgrade same way - do 1, 2, 3 and 4. Thus in case of
problem/failure you can stay with your old server and try again next
day/week/month.
If this insurance is still not enough - sign a contract with a consultant
:)

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:ADSM 3.1 to 4.2.1 Migration

Hello Again,

Since we are getting a new library we are also getting new server hardware
and going to TSM 4.2.1 (5 will be later).  Therefore, we have a 2 way
upgrade (old software to new software, old server to new server).

I gave TSM support a call and asked what their recommended procedure was
and I found out that they really don't have any, but the tech support guy
who responded gave me a procedure that he says has worked for others.

In our case, we need to upgrade the OS on the old server (still at 4.2.1)
to 4.3.3. Do an update install of TSM on top of what we have now.  Export
the database after it has been transformed by the update/install to tape.

Take the export tape and import it into the new server (along with the old
tape libraries).  Then migrate the data from the old library to the new
library.

Is this what others have done?  I have seen snippets of other things being
done,  but usually it appears that server hardware remained the same.

TIA for all of your comments.

Marc

===
Marc D. Taylor
Research Programmer
Beckman Institute Systems Services
Room 1714
Office:  217-244-7373, Fax:  217-333-8206
[EMAIL PROTECTED]
http://biss.beckman.uiuc.edu

Re: Bad performance... again

[Zlatko Krastev/ACIT]

--> The site belongs to a customer who doesn´t like very much applying 
patches.

You can apply *maintenance* not a patch by installing 4.2.2.0. You can 
point to the customer that he/she does not stay at AIX 4.3.0 but is using 
4.3.3 to get *improvements*.

--> 4. There were some noticeable performance problems on AIX (I think 
somewhere between ML08 and 09.  I think they were all fixed at 09).

Actually somewhere between ML9 and ML10 :-) There was "nice" memory leak 
problem in ML9 plus some others *directly* affecting TSM performance. Thus 
you have to upgrade at least:
bos.mp
bos.rte.libc
bos.rte.libpthreads
bos.net.tcp.client
bos.net.tcp.server
ML10 seems good up to now.
Look at post made by Thomas Rupp on 10.04.2002 on thread "Big Performance Problem 
after upgrading from AIX TSM Client 4.1 to 4.2". I've learned this hard way but not 
with TSM :-)

--> To increase the cache-hit percentage you will need to shutdown TSM.

WRONG! Just use 'setopt bufpoolsize '. This also *appends* a 
option line in dsmserv.opt but does not remove the old one. So you can 
clean up a bit. It is better to issue also 'reset bufpool' to clear stats 
and to get correct DB cache hit %. 
If we talk about LOGPOOLSIZE then yes, you have to change option and 
restart the TSM server.


Zlatko Krastev
IT Consultant





Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Re: Bad performance... again

Thanks for that David,

To increase the cache-hit percentage you will need to shutdown TSM.

Backup and edit BUFPOOLSIZE in dsmserv.opt and restart the TSM server.
It's probably worth going through an unloaddb and reload of the database
also to
improve performance. We're looking at doing this as a quarterly procedure.

BUFPOOLSIZE refers to virtual memory, default is probably 4096. There is a
table
in the Admin Guide which recommends increases in BUFPOOLSIZE according to
system memory. I'd recommend being a bit conservative and grow it a bit at 
a
time
performing a "q options" and "q db f=d" to see what's going on with
BUFPOOLSIZE in
relation to cache-hits. You obviously don't want to use up virtual-memory 
at
peak load
times.

Mike.

> -Original Message-
> From: David Longo [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 14, 2002 9:15 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Bad performance... again
>
> Well, I'll take a few shots.
>
> 1.  Network - Have you tried some FTP or similar tests at OS level
> between TSM server and clients to see if Network performance is o.k.?
>
> 2.  Your Atape driver is WAY behind.
>
> 3.  Drive microcode on 3584 is behind (Not as far as Atape though).
>
> 4. There were some noticeable performance problems on AIX (I think
> somewhere between ML08 and 09.  I think they were all fixed at 09).
>
> 5.  On TSM server, what is the "cache hit percent" output of
> "q db f=d"?  If it is much less that 98%, the cache needs to be
> increased.  This can effect a lot of TSM server ops.
>
> 5.  You didn't mention how long this server has been in operation
>  - was it working fine at one point and went downhill?  Also what
> Disk you have on TSM server and how setup?
>
> David Longo
>
> >>> [EMAIL PROTECTED] 06/12/02 10:50AM >>>
> Hi everybody,
>
>
>I know this is a subject that comes very often, and that various
> answers
> were already give, but, after searching through the list archives, I am
> still not totally sure of what I should do:
>
>I have a TSM Server that does his backups not quite fast. First, I
> thought of a network problem, but it is a dedicated backup network 
running
> at 1Gb/s and I only get backups at 10GB/hour. And, the internal server
> operations (reclamation, backup stgpool) are also slow. Right now, I am
> looking at the console a backup stg process which is running for almost 
2
> hours and has backed up only 38GB. It is a new pool, so there is no time
> spent searching the new files, and all the data came from one volume.
>
> My setup is:
>
> TSM Server 4.2.0.0  (Client wants to upgrade to 5.1)
> AIX 4.3.3 ML9 on an F80 with 2 CPUs
> ATAPE 5.4.2.0
>
> Storage is:
>
> IBM3584 with 6 IBM LTO drives. Microcode level is 16E0
>
> The site belongs to a customer who doesn t like very much applying
> patches.
> Should I try to convince him to upgrade TSM/ATAPE/Microcode? Or is there
> anther issue?
>
>
>
> Thank you in advance for your attencion
>
> Paul van Dongen
>
>
>
> "MMS " made the following
>  annotations on 06/13/02 21:31:29
> 
--
> 
> 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 i

Re: TSM 4.2/AIX setup questions

[Zlatko Krastev/ACIT]

All other questions were answered so I would grab only #5 :) and add one
more
5. Firmwares on IBM SSG site are separated for AIX and Windows. Simply
download AIX package, follow the readme and no need to introduce Windoze.

#8: plan carefully your stgpool chain(s).
You may consider some nodes to go to non-collocated pools while others to
use collocated or even filespace-collocated. MOVE NODEDATA is implemented
in v5.1 and is not available in v4.2.x. Thus you can easily merge pools
but cannot separate some node(s) to another pool.

--> If you will be backing up a file larger than the stgpool it may be more
efficient to send it right to tape, this is the general rule.

Actually if a file is larger than the *available space* in the stgpool it
goes direct to next pool. If next one also does not have enough available
space the file goes down the chain again. And if the file is bigger than
the pool you never will find enough available space :-)
Look at Wanda's explanation for maxsize parameter. If a big file hits your
disk pool, fills it near to the top and later smaller file does not find
enough space it would go to the next pool instead of big one.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TSM 4.2/AIX setup questions

Environment: TSM 4.2.x on an AIX 4.3.3 ML10 server (660-6H1) with a
3584-L32
and a 3584-D32 expansion frame.

In the process of setting it up, which is a luxury that I'll have only
once
to get it right. :) So, some questions (since I am still coming up to
speed
on *SM).

1) Is there any particular reason to set a max file size for a disk
stgpool?
   (Assuming a setup where disk stgpool will migrate to tape stgpool)

2) Should the TSM server have its own stgpool for backing up itself?

3) I've heard mixed things about 358x firmware version 22UD... I think we
   have 18N2 (but not near it right now to confirm), although what I've
   heard about 22UD is generally (but not 100% in agreement) positive.
Stable?

4) Whom is supposed/allowed to upgrade firmware? IBM CE only?

5) The only docs for firmware upgrade references a NT/2000 box and the
   NTUtil application, whereas I'm in an all-UNIX (AIX and Solaris,
although
   I do have a laptop with Linux and Windows XP if need be) environment,
so
   wonder how to upgrade the firmware without Windows if it's even
possible.

6) To *SM, all backups are incrementals (except for the first backup of a
   new client), is my general understanding. Is there a way to force a
full
   backup of a particular client as an one-time operation? I'm guessing
maybe
   not, but thought I might try asking, anyway. :)

7) The biggest single question... I don't have a real good understanding
of
   the purpose of copy stgpools. I've read a lot of documentation --
hundreds
   of pages of multiple docs, re-read, read old adsm-l mail, Google
searches,
   etc... but still just don't quite 'get it'. I can set up HACMP
clusters,
   debug really obscure things, but this eludes me. ;)

   What I want to do is:

   client -> TSM server -> disk stgpool -> (automatically migrate to tape
   based on space utilization of disk stgpool) tape stgpool

   That's the general concept of what I want to achieve. Is a copy stgpool
   really needed, to be attached to either one of the primary stgpools?

   I was under the impression that a copy stgpool was something you wanted
   when you wanted to copy a primary stgpool so that you could send it to
   another stgpool when ready (based on whatever trigger...space, date),
   such as in a disaster recovery scenario?

-Dan Foster
IP Systems Engineering (IPSE)
Global Crossing Telecommunications

Re: good readings

[Zlatko Krastev/ACIT]

Rick,

if you only new to the list it is OK. But if you are also new to TSM I
would highly recommend you to start with SG24-4877 "Tivoli Storage
Management Concepts". Read all the chapters relevant to what you have -
"must read" 1-8 + "optional" 9-13,30 + any related to your TDP (if any,
chapters 15-24).
After becoming familiar with the terms and functionality in TSM have a
look at SG24-6277 "Tivoli Storage Manager v4.2: Technical Guide" and (as
Joel suggested) SG24-5416 "Getting Started with TSM: Implementation
Guide".
It also might be worth the effort to look at Richard Sims's ADSM/TSM facts
page (http://people.bu.edu/rbs/ADSM.QuickFacts).

Zlatko Krastev
IT Consultant




Please respond to [EMAIL PROTECTED]
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:good readings

Hey all,
I am a bit new to the list and am in a position to implement TSM 4.2 and
would like to get some good reading material so that I can better
understand TSM.  Would anyone have some good recommendations?  I have a
couple of the redbooks and have been going through them but if anyone
would
have some further recommendations (websites, books, etc) I would
appreciate
them.

R.

Re: Library survey

[Zlatko Krastev/ACIT]

Gianluca,

of course working for IBM you have no option than to say good words about
the company and products :)
But to be honest we have to say that 3583 is just OEMed ADIC Scalar 100
with IBM Ultrium drives in it. Anyway it is still a very good library.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Library survey

IBM LTO is, objectively, the best performer in the field. the drives are
more robust, have much fewer mechanical or firmware problems and are, in
general, very reliable. the 3584 and 3583 are very solid, performing
libraries. it is not by chance that in the LTO market IBM is doing so
well.
even though I may seem to be partisan, for obvious reasons, I try to look
at things as objectively as possible and I have seen a very good
acceptance
from customers for IBM LTO. HP and Seagate have come much later to the LTO
market, even though they are the other two proponents of the standard,
because their drives were riddled with problems and not, in general,
performing well. they have mostly overcome these youth problems but still,
the IBM drive is ahead.

Cordiali saluti
Gianluca Mariani
 Tech Support SSD
Via Sciangai 53, Roma
 phones : +39(0)659664598
   +393351270554 (mobile)
[EMAIL PROTECTED]



  Michael Benjamin
 cc:
  Sent by: "ADSM:  Subject:  Re: Library
survey
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  13/06/2002 02:32
  Please respond to
  "ADSM: Dist Stor
  Manager"





This is a top-of-the-range machine we use, a 3584 D32. Some of the way it
performs functions are a bit mysterious,
like not utilising all available drives when mass loading tape volumes,
but
there are ways around that like pre-loading the library,
these are primarily software/firmware improvements that will eventually
get
implemented.

The Ultrium drives are very robust indeed and we haven't had any failures.

All in all it's the best library I've used bar none, and very scalable.
Properly implemented it will serve most companies storage
needs very well indeed.

> -Original Message-
> From: Joshua S. Bassi [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, June 13, 2002 7:48 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Library survey
>
> We have sold a ton of the IBM UltraScalable Tape Library (3584).  It is
> a rock solid, reliable performer.
>
>
> --
> Joshua S. Bassi
> Sr. Solutions Architect @ rs-unix.com
> IBM Certified - AIX 5L, SAN, Shark
> eServer Systems Expert -pSeries HACMP
> Tivoli Certified Consultant- ADSM/TSM
> Cell (415) 215-0326
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
> Marc D. Taylor
> Sent: Wednesday, June 12, 2002 2:07 PM
> To: [EMAIL PROTECTED]
> Subject: Library survey
>
> Hello SM'ers:
>
> We are currently in the process of getting a new tape library.  It will
> be
> LTO based.  We are currently leaning toward the Overland Data Neo 4000
> series because of its price and expansion capabilities.
>
> Are there others out there who are using the Neo series libraries?  What
> have been your experiences?
>
> My only hangup is that it uses the Seagate LTO.  I have not heard
> anything
> about this one as most of this list seems to have the IBM LTO.
>
> I welcome your thoughts.
>
> Marc Taylor
>
> ===
> Marc D. Taylor
> Research Programmer
> Beckman Institute Systems Services
> Room 1714
> Office:  217-244-7373, Fax:  217-333-8206
> [EMAIL PROTECTED]
> http://biss.beckman.uiuc.edu

**
Bunnings Legal Disclaimer:

1)  This document is confidential and may contain legally privileged
information. If you are not the intended recipient, you must not
disclose or use the information contained in it. If you have
received this e-mail in error, please notify us immediately by
return email and delete the document.

2)  All e-mails sent to and sent from Bunnings Building Supplies are
scanned for content. Any material deemed to contain inappropriate
subject matter will be reported to the e-mail administrator of
all parties concerned.

**

Re: Upgrade from 4.1.2.0 to 4.2.2.3

[Zlatko Krastev/ACIT]

Steve,
but Windows does not have so smart installer as AIX's installp. It would
request from you first to install 4.2.2.0 and then to install 4.2.2.3. And
she is having 4.2.0 install CD.

Diana,
you do not need to put v4.2.1. Go straight with 4.2.2 as Burak suggested.
If you still insist go to
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/server/v4r2/AIX/4.2.1.0/
and download it.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Upgrade from 4.1.2.0 to 4.2.2.3

I just did a conversion of TSM server v4.1.3.0 on Win2000 to v4.2.2.3
and all seems well.

steps:
uninstall v4.1.3.0
install v4.2.1.0 from cd
install v4.2.2.3 from the ibm ftp site


Burak Demircan wrote:
>
> you do not need to install 4.2.1 to install 4.2.2 . am i wrong?
> normally you should be able to upgrade to 4.2.2 just after the 4.2
insallation
> regards
>
>
> [EMAIL PROTECTED]
> Sent by: [EMAIL PROTECTED]
>
> 13.06.2002 08:27
> Please respond to ADSM-L
>
> To:[EMAIL PROTECTED]
> cc:
> Subject:Upgrade from  4.1.2.0 to 4.2.2.3
>
> I would like to upgrade from 4.1.2.0 to 4.2.2.3 (and eventually to 5.1
when
> we can get all the clients off 4.1).  I have a 4.2.0 install CD for the
> server which will run on AIX 4.3.  From what I can tell I must install
the
> 4.2 CD (do I need to put 4.1 maintenance on too before doing this?),
then
> install 4.2.1, then 4.2.2 then the patch for 4.2.2.3.  I can't find the
> 4.2.1 code out on the web to download it, only the 4.2.2.  Everything I
> read seems to point to the fact that 4.2.1 would be installed before
> install 4.2.2.  Can anyone verify this or tell me where I can download
4.2.1.
>
> Thank you,
>
> Diana
>

--

Steve Bennett, (907) 465-5783
State of Alaska, Information Technology Group, Technical Services
Section

Re: Space reclamation to tapepool

[Zlatko Krastev/ACIT]

You cannot have "migration" back to disk pool - TSM will not allow you to
create closed loop of pools and pool of type DISK cannot be set as
reclamation pool.
You have to define pool over devclass of type FILE and set it as
reclamation pool to the tape pool. And the size of file pool does not need
to be large as for the disk one. Its size can be no larger than ammount of
data to be reclaimed from a tape. Example: DLT 8000 with estimated
capacity 80GB, reclamation threshold 60% gives 80GB*(100-60%)=32GB
reclaimable data. If you are in heavy constraint you can shrink further
reclamation pool but either reclamation will run in two passes or you have
to increase reclamation threshold.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Space reclamation to tapepool

Hello TSM'rs

I have a question. Here's my senario, We backup to disk. Then Migrate to
tape once the backups complete.
I have a single drive tape.
the disk capacity is not enough to create another stgpool.
I want to execute the processes of space reclamation to the tapes.
Do I have some risk if it emigrates again from the tapepool to the
diskpool
for tapes with 2% use?
That cautions should take?

your assistance is greatly appreciated.
Thanks,

Carlos R. Bravo Arredondo
[EMAIL PROTECTED]
Tel. (55) 51741924

Re: Access control lists

[Zlatko Krastev/ACIT]

/etc/passwd, $HOME/.rhosts :-) Just kidding.
You authorise user to access the data, not the nodes. And the data resides
on the server. Users do not need to contact your node to get the data. On
the end everything else is stored in TSM server DB, why to store those
ACLs in other place.
But if you ask in which table - I have no answer. It is not stored in any
table I know and I suspect it is in some hidden table. As you know not all
tables are available to us for selects.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Access control lists

When I authorize another node/user to access data from my node, where is
the
access control information stored? I have Win9x, WinNT, Win2k, Novell,
AIX,
HP/UX and Linux clients. I am primarily interested in where this is stored
on the UNIX clients, but am curious about the Windows/Novell clients as
well.

Re: dsmaccnt.log location

[Zlatko Krastev/ACIT]

???
DSMSERV_ACCOUNTING_DIR is an environment variable and has nothing to do
with dsmserv.opt.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: dsmaccnt.log location

Set it in the dsmserv.opt file and restart the server.



David E
Ehresman  To: [EMAIL PROTECTED]
Subject: dsmaccnt.log
location
Sent by: "ADSM:
Dist Stor
Manager"
<[EMAIL PROTECTED]
ST.EDU>


06/14/2002
08:16 AM
Please respond
to "ADSM: Dist
Stor Manager"






Enivronment:  TSM 5.1.0 running on AIX 5.1

In my /etc/profile, I have
 "export DSMSERV_ACCOUNTING_DIR=/var/adm/tsm" which should cause the
dsmaccnt.log to be created in /var/adm/tsm.  But it continues to be
created in the server install path, /usr/tivoli/tsm/server/bin.  Any
ideas what else I need to do to get dsmaccnt.log created in
/var/adm/tsm?

David

Re: DB backups

[Zlatko Krastev/ACIT]

Wanda,

in general I am on your side but some of the arguments are weak:
1. stgpool backups
If the DB is reverted back newly created copypool tapes will be listed as
scratch and primary pools' objects will have no copies. Next backup to
this copypool will fix the things and probably will use same scratches.
2. tape reclaims
Similar as above for reclamation destination tapes and reuse delay
protects reclamation source tapes
3. expiration
It can be performed again without data loss. Yes, for large DBs time for
expiration is an issue but the only penalty will be larger first
expiration *after* recovery.
4. HSM client bringing a file from TSM back to host
Again no data loss. Option to backup the file *before* migration ensures
we will have a copy to restore from.

Now other arguments. Besides some remarks I prefer roll-forward mode :)
- you already pointed hundreds of desktops backing up around the clock.
Sites which *do* backup desktops very often cannot have all of them
available at night. And you cannot predict when a mobile user will be
online or in the office.
- RDBMS servers perform backups during normal window but transaction logs
are coming throughout the day regularly.
- archives - user archived a set of files, got successful completion
result and does not care further.
- some applications use TSM as *the only* storage, example IBM CommonStore
- loss of last minute TSM DB updates will lead to loss of created/revised
documents.
After data came in TSM our task is to protect it. Even with new
functionality of v5.1 loss of DB updates will lose track of both copies.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: DB backups

For some environments, yes.  But not for all.

Even people who backup once overnight, still have to do

(1) backup stgpool to create copypool tapes.
(2) tape reclaims
(3) inventory expiration

All those things change the TSM DB.

And some environments are really 24 x 7:

One of our TSM servers does desktop backups of 500+ clients.  Backups are
spread over 24 hours a day, so for that environment, the TSM db is
changing
EVERY MINUTE.  Really.

And consider also the people who have implemented the HSM client - in that
environment, just having a user "touch" a file is enough to bring it back
from TSM storage to client storage, and the TSM DB is changed.

In either of those environments, losing 12 hours, on average, of DB
changes
can be devastating.


Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert





-Original Message-
From: William Rosette [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 17, 2002 8:52 AM
To: [EMAIL PROTECTED]
Subject: Re: DB backups


You can get "up to the minute" if you do enough database backups, and I
still don't understand the "up to the minute" idea.  If you are doing
backups every minute that seems logical but do not most people backup once
a night? and if there is a database backup is not this database backup and
"up to the day" same as "up to the minute?"



"Jolliff,
Dale"To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]   cc:
OM>  Subject: Re: DB backups
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


06/14/02 12:21
PM
Please respond
to "ADSM: Dist
Stor Manager"






I have suggested this a couple of times, but have been told they need the
ability to restore the TSM server "up to the minute" that rollforward
provides.


-Original Message-
From: William Rosette [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 14, 2002 9:49 AM
To: [EMAIL PROTECTED]
Subject: Re: DB backups


We changed our roll forward to NORMAL and have seen very little (once in a
year) crash due to full recovery log.  This may be an option instead of
the
type FILE.




"Jolliff,
Dale"To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]   cc:
OM>  Subject: DB backups
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


06/14/02 10:01
AM
Please respond
to "ADSM: Dist
Stor Manager"






Is anyone doing db backups to

Re: TEC/DM/TDS sites

[Zlatko Krastev/ACIT]

If you mean list like this one - subscribe to [EMAIL PROTECTED] You
have to send empty mail to <[EMAIL PROTECTED]>. Or get list of command 
by sending mail to <[EMAIL PROTECTED]>.
If you mean site - Tivoli Knowledge Base
(http://www.tivoli.com/support/knowledgebase) allows searches through
tme10 list archives

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TEC/DM/TDS sites

Does anyone know of similar site like this for TEC/DM/TDS?

Re: hardware questions before I buy

[Zlatko Krastev/ACIT]

Jeff,
from financial point this Exadrive might seem very attractive. But are you
sure it would fit in TSM environment without performance degradation. For
me this might be something very similar to cheap "RAID" advertized by PC
mainboards but with all the problems IDE/EIDE/ATAPI devices have - no
release of the controller/device until operation finishes, lack of tagged
(or any) command queueing.
Thus you will get very inexpensive storage but at price of performance
problems. I guess it would be slower than LTO you already have and the
cheaper (and faster) deal would be to buy more cartridges.
And btw. what is the price of an IBM 200GB disk ?? AFAIK they even do not
offer 180 GB as Seagate does and larger SCSI one is 73 GB.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:hardware questions before I buy

We have a small TSM system.  I'm looking to expand it.  Of course, I'm on
a budget.

Currently we are on an RS/6000 H70 with an IBM 3581 tape changer.  We have
almost no disk space available for disk storage pools.  The machine is
dedicated to running TSM.

I am considering adding the following

IBM 3583 with two LTO drives, starting out with an 18 tape capacity.  I'm
not too worried about this part of it, correct me if I'm wrong, but I
think this is a known performer.

Exadrive Diamond SCSI -> ATA Storage Array.  This piece of hardware comes
with a 30 day money back guarantee, and a three year warranty.  I can get
2 TB of disk for the price of about 200GB of IBM SCSI disk.  The company
web site is http://www.exadrive.com  Does anybody know anything about this company, or 
this specific Storage
Array.It plan to use it for disk storage pools for our nightly backups
(around 250GB) , which I will move to tape during the day.

-JeffR

Re: good readings

[Zlatko Krastev/ACIT]

Unfortunately yes :(



Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: good readings

Speaking of Richard Sims, I am guessing that Marist's upgrade didn't fix
Richard's ability to get mail from the list.

bummer.



    Zlatko
Krastev/ACIT To: [EMAIL PROTECTED]
   Subject: Re: good readings
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


06/14/2002
04:14 PM
Please respond
to "ADSM: Dist
Stor Manager"






Rick,

if you only new to the list it is OK. But if you are also new to TSM I
would highly recommend you to start with SG24-4877 "Tivoli Storage
Management Concepts". Read all the chapters relevant to what you have -
"must read" 1-8 + "optional" 9-13,30 + any related to your TDP (if any,
chapters 15-24).
After becoming familiar with the terms and functionality in TSM have a
look at SG24-6277 "Tivoli Storage Manager v4.2: Technical Guide" and (as
Joel suggested) SG24-5416 "Getting Started with TSM: Implementation
Guide".
It also might be worth the effort to look at Richard Sims's ADSM/TSM facts
page (http://people.bu.edu/rbs/ADSM.QuickFacts).

Zlatko Krastev
IT Consultant




Please respond to [EMAIL PROTECTED]
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:good readings

Hey all,
I am a bit new to the list and am in a position to implement TSM 4.2 and
would like to get some good reading material so that I can better
understand TSM.  Would anyone have some good recommendations?  I have a
couple of the redbooks and have been going through them but if anyone
would
have some further recommendations (websites, books, etc) I would
appreciate
them.

R.

Re: CDRW support? Not as of 1/1999

[Zlatko Krastev/ACIT]

Norbert,

unfortunately Richard is still having TCP/IP problems between MARIST and
their site. This prevents him to receive ADSM-L postings.
You can still contact him directly on <[EMAIL PROTECTED]>

Zlatko Krastev
IT Consultant




Please respond to [EMAIL PROTECTED]
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:CDRW support?   Not as of 1/1999

Dear Richard,

you wrote in your ADSM/TSM Quick Facts following entry
CDRW support?   Not as of 1/1999

Was there in the past any CDRW or CDRW Changer supported?
For sample on NT or AIX?

Or is there any easy possibility to make CDR's for Backup Set's?
But only direct to CDR whithout using a HDD partition?

Thanks for answering

N. Martin

Re: Data inconsistencies

[Zlatko Krastev/ACIT]

What have you totalled - sum(capacity) or sum(capacity * pct_util / 100) ?
Latter will give you the ammount of data while former will give you the
space in filesystems (occupied and non-occupied). Also take into account
that not all the data may be backed up - you can exclude some files.
And an example on the end:
100 GB filesystem with 20 Oracle data files 4 GB each will give 80 GB
occupied and 20 GB empty space.
Later data files are excluded from B/A client and Oracle tablespaces being
say 66% utilized will give approx. 53 GB of backups.
And if you have client compression say 2.4:1 will have this data occupying
only 22 GB.
etc., etc. ...

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Data inconsistencies

Hello TSMers,

I have a mystery here I need help clearing up.

I ran these commands...

SELECT NODE_NAME, FILESPACE_NAME, capacity, PCT_UTIL, BACKUP_START,
BACKUP_END FROM FILESPACES  and
I send the output of this command through some REXX code to total the
amount
of data(capacity) backed up.  The result is 13 terabytes.

SELECT VOLUME_NAME FROM VOLUMEUSAGE
>From this command I have 374, 20 gigabyte tapes, totaling 7 terabytes.

f this server has backed up 13 terabytes, where would the remaining data
reside?





Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect
the views of Blue Cross Blue Shield of Florida, Inc.

Re: snmp

[Zlatko Krastev/ACIT]

Password of SNMPADMIN has nothing to do with community name. In fact 
whatever password you set it does not matter.
Community string is necessary for SNMP operations.
Assuming you are using snmpinfo from the *same* box you should use:
# snmpinfo -v -ms -c private ibmAdsmServerScript1.1="q_db_util"
Note usage of '-c private'. This is the community with ReadWrite access as 
per default /etc/snmpd.conf installed by AIX. If your site have modified 
the communities in the file select appropriate one.
Later read the result with any Read community. Do not forget that *each* 
read on ibmAdsmM1ReturnValue invokes the script again.

Example:
# snmpinfo -v -ms -c private ibmAdsmServerScript1.1="datetime"
ibmAdsmServerScript1.1 = "datetime"
# snmpinfo -v -mg ibmAdsmM1ReturnValue.1
ibmAdsmM1ReturnValue.1 = "
   Date   Time
-- --
2002-06-21   10:40:23
ANR1462I RUN: Command script DATETIME completed successfully.
"
Hope this helps. If not ask again.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:snmp

Hello all,
 can somebody help me? I have problem with snmp, I cannot use defined own 
script
 
I can see some information with command: 
# snmpinfo -v -md ibmAdsm
 
but command doesn't work:
# snmpinfo -v -ms ibmAdsmServerScript1.1="q_db_util"
noSuchName at position 0 - with result 255 return code
 
 
Everything is default I set passwd for SNMPADMIN on public as community 
name and I defined script "q_db_util" in TSM server. 
 
I have TSM server 4.1.2 on AIX 4.3.3.
 
 
Thank you for answer 
Filip Há?a
 

Re: dsmaccnt.log location

[Zlatko Krastev/ACIT]

Very close :) Actually not DSMSERV_DIR but "current directory" where the
server is started. Usually rc.adsmserv script changes to the directory
(you can look in it) before to start the server. That's why dsmaccnt.log
gets there when server is started from /etc/inittab. If you halt the
server and start it not through rc.adsmserv (being in another directory)
you will have another accounting log at different place.
>From TSM for AIX Administrator's Guide (v4.2, p.432):
"Accounting records are stored in the dsmaccnt.log file. The
DSMSERV_ACCOUNTING_DIR environment variable specifies the directory where
the accounting file is opened. If this variable is not set when the server
is started, the dsmaccnt.log file is placed in the current directory when
the server starts."
I prefer to modify inittab line to include init level "a" thus being to
start the server again using 'telinit a'.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: dsmaccnt.log location

Well, sorry to confuse!-- I have 6 different dsmaccnt.logs set up on two
different servers, and I don't remember setting or exporting
DSMSERV_ACCOUNTING_DIR (I didn't reaslise it was a valid env variable). I
wonder I how I got them in the right place.maybe it just followed the
DSMSERV_DIR variables' location?

lisa



Zlatko
Krastev/ACIT To: [EMAIL PROTECTED]
   Subject: Re: dsmaccnt.log
location
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


06/18/2002
01:51 AM
Please respond
to "ADSM: Dist
Stor Manager"






???
DSMSERV_ACCOUNTING_DIR is an environment variable and has nothing to do
with dsmserv.opt.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: dsmaccnt.log location

Set it in the dsmserv.opt file and restart the server.



David E
Ehresman  To: [EMAIL PROTECTED]
Subject: dsmaccnt.log
location
Sent by: "ADSM:
Dist Stor
Manager"
<[EMAIL PROTECTED]
ST.EDU>


06/14/2002
08:16 AM
Please respond
to "ADSM: Dist
Stor Manager"






Enivronment:  TSM 5.1.0 running on AIX 5.1

In my /etc/profile, I have
 "export DSMSERV_ACCOUNTING_DIR=/var/adm/tsm" which should cause the
dsmaccnt.log to be created in /var/adm/tsm.  But it continues to be
created in the server install path, /usr/tivoli/tsm/server/bin.  Any
ideas what else I need to do to get dsmaccnt.log created in
/var/adm/tsm?

David

Re: Do you lob it on or do you fully test before that next release?

[Zlatko Krastev/ACIT]

Dealing mainly with customers that have no test environment our company is
forced to be (very) conservative. That's why I personally recommend to
stay somewhat behind latest versions even for new installs.
Tom is pressed with timeframes. We are dealing with customer's data not
ours. So I am very cautious as he is and prefer to install older version
for which there are no complaints on the list for longer period. At the
same time I cannot install for a customer an unsupported version even if
is more stable :(

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Do you lob it on or do you fully test before that next releas e?

I've got a small test environment toverify base funtionality -- but I
really
cannot stress-test in the test environment, so all I can determine is that
my batch scripts work and that I can backup/restore and archive/retrieve,
and get to previously archived/backed up data.

And then I've a 12-hour window on Saturdays I can slam-dunk in. Once I've
got a production system archived or backed up, I've got no way to back out
to the previous server. I am *not* permitted to discard data.

So I live in fear the first week or so on each new server upgrade, and
that's why I wait until there's a version that other people are *not*
reporting problems on before changing. I'd much rather run something
that's
no longer supported than something that won't stay up but is supported.
Especially since I can count my support calls on the fingers of one hand
and
have fingers left over for any given year.

Tom Kauffman
NIBCO, Inc



> -Original Message-
> From: Seay, Paul [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 21, 2002 12:56 AM
> To: [EMAIL PROTECTED]
> Subject: Do you lob it on or do you fully test before that
> next release?
>
>
> After seeing all the pain everyone is experiencing going from 4.2.2 to
> 5.1.1.  I thought I would ask this question to see what
> everyone is doing.
> We intend to create an entire environment to test the upgrade
> with and then
> actually perform it.
>
> What is everyone else doing?
> What is your server platform?
> How are you handling the SAN client incompatibility issues?
>
> Paul D. Seay, Jr.
> Technical Specialist
> Naptheon, INC
> 757-688-8180
>

Re: Another TSM mystery...

[Zlatko Krastev/ACIT]

Client stores the password in encrypted form. Both encrypted and
unencrypted form were treated as zero-terminated string and from there
comes the bug. If encrypted form contained NULL (\0x00) character
somewhere (not necessarily as first char) it was treated as end-of-string
and the rest of password was ignored. Thus no match and authentication
problems.
Fix was to handle encrypted form as binary array (with \0x00 being
ordinary byte value) and not as string.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Another TSM mystery...

Is "passwordaccess generate" in the dsm.sys (or dsm.opt if NT) for this
client?  If so, it may be a known problem that's been discussed here
before... the client and server will generate a new password periodically,
and it is kept encrypted in a file on the client.  Occasionally, the
generated password will start with a hex '00', which causes that behavior.
I'm not sure if it must start with '00', or only contain it, and I'm not
sure if it's the encrypted or un-encrypted form that contains the '00'...
but we have had this happen, and had to reset the password at the server,
then manually run a client session and answer the password prompt with the
new password...

HTH
Robin Sharpe
Berlex Labs



"Hunley, Ike"
To:[EMAIL PROTECTED]
  cc:(bcc: Robin Sharpe/WA/USR/SHG)
06/17/02  Subject:
05:05 PM Another TSM mystery...
Please
respond to
"ADSM: Dist
Stor Manager"







The TSM server received this message 2 weeks ago, last week and today
ANR0424W Session 39912 for node HOC0843P12 (TDP Infmx AIX42) refused -
invalid
ANR0424W password submitted.

Each time we reset the password, issuing

 UPD NODE nodename pswd PASSEXP=0

which should make this a non- expiring password.

How does a perfectly good password, suddenly invalid(no one made changes
they cared to admit to...)?
What would make a non-expired password expire?



Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect
the views of Blue Cross Blue Shield of Florida, Inc.

Re: 3583 with SDG, Windows 2000 and Qlogic 2200 adapters

[Zlatko Krastev/ACIT]

John,

the answer is that someone have put a SCSI adapter in the box and Windoze
being "so smart" reordered ALL the SCSI/FC adapters. SCSI adapters get
numbered before FC ones thus your QLogic get higher number (6, having 5 in
the past). The other possibility is that there was second SAN switch/plane
installed. Again additional adapter but insertion of FC adapter is
somewhat 50/50% chance - PCI slot numbers are considered which one is
getting lower number. If you are unlucky - new inserted FC adapter gets
HBA #5 and your one moves to HBA #6.
If it was AIX - new adapter will get next *available* device name (scsiX
or fcsY+fscsiY) preserving existing device names.
Keep in mind also another thing to be aware - the SDG module in 3583. If
someone makes SCSI channel to FC port zoning, changing number of visible
drives (for example willing to split each device to separate FC ports)
this may affect \\.\Tape0. And \\.\Tape1 can become \\.\Tape0 leading to
element number mismatch - TSM will refuse to work with the drive.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:3583 with SDG, Windows 2000 and Qlogic 2200 adapters

Hi all

Here's the scenario:

TSM 4.2.1.15 Server on Win2K
3583 with San Data Gateway
2109 Switch

Implemented the solution only to be called back with the library not
responding to TSM. After a closer inspection I notice that the library has
now been renamed by Windows from lb2.1.0.5 to lb3.1.0.6.

So, how is this possible. There have been no hardware address changes made
and I made sure to name the libary and the drives independently of the
windows generic naming ie

lb2.1.0.5 was configured as LTOLIB
\\.\Tape0 was configured as DRIVE1
\\.\Tape1 was configured as DRIVE2

I have read in the Qlogic literature that persistent naming is not
supported which means the binding needs to happen elsewhere. I cant zone
the switch to tightly because I will be configuring SAN agents next and
that means all the SAN attached hosts need access to the library.

Has anyone one out there seen this happening in a SAN environment and how
I can make it go away?


Any help is much appreciated

Rgds
John

Re: 3583 with SDG, Windows 2000 and Qlogic 2200 adapters

[Zlatko Krastev/ACIT]

Gianluca,

unfortunately IBM LTO drives *have* to be installed and used through IBM 
SSG drivers not by using adsmscsi.sys driver. Thus for FC-attached 3583 
the best you can do is what John already have done - use changer through 
TSM-driver and drives through Windows (RSM) driver.
I would be more than happy if opposite was true because there will be no 
room for Tivoli Flash 2.

Zlatko Krastev
IT Consultant

P.S. I've tried to sqeeze this to happen in a "unsupported" configuration 
for a customer three weeks ago but desperately failed. No chance to deal 
with drives through adsmscsi.sys.

Zlatko




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Re: 3583 with SDG, Windows 2000 and Qlogic 2200 adapters

Hi all,

the problem rises from what happens expecially in W-2K environment.
Generally speaking :

1. The HBA maps the WWNs of the fibre devices presented by the fabric to
the SCSI addresses that OS understands: in W-2K environments with Q-Logic
HBAs there is also an intermediate step of mapping WWNs to Loop-ID (by 
HBA)
then to SCSI addresses known by the OS;
  WWNs(Fiber attached devices)> LoopID(Q-Logic HBAs)
-->SCSI Addresses (Host)

2. The ordering of the devices  comes from the sequence represented in the
Name Server Table of the switch: this sequence is the one used by the
QLogic HBAs in W-2K environments to assign Loop IDs;

3, When devices are added, removed , fail or are swapped form a port to
another of the switch, the existing assigned Loop ID and hence the SCSI
address, may change.  W-NT/2K gives \\.\Tapex names are given starting 
from
the lowest SCSI address first and then numbered in ascending order 
starting
from zero; this cause problems when the SCSI address change for any 
reason.

4. the IBM SAN Data GW determines the LUN address of the tape devices
(static SCSI ID to LUN mapping). It adds one more mapping level  to be
considered, but this could not be a problem because when powered up, the
devices are automatically mapped and this mapping will be retained; if
additional devices are added they go to the end without changing the
previous device mapping.

Unfortunately, as you reported, Qlogic doesn't support Persistent Binding
on W-2K environments so it is strongly reccomended to use an alternative
naming convention:

- use device alias name in the form of mtx.y.z.n for all tape devices: 
this
identifies a device explicitly by its SCSI Target ID (x), LUN (y), SCSI 
Bus
Number (z) and SCSI Port on the Host (n);

- this naming convention is used by default on W-2K environments by the 
TSM
supplied device driver (ADSMSCSI).

So try to use this naming convention and the TSM supplied device driver 
for
W-2K environments.

I hope this helps..and good luck!!!









Cordiali saluti / Best regards

Gianluca Perilli



Gianluca Perilli
Tivoli Customer Support
Via Sciangai nœ 53 - 00144 Roma (Italy)



  
  rs6000   
 cc:
  Sent by: "ADSM:  Subject:  3583 with SDG, 
Windows 2000 and Qlogic 2200 adapters 
  Dist Stor   
  Manager"   
  <[EMAIL PROTECTED]   
  .EDU>   
  
  
  22/06/2002 16:42   
  Please respond to   
  "ADSM: Dist Stor   
  Manager"   
  
  



Hi all

Here's the scenario:

TSM 4.2.1.15 Server on Win2K
3583 with San Data Gateway
2109 Switch

Implemented the solution only to be called back with the library not
responding to TSM. After a closer inspection I notice that the library has
now been renamed by Windows from lb2.1.0.5 to lb3.1.0.6.

So, how is this possible. There have been no hardware address changes made
and I made sure to name the libary and the drives independently of the
windows generic naming ie

lb2.1.0.5 was configured as LTOLIB
\\.\Tape0 was configured as DRIVE1
\\.\Tape1 was configured as DRIVE2

I have read in the Qlogic literature that persistent naming is not
supported which means the binding needs to happen elsewhere. I cant zone
the switch to tightly because I will be configuring SAN agents next and
that means all the SAN attached hosts need access to the library.

Has anyone one out there seen this happening in a SAN environment and how 
I
can make it go away?


Any help is much appreciated

Rgds
John

Re: Device locking danger.

[Zlatko Krastev/ACIT]

And have in mind that someone can do it also from ANY MgSysSAN node !!
Thus it would be good to disable 'configure' method for smcN on Storage
Agent systems to prevent device become "Available" and be used from that
box's administrator causing grief to you at the server box.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Device locking danger.

Please note, this may be common knowledge to some of you but I thought I'd
mention it again.

TSM Server can have problems if you are accessing a device like /dev/rmtX
or
a SCSI media changer
/dev/smc0 with tapeutil. You will see in the actlog the server is unable
to
access the device as you
have already initiated an exclusive lock on the device.

Therefore, if you are going to do tapeutil procedures or anything else
that
accesses/queries the devices,
do so when the server is inactive, and DO check it's health afterward and
the actlog for error messages.

We've seen this occur ourselves a couple of times now on TSM 4.2.2.0

Comments?

**
Bunnings Legal Disclaimer:

1)  This document is confidential and may contain legally privileged
information. If you are not the intended recipient, you must not
  disclose or use the
information contained in it. If you have
received this e-mail in error, please notify us immediately by
return email and delete the document.

2)  All e-mails sent to and sent from Bunnings Building Supplies are
scanned for content. Any material deemed to contain inappropriate
subject matter will be reported to the e-mail administrator of
all parties concerned.

**

Re: Adding a second library

[Zlatko Krastev/ACIT]

Stephen,

you already found the *best* answer yourself - yes, set new stgpool as
next to existing one and lower migration thresholds to 0. Just some
additional remarks:
- set the "old" pool(s) as read-only and (optional) set maxscratch=0. This
would prevent nodes to fill the pool while you are trying to drain it to
the next one - might be endless :)
- later when you have time (even it is immediately) change all the
references to "old" pool(s).
Yes, this would also reclaim the tapes but will also recreate the
aggregates. The latter would not be performed if you use 'move data'! And
you should perform "moves" for each tape while migration is automatic
server-driven process.
I hope this sets the line straight.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Adding a second library

I've added a second 7337 library to our ADSM system (15 DLT robot with 2
drives). I've got the system seeing the library, and I have a new
devclass defined with the new library.

What I would like to do is have two of our stgpools (AFS_TAPE_POOL and
COPYPOOL) we have defined use this new library, with the others staying
in the original library. I can't change the devclass on a stgpool with
the update stgpool command, so I'd have to create a new stgpool.

What's the best way to get the data in the old stgpool out of that pool
into the new pool? Should I just set NEXTpool to point to the new pool
and set the migration level to 0%? Then when all the data is moved out
of the original pool delete the pool? (This would give the added benefit
of reclaiming all wasted tape space at the same time)

Steve Cochran
Dartmouth College

Re: One Client Two TSM Server

[Zlatko Krastev/ACIT]

You did not stated what is the client OS. I assume you are talking about
Windows.
The answer is to create two dsm.opt files not two set of binaries. Then
use "dsmc -optfile=". Also you can set -optfile
parameter for a service and install two services with different
optfiles/settings. This is for example how TSM client has to be set-up on
MSCS system. Look for more examples in the Using B/A client manual.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:One Client Two TSM Server

I have installed an TSM Test Server on it so that I can try same things,
but when I want to connect with the command line to the real TSM server I
always change the dsm.opt for the new settings. Is this the only way ? By
the way I thougth about the possibility to  install a second version of
the
TSM Client, but the install process checkes that there is already one
installed.

Oli

Re: TDP for Informix - Average Filesize

[Zlatko Krastev/ACIT]

The answer is - you can't. Sorry. We've discussed this in the past but
with no success. And AFAIK the is no DPI v4.2.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TDP for Informix - Average Filesize

Hi all,
I know, there is the answer in the Archive, but I can't find
it...sorry...
So again the question =>
How can I tell the TDP for Informix (the API) the value for the Average
Filesize
?
When I backup my databases I want to tell the TSM Server, that the
Database/Tablespaces which the TDP for Informix will send, will have about
5
Gigabytes..

All hints are welcome...

Regards
Gerhard Wolkerstorfer

Re: ANR2716E Schedule prompter was not able to contact client...W HY?

[Zlatko Krastev/ACIT]

Ports 1500 and 1501 do *not* need to be bi-directional.
Connection on port 1500 is always initiated from the node to the server.
Connection on port 1501 is always from the server to the node. Just
firewall admin should set them correct.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: ANR2716E Schedule prompter was not able to contact client...W HY?

I agree on adding the actual IP address for the TCPCLIENTADDRESS option.
This is necessary in machines with more than one network card as well.  I
usually query the activity log and search for the node to see what IP it's
actually using to connect to the TSM server.  Then I ask the administrator
to use that IP in their dsm.sys.

Also, if you are connecting over firewalls, ports 1500 and 1501 must be
open bi-directional for communication to take place.

Greg A. Garrison
Account Storage Manager
IBM Global Services, Service Delivery Center - West
9022 S. Rita Road, Rm 2785, Tucson, AZ 85744
Phone (520) 799-5429  Internal 321-5429
Pager 800-946-4646 PIN 6034139
e-mail: [EMAIL PROTECTED]



  "Garrison, Tony"
 cc:
  Sent by: "ADSM:  Subject:  Re: ANR2716E
Schedule prompter was not able to contact client...W HY?
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  07/08/2002 12:25
  PM
  Please respond to
  "ADSM: Dist Stor
  Manager"





I have had this problem with several servers.  I solved the problem on
several by utilizing the IP address in the dsm.opt as the TCPCLIENTADDRESS
instead of the node name.


Tony Garrison
I/T Sr. Systems Programmer
USAA
210-913-9836



-Original Message-
From: Villegas, Beatrice [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 08, 2002 1:59 PM
To: [EMAIL PROTECTED]
Subject: ANR2716E Schedule prompter was not able to contact
client...WHY?


Hi all,

We are running into an issue with several of our AIX servers. Every 1 to 2
days, one of the client servers incremental backup is "missed" or fails
because of:

ANR2716E Schedule prompter was not able to contact client SY using type 1
(10.160.97.213 1501).

I have checked all the obvious:

1.  dsmc sched is running.
2. There are no apparent network problems.

It seems to me that the process: dsmc sched just hangs.
Once I kill it and re-start it, the backup runs fine.

These are my levels: Server: AIX 4.3.3 ML10 TSM 4.2.1.7
   Client: AIX 4.3.3 ML8 TSM Client 4.2.0.0

Anyone has any ideas of what could be wrong? Is this a known problem?

Thanks in advance,

Beatriz

Re: TSM 4.2, Private won't go into scratch

[Zlatko Krastev/ACIT]

1. Ensure expiration is happening - if expiration interval in 'q stat'
output is 0 there must be admin schedule for 'expi inv'.
2. 'q stg  f=d' will show you the reclamation
threshold. It usually has to be 60-70 (%). If is 100% reclamation will
never start.
3. compare the percentage in 'q vol' against the threshold from p.2 and if
necessary lower the threshold with 'upd stg  recl='
And do not search yourself, there are computers for that (and search
functionality in help). Just find time to read redbook SG24-4877.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TSM 4.2, Private won't go into scratch

Hi everyone. I have a concern.
Maybe I should RTFM, but don't have enough time to search.
I have a following concern:

Magstar 3575-L12 and 40 tapes currently in slots. I backup everyday
54GB, which occupies 5 - 7 tapes. I set in backup mgmt class number of
copies to keep 2 whenever they have been deleted or not. (retain extra
and only version are set to 2 as well). I've set backup retention to 7
days.

The collocation is 'yes'
The problem is, that the tapes won't go into scratch, it looks like the
reclamation process won't start.
What should I check?
Thanks in advance...
zee

Re: Server partitioning using TSM library sharing

[Zlatko Krastev/ACIT]

Scott,

you hit the bullseye - the main problem would be volumes. But not only
ones used by single (deleted) node. The ones used by two nodes might be
bigger problem. Let say volume CBA321 hold the data for both nodeA and
nodeB, who will be the owner of the libvolume? Collocation is the key - so
you met an important prerequisite :)
Later you should not have problems - once libvolume (note!) is updated to
be owned by server-B, server-A ought not to change its status to scratch
even if is library manager. On filespace deletion data will dismiss from
*volume* and it would be deleted from the pool. But libvolume will be
owned by other server (which knows there is data) and the status would not
change.
Of course you can set maxscratch=0 on pools as insurance but this would
affect normal operations (if your server is so big to force splitting it
would not stay idle for long and "filling" tapes quickly will become
"full" ,-) and will not give too much additional security.
Also I would add a step "0.9 ) Update all volumes to read-only." and move
step 7 before step 4 to minimize disruption of service to nodes associated
with server-B.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Server partitioning using TSM library sharing

Hello fellow TSMers,

We have a fairly large TSM server that we are planning to partition into 2
servers. In other words, add a second server and split the client nodes
across the two.

The hardware environment is two AIX TSM servers, both fibre attached to a
10 drive 3494 ATL.

What I am proposing to do (and looking for input) is as follows:

1) Restore a copy of TSM server-A's database to the new TSM server-B
2) Reconfigure the library and drive configuration on TSM server-B to be a
library client to the shared library manager server-A.
3) Identify the nodes that are to be associated with each server.
4) Identify the volumes associated with the nodes for each server (Storage
pools are currently fully collocated by node).
5) Run update libvol to change the owner on the appropriate tapes to be
owned by server-B.
6) Delete the filespace and node definitions for the nodes NOT associated
with each server.
7) Reconfigure half the nodes to point to the new server-B.
8) Pat myself on the back and take the rest of the day off :-)

It seems too simple  Has anyone done this before? (hard to type with
my
fingers crossed)

The big question of course is: what happens to volume ABC123 on server-A
when the filespaces are deleted and the volume empties, gets deleted from
the storage pool, and returned to scratch? Server-B still thinks there is
data on that tape and this proposed solution would only work if he was
allowed to request a mount and read that volume.

Any and all feedback is appreciated!

Scott
Scott McCambly
AIX/NetView/ADSM Specialist - Unopsys Inc.  Ottawa, Ontario, Canada
(613)799-9269

Re: TSM and MS Exchange (MailBox Restore and Exchange 2000 Improvements)

[Zlatko Krastev/ACIT]

Tony, could you explain a bit more. I am somewhat confused.
You (instead of CA?) "fought" to fix Arcserve agent for 8 months??? Was it
so broken? What means 95% operational, what are the rest 5%, what was the
percentage before those 8 months? And what on the end is "tolerable",
something you still did not got fixed?
TSM does NOT do brick level restores because Microsoft does not do it -
the backup APIs are for information stores. Other vendors are attempting
to use messaging APIs and DO NOT restore messages but create new ones with
same content. This was explained on this list many times.
There was something in one of the discussions remark that Microsoft (not
Tivoli) is planning to enhance/modify their APIs. But if Microsoft does
not provide an API for mailbox restore then Tivoli simply would not do it.
There is a joke about a gynecologist who painted a room through key hole.
But I would not accept all rooms in my office to be painted using this
technology and with that speed.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: TSM and MS Exchange (MailBox Restore and Exchange 2000 Improv 
ements)

Actually, we are using Arcserve 2000 to backup Exchange5.5 on W2K
member serves. We fought Arcserve for over 8 months to fix their agent and
it looks like they have it 95% operational and tolerable.  We are seeing
through=put speeds of up to 100mb/minute. We are backing up servers with
databases of up to 15gb. All-be-it we are using old DLT4000 technology,
the
backups are getting done and we have been able to restore peoples
individual
folders (i.e. sent items, inbox, etc...)

Now I have heard that TSM might be doing this in version 5.1x, I do not
know
how true this is, but I now they DO NOT do it now...

Hope this helps
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 8:24 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM and MS Exchange (MailBox Restore and Exchange 2000
Improv ements)


Define what mailbox means to you.  If you are talking about the calendar
and
other little goodies including public folders, none do that except maybe
CommVault.  And, I do not think they can do the public folders.

The thing that Veritas and Arcserver created are for marketing only and
really are so slow you can only use it for a few select mailboxes.

None replace the normal exchange backups that you have to do to be able to
recover the exchange stores.

I found out just yesterday that Exchange 2000 has a reserved area you can
restore an information store to.  Once you have done that you can truly
recover a mailbox and its contents.  This was Microsoft's answer to the
problem.  But, Exchange 2000 requires active directory and other hurdles
to
get there.  However, my Exchange boys point out you must not put any
mailboxes you might want to recover in the "base" information store
because
that one cannot be restored to the reserve area.  That one has all the
exchange specific extensions to active directory.

Paul D. Seay, Jr.
Technical Specialist
Naptheon, INC
757-688-8180


-Original Message-
From: Consiglio, Tony [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM and MS Exchange


We have not moved to version 5.1x yet, but we are on version 4.2.2x and
the
answer is most definitely not! There are only 2 other outside vendors that
back up bricks, 1.) Veritas 2.) Arcserve2000

The only way to do individual folder recovery (i.e. Inbox, or Sent items,
etc..) is to export to a PST file then back up that file.

-Original Message-
From: McMullen David E [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 10:43 AM
To: [EMAIL PROTECTED]
Subject: TSM and MS Exchange


We are evaluating TSM here and a question came up with regard to TSM and
Exchange.  Will TSM backup and restore individual mailboxes?

TIA

David McMullen
SMC/LAB Support
512.460.4559

Re: Restoring MSCS cluster node

[Zlatko Krastev/ACIT]

Full "bare metal" can also be assumed as restore with disk replacement. So
look at MS KB article Q243195.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Restoring MSCS cluster node

Hi.

Has anyone got an idea how to perform "bare metal" restore of MSCS
cluster node (win2k, winNT)? I have performed a lot of tries to do that.
Sometimes it succeeds sometimes doesn't. According to the redbook
sg24-6141 "Deploying the TSM client in a win2k env" I restored ALL
system object including cluster db but cluster services were not running
(of course) and restore failed. So I restored system objects except
cluster db (first time it succeeded).

If you know any better redbook than above or if you have any
experience
in it please HELP ME!



--

--== KKus ==--

Re: Web Admin Interface - grrr

[Zlatko Krastev/ACIT]

The thread was initially for web admin but my vote definitely goes to CLI 
(I had not the chance to work with ADSM 3.1 so am not familiar with GUI).
I am another person using *only* CLI. Being at customer site when someone 
opens web interface for TSM administration I use again only its CLI 
functionality. Even do not know what is where in web interface.
My day-to-day operation uses just two CLI sessions - one in consolemode 
and second for entering commands. Command line editor helps enough and I 
am not afraid to type single command with 2-3 lines of parameters. Only 
one problem till now - telnet clients do not handle "Insert" key correctly 
so I have to retype rest of the line when something is inserted (AIX 
dsmadmc through telnet). CLI using X Windows or local admin client do not 
have this problem.
And I would be happy if someone may point me to a method for automating 
TSM operations using WebAdmin (without CLI). So if you want to automate 
your repetitive tasks you for sure will need CLI knowledge. Why then to 
waste efforts learning web admin.
As on Andy's signature - "Command line is your friend".
My opinion does not bind anybody except me.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Re: Web Admin Interface - grrr

Web admin,

what is that. I (and so do my coworkers) only use the command line
interface. The web interface just isn't good enough. I feel the same way
about the "good old gui". I had some bothers with listing the volumes with
the gui's. It would take to long, while the cli returns the query in an
instance.
One other thing is that the web interface tends to time-out while were are
doing some processing. I would like to see the web-timeout-feature out to
only count the idle time in stead of total time.

Anyway, CLI works best for me.


Ilja G. Coolen


ABP / USZO 
CIS / BS / TB / Storage Management 

Telefoon : +31(0)45  579 7938 
Fax  : +31(0)45  579 3990 
Email: [EMAIL PROTECTED]
Mailbox  : Centrale Mailbox - BS Storage (eumbx05)
Intranet : Storage Web
 
 

 
- Everybody has a photographic memory, some just don't have film. - 

-Oorspronkelijk bericht-
Van: Rupp Thomas (Illwerke) [mailto:[EMAIL PROTECTED]]
Verzonden: maandag 12 augustus 2002 18:45
Aan: [EMAIL PROTECTED]
Onderwerp: Web Admin Interface - grrr


Hi TSM-ers,
 
Our Network Storage Manager (NSM - 3466) was just upgraded from 4.2.1 to
4.2.2.8.
Now the format of the QUERY SESSION from the lefthand tree OBJECT VIEW /
SERVER /
SESSION has changed from FORMAT=STANDARD to FORMAT=DETAILED.
 
Instead of one line per session I get now 12 lines. That makes it 
impossible
to see what's
going on (?$%&?)
 
How can we convince Tivoli to create a useful administration interface (be
it GUI or a Java Applet).
Am I the only one who has problems with the admin interface and still
running the old
3.1 Windows GUI?
 
Kind regards
Thomas Rupp
Vorarlberger Illwerke AG
MAIL:   [EMAIL PROTECTED]
TEL:++43/5574/4991-251
FAX:++43/5574/4991-820-8251
 
 
 

--
Dieses eMail wurde auf Viren geprueft.
 
Vorarlberger Illwerke AG

--

Re: Anybody using TDP for Informix on aix v5.1 64bits ?

[Zlatko Krastev/ACIT]

The error is resulting from the major change made to 64-bit environment
between AIX 4.3 and 5L.
Look at IBM Announcement Letter ZP02-0172:
"IBM Tivoli Storage Manager for Databases
...
-   Tivoli Data Protection for Informix Version 4.1 for AIX
...
--  AIX 4.3.3 (32-bit or 64-bit) or AIX 5.1 (32-bit) "
I know this does not help much.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Anybody using TDP for Informix on aix v5.1 64bits ?

Hi *SM'ers !

I'm having trouble trying to backup an Informix database (Informix server
9.30 fc2x5 64 bits) which is installed on an AIX machine (aix 5.1 64 bits)
: I cannot find a TDP for Informix client that works on such a system. On
Tivoli's web page there is no information about an eventual release
supporting aix 5.1 64 bits for this client, and I was wondering if anybody
founded a trick  to perform Informix backups in that kind of environment.
I already tried with a TDP for Informix aix43.64bit.4.1.3.0 client, but
always get an infamous "An unexpected error occurred:  Could not load
module /usr/tivoli/tsm/client/informix/bin/bsashr10.o.The program is a
discontinued 64-bit object file." message :-(
Anybody having a clue ?
Thanks in advance !

Arnaud
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01   |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Upgrade from 3590E to 3590H

[Zlatko Krastev/ACIT]

Actually the steps are just the same as for migration from 3590B to 3590E.
IBM CE will perform the upgrade and you will do the rest.
The latter is well documented and you can also find plenty of info in list
archives (http://www.adsm.org/).

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Upgrade from 3590E to 3590H

Hello, everyone.

Platform: IBM pSeries 6M1
OS: AIX 4.3.3.10
TSM: 5.1.1.1
Atape: 7.0.7.0
atldd: 5.0.7.0

I am getting ready to perform an upgrade from 3590E to 3590H drives in
my 3494.  Each of the 6-drives is directly fiber-channel attached to the
TSM server.

Has anyone gone through an upgrade such as this?  If so, can you share
you experience with me?  I guess, what I am looking for is the steps in
TSM and AIX that I need to go through to successfully do this.

TIA

Mahesh

Re: IBM vs. Storage Tek

[Zlatko Krastev/ACIT]

My personal recommendation is to evaluate upgrade to 3590H. I am surprised
why this is not the IBM's first proposal. Arguments:

LTO definitely is downgrade to what you have now both in terms of
performance and reliability as others already answered. Higher capacity
per volume and much lower price are main advantages. Former will soon
change while the latter will never change.
For large data streams native rate of LTO (15MB/s) is higher than for 3590B (9MB/s) 
and slightly above 3590E/3590H (14MB/s). Utilizing different
compression algorithm on compressed data the rate of 3590B (27MB/s) is
comparable to LTO (30MB/s) while 3590E/H definitely outperforms it (42MB/s). But for 
smaller files you have to count also mount time and there 3590s are more than two 
times faster than LTO. With LTO is much
harder to get some benefit from filespace collocation while this can help
in many cases with high-end tape drives.
Reliability of LTO is not bad but cannot compare to 3590/9x40.
Bigger volume ought not be such a problem for reclamation - it should be
nearly the same would you reclaim 3 volumes 100 GB each or 30 volumes 10
GB each for same average percentage.
If LTO gets damaged you for sure will have to restore much more. But this
is true whenever you go to *any* higher capacity technology - just the
same for 3590E/H or 9940.
Same remark for collocation - it is not related to technology but only to
capacity of the cartridges. There are two ways to prevent it - stay with
(older) lower capacity technology or limit maxscratch forcing more than
one node's data to be put on a volume. And you can always define several
pools with different maxscratch settings so it ought not be a big problem.

Upgrade to 3590H would be more expensive than brand new LTO but you will
get much better product. All remarks about performance and reliability
ought to be enough to justify higher price. You will not be forced to get
rid of those 5500 cartridges and buy new LTO ones. You will get 60 GB per
tape as from 9940A. SAN-attachment also is not a problem with fiber drives
and dual-ports (vs. single ported LTO) add to reliability.

StorageTek silos with 9840/9940 drives are very good products. If we want
to compare apples with apples we have to compare them with IBM 3494 + 3590B/E/H 
drives. Comparison with DLT or LTO would be apples vs. oranges. So the statement "it 
costs twice" returns nothing useful. Count again the
need for new 9x40 cartridges and plan what will do with old 3590 ones.
But for me this would be replacement of Mercedes with Cadillac - both are
very good, both are very expensive and both give the same results with
different vendor's approach.


Zlatko Krastev
IT Consultant





Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:IBM vs. Storage Tek

Hello,

I know I've asked about this before, but now I have more information so I
hope someone out there has done this.  Here is my environment for TSM.
Right now it is on the mainframe and we are using 3590 Magstars.  We have
a
production and a test TSM server and each has about 13 drives and a total
of 5,500 tapes used for onsite and offsite tape pools between the 2
systems.  Two scenarios are being considered (either way TSM is being
moved
onto our SAN environment with approximately 20 SAN backup clients and 250
LAN backup clients and will be on SUN servers instead of the mainframe)
Here is what I estimated I would need for tapes:

 3590 9840 9940A LTO
 10 GB 20 GB 60 GB 100 GB
Production
Onsite1375 689  231  140
Offsite   1600 800  268  161
Total 2975 1489 499  301

Test
Onsite963  483  163  101
Offsite   1324 664  223  135
Total 2287 1147 386  236

Grand
Total 5262 2636 885  537

1. IBM's solution is to give us a 3584 library with 3 frames and use LTO
tape drives.  This only holds 880 tapes and from my calculations I will
need about 600 tapes plus enough tapes for a scratch pool.  My concern is
that LTO cannot handle what our environment needs.  LTO holds 100 GB
(native), but when a tape is damaged or needs to be reclaimed the time it
takes to do either process would take quite some time in my estimation.
Also, I was told that LTO is good for full volume backups and restores,
but
that it has a decrease in performance when doing file restores, archives
and starting and stopping of sessions, which is a majority of what our
company does with TSM.  Has anyone gone from a 3590 tape to LTO?  Isn't
this going backwards in performance and reliability?  Also, with
collocation, isn't a lot of tape space wasted because you can only put one
server  per volume?

2. STK 9840B midpoint load(20 GB) or 9940A(60 GB) in our Powderhorn silo
that would be directly attached to the SAN.  From what I gather, these
tapes are very robust like the 3590's, but the cost for this solution is
double IBM's LTO.  We would also need Gresham lice

Re: Eternal Data retention brainstorming.....

[Zlatko Krastev/ACIT]

Very well written !!!
May I slightly improve it:
1. Mark diskpool volumes read-only. Migrate disk pools and mark all
primary volumes read-only (or only ones which do not have copypool
backups). Check out all read-only tapes.
2. Like your step 1 but take only one db backup. The rest as described in
several copies. Do not forget OS and TSM documentation CDs (five years
later several investigators were changed and none of them knows what TSM
is and how to beat it - let them RTFM).
3. Mark diskpool volumes back to read-write.
4. Set up a test server. Disable expiration, restore the (only) DB backup,
modify all mgmtclasses/copygroups/stgpools. Mark primary tapes (of
backed-up "important" stgpools) unavailable. Backup the DB.

If cannot afford additional cartridges or investigation is supposed to be
short-term - make few more DB backups; set reuse delay on production
server's pools to . "Non-important" primary volumes and "important"
copypool volumes hold the data for both production and "investigation"
servers. Sit and wait this to finish sooner. Skip steps 5-10, ensure step
11 is done and do not dream about step 12.
If forced to keep the data long-term regardless the price:
5. Backup to copypool(s) even the "non-important" (non-backed up) storage
pools. Check-in (read-only) primary volumes in production server's library
and mark back to read-write (in production DB) for normal day-to-day
operations.
6. Mark all primary volumes unavailable and restore primary pools on the
test server (it now became DR test server :).
7. Return (production) copypool volumes to vault for normal DR. Delete
volumes from DR test server and backup all affected pool to make copies
for "investigation" DR.
8. Make additional copypool copies if necessary for very-long-term data
retension.
9. Backup the DB several times.
10. As your step 2.
11. Get signature from Legal as Tab pointed that he/she understands how
TSM is working and will not bother you to downgrade the production server.
12. Sit back and relax - you've done the task and covered your aZZ :)

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Eternal Data retention brainstorming.

What kind of shelf life are you expecting for your media?  Since they've
discovered that optical has data decay, it's not even "forever"!  I've
seen
some others on the list point at it, but how will you restore this data in
10 years?

Here's what I'd look at doing:

1.  Take about 5 dbbackups (or snapshots) and send them to the vault. Take
a few OS level backups of your server (bootable tape images).  Send them,
too.  Send volhist, devconfig, a prepare file, TSM server and client code,
OS install code, everything else that makes your environment your
environment, including the clients, offsite.  This is DR - in the most
extreme sense of the term.
2.  Box up the vault.  Seal the boxes, leave them there.
3.  Start marking offsite volumes as destroyed (or just delete them) in
TSM, and run more Backup Stgpools.  They'll run longer, as you're
recreating the old tapes.
4.  Go back to step 1 and repeat once.  If this data is really that
important to have forever, make sure you can get it back!
5.  Start sleeping - you're going to be WAY behind on that!

Now, for the people making the requirement - they need to get a contract
to
have accessible like hardware to do the restores to.  Not just the TSM
server and tape library, but the clients, too.

Having the data available is one thing, being able to restore it is
another.

Nick Cassimatis
[EMAIL PROTECTED]

Today is the tomorrow of yesterday.

Re: TSM and protocol converters

[Zlatko Krastev/ACIT]

IBM SAN Data Gateway supports IBM 3575. You can attach both 3575s to same
SDG.
For 3583 there is SDG module with 4 LVD ports which is field installable
in the library (as an upgrade). It is cheaper than standalone product and
does not occupy additional space.
Both standalone and module versions are supported from hardware and
software (TSM) point of view. And I personally had no problems with them.
For TSM 4.1 you will have to replace SCSI TSM driver with FCP+SCSI one
(which is well documented). For v4.2 and v5.1 there is no SCSI-only driver
fileset.
I do not know "TSM supported" FC/SCSI converter for HP DLT 4/40 but any
which works with the library ought to work with TSM (statements on Tivoli
site are somewhat fuzzy on this topic).
Have in mind two issues:
- not every SAN component is compatible with any other SAN component. For
example IBM SDG (Pathlight) will for sure work with IBM 2109 (Brocade
Silkworm) switches but AFAIK will not work with McDATA or Inrange
Directors.
- number of necessary FC adapters - 4 LTO + 2x4 3570 + 4x DLT ~= 288 MB/s
with compression. So you will need at least 3 FC adapters.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TSM and protocol converters

I'm spec'ing a new TSM server.  To avoid having to spend a fortune on a
huge server just to get the I/O slots I need to support HV Diff SCSI, I'm
thinking of using protocol converters to reduce the number of I/O slots in
the new server.

In other words, the server would provide Fibre Channel or Gigabit E or
even LV Diff SCSi but I would connect my existing libraries via their HV
Diff SCSI interfaces, with the protocol converter in the middle.

Assuming this is technically feasible (and I know there are FC to SCSI
converters) would TSM work in such an arrangement?  What would change
relative to simply plugging in a SCSI cable into the server as I have now?

Server is "pSeries" or RS/6000; TSM is currently 4.1 but the new server
would (very soon) enter service at 5.1.

Thanks in Advance,

Tab Trepagnier
TSM Administrator
Laitram Corporation

Re: Changing tape drives

[Zlatko Krastev/ACIT]

Two simple steps:
1. create manual library and (the only :) drive for the standalone drive
2. update device class to point to new library - UPD DEV 
LIBR=
Steps are very well described in the TSM docs.
If you have problems with these post again to the list.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Changing tape drives

Hello,

does anybody have a short howto on configuring drives/tapes/libraries?
I had a DDS3 tape Library with 6 tapes which is currently under repair and
i
now have to restore data from a normal DDS3 tape which i kept as a backup
;-) drive.
I messed around for some time but can not get it to work. Does anybody
have
a quick list with steps to do to deconfigure and configure drives?
Kind regards
O. Oexmann
P.S.: I have to do this an a windows machine..

--
| Media Support Group GmbH   |
| O. Oexmann |
| Maarweg 149-161|
| D-50825 Koeln  |
| phone +49 221 3091-567 |
| fax   +49 221 3091-569 |
| mailto:[EMAIL PROTECTED]   |
| http://www.media-support.de|
--
| No electrons used in the   |
| production of this message were|
| harmed or mistreated in any manner |
--





O. Oexmann.vcf
Description: Binary data

Re: Restore filesystem to directory on AIX-client

[Zlatko Krastev/ACIT]

# dsmc -virtualnodename=
dsmc> restore {/home}/* /tsmarchive/ -su=y

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Restore filesystem to directory on AIX-client

Hello,

Server AIX 4.2.x , Client AIX 4.2.1.x

Long time ago we back-up AIX-client file-systems from one particular
client,
like /home, /usr, /u01, /u02 and so on. The system was out of service for
a
few months and now back in business. The last active versions are still on
our TSM-server and we like to restore them (for some reasons) to a
directory
on another machine.

We want to restore to file-system '/tsm_archive' to directory
'/node_archive'. We start the restore of the above-mentioned file-systems
to
the following location:  /tsm_archive/node_archive and like to restore the
complete path.

We tried several ways but every session is restoring the files in /home,
/usr and so on to /tsm_archive/node_archive, but without directory /home,
/usr and so on. Sub-directories are restored in the right way. I guess it
have to deal with the fact that /home, /usr, /u01 and so on were
file-systems once and now we like to 'see' it as a directory. I accept it,
but is there a sneaky way to restore the file-system to a directory and
preserve the original structure.

Thanks,

Brian.

Re: Moving tivoli's database (UNIX)

[Zlatko Krastev/ACIT]

Your calculator is fine but it would be a hard job.
- DB volumes occupy ~6GB (6000 MB not 6144), DB is assigned to 4000 MB of
which 1304 are not used. Total used space (without spare room for
anything) is ~= 2700 MB.
- rootvg is having 1376 MB in unallocated partitions (the line from `lsvg
rootvg`),  / filesystem is having 1.3 GB free and /usr can be reduced with
more than 0.55 GB. I do not know why they have grown so much but can be
reduced only by re-installing AIX on the node (from mksysb for example).
Look carefully at /usr usage - uninstall of some never-used html filesets,
CDE (if not used), many unnecessary devices.* filesets, etc. can give you
much more space. Also commit of filesets would also free some space. Look
in `lslpp -L` in detail and you probably will find something to uninstall.
So if reduction of rootvg usage in "another story" suceeds it would be
possible to put DB in rootvg.
BUT (!!!) it would fit without mirroring (except if / and /usr are
mirrored now). It is possible if you have only one disk in wide node to
put second one (as David pointed wide nodes have room for two internal
disks). Other option is to replace disks with bigger ones during AIX
re-install (or no re-install if are big enough).
TSM unload/load DB can recover additional 450-490 MB ( (1024-575 pages) *
4kB = 1796 MB not used; 1796 - 1304 = 492 MB from reorg).
Conclusion: 2300 MB used (575 000 pages) can fit in rootvg freed space
(1376 + 1382 +  553 = 3311 MB) only without mirroring and with enough
space for minor DB expansion. If / and /usr are mirrored their reduction
will give enough for very tight DB fit ( (1376 + 2x1382 +  2x553) / 2 =
5246 / 2 = 2623 MB).

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Moving tivoli's database (UNIX)

Unless my calculator has slipped a decimal point, it won't fit
with a shoehorn and a big hammer!  Need 6GB + for your DB.
Also what happens if you do an AIX or PSSP upgrade?  No room!!!

It's not considered good TSM practice either even if it would fit.
Just guessing that this is a "wide node" and you have 2 internal disks
for rootvg, then you can add two more for the DB by itself.  Get two
and big enough for expansion.  You should use mirroring but TSM
mirroring not AIX mirroring.  There have been a few discussions on
this in the past as it provides more protection.

If no room internally, then either tell them you need some other
external disks or stay on EMC!  Don't put your DB on some cheap
disk nobody else wanted for their system.

David Longo

>>> [EMAIL PROTECTED] 08/21/02 05:30PM >>>
Hi all - it's me again...

Environment:
SP Model 9076 (1 Frame w/ 7 nodes)
AIX 4.3.3 ML8
P.S.S.P 3.2
ptfset 8
TSM 4.1.5

Currently our TSM database resides on mirrored EMC disks - I have been
instructed to move TSM's database (yes, just the database) into the
rootvg.  Does anyone have any ideas on how I can do this?

Also, and perhaps more importantly - our rootvg only has approx 2GB avail
(I've been instructed to "reduce" /usr to give it another .5GB - but
that's another story)...so when I get done we'll have approx 3GB free in
rootvg...however, I think our TSM DB is too big for rootvg to begin with.
??  Could someone please review the enclosed info and let me know what you
think?

Thanks in advance for your time;
Theresa

Filesystem Info:
Filesystem1024-blocks  Free %UsedIused %Iused Mounted on
/dev/hd4  1523712   1382308   10% 3457 1% /
/dev/hd2  3637248553124   85%79072 9% /usr

lsvg rootvg:  FREE PPs:   86 (1376 megabytes)

q db info:

  Available Space (MB): 6,000
Assigned Capacity (MB): 4,000
Maximum Extension (MB): 2,000
Maximum Reduction (MB): 1,304
 Page Size (bytes): 4,096
Total Usable Pages: 1,024,000
Used Pages: 575,056
  Pct Util: 56.2
 Max. Pct Util: 58.6
  Physical Volumes: 3
 Buffer Pool Pages: 32,768
 Total Buffer Requests: 34,510,747
Cache Hit Pct.: 98.87
   Cache Wait Pct.: 0.00
   Backup in Progress?: No
Type of Backup In Progress:
  Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 35.52
Percentage Changed: 1.58
Last Complete Backup Date/Time: 08/21/02 09:40:14




q dbvol info:

Volume Name (Copy 1): /tivoli/db/dbb.dsm
 Copy Status: Sync'd
Volume Name (Copy 2):
 Copy Status: Undefined
Volume Name (Copy 3):
 Copy Status: Undefined
Available Space (MB): 2,000
Allocated Space (MB): 2,000
 Free Space (MB): 0

Volume Name (Copy 1): /tivoli/db/dbc.dsm
 Copy Status: Sync'd
Volume Name (Copy 2):
 Copy Status: Undefined
Volume Name (Copy 3):
 Copy Status: Undefined
Available Space (MB): 2,000
Allocated Space (MB)

Re: ANS1312E Server media mount not possible

[Zlatko Krastev/ACIT]

Usual reasons were already explained but there is another one I had
recently:
A node is using client compression with large number of threads (16-20).
Each thread is allocating some space in disk pool and starts
reading+compressing the data. If space is very close to *compressed*
ammount of data to be stored few last started threads attemted tape
writes. Space was not enough to be allocated and first threads were not
finished compressing to reduce allocation with actual size. From there
came some tape mount requests.
The case was:
- 600 GB Oracle DB spanning more than 20 filesystems
- data files of 1,2 or 4 GB
- compressed usage was about 130-150 GB
If we had less than 160-170 GB in disk pool we've seen occasional tape
mount requests close to end of backup. Compression ratio highly depends on
data contents and we cannot blame TSM for being unable to predict
precisely.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:ANS1312E  Server media mount not possible

I assume that "ANS1312E  Server media mount not possible

Explanation:  Server media mount not possible. The server timed
out
waiting for a mount of an offline volume." refers to mounting a
sequential acess media?  If my assumption is correct, under what
conditions should a backup process request a server media mount?

I am getting ANS1312E for a node which goes to a disk storage pool
which has a max size threshold of NOLIMIT.  I would not expect it ever
to request a server media mount.

Any ideas?

David EHresman

Re: Restoring Data - Server doesn't exist anymore.

[Zlatko Krastev/ACIT]

Wanda,

not always you should reset the node's password. Invocation with
-virtualnodename asks for ID and defaults to that node's name. Type there
an administrator's ID (from 'q admin') with enough rights over the node
and later enter administrator's password. Session is established but
node's password is not touched even being unknown - just like what we get
with UNIX su command.
This I use for test restores of live node's data or when we expect the
node to become back in service.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Restoring Data - Server doesn't exist anymore.

Not to worry, this is easy:

Change DEAD client's password to something you know, if you don't know
already.

You will have to a restore to a Wintel machine that has the TSM client at
4.1.2.12 or higher.

Start the TSM client on the destination machine this way:

CD into the tsm/baclient subdirectory
dsm -virtualnodename=DEADCLIENTNAME

This is a way of telling TSM that you are masquerading as the DEAD client.
You will be prompted for the password of the DEAD client.
The file tree that you see, will be the DEAD client's file tree.

You will have to specify a RESTORE TO destination for every restore, even
if
the directory name on the destination machine is the same as the original
directory on the DEAD machine.  (Because if you tell TSM to 'restore to
original location', it tries to find the directory based on the original
UNC
name, which won't match.)

That's all there is to it!


Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert







-Original Message-
From: Pearson, Dave [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 2:22 PM
To: [EMAIL PROTECTED]
Subject: Restoring Data - Server doesn't exist anymore.


Hi all,  I have never done this and your help would be greatly
appreciated.

We have TSM Server V4.2.1.7 on AIX 4.3.3 and TSM Client V 4.1.2.12
was on Window NT

The Window NT box does not exist any more.  Been gone for a month.
We usually keep the TSM Client node and backups for a couple of months
before we blow them away. Now someone came to us and said they need info
from the non-existing NT box.  We still have the backups on TSM.

How can I restore the data that is needed from the nodes and
backups
without the old NT box?

Thanks for any help can give me

Dave Pearson
System and Network Service
425.347.4420
[EMAIL PROTECTED]

Re: TSM reads tar/cpio data tape ?

[Zlatko Krastev/ACIT]

You already got the answer yourself. Neither tar & cpio can read each
others data nor TSM can read tapes created by them. Each program is using
own tape data format and cannot interpret other formats.
Have in mind TSM will store the "temp directory" path and filesystem path
info. Also you cannot restore first tape, backup to TSM, cleanup the dir,
restore second tape and backup to TSM. On second backup TSM will expire
data from first tape and soon you will lose it.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:TSM reads tar/cpio data tape ?

Hello TSMers,

I have a questions about TSM.  Is TSM able to read data directly from tape
that use TAR or CPIO to backup ?  What I would like to do is:  put a tape
into tape drive and the tape contain data that I use tar or cpio.  TSM
will
be able to read the data and put these data into storage pool directly.  I
think it can't be done and one has to restore it to temp. directory and
backup using TSM, right ?

It is because TAR & CPIO was being used for backup before TSM but I want
those data back and put it in TSM.

Thanks & Regards
William

Re: Backup of 300 GB Data within 12 Hours

[Zlatko Krastev/ACIT]

SAN for sure would help.
We made a server for customer to backup 600+ GB Oracle DB with TSM client 
compression for 5 hours over Gigabit Ethernet. SAN-attached LTO can be 
even better but you have to use tape drive compression, not TSM client in 
such case.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Backup of 300 GB Data within 12 Hours

Hi,

what is your opinion about backing up or restoring 300GB data with TSM
within 12 hours from one client? Possible or not? Do I have to use a SAN
that I get acceptable transfer rates? If there is anybody out there who
backs up such a big amount of data:

How is your "TSM"-area constructed? (e.g. Server-type, LAN, SAN ...)

MfG
Sascha Bräuning


Sparkassen Informatik, Fellbach

OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach

Telefon:   (0711) 5722-2144
Telefax:   (0711) 5722-1630

Mailadr.:  [EMAIL PROTECTED]

Re: Antwort: Re: cache hit rate

[Zlatko Krastev/ACIT]

Sascha,

This rule is for UNIX servers (AIX, Solaris, HP-UX). You can find where 
the rule originates from - in redbook "Getting Started with Tivoli Storage 
Manager: Implementation Guide" (SG24-5416-01) on p.270 you can find a 
description
"Tivoli Adaptive Algorithm:
Tivoli Storage Manager can use the SELFTUNEBUFPOOLSIZE YES parameter in 
the server options file to activate self-tuning. When you activate this 
option, the server will check the cache hit ratio each time inventory 
expiration is run. If the value is less than 98%, then it will increase 
the BUFPOOLSIZE by a predictable factor related to the actual cache hit 
ratio achieved. An upper limit for BUFPOOLSIZE with self-tuning is imposed 
of 10% of the real memory for AIX, HP UX, Sun Solaris and Windows NT, and 
50% of the region size in OS/390. If you still need a larger BUFPOOLSIZE 
and it is acceptable in your environment, you will have to set the value 
manually."

And because your question was about OS/390 TSM servers the correct answer 
ought to be 50% of the TSM server region. If 49152k is 10% of the region 
size then the correct answer probably is 245760k. Of course if 49152 is 
10% of total memory of the mainframe then the region is smaller and 
bufpoolsize must be too.
In fact you are achieving 97.7% with only 32 MB so 48 MB might be enough 
to get over 98%. Many people on this list reported that 
SELFTUNEBUFPOOLSIZE served them well and it might be worth to try it 
yourself.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Antwort: Re: cache hit rate

Hi,

an IBM Technician gave me the following rule:

bufpoolsize = 10% of your memory.

I think 49152 is ok ...

MfG
Sascha Bräuning


Sparkassen Informatik, Fellbach

OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach

Telefon:   (0711) 5722-2144
Telefax:   (0711) 5722-1630

Mailadr.:  [EMAIL PROTECTED]

Re: Question about log file

[Zlatko Krastev/ACIT]

Lindy,

you can read a nice redbook called "Tivoli Storage Management Concepts"
(SG24-4877-02) which would help you to understand all those magical TSM
terms. It can be found on http://www.redbooks.ibm.com/
The book is ideal for newcomers in TSM world and even people having lots
of experience with TSM still can learn from it. From time to time I
personally am re-reading some pages of it to refresh my memory on some
rarely used topics.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Question about log file

Hi TSMers,

/tmp> tail pipinitbup.20020820

Total number of objects rebound: 47

Total number of objects deleted:  0

Total number of objects expired: 48

Total number of objects failed:   0

Total number of bytes transferred: 5.31 GB

Data transfer time:  616.28 sec

Network data transfer rate:9,036.59 KB/sec

Aggregate data transfer rate:  1,653.90 KB/sec

Objects compressed by:0%

Elapsed processing time:   00:56:07

What is Rebound ? Deleted ? Expired ?

Please can you assist me in understanding what the above stands for.

Thank you for your assistance.


> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> *  +27-31-3642185
 <<...OLE_Obj...>>  +27-31-3642946
 [EMAIL PROTECTED] 





WARNING:
Any unauthorised use or interception of this email is illegal. If this
email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, BoE Ltd does not
accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.boe.co.za/emaildisclaimer.htm

Re: Select problems in 5.1.1 ... again

[Zlatko Krastev/ACIT]

Andy,

but Dennis is reporting this on 4.2.2.9 as well so maybe the APAR have to 
updated (and worked on).

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Re: Select problems in 5.1.1 ... again

This looks like APAR IC34207, of which the pertinent text is shown below:

===
ABSTRACT:
BACKUP/ARCHIVE INFO IS INCORRECT IN SUMMARY TABLES.

ERROR DESCRIPTION:
Backup/Archive stats are wrong in the TSM Server Summary Table.
This is having on all platforms of the TSM Server V5.1.X.X.
.
The status are being truncated by the 1000...
===

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

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




Paul van Dongen <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/21/2002 06:53
Please respond to "ADSM: Dist Stor Manager"

 
To: [EMAIL PROTECTED]
cc: 
Subject:Select problems in 5.1.1 ... again

 

   Hello all,

   I have just finished (about ten days now) an upgrade of TSM 4.2 to 5.1.
Being aware of the zero bytes problem in the summary table, I upgraded to
5.1.1.2. Now, I don´t get zero bytes in my summary entries for backups, 
but
all my files (examined and affected) counters are being divided by 
1000
Someone got this problem too?

   Here is an example:

Summary table:

   START_TIME: 2002-08-09 19:29:20.00
 END_TIME: 2002-08-09 19:47:19.00
 ACTIVITY: BACKUP
   NUMBER: 8015
   ENTITY: 
 COMMMETH: Tcp/Ip
  ADDRESS: 10.131.64.29:54333
SCHEDULE_NAME: 
 EXAMINED: 40
 AFFECTED: 39
   FAILED: 0
BYTES: 3857289012
 IDLE: 1076
   MEDIAW: 0
PROCESSES: 1
   SUCCESSFUL: YES
  VOLUME_NAME: 
   DRIVE_NAME: 
 LIBRARY_NAME: 
 LAST_USE: 



Tivoli Storage Manager
Command Line Backup/Archive Client Interface - Version 5, Release 1, Level
1.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

Node Name: XX
Session established with server YY: AIX-RS/6000
  Server Version 5, Release 1, Level 1.2
  Server date/time: 08/09/02   19:29:20  Last access: 08/09/02   18:59:46


Total number of objects inspected:   40,769
Total number of objects backed up:   39,934
Total number of objects updated:  0
Total number of objects rebound:  0
Total number of objects deleted:  0
Total number of objects expired:  0
Total number of objects failed:   0
Total number of bytes transferred: 3.59 GB
Data transfer time:  221.48 sec
Network data transfer rate:17,012.47 KB/sec
Aggregate data transfer rate:  3,492.59 KB/sec
Objects compressed by:0%
Elapsed processing time:   00:17:58


Thank you all for your help

Paul van Dongen

Re: Managed Services

[Zlatko Krastev/ACIT]

Just re-type this line again. I guess you have some hidden character in
"ManagedServices" word. If you tar (!!! to prevent modification from
mailers) and attach your dsm.sys we can verify this.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Managed Services

I am attempting to run the dsmcad and dsmc commands and am getting the
error
ANS1036 Invalid option  ManagedServices  scheduler webclient

I am pretty sure that this is an ignorance issue but can't seem to figure
it out.

Any one ever see this before?

Version 4.2.1

Server AIX

Client Linux 2.4-18

Re: TSM backing up in a DMZ zone.

[Zlatko Krastev/ACIT]

Mark,

I have to disagree with you. This is a nice solution from TSM performance
perspective but throws away most of the security achieved by building a
DMZ. The idea of DMZ is to isolate exposed servers and id case of
intrusion in one of them internal corporate network still to be not
reachable by intruder. If we assume an intrusion as "a failure" DMZ is
trying to eliminate some of single-point-of-failure threats.
In fact what you suggest renders DMZ as part of internal network but just
a separate segment. If a DMZ-server is compromised the intruder will not
attack the firewall (fortified and full of intrusion detection alarms) but
will attack the TSM server box and all other servers on the "TSM
backup/archive network segment".
Opening of port 1500 from DMZ to (only) TSM server is a solution. The
drawback is that port 1500 is used for both B/A, API and Administrative
clients. This still is less vulnerable - instead of attacking the whole
box (OS, Mail, TSM Web admin, etc.) only TSM data port is exposed. For
example TSM vulnerability described in Tivoli Flash 4
(http://www.tivoli.com/support/storage_mgr/flash_httpport.html) is not
exposed.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: TSM backing up in a DMZ zone.

> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> Seay, Paul
>
> See my responses inline.
>
>
> From: William Rosette [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 31, 2002 10:01 AM
> To: [EMAIL PROTECTED]
> Subject: Re: TSM backing up in a DMZ zone.
>
>
> HI TSMr's,
>
>   I have a DMZ Zone going in this Tuesday and they are asking me
(TSM
> admin) to see if TSM can backup servers/clients in the DMZ zone.  I have
> heard some talk on this ADSM user group about that very thing.
> We are going
> to be using a Cisco Pix Firewall and eventually use a Nokia Checkpoint.
I
> gave them some options but I want to know if there are any more
> options that
> y'all might have.  Here are the ones I suggested.
>
> 1. Put a TSM remote server in the DMZ and share the library
> (3494) with the
> other server.
> This one requires port 3494 to be opened through the firewall so that
the
> TSM server can talk to the library.  This one to me has some serious
risks
> if the TSM server is broken into.  The reason is there is no
> security in the
> library to block the mtlib and lmcpd interfaces from being used to mount
> tapes belonging to other systems from being mounted in the drives of
this
> remote TSM server.
>
> 2. Since most clients (NT & Linux servers) backup in 5 to 15 minutes and
> will not need to be backed up maybe once a week, open an obscure
> port once a
> week for 30 minutes for all backups.
> The port on the TSM server side has to be set for all clients.  But, you
> could create a small second TSM server processs on the machine inside
the
> firewall or locate the remote one inside the firewall that uses this
> specific port and only allows connections from the NT & LINIX servers.
> Then, set your firewall up so that only port and connection works
> to the TSM
> server.  This is probably the most secure.
>
> The big negative is that the backup will be slow depending on
> your firewall
> and network.
>
> 3. Port access through Cisco script when backup happens.
> I am not familiar with this but it looks like 2 with some more security.
>
> 4. Direct connect to TSM server.
> Not sure what you meen by Direct Connect.
>
>
> I understand that probably each one has its security leaks and some more
> than others.  Is there someone who can share a good DMZ SLA?

There's another way.

1. Install a second NIC in each client in the DMZ.
2. Install a second NIC on the TSM server.
3. Create a private network for the DMZ clients and the TSM server to use.
4. Designate a TCP port for the server and clients to communicate through.
5. Set client backups to prompted instead of polling.
6. Turn on the second TSM server NIC
7. Run the backup
8. Close the server NIC.

(Steps 6-8 should run as a client schedule event with a PRESCHEDULECMD.)

This obviates the security risks in having a TSM server in the DMZ.

[I'd suggest using IPX only (instead of IP) for the private network comm
protocol (for additional security), but there seem to be some issues with
using IPX only on the TSM 5.1 server.]


--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
Certified AIX system engineer
MCSE

Re: Monthly FAQ posting

[Zlatko Krastev/ACIT]

I hope I can also contribute somehow to the FAQ with few additions and
suggestions for correction.

01-08. What is the audience of the list?
A.: Many people related to ADSM/TSM/ITSM are actively participating on the
list - *SM administrators & users, *SM consultants & solution designers,
IBM/Tivoli developers & support people for both TSM and TDP, people from
Hardware (disk/tape storage) and Software (TSM add-ons, tools, etc.)
TSM-related vendors, IBM/Tivoli partners & competitors. All participate on
voluntary basis and no one is obliged to answer your post (look Question
02-03).

02-03. ...
+ Use subjects! Posts without subject or with non-descriptive subject
(like "Please Help!!!") have lower chance to get answered.
(Sorry, this actually is related to netiquette but many people will not
follow your links in 02-04 as do not read "how to unsubscribe" (IMO))

03-03. What means  ?
The whole ADSM/TSM/ITSM backup ideology from product creation is
completely different compared to other similar purpose products. Many
terms are TSM-specific and their explanation can be found in redbook
"Tivoli Storage Management Concepts" (SG24-4877-02). The book very quickly
and with enough detail can introduce you in the TSM world.

04-07. Latest stable versions are available at 
http://www.tivoli.com/support/storage_mgr/adsercli.htm (I think it should be better 
than ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/  and 
you had a typo in "maintenenace" :). The latest possible versions which do not undergo 
exhaustive testing
are available as patches and can be found at 
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/patches.
Client versions are installable and do not require previous version of the
client to be installed. TSM Server code and TSM for Applications (former
Tivoli Data Protection products) code are updates to already installed
base code. The latter is available on the media (CD) recived when the
correspoding product was purchased.


Zlatko Krastev
IT Consultant





Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Monthly FAQ posting

I've decided to create something that's been missing from the list.

I will be posting this FAQ on a monthly basis. There are a goodly number
of
questions and situations that crop up on a regular basis, and it would be
nice to have the answers gathered into one place. Hopefully, this will cut
down the number of repeated questions.

Naturally, I'm going to miss some questions that should appear. I would be
grateful for any requests to include additional material. (Please send
them
directly to me, rather than to the list; my address is at the bottom of
the
FAQ.)

updated
08/24/2002

QUESTIONS

01.   About the list itself
01-01.  How do I subscribe to ADSM-L?
01-02.  How do I unsubscribe to ADSM-L?
01-03.  Why don't I see my questions on this list?
01-04.  How can I see my questions on the list?
01-05.  Who decides what questions go on the list?
01-06.  Is there a digest or archive of the list?
01-07.  How do I get more information about the list?

02.   Types of questions asked
02-01.  What subjects are covered in this list?
02-02.  What kinds of questions can be asked?
02-03.  What kinds of questions can I expect answers to?
02-04.  What levels of netiquette are expected?

03.   Available ADSM/TSM/ITSM resources
03-01.  What FAQs are already out there?
03-02.  What other sources of help can I find?

04.   Quick facts about questions asked on ADSM-L
04-01.  Is it called ADSM, or TSM, or ITSM? What's the deal here?
04-02.  What are backupsets? How can I use them?
04-03.  How does TSM do full/incremental/differential backups, just like
  my old backup software  used to?
04-04.  How do I unsubscribe to ADSM-L?
04-05.  How do I do mailbox-level restores of Exchange using the Tivoli
Data
  Protection Agent for Exchange?
04-06.  How do I force TSM to do a full backup of a client?
04-07.  Where can I download the latest version of TSM/TDP?

ANSWERS

01-01.  Send an email to [EMAIL PROTECTED] with a blank subject line
and a message consisting only of the line SUBSCRIBE ADSM-L.

01-02.  Send an email to [EMAIL PROTECTED] with a blank subject line
and a message consisting only of the line UNSUBSCRIBE ADSM-L. Do NOT try
to
unsubscribe by sending email to [EMAIL PROTECTED] All that does is
annoy
the list members, and doesn't get you off the list.

01-03.  That's the normal behavior of ADSM-L.

01-04.  If you want to see your own questions, send an email to
[EMAIL PROTECTED] with a blank subject line and a message of the line
SET ADSM-L REPRO.

01-05.  The list members. There appears to be no active moderation of the
list. (No, that's not a license to abuse the list. Complaints from the
list
members do get listened to.)

01-06.  Indeed. There is an indexed

Re: baffling tape, 3584 HW compression, and stgpool design

[Zlatko Krastev/ACIT]

Dan,

David already answered to question 2 but as an additional remark - when
TSM started to write a tape volume uncompressed the tape has to become
back scratch to start write on it with compression.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: baffling tape, 3584 HW compression, and stgpool design

For question 2, on my 3584 drives I have the FORMAT=ULTRIUMC and
it uses comperssion.  I'm getting about 275GB average on my tapes
(IBM tapes), have gotten nearly 400GB on some!

David Longo

>>> [EMAIL PROTECTED] 08/27/02 04:34AM >>>
Couple unrelated questions:

1. When I query a 3570 library, there's one tape that baffles me:

adsm> q libvol 3570lib1

Library NameVolume NameStatus   Last Use Home
Element
----- 
3570LIB1133060 Private   34

   I can't do anything with it -- ie, I can't discard the data on it
because
   ADSM says it doesn't belong to a storage pool, and yet, no indication
that
   it's a DbBackup. All other tapes in the library are sane and belongs to
   either scratch, a storage pool, or a dbbackup.

   So what could it be, and how do I wipe that lone offending tape and
change
   its status to scratch? (This is with ADSM 3.1+patches)

2. How do I enable hardware compression for LTO tapes? Some sort of device
   class or drive definition parameter? (This is with TSM 4.2.2+patches)

   I've looked through docs set and not finding anything that addresses
this.

   I'm currently using:

   tsm> DEFINE DEVCLASS 3584_DEVCLASS1 DEVTYPE=LTO FORMAT=DRIVE-
 MOUNTLIMIT=10 MOUNTWAIT=60 MOUNTRETENTION=0 LIBRARY=3584LIB1

   tsm> DEFINE DEVCLASS 3584_DEVCLASS2 DEVTYPE=LTO FORMAT=DRIVE-
 MOUNTLIMIT=2 MOUNTWAIT=60 MOUNTRETENTION=0 LIBRARY=3584LIB1

   The mountlimit of 10 and 2 is to put an hard upper bound on number
   of drives that the backups (10) and offsite copying (2) can use.

   The mountwait of 60 minutes is to avoid having jobs fail if they're
   sitting there, waiting for a particularly huge 300GB job to finish and
   free up a drive for it to use.

   Mountretention=0 is because this is a fast automated library (3584 with
   12 drives); I can see setting it to 10 or so if it was a smaller human
   operated library or requiring operator tape swaps like the 3570
library.

   3584LIB1 refers to the library, obviously. ;) (device /dev/smc0, etc)

   As I understand it, FORMAT=DRIVE means it uses the drive's compression
   settings. I haven't seen any explicit mention of what this defaults to
   nor how to adjust it in either the 3584 or TSM docs.

   Or would I use something like DEVTYPE=LTOC...?

3. Is there really a reason to use multiple storage pools for the same
   tape repository?

   Ie: the TSM 4.2 docs suggests an out-of-box default setup such as
DISKDIRS,
   DISKDATA that then migrates to TAPEDATA, which then copies to OFFDIRS
   and OFFDATA (offsite copy pool tapes). This makes sense. (I understand
the
   purpose for each and every one of them, and how they're organized.)

   Is there a good reason why someone might want to split up diskdata and
   tapedata into multiple stgpools? I ask because I've heard references to
   other folks having multiple stgpools, and wondering what I'm missing
here.

   That's the only thing I think that eludes my understanding in preparing
the
   new design, at this point.

Any insight or comments much appreciated. Thanks!

-Dan



"MMS " made the following
 annotations on 08/27/2002 10:08:01 AM
--
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: migrating to DB2

[Zlatko Krastev/ACIT]

There is whole redbook on this topic - "Backing Up DB2 Using Tivoli
Storage Manager" (SG24-6247-00).
It ought to answer most of your questions and will give you examples which
are more detailed than you can find in an answer on the list.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:migrating to DB2

Hi ,
current :running TSM 5.1 with informix database on AIX 4.3.3

   Soon we'r going to migrate database from Informix to DB2 , So need to
plan new designs on TSM for DB2.
I appreciate if anyone writes some documents and their experiance.


thanks in advance.

/muthyam


+
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.
+

Re: Antwort: Re: Very small server to server volumes

[Zlatko Krastev/ACIT]

Markus,

do you have collocation on the copy pool? This might explain why small 
chunk of data resides alone on a virtual volume.
Another possibility is that your virtual volumes devclass at that time had 
maxcap=500MB or 1000 MB and you later modified it to be 10GB.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: 

Subject:Antwort: Re: Very small server to server volumes

Hi,
thanks for the tip about space reclamation and the value for the mount 
limit.
That is OK now.
I still don't understand why I get all these small server to server 
volumes.
I've got one ba stg job running once daily,
when the data is backed up, one server volume should be mounted, there is 
a
constant stream of data to fill the volume close to its estimated 
capacity, I
can't see how  it should send 500 kb, close the volume and mount a new 
one.

Mit freundlichen Grüßen / Best Regards

Markus Veit

_
Bayer AG
IM-CTS-PSO-SBB
Leverkusen, W  5
Tel.: +49(0)214/30-71254
Fax:  +49(0)214/30-9671254
E-Mail:  [EMAIL PROTECTED]
Internet :  http://www.bayer-ag.de




  
  
  
   An: [EMAIL PROTECTED]
 
   Kopie:
   Thema:   Re: Very small 
server to server volumes 
  
 [EMAIL PROTECTED]   
 U  
 Received :  28.08.2002   
 15:44   
 Bitte antworten an "ADSM:   
 Dist Stor Manager"   
  
  




Sure...
what you'll find is that for each ~operation~ in a server to server
enviornment, once that operation finishes, it closes out a virtual 
volume"."
So say you have an Est Cap of 10 GB but your backup stgpool to the remote
server /virtual volume only pushes 2 GB.  Then that virtual volume will be 
2
GB and won't have any more data written to it.

For your reclamation not working, check into the "mountlimit" of the 
device
class of device "server".




Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-Original Message-
From: Markus Veit [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 4:25 AM
To: [EMAIL PROTECTED]
Subject: Very small server to server volumes


Hi TSM'er
2 x TSM Server 4.2.1.9
OS W2k SP2

we have on both  servers a  server to server  copy storagepool, as well as 
a
local copy storagepool.
One of the servers keeps generating server to server volumes that look 
like
this.

BY0O83.BFS.026016225  CP_TO_CROSS  LTOCROSSD-1.0   76.2 Full
BY0O83.BFS.027744232  CP_TO_CROSS  LTOCROSSD-0.5   64.6 Full
 this means that the estimated capacity of that volume is 0.5 MB and is 
used
64.6%, the volume contains data.
The space reclamation doesn't seem to work. ( it should, shouldn't it). 
The
volumes are set to be 10GB.

When I try to do a move data on a volume I get the following message.
 ANR1145W Move data process terminated for volume
  BY0O83.BFS.026585208 - insufficient number of mount
  points available for removable media.

Anyone got an idea what that could be, or which strategy I can use to have 
a
copy storagepool at a different site.
I was thinking of something like library sharing. Anyone got any 
exoirience
with
library sharing?
Thanks

Mit freundlichen Grüßen / Best Regards

Markus Veit

_
Bayer AG
IM-CTS-PSO-SBB
E-Mail:  [EMAIL PROTECTED]
Internet :  http://www.bayer-ag.de

Re: tsm client is down-level with this server version

[Zlatko Krastev/ACIT]

Looking at the length of this thread and shaking my memory this question
might be a good candidate for the Monthly FAQ (Mark, what do you think ?)
And maybe Gianluca can quote how many times this happened without being
reported on the list.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: tsm client is down-level with this server version

>>
Would it be possible to provide a safe and tested script, or an APAR
that introduces a new secret command, that can untangle this mess in
some automated way? The current method of fixing it is way too costly.
<<

Coincidentally, I just had that conversation with one of our server
developers, and they will look into doing this (no commitment right now,
but the odds are pretty good).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

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




Roger Deschner <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/29/2002 09:03
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: tsm client is down-level with this server
version



We've got half a dozen clients stuck like this right now. The first case
I had was an important, tenured, and extremely impatient professor who
had converted from Win 98 to Win XP, decided that XP "stinks", and
wanted to format his hard drive and restore his comfortable old Win 98
system from ITSM. (This is what backup is for, right?) Because this was
basically a point-in-time restore, deleting the node was not a possible
strategy. He was incredulous that it took me several days of
communication with IBM support to straighten it out and peppered me with
emails demanding that I work faster on it the whole time I was
exchanging special commands and their outputs.

The second was an aggressively confused user who was backing up two
computers using one node, and who thereby un-did the fix mere hours
after I had spent several hours with IBM Support fixing it. I refused to
fix it again for this user and made their node restore-only until I
communicated with their supervisor about our one computer per node
policies.

I have not even begun to figure out the rest, because I know it is a
huge black hole for my time. Before I even call Support, I've got to
reach each end-user and figure out how they caused this, to insure that
they don't inadvertently un-do it after we (me and Support) spend
several hours fixing it.

Those who would want to try the solution on their own are misguided; it
cannot be done - Andy Raibeck is absolutely correct in this regard. You
must call Tivoli Support, but while they will be able to help, it will
be a lengthly and complicated process. Budget several hours per case.
And type carefully!!!

I really wish the existence of a correcting APAR was made more public.
I'm going to install it soon (today!), but I'll still have those half
dozen clients who appear to have "unicode cooties" to untangle.

Would it be possible to provide a safe and tested script, or an APAR
that introduces a new secret command, that can untangle this mess in
some automated way? The current method of fixing it is way too costly.

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]

Re: backup performance with db and log on a SAN

[Zlatko Krastev/ACIT]

ESS is a complex piece of equipment and as any such one can be configured
in zillions of ways - some good, some bad and some of them perfect. With
proper configuration of the *whole* system you can get impressive results.
Check the settings of the AIX, FC HBAs, zoning and mainly the ESS LUNs. It
would really help if you know internal structure and StorWatch Expert can
also help a lot (Daniel, StorWatch Specialist is for configuration only).
What you got is insufficient from the HW you have and others already
pointed - Paul is backing the TSM DB much faster and only 10% improvement
for Oracle is also simply not enough.
Some hints:
- are your DB & log using two LUNs over same LSS? TSM is attempting to
parallelize access but it ends back over same RAID-5 array inside ESS.
Spread the load over more arrays. If you can, redefine 4 DBVs in different
LUNs in *different* LSSes. Fill the rest of LUNs with file pool, disk pool
or anything less used.
- what is using the other 159 GB (205 - 36 for DB - 10 for log)? If Oracle
is using the same LSS heavily your DB read speed might suffer.
- where the Oracle is running? If on the same system as TSM server (I
doubt) the system might be overloaded easily. If not - only two ports for
2 TB Shark can be the bottleneck.
- use topas or monitor tools and watch the reading speed from the disks
during TSM DB backup. Do not count the throughput twice - you will see
vpath and hdisks (18 MB/s on hdiskA + 19 MB/s on hdiskB + 37 MB/s on
vpathAB is *not* 74 but only 37 MB/s).

And some comments:
--> What kind of a machine are you running? <--
Daniel is completely right. Each of FC HBAs and Gigabit Ethernet would
load the PCI bus the are connected to alone. If two of them are put in
slots on the same bus the latter is overloaded andperformance will suffer.
Count also SCSI RAID adapter(s) - 3 or 4 SCSI buses 80 MB/s each.Check how
many adapters you have and how many I/O drawers. While you can put many
adapters in single drawer it might be at the price of performance. I've
heard from some IBMers that adapters can be configured for "Best
operation" (performance) and "Connectivity" (price).
While I wrote this additional post came in:
--> We have a P-Series 660 7026-6H1 with 12 PCI slots. <--
So you have single drawer (with 14 slots actually but 2 are occupied by
IPL disks) which means total of 500 MB/s for the whole drawer and 4 (four)
PCI buses. And I counted 4 FC adapters + one SCSI RAID + unknown number of
gigabit and fast Ethernet + 4 not used SCSI adapters. So your I/O drawer
is almost full and at least one PCI bus is overloaded with 2 FC or FC+RAID
adapters.

--> The tsmserver host has 4 HBAs.  Two are connected to each switch, with one
zoned for tape traffic and the other zoned for disk traffic. <--
--> ... especially if you are using the same HBA for both a SAN Data Gateway
(IBM 3583) or other similar solution and the SAN disk <--
I have seen an IBM document titled IBM LTO Tape Library Sharing and there
is info that sharing of same FC HBA or SAN Data Gateway for both disk and
tape access is not supported. But in the same document there was a clear
statement:
"A number of customers in the past six months have had tape and disk on
the same FC HBA, had problems, separated the tape and disk on separate FC
HBAs, and the problem went away. The exception to the rule is ESS / 3590 /
2109 / pSeries with FC 6227. This configuration has been tested and is
supported."
Many but not all - for example we've implemented for a customer nice
working TSM implementation where a MgSysSAN node is reading from ESS and
writes to 3583 with good 32-34 MB/s.
So either this document is wrong/obsolete/whatever or for the
configuration Eliza has it ought to be possible to share HBAs for disk and
tape *without* any performance penalty. My personal experience also up to
now is proving this can be done even with LTO. Fiber-attached 3590 drives
should work not only because I think so but also because IBM wrote it.

--> IBM helped set up the Shark and the switches.  I assumed that the guy knew
what he was doing. <--
Do not assume this for granted! Unfortunately as in any big company there
are many people at different levels of knowledge. Same as the work they do
- some good, some bad and some of them perfect. If every IBMer was perfect
their competition would be no more on the market.
In the light of the facts (not enough PCI slots for TSM server
performance, not enough ESS ports, etc.) I would not say those guys knew
what *exactly* were doing.

Sorry for the very long post. I thought there are too many facts
influencing the throughput to be commented.


Zlatko Krastev
IT Consultant





Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:backup performance with db and log on a SAN

I recently moved the 36G TSM database and 10G log from attached SCSI disk
drives to a SAN. Backing the db now takes tw

LAN-free backup goes SAN, LAN, SAN

[Zlatko Krastev/ACIT]

Hello all,

If you do not like to read long posts please skip this one - it can be
boring.

I have a very nasty problem at customer site and asking for your help are
we the only having it. If not can we fight it together.
Environment:
Server: v4.2.1.15, Windows 2000 SP2
Client: v4.2.2.1 (was 4.2.1.25), AIX 4.3.3ML09 + patches
Storage Agent: v4.2.1.15, TCP/IP or Shared Memory
SAN: IBM 2108-F16 (Brocade) switch + IBM 3583-L18 (ADIC) LTO with 2 drives
Storage policy: Stgpools use defined volumes and no scratches.
Yes, I know it's very unusual combination (Windows TSM server + AIX
nodes). Even support in the beginning thought it is AIX server w/ Win
client.

The node in question is somewhat mixed - small (<50kB) and large (Nx100MB
or 1-4GB) files. So for performance small files are directed to go over
LAN. Large files are bound to direct-to-SAN-tape class and storage agent
should take care of them. DIRMC is pointing diskpool as it ought to.

Now the problem:
1. Client starts backup, sent several directories over LAN, on first file
reported ANS1114I and waits server to mount a volume on behalf of storage
agent (OK)
2. Variable number of files are backed up for less than 1% of the volume
mounted (OK)
3. Client reports another ANS1114I (here is the problem).
Under the covers it seems than client requested this and next several
files to go over LAN instead of LAN-free. So mount is performed by server
for its own use (normal MgSysLAN path).
4. Another bunch of files are backed to second volume. 'Q SES' shows tens
of MBs so files go over LAN.
5. Third ANS1114I is reported and client resumes normal operation
6. Backup completes with no error, everything is backed up but for
enourmous time - test with 3-4 GB went good 20 minutes instead of 5.
The result of this SAN-LAN-SAN sequence is two volumes less than 5%
utilized, 5-minutes backup taking between 20 and 40 minutes and unwanted
data spread. Contents are
VOL1: file set 1, file set 3
VOL2: file set 2
And if accidentally second drive is busy (migration most often) the
process might go to bed in step 3 and wake up one hour later (when drive
becomes available on the end).

Partial workaround:
If DIRMC is set to point the tapes LAN-free works as it ought to and 4.3
GB take 5 minutes including mount time. But backup of 20kB in 5 files is
taking again 5 minutes just because DIRMC required tape mount. This moves
the problem in other area without solving it at all.

Support requested client upgrade from v4.2.1.25 to v4.2.2 with no success.
Upgrade of the storage agent (plus the server and other agents) is
postponed because we want to ensure this problem is resolved before to
introduce new ones in v4.2.2.

As always any hints, advices or similar experience are thankfully welcome.


Zlatko Krastev
IT Consultant