We are running TSM Server v5.5.1.2 on AIX, and have a number of TSM clients
v5.1, 5.2 and 5.3 (principally running on Windows XP systems, but a smattering
of ones running on Mac OS X and Linux and other UNIX systems). So far, so good.
Minns, Farren - Chichester wrote:
Hi All
I'm still running
Abid:
Just a wild guess, but do you have the right version of Java installed on that
system?
Abid Ilias wrote:
FYI
I have downloaded and installed the new TSM Client version 6 on a Windows XP,
the web GUI is coming up blank, I think it is broke. Also now the Admin
Command line link is mis
Folks:
Our group has been approached by a customer who asked if we could
backup/archive 50 petabytes of data. And yes, they are serious.
We've begun building questions for the customer, but as this is roughly 1000
times the current amount of data we backup, we are
on unfamiliar turf here.
lly, but I was curious
if anyone has heard or seen anything from IBM officially on 10.5
compatibility (or any testing anecdotes from other TSMers on this
listserv) .
Thanks.
--Cody
--
Robert (Bob) TaldaPh: 607-255-8280
Prog/Analyst, EZ-Backup Service Fx: 607-25
A little late to the party, but this is what we've done here, with no
ill effects (been working fine since March).
David Bronder wrote:
An alternative in this particular case would be to install the RPM with
the "--nodeps" option to ignore dependencies. AFAIK, the /usr/bin/ksh
dependency is onl
This issue impacts the 5.4.0.0 and 5.4.0.2 versions of the client as well...
And our users do find the message confusing, given that we insist on
10.4.7, based on the documentation provided by IBM...
Heinz Flemming wrote:
According to Gretchen L. Thiele:
Checking to see if anyone else has thi
Andy:
As usual, your suggestion was better than most manuals...initial
testing (well, okay, on my
workstation) indicates that the clientoptset settings will override the
operating system directives
(so the hierarchy for includes/excludes seems to be client options file,
client OS directives,
serv
Andy et al:
Ironically, missed this exchange because I've been dealing with the
same problem Chris reported,
though I didn't know it at the time.
In our situation, the user reported seeing 2.8 million files expired
after a manual backup.
Upon much further investigaion, as best as we can deter
Just a little more detail on "initial good, then ran into some problems"...
We were working with the local team designated to figure out what Cornell
services did, and didn't work, on Intel-Macs. The team was composed of
experienced Apple developers and users.
- One developer was able to instal
There is one other possibility...
We are working with IBM on a very similar sounding problem impacting
the 5.3.2.x client for Macintosh, which, for the first time, uses a
dsmcad process to invoke schedule backups. Hence, the possible link to Linux
Here, the problem is that the generated passwor
Many thanks to all who responded, most particularly to Richard Sims, who
(no surprise) steered me in the right direction.
In brief, on a whim, I restarted the TSM server (potentially costly whim);
this didn't help, but it did change the error
tsm: ADSM2>def logcopy /dev/rD100b2L01L002 /dev/rD100b
Environment:
Storage Management Server for AIX-RS/6000 - Version 5, Release 2, Level 4.3
AIX 5.2 ML 5
FAStT 900 Disk Array
Folks:
Appreciate a little patience here; I'm still new to a lot of this, and
my terminology is a little weak. And of course, this had to happen while
our senior person (P
12 matches
Mail list logo
