TSM Server 6.3.3.100 for AIX 7.1-01-06 (database size 80GB utilized 50 %)
For all previous versions of TSM (latest 5.5.6) I was backing up in offline
mode (stopped TSM Server):
1) file system with all configuration files (dsmserv.opt, volume history,
device configuration, etc);
2)
Hi,
We have a strange storage pool problem.
POOL48 is next storage pool of DISKPOOL.
Both are from type FILE.
The output of q stgp is not very clear, but you can see that POOL48 is next
storage pool of DISKPOOL:
Storage Device Estimated Pct Pct High Low
Next
Grigori,
Did you happen to use a scripted install for the TDP?
If so, would you be willing to share?
Thanks,
Steve Schaub
Systems Engineer II, Windows Backup/Recovery
BlueCross BlueShield of Tennessee
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Hello Steve,
If you mentioned client part we have done everything manually without scripts.
TSM server site scripts are:
register node KWTMB1 XXX passexp=0 userid=none type=client domain=NT
compression=yes archdelete=yes backdelete=yes
url=http://KWTMB1.kuwait.aub.net:1581
register node
I am sorry, a few last lines have been joint into one line. I will repeat
scripts again:
register node KWTMB1 XXX passexp=0 userid=none type=client domain=NT
compression=yes archdelete=yes backdelete=yes
url=http://KWTMB1.kuwait.aub.net:1581
register node KWTMB1_EXC XXX passexp=0 userid=none
Speaking of tuning, I have a question about Linux kernel parameters.
Back a while ago we started having intermittent problems running a DB
backup on one of our V6 systems. From what I posted here, a responder with
the same problem came upon some documentation listing recommended kernel
parms for
On Apr 17, 2013, at 9:16 AM, Zoltan Forray zfor...@vcu.edu wrote:
Speaking of tuning, I have a question about Linux kernel parameters.
Back a while ago we started having intermittent problems running a DB
backup on one of our V6 systems. From what I posted here, a responder with
the same
I understand the ulimit values. Back to my question on what limits/values
should we be setting? I have seen various suggestions of which one said
4096 but that isn't working..
On Wed, Apr 17, 2013 at 9:32 AM, Richard Sims r...@bu.edu wrote:
On Apr 17, 2013, at 9:16 AM, Zoltan Forray
Hi Steve,
What we are doing are installing as the documentation tell us.
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/index.jsp?topic=%2Fcom.ibm.itsm.mail.exc.doc%2Fdpc_con_ins_silent.html
But then do we copy default CMD/OPT/CFG files and all the customer lines are we
scripting in a
Hi all,
I am looking to find out what data is stored on my TSM servers for a
node which is defined as a server. Specifically to find out why/what
data is being stored for each server to the other one to amount to
approx. 3.8TB and 4.2TB respectively which is causing me a bit of a
headache as I am
On 04/16/2013 04:25 PM, Neil Schofield wrote:
I'm in the throes of an upgrade from TSM Server 5.5 to 6.3 and have had a
bit of a problem re-writing some of our custom SQL scripts. I was wondering
if anyone can point out what I'm doing wrong.
I don't know from do wrong; but the way I
On 04/16/2013 04:58 PM, Alex Paschal wrote:
Back in the day, it almost always used to be a duplex mismatch. Get off
my lawn! :-)
That answers the description of 'transmitted relatively slowly', now,
doesn't it? :)
- Allen S. Rout
- Throwing down with ADSM 2.1, yo yo. ;)
On 04/16/2013 08:15 PM, Nick Laflamme wrote:
If you absolutely need for nodes to be isolated on their own media,
why aren't they in their own individual domains which point to their
own storage pools, all of which might share a library?
That'd work; You could also make it an absolute
On 04/16/2013 09:26 PM, Grant Street wrote:
I understand that getting a good backup is the most important, but
when you offer a feature that is best efforts with no way to
verify, why have the feature?
Your conceptualization of the feature is inverted from the
conceptualization under which
Hi Grant,
I used to track collocation group spill overs when my servers were version 5
and used tapes. Now I am on v6 and almost all disk, so I don't do that anymore.
Anyway, I used a mysql database on my desktop system. I would dump data from
the tsm servers and load it into mysql where I
Allen
Thanks for the suggestion. The problem I've got is that the reports are
the sort of ad-hoc SQL scripts that are run by administrators and
operators from the admin client. While using '-comma' does reduce the
column width, it is not appropriate in this scenario.
The fact that only the
Hi,
the output is very interlaced and so not that easily readable. Which
command did you use to migrate the data from one pool to the other one?
Regards,
Michael
On Wed, Apr 17, 2013 at 11:42 AM, Stef Coene stef.co...@docum.org wrote:
Hi,
We have a strange storage pool problem.
POOL48 is
My apologies if it's already been posted and no doubt some of you were
already aware of IBM's announcement of the end of support for TSM 5.5 and
6.1 next April, but I thought it may be of interest to a few on here:
You might try this query:
select cast(vu.stgpool_name as char(9)) as Pool, -
(select access from volumes where volume_name=vu.volume_name) as Access, -
cast(vu.volume_name as char(9)) as Volume, -
cast(count(distinct nd.collocgroup_name) as decimal(4,0)) as Groups, -
cast(count(distinct
-Neil Schofield wrote: -
The fact that only the FILESPACE_NAME column is twice as wide as it
should be makes me wonder if it's a bug?
It probably has something to do with the possible occurrence of
Unicode characters outside the ASCII character set in filespace
names.
Thomas Denier
Hi, Stef. There is only a loose correlation between the devclass
directory and the volume directories. Would you please post the output of:
q vol /home/app/tsm/diskpool/diskpool13/diskpool/297D.BFS
On 4/17/2013 2:42 AM, Stef Coene wrote:
Hi,
We have a strange storage pool problem.
Seeking your experienced advice or reasoned opinion:
We have a TSMv5.5.7 service with very fragmented 500GB DB @ 76% utilized
but only 8% reduceable. As soon as possible we will start TSMv5-v6
migration to new 1200GB DB and 200GB Log. Another TSMv6 service with
800GB DB @ ~50% utilized
On Wednesday 17 April 2013 19:09:31 you wrote:
Hi,
the output is very interlaced and so not that easily readable. Which
command did you use to migrate the data from one pool to the other one?
Either an update stgp with low and high parameter or migrate stgp triggers the
same result.
The
You can also do:
select substr(filespace_name,1,20) from filespaces
and get only 20 chars back.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Neil
Schofield
Sent: Wednesday, April 17, 2013 1:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re:
I would say if you think you might grow it, start with 4 LUNs, not 6. I think
I heard somewhere that fewer DB volumes are better and too many can be a
problem. I have no experience with this. Most of our databases are on 2-3
volumes.
At 02:47 PM 4/17/2013, James R Owen wrote:
Seeking your
Wanda
You can also do:
select substr(filespace_name,1,20) from filespaces
and get only 20 chars back.
Well that's interesting because it makes the problem worse! Using either
CAST or SUBSTR truncate my data to N characters, but CAST gives me a
column width of (N+1) for NODE_NAME and (2N+1)
I had a link to TSM infoCenter Central.
Now it brings up a perfectly useless TSM Developerworks Public Wiki page.
https://www.ibm.com/developerworks/community/wikis/home?lang=en
If you scroll down that page and click on Tivoli Storage Manager, then click
the link to Documentation Central, it
Well that is odd -
I don't know why 2n+1, but at least I get consistent results:
tsm: LFTSMselect (substr(filespace_name,1,10)) as FS1, char(filespace_name,10)
as FS2, cast(filespace_name as char(10)) as FS3 from filespaces
FS1 FS2 FS3
The difference is not in char vs substr vs cast, but in filespace_name vs
node_name:
tsm: LFTSMselect (substr(filespace_name,1,10)) as FS1, char(node_name,10) as
NN1, cast(filespace_name as char(10)) as FS3 from filespaces
FS1 NN1 FS3
-
TSM Server 6.3.3.100, TSM Client 6.4.0, TDP for MS SQL 6.3.1
MS SQL backups are coming to domain default management class.
I have tried next include statements from dsm.smp (it was successfully used on
TSM Server 5.5.6 with older version of TDP for MS SQL):
INCLUDE \...\meta\...\* MSSQL
Wanda, for now use the following link to access all the info centers for
all the TSM releases. I will talk to a developer in the morning to see what
has happened here.
31 matches
Mail list logo
