This is my first post here after months of lurking. I'd like to start by
thanking Richard Sims for his marvelous ADSM.QuickFacts. Because of that
file, my employer thinks that I'm far smarter that I am. Thank you!
There's one thing, though, that I haven't been able to figure out in the
TSM doco
Thanks for the responses...good stuff.
> Perhaps you have your
> resourceutilization set to greater than 1 and your management class/copy
> group is sending the data directly to tape.
Is there a reason to set resourceutilization to more than one if a backup
is performing OK? To put it differentl
> Is it possible that there are two or more sessions running for the TDP
client simultaneously?
Yes, absolutely. The Oracle DBAs have observed that this happens most
frequently when there's media wait, in which case multiple log backups
could be running simultaneously.
How do others handle this?
> Sorry for the long-winded response, I was on a roll! Hope it helps...
This is exactly what I needed. I was considering putting the Oracle TDP
backups to disk (though we're tight on disk space). I didn't realize that
they wouldn't go down the storage hierarchy, though. Thanks for the
heads-up
What are folks using to do TSM trending? I need to answer questions like
these:
- How long will our current supply of scratch tapes last, assuming
constant usage?
- If I add TSM clients similar to an existing client,
how will it affect my tape usage?
- What's our peak drive usage (smoothed over
> Remember that LAN-free backups are often no faster
> than 100MB/1GB Ethernet LAN-based backups. (In a few
> cases they will actually be slower.)
Mark, can you say some more about that? We're hoping to start doing
LAN-free and I was hoping that we could see some nice improvements in
large backup
> Does anyone know if COMMTIMEOUT is a dynamic variable? I would like to
> change it but I am not sure if I need to restart TSN for it to take
> effect.
I believe SETOPT will change COMMTIMEOUT dynamically.
anker
Wow! What a massive outlay of effort. I'm not familiar with virtual
volumes. If your problem is specific to them, then what I have to say is
way off base, in which case I apologize in advance.
First, I do BACKUP STORAGE POOLs hourly from my *disk* pools. This gets
most of my data out to the co
> They would like backupsets created so that when we have a dr drill they
> can restore the filesystems that I put in the backupset immediately and
> very quickly without needing many tape mounts, etc.
Is group collocation not an option?
anker
> I'm not at TSM 5.3 yet,
Sorry...I read your original post too quickly and mistook the AIX level
for your TSM level.
I don't suppose you can hold your customer off until you move to TSM 5.3?
We had a brief fling with backupsets under TSM 5.2 and were sorely
disappointed. We never really figure
> You sound like your infrastructure is more steady-state than
> mine. 90% of my daily workload comes in between 1700 and 2300, so I
> don't do copies hourly.
Yes, that's a wicked tight window you have! My backup window is
wider--about 1700-0700, so I go ahead and let the copies run hourly all
n
One of my fellow sysadmins is planning to set the clock on a TSM client
ahead by eight months (to test daylight savings time changes). He asked
whether TSM would expire files that had exceeded their normal 31-day
retention. I assured him that all expiration processing is done on the
TSM server an
We need to move an HSM-enabled filesystem from one TSM client node to
another. The old client node is a venerable S70 (Regatta class machine)
running AIX 5.2 with a 5.2.2.0 TSM client. The new client node will be
running AIX 5.3 with (unless I hear recommendations to the contrary from
the list) t
Excellent information, Ian. Thanks for the heads-up on JFS2 and on the
re-backup.
anker
I have another test for the HSM wisdom of the list. I mentioned that
we're preparing to move an HSM-enabled filesystem from one TSM client to
another. The filesystem in question has a couple of directories inside it
that aren't HSM-appropriate. My users have suggested that when we build
the HSM
> I believe that the best HSM transfer method is to first perform a
> recursive dsmmigrate of all its file system data, which leaves only
> stubs or small files in the file system. This is to make the later
> restoral faster. On the new system, you would establish a file
> system having the name
> We're considering using HSM
HSM has been nothing but a headache for us. It's a vicious, horrible
piece of code. We've been running TSM for 8 years and have been very,
very happy with it--except for the data that was lost in an HSM mishap.
Managing HSM is a nightmare. I would cut my own head
We are looking at upgrading our TSM servers from TSM 5.3 to TSM 5.4. In
reading the deployment guide, I noticed that TSM 5.4 no longer supports
Windows 2000. I mentioned this to our Windows folks, who are now in a
state of panic, since we have quite a lot of W2K in house. On giving it
more thoug
We appear to have lost some files in HSM. One of our users created some
files ten days ago. He inadvertently deleted them four days ago. Since
our migration expiration option is 7 days, the files should still be
available via the dsmmigundelete command. Right? This assumes that
1.) The dir
We're about to upgrade from TSM server 5.3.3.0 to 5.4.1.1 on 2 TSM
servers. I've read through the upgrade procedure. It looks simple
enough. We're already running 5.4.1.1 on another TSM server with no
problems, so I'm not too concerned about that. I've looked through the
listserv archives and n
> I would suggest you go all the way to 5.4.2.0.
Thanks for the comment, Mark. Usually I'd agree with you. In this case,
we want to match the level we have on our third TSM server. We like to
keep as few variations of maintenance inhouse as we can, and that level
has worked flawlessly for us.
21 matches
Mail list logo
