This should also show you the amount of active data on a node in MB:
select sum(capacity*pct_util/100) from filespaces where node_name=''
-Original Message-
From: William Rosette [mailto:[EMAIL PROTECTED]
Sent: 21 July 2003 19:36
To: [EMAIL PROTECTED]
Subject: Re: Stats
Thanks
Maybe this:
SELECT nodes.NODE_NAME, sum(filespaces.CAPACITY) as capacity,
sum(filespaces.CAPACITY*filespaces.PCT_UTIL/100) AS "MB USED" FROM
NODES,FILESPACES WHERE NODES.NODE_NAME=FILESPACES.NODE_NAME AND
PLATFORM_NAME LIKE'W%NT' AND CAST(LASTACC_TIME AS DATE)>'07/01/2003' group
by nodes.node_name
Rather the other way round. The SQL is being converted to a native
database call. I would presume most query commands would be quicker than
their equivalent "SQL" queries.
For tuning SQL queries you can look at the indexing of the columns in a
table:
select tabname, colname, colno, index_keyseq,
Hello Adam,
An idea might be to define for each client two node definitions,
NODENAME and NODENAME_ACTIVE. NODENAME would be your normal daily
backups keeping x versions for y months. NODENAME_ACTIVE would be a
separate incremental backup of the same client that you backup to a
management class th
Have a look at your dsmaccnt.log, in particular the MediaWait and
CommWait columns. If you see large figures in both then this suggests to
me that the network connection is not feeding the TSM server fast enough
to support streaming. You must either increase your network throughput
or backup to dis
Have you run a client performance trace? This may give you an idea about where
the client is spending it's time. What type of disk is the data stored on that
you want to back-up from/restore to? Are these the same type of disks where you
see 60MB/sec? (How many parallel sessions do you run to ge
Yes I agree most stongly. Please IBM, give us access to the admin API.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Steven Harris
Sent: Friday 11 March 2005 01:49
To: ADSM-L@VM.MARIST.EDU
Subject: Re: If we all complain, do you think they will add
If you are upgrading library manager and clients you should be careful. The
upgrade process will define paths on all your servers, and it all looks and
works ok. Until you want to define a new drive (or delete/redefine a drive)
on a library client. Then you will discover that the 4.2 Admin Guide is
You can use DELETE VOLUME command.
-Original Message-
From: ZENG Brian (800043) [mailto:[EMAIL PROTECTED]
Sent: 14 November 2003 15:59
To: [EMAIL PROTECTED]
Subject: How to Change the status of a volume from private to sratch out
of a storage pool
The TSM4.2 Adminguide states:
"the UPDA
Hi Matthew,
something like this may help you:
where cast((current_timestamp - start_time)hours as integer) <= 4
Cheers,
Paul.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Warren, Matthew (Retail)
Sent: 08 January 2004 11:24
To: [EMAIL PROTECTE
Hello Goran,
you named the column "attempts" but it's actually called affected. The number of
attempts (for the db backup) would be a count() rather than a sum() fuction. The
number you summed probably refers to the number of database pages backed up.
Paul.
-Original Message-
From: ADS
ly. nah ? it's friday and the spring has come lets enjoy the
weekend and bother with this next week ...
have a nice weekend.
g.
- Original Message -
From: "P Baines" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 19, 2004 4:08 PM
Subject
If the object_ID is nnn then issue the command:
SHOW BFO 0 nnn
Which will show you the volume name(s)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSM_User
Sent: Thursday 09 September 2004 03:59
To: [EMAIL PROTECTED]
Subject: Select to
Hello Luc,
I think the only way to do this from the TSM scheduler is to define
three schedules, one with a start time of 00:00, one at 00:20 and one at
00:40. Then set the periodicity to one hour for each of the three
schedules.
Cheers,
Paul.
-Original Message-
From: ADSM: Dist Stor Man
Hello,
Assuming for nodeX the "q occ nodex /filespace" output looks like this:
NODEX Bkup/filespace 5 NEWPOOL-COPY1,047
278,526.2 278,526.2
NODEX Bkup/filespace 5 NEWPOOL 1,047
278,526.2 278,526.2
NODEX Bkup/f
Yes, this is true. IBMs take on this is that it is up to the customer to
make the library "master" server highly available. So cluster the TSM
server. If you've got fibre attached disks for your TSM DB, Log and disk
pools, then include both of your 630's in the same zone as the TSM disks
so that yo
16 matches
Mail list logo
