Hello, I'm getting an error when starting TSM Server and the server is not
starting
We have TSM 5.2.1.0 on an Z/OS.
We did an UNLOADDB followed by a LOADFORMAT a LOADDB an AUDITDB. All of them
ended ok, but when I try to start the TSM Server I get the messages:
ANR0900I Processing options
Anton -
I'm sorry to see you in this situation. The List archives reflect only
two instances of people encountering this in the past, and they posted
no follow-up resolution. I recommend that you contact TSM Support as
your next step.
I rue the day that IBM started encouraging customers to take
Hi Li!
It depends. If you are doing LAN-free to a similar device, then you do not
have to use separate adapters.
However, when you are doing LAN-free to tape or to storage which requires a
different device driver, then you will need separate adapters. IBM does not
support disk and tape I/O through
Here's one possibility:
If the TEC server is not up or not accessible when the TSM server
starts, the Tivoli event logging will be disabled. You can restart it
with the BEGIN EVENTLOGGING TIVOLI command.
This has been happening to me sporadically because sometimes the TSM
server starts before
Rob,
I couldn't agree more with Mark. Please read the introduction to TSM.
When I look at the name of your copy storage pool (3581_week2) it seems
that you are still working in a full/incremental way. This is not how
TSM works.
This is about the 'progressive backup' in TSM and taken from the TSM
and things such as an admin sched of BEGIN EVENTLOGGING TIVOLI to run
every 24 hours can be very handy...
(helps recover from any connectivity problems with your TEC server)
Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918)
I have a client that is trying to set up encryption for some files. TSM 5.3
client:
ENCRYPTIONTYPE AES128
ENCRYPTKEYSAVE
The first time he used the GUI to backup the files he was prompted, but there
was no indication that the INCLUDE.ENCRYPT files were
encrypted.
Is there a way
(from the Windows Administrator's Guide, page 201)
[When checking in a single volume into an automated library,] a REPLY
command is not required if you specify a wait time of zero using the
optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The
default wait time is 60 minutes.
--
Mark
Anybody out there know how long 3590 K series tapes last ( I assume in
years). I am trying to figure if our recent batch of tape/drive errors are
from tape drives and old tapes. Seem to be older number tapes giving the
errors,
Would appreciate any knowledge on the subject or direction of where
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of William Boyer
I have a client that is trying to set up encryption for some
files. TSM 5.3 client:
ENCRYPTIONTYPE AES128
ENCRYPTKEYSAVE
The first time he used the GUI to backup the files he was
prompted, but there
That's exactly the workaround I was just about to implement. I presume
there is no harm in issuing this command multiple times? As far as I can
see there is no problem doing that, but you never know. The weirdest
problems are the ones that don't manifest themselves until after you've
done
Oh, sure, blame the media. (old joke :-)
In http://www.thic.org/pdf/Oct00/imation.jgoins.001003.pdf
Imation says that for the Avanced Metal Particle 1 tape formulation used
in 3590 that media life should be expected to be 15 - 30 years, with
5 - 10% magnetization loss after 15 years.
The greater
I'm sure it really depends on the number of mounts and
reads/write cycles that the tape goes through. The problem with the
3590E tapes is that once they are taken out of the library, the number
of mounts is lost, so actual mounts per tape is a pure guess if you have
offsite copypool tapes
== On Wed, 30 Mar 2005 07:25:17 -0500, Richard Sims [EMAIL PROTECTED] said:
I rue the day that IBM started encouraging customers to take their TSM
system out of service and run salvage utilities to reorganize the db, as
situations like this inevitably result, particularly as these utilities
Oh mighty Gurus.
Please forgive my naive question..
We are running out of slots in our library and I have examined
some of the tapes and have found that some of them haven't
been read for 1 1/2 years and some haven't been written to
in 3 or 4 years.
Can I eject these tapes and store
Never got a reply to this, so just in case it never got posted:
Our DR tests of using a backup TSM server with the exisiting 3494 tape
libraries ran into problems.
The setup:
- both the DR TSM server and the Prod TSM server are connected to the
switch and the libraries (lmcp) points and the
#1, what's your retention for this data if you don't need it reuse the tapes.
#2 if they aren't at 100% do move data on them to free up the tapes that way.
#3 if your solution calls for long term storage then just check them out and
you should be good to go.
-Original Message-
Quick answer. User the query media and move media commands.
Query can show you in order, how long tapes have not been used.
Move media then allows you to move (er checkout) tapes that haven't
been accessed in a certain number of days.
If one of these tapes is later needed, TSM will prompt for
Sorry, I think maybe you were also looking for clarification on your checkout
command. This is what we use.
checkout libvolume library volume checklabel=yes
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Dave Zarnoch
Sent: Wednesday, March 30, 2005
We have had to do this in the past to free up library space.
Rather than using the checkout libvol command, I would suggest using the
functions within the TSM server to store tapes outside of the library:
the move media command.
Do a 'help move media' for how it works.
On Mon, 28 Mar 2005 12:11:38 -0500, Rob Berendt [EMAIL PROTECTED] wrote:
Judging by one of your other emails, is reclaimation a process to merge
partial tapes together? If so, that really doesn't interest us. It
doesn't fit into our backup strategy.
May I suggest that perhaps your backup
This is for a client Oracle TDP on Solaris 8 with TSM Server W2K, v
5.1.6.3.
Simple question, is warning message ANR0425W password has expired anything
to worry about? Because I can't seem to make it go away and it doesn't seem
to be stopping the backups?
The help file shows, System Action:
We recently migrated from a locally attached 3590 E11 tape drive to two
3592 tape drives in a 3494 tape library. We installed TSM 5.2.4.0 on a
p5 570 lpar running AIX 5.3. Our data is on an IBM ESS 800. Every day
we quiese the application and flash copy it then mount the flash copy
volume
On Mar 30, 2005, at 2:14 PM, Miller, Ila wrote:
...The data is mounted to the TSM server so
the TSM server is also the client and the data should not be going over
the network at all. ...
Just a minor thought: Your COMMMethod is probably TCPIP, meaning that
the I/O would be going through the
We also recently migrated from SCSI attached 3590E drives to SAN
attached 3592 drives (both in a 3494 library).
Unfortunately, we only saw an increase in the performance with
the new tape drives.
As Richard mentioned, it may be an issue with the mounting of
the data on
Oh mighty ones!!
Thank you so much for all your help!
I was able to move 100 tapes out of the silo
I used the move media command.
DaveZ
You are correct Richard, my version's command is tdpoconf password. This
prompts you for the existing password and the twice for the new one.
I have successfully used this to change the password as with the GUI on the
server side and the command line on the server side.
I have successfully made
COMMMethod is set to SHAREDMEM and has been that way from the start.
I'm got tracing turned on now so we will see if that reveals anything.
Here is the summary of our archive from last night. Network(FIBER)
throughput seems to be ok but the Aggregate is abysmal. Compression is
also turned off
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Galloway, Gary M
COMMMethod is set to SHAREDMEM and has been that way from the start.
I'm got tracing turned on now so we will see if that reveals anything.
Here is the summary of our archive from last night. Network(FIBER)
Daniel,
one can remove last database backup using an undocumented parameter
force=yes in the delete volhist command.
S pozdravem / Best Regards,
Martin Trcka, IT Consultant
Tech. Support Department
GC System a.s., Spitalka 41, 60200 Brno, Czech Rep.
mob: +420 602 452 361
fax: +420 543 537 333
I turned on tracing and ran an archive with the following command:
dsmc archive -traceflag=service,memory
-tracefile=/tmp/tsm/trace/dbext_trace.out -tracemax=5000 -verbose
-desc=Old IDX Tape Backups for /restore/dbext - 2005Mar30
-filelist=/tmp/tsm/archive_list_dbext_2005Mar30 -archmc=AIX-1YEAR
Posting at the request of Darrius Plantz ([EMAIL PROTECTED])
ADSM.org URL added to the TSM support website!
Please see the IBM Tivoli Storage Manager website at:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorag
eManager.html
Look for the section titled Other
I want to add a comment.
The point to me is that an audit db FAILS to detect and correct the error.
Period. And thats is not good since we reley on our db to read our tapes.
An unload may discover a corruption and we have the possibilities to audit
or dump our db.
And when thoose option
33 matches
Mail list logo
