Just went from v6.3.5.100 to v7.1.1.300. The procedure went smoothly,
but so far I'm not impressed with the client backup - slow to start, slow
to run. I'd hate to think that the only solution for the performance is a bit
of sleight of hand to reconstruct the tablespace.
Database is only ~350G wi
If you are not using HSM, the virtual mountpoint approach is a good
one. Since we do have an integrated TSM/HSM system on GPFS, we
can't do that. It takes a bit over 3 days to wade through 130+
million files. Not enough disk to use mmbackup, which basically
'journals' the changes. I do run incremen
Which site are you using? I had problems with ftp.software.ibm.com
last week and went back to index.storsys.ibm.com which I can get to
this morning.
Gretchen Thiele
Princeton University
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Gill, Geof
ist.edu] On Behalf
> Of Gretchen L. Thiele
> Sent: Friday, October 23, 2009 12:40 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] IBM FTP server asking for userid and password
>
> Is there any reason why ftp.software.ibm.com is asking for a userid
> and password now? I&
Is there any reason why ftp.software.ibm.com
is asking for a userid and password now? I've
rerouted all requests for TSM software to
index.storsys.ibm.com, but this one can be
flakey at times, too.
I did try userid=anonymous and password=email,
but no luck.
Gretchen Thiele
Princeton University
the accounting records (set accounting on) - fields
26-29 relate to migration and recall activity.
Joerg Pohlmann
250-245-9863
- Original Message -
From: "Gretchen L. Thiele"
Date: Thursday, September 24, 2009 7:56 am
Subject: [ADSM-L] GPFS, HSM and backups
To: ADSM-L@VM.MARIS
We've been using GPFS-directed HSM for a while now,
working quite well (with a few bugs, but they're
being worked on).
The 'problem' I'm seeing is the mounting of HSM
media (tapes, in particular) during the running of
an incremental backup. Since we have the requirement
that nothing can be migrate
Just got a report from a user that running TSM 6.1.0.2
on OpenSolaris 5.11 (SPARC) is core dumping on 'dsmc incr'.
This is the first I've seen of OpenSolaris, but it's
probably not the last (big upsurge in Ubuntu installs, too).
I'm heading over to see the 'victim', but thought I check
in with t
and Storage Administrator
HFS
OUCS
http://www.oucs.ox.ac.uk/hfs/
Gretchen L. Thiele wrote:
> I've just run into a roadblock with the TSM gui on the Macintosh -
> both v5 and v6 clients. There apparently was a Java software update
> (1.5.0_19) that was just released and I bel
I've just run into a roadblock with the TSM gui on
the Macintosh - both v5 and v6 clients. There apparently
was a Java software update (1.5.0_19) that was just
released and I believe it to be causing the problem
with the TSM client.
If you start the GUI, you get an ANS1971E (v6) or
ANS5179E (v5) -
I'm getting pressured (gently now, much stronger
in the future) to come up with a way to back up
our desktops without leaving them on overnight.
I don't think 'wake up on lan' is appropriate
since the TSM servers are on their own separate
segment on the network. I've looked into prompted,
but we d
I notice that there are 5.4.1.2 server versions on the ftp site this
morning,
but nothing in the README that points to the problems that have been
fixed. Is this just a repackaging of 5.4.1.1 in light of the security
announcement
earlier this week?
Also, as I moved from 5.4.0.x to 5.4.1.x on my A
Yes, it came out in 5.3.something (at least here it did).
It's now being addressed by APAR IC53464.
Gretchen Thiele
Princeton University
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Fred Johanson
Sent: Thursday, August 23, 2007 1:12 PM
To: ADSM-
Checking to see if anyone else has this problem with TSM v5.4.1.0
for an Intel Mac...
I just upgraded a Mac to 10.4.10, but the TSM client installation is
failing, stating that I must be at OS X 10.4.3 or higher. I don't think
the installer is parsing the trailing '10' correctly...
I have not
Thanks!
Ochs, Duane wrote:
ftp.software.ibm.com/storage/tivoli-storage-management/
Just used it this morning.
Greetings,
Where is everyong ftp'ing their TSM software from these
days? The ftp hosts that I've been using are
index.storsys.ibm.com and service.boulder.ibm.com.
Both appear to be empty.
Gretchen Thiele
Princeton University
A more recent client, v5.3.2.1, is now available. I haven't seen
any major problems yet.
On Dec 2, 2005, at 4:22 AM, James R Owen wrote:
Farren,
Is there some reason that you can't upgrade to the latest Mac TSM
client: 5.3.2.?
All/most of our OSX backup complaints were fixed with Mac TSM clien
Oops, I meant that v5.2.4.0 was visible to me with IE, the
other browsers were 'iffy'. I also think that IBM/Tivoli
believes 5.2.4.0 to be a maintenance level, hence its
location. I've seen this modus operandi before. It's only
when the level changes does it become a 'patch'.
Watch out for memory
Roger,
There is a v5.2.4.0 client available (as of April 1st). It isn't
visible via IE or Safari (haven't checked since the Safari software
update), but you can 'see' it if you use command line ftp or Netscape.
Our Mac Tiger people have been running this fairly successfully for
a while. It would
Is anybody experiencing a 'freeze up' on v5.3.1.0? I'm running AIX 5.1
with all of the requisite updated libraries. Not doing anything out of
the ordinary when the server just runs like mud. Can't issue any
commands, all new sessions in a Start state. It means killing off
the process from the opera
Would you please elaborate on your problem with FILE volumes?
Are you no longer using them?
Thanks,
Gretchen
Jurjen Oskam wrote:
On Mon, Jan 24, 2005 at 01:15:47AM -0700, Paul Fielding wrote:
I'm interested to know if anyone has tried installing 5.3 yet and what
they've found...
Yes, we're on AIX
By 'disrupt' I mean moving a node to another server...
I presume renaming the node would preserve the 'set
access' rules.
No select that I can issue to see what they've done?
Andrew Raibeck wrote:
I can't think of any other way to do what you are talking about.
Just out of curiosity: how would you
With a lot of my clients keeping more than one machine (one at home
and one at work, typically) and wanting to restore between the
two or three, I've been doing a lot of node moves (export/import)
between servers.
To access each other's data with the nodes on the same server
requires the 'set acces
The group by statement is incorrect, use the following:
group by pending_date
the conversion to date format is already taken care of
in the first part of the select statement.
David E Ehresman wrote:
tsm: ULTSM> select date(pending_date) as "Date",count(*) from volumes
where -
cont> status='PENDING
select volume_name, status from libvolumes where status='Scratch'
or, if you have multiple libraries attached:
select library_name, volume_name, status from libvolumes where
status='Scratch'
Sandra wrote:
Dear All,
Please give me the knowledge of a query that can give me the names of tapes,
that in
I am currently testing a NAS device from NetApp and using it as a
primary disk pool (it's being used 'raw', then I'll set it up as
devt=file and so forth). NetApp gave me a white paper on using their
devices with TSM and it's available on their web site, netapp.com,
search for TSM and you'll find i
A new Mac client, v5.2.2.10, was just released. Has anyone been
able to run the Mac client successfully on a dual G4 or dual G5?
OS is 10.3.x. I know one of the duals is an XServe, not sure
about any of the others that are having problems.
Gretchen Thiele
Princeton University
Hi Bill,
Where is your status.dat file? I suspect that since you used the
default install first, it is in /opt/tivoli/tsm/server/license - since
that
is where the preinstall file looks for it. I use pretty much the
same command, although without the -a option. What do you
have in your admin file?
has changed somewhat, has anyone been able to
install the Solaris v5.2.2.4 server patch in a directory other
than the default?
Original Message
Subject: v5.2.2.4 patch on Solaris
Date: Wed, 14 Apr 2004 13:12:45 -0400
From: Gretchen L. Thiele <[EMAIL PROTECTED]>
To: ADSM:
Has anybody successfully installed this patch yet (yup, I realize that
it just came out last night)? I was upgrading from v5.2.2.3 to v5.2.2.4,
when it gave me the "license hasn't been accepted yet" message. It
further instructs to remove the partial install, install v5.2.2.0
(which I did ages ago)
Hi Andy,
That's what I'm doing, but I'm not seeing the results that you are.
I do notice that there is a difference in the servers we are both
using, yours is v5.2.0.0 (Windows) and mine is v5.2.2.1 (AIX).
What your output shows is exactly what I want to happen... either
a problem with the platfor
I've tried this, but the files are not expired on the server
(no Expiring ---> message in the dsmsched.log). The unexpected
or unpleasant side effects that I am referring to are actually
expiring the files on the server - maybe people didn't expect
this to work this way? Principle of least astonish
Due to a change in policy (and limited storage), we're going to limit
what we back up. The problem lies in how to 'expire' the files on the
server without re-backing up the data, while maintaining deleted files
for the duration of retonly. While we could rename the filespace and
implement the new p
What does 'q path' show?
Gretchen Thiele
Princeton University
Lee, Gary D. wrote:
Have a devclass 3590 with mountlimit=4. However, when doing migration, I never see more than three drives in use. Even though I seem to have available mountpoints, always there is at least one process waiting for
Actually, you now need to go to a v5.2.x.x client. It's not perfect, but
it's better (still needs to run when the user(s) is(are) logged off!
ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance/
client/v5r2/Mac/v520/
Gretchen Thiele
Princeton University
On Wednesday, Aug 6, 2003, at 1
I get the same responses from my Windows v5.2 clients running a normal
schedule on a v5.1.7.0 server. After this, the regular incremental
backup runs normally. It's a nuisance bug, I think. It's on my list of
things to call in about.
John Stephens wrote:
Andrew:
Thank you for the response, I have
The scheduler and scheduler daemon work fine. But my caveat is that
I haven't tried to run it as 'root', only from a logged on (and left
on) user. Ideally, I'd like it to run as the Windows scheduler does,
backing up even if no one is logged on. This may be implemented, but
I haven't found it or fi
Well, on the whole, I'm happier with this client than I have
been in a long time. There is unicode support, so make sure
that you have 'autofsrename yes' in the client files or just
update the node on the server.
A couple of oddities, though.
1) There isn't an exclude.dir for the OS X System folde
On Saturday, Jun 21, 2003, at 10:02 US/Eastern, Bill Boyer wrote:
So you mean that the new TSM V5.2 is only supported on AIX 5.1 and
above?
Correct, AIX 4.3.3 is not supported for TSM v5.2. I vaguely remember
this restriction being discussed, because I had planned to get to AIX
5.1
this summer. I
Well, even though the v5.2 Quick Start Guide says that AIX 4.3.3 is
supported, it isn't. There's an error in the Quick Start Guide for
AIX on the web page. Oh well, was worth a shot.
Heading off to work on an AIX upgrade!
Gretchen Thiele
Princeton University
Pearson, Dave wrote:
Where is the TSM Version 5.2? I only see up to 5.1...
It isn't available on the web pages - this is a physical distribution
on CDs.
HOWEVER, checked the doc and it says that AIX 4.3.3 is supported, but
when I go to install, everything fails because I'm missing two
prerequisite
WAHOO! The v5.2 media is here!
Off to install it on our test server...
Gretchen Thiele
Princeton University
I've had v5.1.7.0 in test for a bit and went live with it on two
servers this morning.
I was pleasantly surprised (and pleased) that I could now delete
filespaces
and nodes that had been problematic earlier (see my earlier posting on
auditing a db and Jim Owen's explanation of the problem).
Server
Arrgh. Thanks, Jim, for posting all of this information. I've gone back
and
reviewed our logs for the past couple of days and I can't believe how
many
of the imbkins.c messages I'm finding. I suppose this means that I'll
have
trouble deleting these accounts when the time comes.
Although most of the
This is a client publication that was last updated circa v4.2.x.x,
so it is in the v4.2 client publication section:
http://publib.boulder.ibm.com/tividd/td/IBMTivoliStorageManagerClient4.2.html
Where can I find the following publication:
Tivoli Storage Manager Trace Facility Guide GC32-0792
Gretc
I've found that you can indeed delete licenses by setting the number
of licenses to zero (I think you must be fairly current with your
server, mine are at v5.1.6.3):
register license file=./library.lic number=0
removes all of the library entries. Similarly,
register license file=./mgsyslan.lic nu
Dameon White wrote:
>
> We just bought a used STK L700 with 4 DLT7000 drives. We
> have TSM 5.1.5.2 on AIX and I am confused as to why/if I
> would need to use ACSLS to manage the library? Does ACSLS
You don't need ACSLS for an L700. I found that I could do
everything I wanted without it (I do h
On Wednesday, Feb 26, 2003, at 04:17 US/Eastern, Gerhard Rentschler
wrote:
In my opinion 5.1.6.2 seems to be the stable version we have been
waiting
for.
I think I can second this. I've been at v5.1.6.2 on our production
servers for about
a week and the big issue here was the recovery log pinning.
The problem I was having with v5.1.6.1 can be traced to a monitoring
package we were trying out. It's a problem that manifests itself
on heavily loaded servers with a ton of scheduled sessions. Working
with the vendor to do further problem determination.
Now, as for v5.1.6.2, I've put it on my tes
The two situations where I could force a core dump in v5.1.6.0 have
been resolved, but I think there is now a different problem in
v5.1.6.1.
Granted, my servers run flat out all the time with sessions constantly,
but I rarely pin the 13 GB log with dirty pages (at least not over
60 to 70%). It's h
Hi Geoff,
I noticed that v5.1.6.1 was made available late on Friday and I, too,
put it on test servers this weekend. So far, so good. I plan to go
live this week.
In debugging the v5.1.6.0 problem, I was asked to enable a server
trace. This bogged down the server but at least avoided all of the
c
Just a heads up to anyone who might have installed AIX server
version 5.1.5.4 prior to last Thursday (12/12) morning. The
.gz file was replaced and now includes a 5.1.5.4 version of
the common services file (server.com). It doesn't appear that
the server.rte and messages file were changed.
Gretche
Be advised that v5.1.5.3 was pulled off the ftp site on Friday
and replaced with 5.1.5.4. There is a problem with the expiration
not actually deleting the files. A new cleanup utility will be
introduced in v5.1.6.x (per support contact yesterday).
I was advised to upgrade our v5.1.5.3 servers *imm
I've just put v5.1.5.1 into test and it looks like the SYSTEM OBJECT
problem (failure to expire the elements in the SYSTEM OBJECT filespace
for Win2K and WinXP) is back. Has anyone else seen this?
My test server: Solaris 2.8, TSM v5.1.5.1
Clients: WinXP, TSM v5.1.1.0 and Win2K, TSM v4.2.1.0
I ra
>> SHOW LOGPIN is not in v5.1.1.6. It was added back in on the newest
>> maintenance/patch - v5.1.5.1.
>
>The command is:
>
>show log pin
>
>...and it works on 5.1.1.6 on AIX
But it's not the 'same' command. 'show log pin' is different from
'show logpin'. For example, on a v4.2.2.12 system (looks
>What is the show command to see who has the log pinned? Is it in AIX server
>5.1.1.6 level?
SHOW LOGPIN is not in v5.1.1.6. It was added back in on the newest
maintenance/patch - v5.1.5.1.
Gretchen Thiele
Princeton University
>I found that the SYSTEM OBJECT which were not unicode were never deleted
>unless I did it manually. A QUERY OCC * "SYSTEM OBJECT" (without the
>NAMETYPE=UNICODE option) will let you know if you have that problem. Also,
>did you run the command CLEANUP BACKUPGROUPS? For me, on 5.1.1.4 it ran bu
>You can always rename the filespace and allow a backup or two to
>complete before deleting the old filespace.(At least on the NT platform)
This is an excellent suggestion! Also, you don't want to do so many
at a time that your database becomes 'unbalanced' (a level 2 caveat).
Again, identify th
Hi John,
>I've looked at our servers and have over 1.2 terabyte in system object
>data, and 11,700,000 files. This from 1400 nodes. Do you mean to say by
>"delete them" you actually go out and del fi * "SYSTEM OBJECT"?
Yup, delete them, they'll back up again. We had over 15TB in
these files an
I ran into this in my conversion, too:
>ANRD imutil.c(6663): ThreadId<67> Failure deleting
> member 0 585368742 for group 1637 3 - encountered
> repeatedly in loop.
It took an audit (fix=yes detail=yes) to correct. If you
try to run expire invent, you will notice that it has a
tough time end
Hi Fred,
>I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't
>run expiration for six weeks.
It's a pain, I've got a routine set up to find the oversized SYSTEM
OBJECT filespaces and then delete them, but I have two servers with
thousands of WinXP/2K nodes that bloated th
Hi Fred,
I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday.
All I can say is 'not pretty'. This is due to the SYSTEM OBJECT
problem. If you don't know what this is, you will soon if you
have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6
servers.
The basic problem is that T
Is this problem unique to us? Probably not. It's related to a client
problem that showed up about two weeks earlier. An error about
deleting entries from the Expiring.Objects table (or something close
to that). Check out all of your recent ANRDs.
In any event, this error represented a 'corrup
Here is the newly minted APAR number for the problem I experienced
last week:
IC33977
This was the problem that prevented me from upgrading to v5.1.x and
requires a database audit.
It was too late to get everyone's agreement last Friday to run
the audit, so it will happen over the July 4th week
I now have an answer from Level 2 - it's a known problem and
requires a database audit to resolve. This is an 86% utilized
100 GB database and should run two, if not three days (I hope!).
Again the error message was:
ANRD iminit.c(820): ThreadId<0> Error 8 converting Group.Members to
Backup.
>Did you apply the latest patches to 5.1.0.0? (5.1.0.2, I believe.)
Yes, when the v5.1 CD didn't come up, I applied v5.1.1.0 (in
the maintenance section of the ftp site). Same results. It's
acting like some of the database wasn't converted with the
upgrade. I then tried to do ./dsmserv upgradedb,
I now in the process of recovering to v4.2.2.5 from an attempted
upgrade to v5.1.0.0 (from the CD). All went well from an installation
point of view, but when I started the server I got:
ANRD iminit.c(820): ThreadId<0> Error 8 converting Group.Members to
Backup.Groups.
Called it in as a sev
Well, I suppose this makes sense. There was a file called
TSM Timer.txt (or something close to that) in previous versions.
This was a flat ASCII file that kept a date/time stamp for
either the next scheduled event or the next/last contact with
the server. I'll give this a shot, too.
>I can't seem
I was experiencing the same phenomenon - each reboot of the
server would blot out my mtx devices and I have to remove them
and then redefine them. Trying to troubleshoot another problem,
I found that the microcode for the FC adapter cards was
woefully backlevel. Once the cards were updated, no mor
On our well-behaved and moderately loaded system, I am not seeing a
problem with anything in v4.2.2.2 (AIX 4.3.3). However, on the more
'abused' systems, ones that are constantly migrating and have users
on them all the time, the expiration hangs whenever there is a
migration, reclamation or move
So far, the v4.2.2.2 patch on AIX 4.3.3 has held its own for the
past 24 hours, even through several expires. A little more testing
today and then I'll apply it to my problem servers.
I have been collecting a sampling of the output of the show logpinned
command to see what the results look like a
At Andy's suggestion, I called this problem into support. Not for
the faint of heart, but the critical restore that I needed to get
done today has now completed.
This only affects WinNT and Win2K clients and the problem is the
server, not the client. Support says that it will be fixed in the
next
Server: v4.2.1.11 (AIX 4.3.3)
Client: v4.2.1.0 (Win2K), and later patch levels as well
I am getting hit hard by the problem with the Windows client
(or is it a server problem?) resetting the platform and the
version so that an earlier operating system can't access the
account.
Case 1: Client bac
I'm currently in the process of migrating 8 v3.1 servers on VM,
one v3.7 server on Solaris and one v4.1.2.0 server on AIX to
totally different 'homes'. Mostly migrating to AIX v4.3.3 and
TSM v4.1.4.0 (I'm a little gunshy about going to v4.2.whatever
after reading the list lately and with all of th
>At minimum, a command line dsmc & dsmadmc functionality with support for
>HFS+ and UFS file systems. This way the scheduler could be put in a cron
>entry for nightly processes. Personally, I don't care much about a gui
I pretty much agree with the above, but I *do* care about gui for
most of my
We have another issue with Win2K backup of the SYSTEM OBJECT,
namely, that it doesn't update its backup status when an incremental
is run on it:
Node Name:
Filespace Name: SYSTEM OBJECT
Platform: WinNT
Filespace T
Here's a bit more history on the CompuServe Forum. It was set up
and officially supported by IBM because they were in control of
the content and managed the forum itself. This was a service,
pre-web, that CompuServe was offering companies. At a previous
employer, we used CS forums for customer fee
>I can see where a full-function GUI client may take them
>a little time to complete, but the underlying API of MacOS X is BSD
>Unix. I'd expect a command line only client would be easy enough to port
>at least on an unsupported basis to accommodate the early adopters.
There isn't a FreeBSD clien
Much to my dismay, Apple announced yesterday at the start of the
WWDC that they would start shipping all new Macs with OS X along
with OS 9.1 as of yesterday. They will dual boot 9.1 and X, but
I'm sure the pressure to go to OS X will be strong.
We're getting more and more Macs and I can't back t
OS X is very keen (as Richard noted) and will ship on all new
Macs (as Paul noted). It is UNIX essentially, but it's based
on BSD. I have a small, but vocal contingent wanting TSM on
FreeBSD - maybe we could knock off two at once? The alternative
is to hope that TSM works in Classic mode and find
K! I've got a thousand Macs, all of them headed for OS X
this summer. I heard that the Mac developer left and there was
some scrambling to get out a new Mac client that could actually
*restore* (thanks for that!), but to not support OS X would
be devastating for us.
If it hasn't been mentione
I have the same problem, AIX v4.1.2.0. I used the 'delete
backupset' command and it completed successfully, but the
entry still clogging up the volume history file. I'd like to
get rid of it without taking down the server, editing the
file and starting the server up again. The backupset expired
ov
The short answer appears to be "not very well".
We've had a myriad of problems with our Mac clients. First
the scheduler and now the inability to restore folders.
Granted, we are running ADSM v3.1.2.5x on VM, but support
assured me that v3.7 and even v4.1 clients would work
(new features, of cour
I downloaded the Linux client while at SHARE last week and ran
a simple subdir backup to one of my servers at home. All went
well until I went to restore the files - they were nowhere to
be seen! So I shut down the GUI and started it up again (we've
had to do this if we want to do multiple archive
84 matches
Mail list logo
