Thanks. One thing I'm not clear on is whether I need to set the old B tapes to
readonly or can I let TSM do it for me. IBM says that the new drives will not write
over a non-scratch tape in the old format. When TSM calls for an output tape and the
drive detects the old format will it genrate
Thanks. I just sent an email query for the archives. I had been trying to seach them
from the web, but had no luck. The LSOFT pages show a web archive link at:
vm.marist.edu/htbin/wa
but when I try to link to it I can't get connected. Is there really a web interface
for ADSM-L archives?
-
We are running TSM 3.7.3 on OS/390 2.8. We are getting ready to upgrade our tape
drives from model B's to model E's. IBM says that the upgraded drives will read the
old tapes just fine, but will write them at the new density. I am unable to determine
what, if anything, I need to do to config
This sounds like what we saw when converting to 2.8 last year (are just now working on
2.10). I think it has to do with the telling TSM which TCPIP you are using, IBM's or
something else. There should be an ANRDDDEF member in the SYS1.SAMPLIB for R10. It
has comments describing how to setup
Yes, the backup worked when I corrected the format of the INCLUDE statement to match
your suggestion below. I guess I didn't pick up on this when revewing the INCLUDE
statement in the documentation. Thanks to all who offered help on problem.
---
The select output shows that all the files being backed up, even as recently as last
night, are still using the STANDARD mgmtclass. Below is the configuration information
you asked for in your note.
Thanks for any help.
_
Subject: Re: Can't Get New MGMTCLASS to Work
>Date: Wed, 28 Mar 2001 12:48:55 -0500
>
>Did the NetWare folks recycle the scheduler on the Novell server after
>making the requisite change to the dsm.opt file?
>
>Jack Coyle
>
> > --
> > From: Lo
We are running 3.7.3 server on OS/390. On one of our NetWare servers running client
level 4.1.1 we wanted to start collocating a filespace we were not collocating before.
I defined a new management class and backup copygroup for it. I pointed the
copygroup to new storage pools (a disk pool m
It did not have a max size set on the pool, but the pool was full enough that it could
not fit 5G more into it. This apparently is treated like a file size limit and tries
to dump the large file directly to tape (at least when the storage pool is not full
enough to trip the migration limits).
Thanks, I had looked at these and reset the Novell nodes, just yesterday, I didn't get
around to the Unix ones then or might have avoided this problem today. I did reset
the MAXNUMMP for this node (and my other old nodes), but as I said, I had already
migrated the pool. So, I will have to do
Thanks for your suggestions.
Yes, I had available drives. The only other process using a drive was a DB backup.
Yes, the disk pool is shared and was full enough that the 5G would not fit, so that
explains the tape mount attempt. But I can still find no reason for the job to fail.
We do have
A client is reporting the error below trying to backup a file. The ANS1301E error is
vaguely worded "server detected system error". I can find no errors in my TSM 3.7.3
server log or my OS/390 system log during the time of this backup attempt. Since it
is an "ANS" message, is this error real
For what it is worth, we are at 3.7.3 on an OS/390 server. The automatic delete of
the the backupsets when their retention period is exceeded does not happen. But a
DELETE BACKUPSET command did work to delete the backupset from the VOLHIST and allow
the tape to be scratched.
I have just been made aware that I should be backing up the directory structure for my
Novell servers separately and I have few questions. I have reviewed the documentation
about the dirmc option.
Is there some way to calculate the size of the storage pool I should use for this
management c
We are running TSM 3.7.3 on OS/390 2.8. I have a request from my boss to temporarily
extend a retention period for some server backups. I know where I can reset the
retention information, but it was not clear to me if this would be retroactive for
existing backups or just affect new backups.
I'm just wondering if anyone has any real life experiences to relate about generating
TSM backupsets under TSM 3.7.3 running on OS/390.
We recently had a server failure that took us awhile to restore, for various reasons.
We are looking at possibly generating backupsets on some sort of regul
Thanks for the quick responses referencing the UPDATE NODE command. I have
successfully migrated my nodes.
Louis J. Wiesemann 502-852-
I am running TSM 3.7.3 on OS/390 2.8. I have a set of nodes defined that have already
run some backups, but now I would like to place them in a separate domain. After
looking at the documentation, the only way I can see to do this is to EXPORT and then
IMPORT them back into the new domain. A
What determines that a restore job will be "restartable"? I've looked in both the
server and client manuals but all I have found are instructions for restarting or
querying restartable restores. The online help for the client had some information
about options that would make a restore non-re
ile with the exact name of the file you do not want restored in
the directory where that file lives, and then have TSM clinet not
overwrite existing files. Durring the prepar phase, this file will be
disqualifed for restore operations, and thus skiped.
Keith Davey
On Wed, 20 Dec 2000, Louis Wiese
Is there a way to exclude files when restoring? All of the documentation describes
excluding on backups, but I could find nothing about excluding on restores. We're
trying to restore a volume (NetWare TSM client 3.1.08), but it keeps hitting a certain
file and ending the restore. We would li
I'm just looking for any guesstimates anyone might have for the throughput we might
"expect" to see restoring a Netware 3.1.08 client with a TSM 3.7.3.0 OS/390 server.
This is over a 100M ethernet with 3490 tape robot on the server. We have split the
restore up over 4 sessions and have disabl
We are running TSM 3.7.3.0 and trying to complete a large restore from over the
weekend which had to be restarted last night due to a hardware problem. It is my
understanding that restore requests will only use one tape drive for mounting restore
volumes. My boss is asking if there is a way
This is from our GroupWise people:
Our GW is running on NW5.0 SP5.
Yes, we back up all the GW boxen with agents running. I haven't checked the logs that
closely but suspect we're not getting open files. We're investigating reimplementing
St. Bernard OFM product at
We started getting these on our OS/390 server when issuing commands from our TSO admin
client after upgrading the server from 3.1.2.50 to 3.7.3. Support indicated that it
was not a real problem, just a nuisance message. They also told us that it was just
an issue for the TSO client that they
We have seen this problem a couple of times now and were wondering if anyone has any
suggestions for an easy way to deal with it. We have seen someone who is not a
registered node on our OS/390 TSM 3.7.3 server attempt to access the server with a
client. Of course, they get rejected as an inv
I am also working on the upgrade to TSM. Can anyone give more specific information
about how long I might expect the UPGRADEDB to take? I only have an 8G database, but
some other database processes I have used took many many hours. It would be nice to
have some idea how long this might take.
The last time I tried this (on ADSM v3.1.2.40 with about a 6G DB) it ran for a day and
a half over a weekend before I canceled it. This was on a 9672-R51 with 512M memory.
Louis J.
I have a client running the TSM 3.7.1 client on AIX. They are trying to backup some
files that they do not own but do have access to. The client documentation indicates
that you can backup files you don't own if you have been given access. They were
previously using a version 2 client and we
29 matches
Mail list logo
