SearchFAQMemberlist Log in
Reply to topic Page 8 of 42
Goto page Previous  1, 2, 3 ... 7, 8, 9 ... 40, 41, 42  Next
No Title
Author Message
Post No Title 
Sometimes we have the same performance as you mention, but that's when 10
clients are backing up at the same time...

We compared our AS/400 TSM setup with our German division who uses the NSM
box (Unix) and our performance rates were better... We also compared with
another comapny who uses ADSM on OS/390... same results...

Like any platform, you need to fine tune... and monitor...


Frederic Landreville
JT International S.A. Geneva, Switzerland
Tel: +41-22-703-0323 Fax: +41-22-703-0324

----- Original Message -----
From: "Rafael J. Goldschmidt" <rafagold < at > ARNET.COM.AR>
To: <ADSM-L < at > VM.MARIST.EDU>
Sent: Wednesday, April 12, 2000 3:36 AM
Subject: TSM / 400 performance.


I want to share with you information about TSM performance, using an
AS/400
as a TSM server. What I discovered is that performance is NOT tied to the
network speed, NOT tied to the tape drive speed, BUT to the files size and
to the client performance. I did not use client compression as I verified
that this feature punishes overall performance.
I saw a 4 GB/hour speed, with files whose average size was about 3 MB
each.
For bigger files, better performance.

Saludos / Regards / Au revoir

Rafael J. Goldschmidt -
Elcano 5039 (C1427CII)
Ciudad Autonoma de Buenos Aires - Argentina
Telefonos: 54-11-4421 4782
Internet: rafagold < at > arnet.com.ar


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Post No Title 
#define DSM_RC_REJECT_ID_LOCKED 61

Make sure the NODE hasn't been locked out.
"QUERY NODE F=D" on the TSM server will tell you this answer.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler < at > us.ibm.com


Werner Nussbaumer <W.Nussbaumer < at > DATACOMM.CH> < at > VM.MARIST.EDU> on 04/13/2000
04:27:15 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>

Sent by: "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>


To: ADSM-L < at > VM.MARIST.EDU
cc:
Subject: ERROR 61



Does anyone know what the following error message means:

"Error 61 initializing ADSM API" ?

Thanks for help,
Regards
Werner Nussbaumer

Post No Title 
Without the 15 page explanation, let me suggest that a solution to your
problem may lie in the definition of multiple virtualmountpoints within your
75GB filesystem. Otherwise, you will have only one long running consumer
session session.

Bill Smoldt SSSI
Storage Solutions Specialists, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Mark Owens
Sent: Friday, April 14, 2000 10:25 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Multithreading w/TSM 3.7.2

AIX Server : TSM 3.7.2
TSM Client/Aix : 3.7.1
AIX : 4.3.2 & 4.3.3
commethod : sharedmemory


Hi All,

With TSM 3.7, Tivoli has provided the resourceutilization parameter in
dsm.sys
and the maxnummp parameter when you register your node. To the best of my
knowledge, maxnummp equates to mount points and when using a tape
storagepool
this equates to the number of tape drives that will be used for the backup.
The
resourceutilization throttles system resources and the number of sessions
used for the backup.

While testing with a single node, maxnummp=2 and resour=7 and a 75gig test
filesystem I'm noticing two sessions are started, two tape mounts occur,
each
session performs a backup. Then, after approx 2-3 minutes the last session
started
ends....... no error.......tape not full....... after the retention timer of
1 minute the
tape dismounts. The odd thing is the backup has not completed, the remaining
session
is left to complete the backup. I'm told TSM 3.7 performs some sort of
pre-backup
calculation to determine the optimal number of sessions to start and remain
active in
order to complete the backup.

Clearly (depending on the number of resources at my disposal) I'd like to
complete
the backup as soon as possible with as many tapes as possible without TSM
stopping
the active sessions I have running. Has anyone else experienced this or been
able
to have numerous sessions active writing to muliple tapes?

Mark

Post No Title 


Post No Title 
Don't forget that after EXTEND DB the next DB backup must be a full backup.

Lindsay Morris writes:
Create it in AIX first.
Maybe:
smitty: make LV
smitty: make FS on existing LV
mount new-filesystem
dsmfmt -db /new-filesystem/filename 500 #megabytes

**THEN**
dsmadmc ... define dbv /new-filesystem/filename
dsmadmc ... extend db



Roy Lake wrote:

Hi Chaps,

Could you please confirm the correct way to increase the db size in AIX =
for TSM 3.7 is as follows:-

I have done a q db, and get the following (so I can't extend it at the =
moment)

Available Assigned Maximum Maximum Page Total =
Used Pct Max.
Space Capacity Extension Reduction Size Usable =
Pages Util Pct
(MB) (MB) (MB) (MB) (bytes) Pages =
Util
----------- ----------- ------------ --------------- =
-------- ------------ ----------- -------- -------
800 800 0 132 =
4,096 204,800 168,936 82.5 82.5

1) define dbvolume /adsm/db/dbvol9 formatsize=3D100

(This will create a TSM ready db volume 100 meg in size in the given =
filesystem - correct????)

2) extend db 100

(This will extend the current database size to include the 100 meg that =
I just added)

Is this the correct way to do it, or do I have to create the db file in =
AIX first?

Kind Regards,

Roy.

--
Mr. Lindsay Morris
Certified: AIX,ADSM, TSM, HACMP,SP
Gresham Enterprise Storage
lmorris < at > openmic.com
606-253-8000

--
Reinhard Mersch Westfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583
E-Mail: mersch < at > uni-muenster.de Fax: +49(251)83-31653

