Hi *SMrs
we have some issues with a fully working client,
Platform: HPUX
Client OS Level: B.11.00
Client Version: Version 4, Release 2, Level 1.0
running direct to tape on a server Sol-2.8 version 4.2.20 and we are
seeing that the backups are f
Yep... just see the README; the usual conditions for upgrade on either the
server or the client is (a) once you upgrade the client, you *can* use the
new client features (ie, the ones specific to client operations), and you
*cannot* go back (this is a more recent caveat, in that new levels add new
To really know if you need a second server, you need to know what your
current server is doing. An M80 with 5GB of RAM and 2 drawers of SSA drives
should easily handle 1.5 to 2.5 TB/day; the wide variance is a function of
the number of db-inserts that occur. Do you know your current backup load?
I'd like to hear from anyone who has dealt with performance issues and TSM
that might be able to tell me if the environment I have is at its limits or
some upgrades might help. What I have is an RS/6000 M80 on AIX 4.3.3 running
TSM, that's all it does.
My TSM environment is such that there are abo
Hi Paul,
On Sun, 2002-11-03 at 14:25, Paul Mather wrote:
> Tivoli provide no FreeBSD TSM client. (Boo, hiss!)
Contact your local Tivoli salesdroid and request one. They can fire the
request back into IBM. If we get enough requests, they might actually
think about doing one.
> They do provide
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of
David Fosdike
> We created two new MCs in POLICYSET STANDARD
> 1. STANDARD_NC to backup to diskpool DISKPOOL_NC
> 2. STREAMING_NC to backup to sequential pool LTOPOOL_NC
>
> We validated the policyset and activated it.
>
> We
Has anyone seen this happen?
We are at 5.1.1 (server and client) under W2K - our default MC is STANDARD
in PS STANDARD which backs up to primary pool DISKPOOL.
We created two new MCs in POLICYSET STANDARD
1. STANDARD_NC to backup to diskpool DISKPOOL_NC
2. STREAMING_NC to backup to sequential poo
Had this problem on an AIX system with 4 instances. What I did was create a nodename
for each instance. CLIENT1_INSTX and CLIENT1_INSTY. Each instance has it's own DSM.OPT
file that is pointed to by the DSMI_CONFIG environment variable set in the USERPROFILE
for the instance.
Shout if you need
Sure can. I am running lots of 5.1.5.x (the latest) with my 4.2.2.13
server. Before I upgraded my server, I was running 4.1.4 with lots of 5.x
clients.
Just remember, once you go up in client levels, you can't go back down, as
far as restores are concerned.
Bill Dourado <[EMAIL PROTECTED]>
Se
Jacque, to eliminate the network as a bottleneck try ftp'ing a file
between the TSM server and the client. If the FTP is also slow, then you
have a network problem and not a TSM problem.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU] On Behalf Of
Jacque Mer
Need much more information, just to get started...
You say TSM 4.2, but what level? 4.2.0, 4.2.1, 4.2.?
What kind of server machine do you have? How much memory? How is your
database/log set up? Does this machine serve other functions?
How many clients are you backing up? Are they backing u
I am seeing very slow backups (320k/sec) from my clients.
I am using AIX 5.1 with TSM 4.2 and Linux client 4.2.
I have a 100meg connection to my clients.
I am using the recommended settings as called out in the
performance tuning guide.
Can someone point me to some information that I can us
Don,
What I need to know in the short term, (if anybody has experience) , is
it OK having 4.2.3.1 clients
running on TSM Server 4.1.1.4 ?
Bill Dourado
Ext 5134
DFrance
cc:
Sent by: Subject: Re: D
1) My primary advice is that you follow the advice I gave you before, and
work on getting the ODBC driver set up correctly. I pointed you to
detailed diagnostic information in the README file, and offered to have
you send me the results so that I can get a better understanding of the
problem. Once
14 matches
Mail list logo