Post No Title 
IY06778 MULTITHREADED EXPIRATION RUNS VERY SLOWLY, BITFILES EXAMINED
INCREMENT VERY SLOWLY

The expiration algorithm has been altered to improve
it's performance while expiring archive files and directories.

In addition, a new parameter has been added to the
"EXPIRE INVENTORY" command. The parameter is "SKIPDIRS".
The minimum abbreviation is the first two letters of the parameter
or just "SK".
The parameter accepts either a "YES" or "NO" for the value.
So, to specify this parameter on the
"EXPIRE INVENTORY" command, examples are:

"EXPIRE INVENTORY SKIPDIRS=YES" In this case,
expiration would run and for any DIRECTORY type objects
stored on the server, expiration would skip those objects.
So, even if the directory was eligible to be expired based
upon the policy criteria, the object would be skipped because
this parameter was specified.

"EXPIRE INVENTORY SKIPDIRS=NO" In this case, expiration
will process as it does today - it will expire any
possible files or directories based upon the appropriate
policy restraints.

By allowing expiration to skip directories this will help
customers to keep reclamation processing working. Typically,
the file objects are likely to be taking up space on
sequential media (where this is the storage pool configuration
that a customer is using.). By allowing expiration to
expire the file objects, we free up more of the sequential
media space and allow reclamation to continue having tapes
to reclaim.
--
Richard

Post No Title 


Post No Title 
It should not be too hard to work out with this info
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

Post No Title 
The V3 nodename can now restore files that were backed up using the V2
client. The above is documented in the ADSM V3R1 OS/2 Backup Archive
Client manual, Section 3.5.5, Authorising Anoth User To =
Restore/Retrieve
Your Files. This may be of some use to you.

Only other thing is that when we start the V3 backups, a new FILESPACE
appears in the database. I am puzzled as to why you do not see the new
one.

I hope this is of some help


Regards

Jeff White
Systems Programmer
CIS (Insurance)
Manchester

************************************************************************=
*

This e-mail may contain confidential information or be privileged. It =
is
intended to be read and used only by the named recipient(s). If you are =
not
the intended recipient(s) please notify us immediately so that we can =
make
arrangements for its return: you should not disclose the contents of =
this
e-mail to any other person, or take any copies. Unless stated otherwise =
by
an authorised individual, nothing contained in this e-mail is intended =
to
create binding legal obligations between us and opinions expressed are =
those
of the individual author.

The CIS marketing group, which is regulated for Investment Business by =
the
Personal Investment Authority, includes:
Co-operative Insurance Society Limited Registered in England number =
3615R -
for life assurance and pensions
CIS Unit Managers Limited Registered in England and Wales number =
2369965
(also regulated by IMRO) - for unit trusts and PEPs
CIS Policyholder Services Limited Registered in England and Wales =
number
3390839 - for ISAs and investment products bearing the CIS name
Registered offices: Miller Street, Manchester M60 0AL Telephone
0161-832-8686 Internet http://www.cis.co.uk E-mail cis < at > cis.co.uk

CIS Deposit and Instant Access Savings Accounts are held with The
Co-operative Bank p.l.c., registered in England and Wales number =
990937,
P.O. Box 101, 1 Balloon Street, Manchester M60 4EP, and administered by =
CIS
Policyholder Services Limited as agent of the Bank.

CIS & the CIS logo (R) Co-operative Insurance Society Limited

************************************************************************=
****
****

Post No Title 


Post No Title 
--
Joshua S. Bassi
Senior Technical Consultant
Symatrix Technology, Inc.
jbassi < at > gloryworks.com

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Cook, Dwight E
Sent: Friday, May 05, 2000 9:58 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: Tape library sharing on AIX


Are you meaning 3590 drive sharing ?

I already share 3494ATL's between TSM 3.7.2.0 environments...

One can already share drives (with some manual intervention) but I haven't
heard the latest on automatic 3590 drive sharing...

Dwight

----------
From: William Boyer[SMTP:wboyer < at > PTD.NET]
Reply To: wboyer < at > ptd.net
Sent: Friday, May 05, 2000 11:48 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Tape library sharing on AIX

Anyone know when support for tape library sharing will be supported on
AIX?
The TSM Library Sharing web site says that support for AIX is planned for
1Q2000.

Bill Boyer
DSS, Inc.


Post No Title 
Question. What does the error description the source slot or dirve was empty
in an attempt to move a volume?

05/06/00 08:27:45 ANR8300E I/O error on library STKLIB (OP=00006C03,
CC=314, KEY=05, ASC=3B, ASCQ=0E, SENSE=70.00.05.00.00.00.00.0C.0-
0.00.00.00.3B.0E.00.00.00.00.00.00., Description=The source slot or drive
was empty in an attempt to move a volume).

Post No Title 
--
Sent through GMX FreeMail - http://www.gmx.net

Post No Title 
I reinstalled SQL server to the box first so the master does not know of the
original db. I tried both just restoring (which worked with smaller db's)
and creating the shell then restoring. Interesting note, if I create the
shell first after the error the shell no longer exsists. Any ideas?? thanks


Jim Murray USN(ret)
Senior Systems Engineer
Liberty Bank
jmurray < at > liberty-bank.com
860.638.2919
Many a false step is taken by standing still.
-- Arnold Glasow

Post No Title 


Display posts from previous:
Reply to topic Page 8 of 42
Goto page Previous  1, 2, 3 ... 7, 8, 9 ... 40, 41, 42  Next
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB