Hi,
I am trying to define a drive in TSM level but getting the (ANR8420E)
above-mentioned error.
At OS level the tape drive has been defined in /dev directory as st0
(Seagate DAT 20/40, internal drive 4MM with IBM stamp, 9SP40-000). The
working of DAT drive has been checked at OS level with the
Hello all!
Problem solved! I forget about HBA Bios. Guys some time ago upgraded QLogic HBA
firmware, by default in BIOS option FibreChannel Tape support is disabled.
Yesterday i check HBA Bios on all windows servers, change this option to
Enabled and all worked fine!!!
Hi experts,
After checking the logs it has been observed that dsm generated an core dump
on one of the backup node.
What could be the possible reasons for the same?
Any suggestions or ideas are welcome?
ERROR DETAILS are as under: -
hi,
thanks
q: how about LTO2 drive , can it read or write LTO3 media ?
if yes then probably with LTO2 specs , right ?
goran
- Original Message -
From: pelson [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Sunday, May 08, 2005 12:09 AM
Subject: Re: hi tsm'ers ! UPGRADE question
We are
On May 16, 2005, at 3:31 AM, Akash Jain wrote:
Hi experts,
After checking the logs it has been observed that dsm generated an
core dump
on one of the backup node.
What could be the possible reasons for the same?
Any suggestions or ideas are welcome?
...
SIGNAL NUMBER
6
...
When
Hi,
It seems like you forgot to define the path from the
server to the tape drive, and the 2nd line doesn't
quite look right to me. It should look like this:
define drive manlib IBMDRV
then define the path:
define path server_name IBMDRV srctype=server
desttype=drive library=manlib
Hello everyone,
Ok we just returned from our DR Test and unfortunately it was a flop. No
big deal I learned something.
Management now wants to know the cost involved at having TSM up
constantly at a hotsite. For some reason I cannot wrap my mind around
exactly what would be the best way to do
I've got a client node, which is a moderately large AIX server, and
which PASSEXP is set to 0, and which is using PASSWORDACCESS GENERATE,
that all of a sudden started getting:
ANR0425W Session 44114 for node NODENAME (AIX) refused - password has
expired.
I got it backing up again by setting a
Hello !
What I would like to get is a select like this below, but I would aslo like
to get some information if the listed volumes are in a process or session?
If that is possible, how do I do?
Select cast(volume_name as char(6)) as Volume,
Cast(substr(stgpool_name,1,16) as char(16)) as Storage
Hello all,
I recently upgrade my tsm servers to AIX 5.3 ML1 running tsm 5.2.3.3
since our aix upgrade, our database backups went from 20-35 minutes per
server to about 2-4 hrsanybody else experienced this and any
suggestions? This is the only significant event that has happened to
lead me to
One of the client admins here installed Windows TSM Client Version 5, Release 2, Level 4.0 on a Win2000 machine.
All is okay for about 5 seconds then the TSM Scheduler service just stops. The client dsmerror.log shows the following message;
UseExternalTimer: Unable to open timer file '\s4l8.',
Andrew --
Was the problem in recovering the TSM server, or recovering the
applications after the server recovery? What platform/version?
I've been recovering TSM (AIX) in about 4 to 6 hours for several years
now, and recovering SAP/R3 (Oracle) and MS-Exchange to most recent
available backups in
Shannon -
I don't have enough context on your environment, but it should like
your site is not using the TSM Scheduler directly, but instead via the
Client Acceptor Daemon. Per the client manual: the CAD serves as an
external timer for the scheduler. When the scheduler is started, it
queries
I have never heard of this applicance; but my first question would be,
whatcha gonna do when you have to take your tapes to a DR site?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Johnson, Milton
Sent: Thursday, May 12, 2005 10:18 AM
To:
1) You will need appliance(s) at the DR site, consider it an accessory
to your library.
2) The appliances I've seen allow:
A) Backing up the keys to DR media (CDROM, Smart Cards, files, etc.) for
use at the DR site
B) Hot appliance(s) can be kept off site but on the network, (i.e. your
DR Site or
Actually the problem was the server that we received from our Hot Site
provider.
The server is an AIX 5.1 server with TSM version 5.2.1 installed.
The problem was that the fibre attached disk that they gave us were
extreemely slow. I have a 48 GB database and formatting the database so
I could
I have a 48 GB database and formatting the database so
I could restore to it took 9 hours in itself, TSM was available in 12
hours. In a 24 hour DR Test this is not good
Two thoughts.
1. If it took that long to format, it might not just be a disk issue. What
CPU configuration was on the
Not withstanding the issues of the time it took to format the volume,
when it comes to bandwidth TO the hot site, you could look at buying
some dark fiber along the way somewhere between the primary and standby
sites. We've actually been investigating this ourselves but not with any
real effort as
ARGH!
My database is 30 GB. And I format it as 3 10 GB volumes. Our hot-site
config has three fiber HBAs into the disk, with SDD used for virtual
pathing; the format/format/db restore takes about 45 minutes.
They didn't, by chance, have the tape drives fiber-attached via the same
HBAs as the
We have a 16GB TSM DB. The disk on the DR was preallocated and
defined.
A restore took 20 minutes.
[EMAIL PROTECTED] 05/16/2005 1:56:49 PM
I have a 48 GB database and formatting the database so
I could restore to it took 9 hours in itself, TSM was available in 12
hours. In a 24 hour DR Test
I don't know the specific trouble, but I suspect it is some kind of
configuration issue. The only advice I can offer is to try removing and
reinstalling the client:
1) Stop all running instances of the TSM client, including services
(journal, scheduler, CAD, remote client agent) and interactive
We have a mix of AIX and Windows.example below.
On deleting individual filespaces on AIX there is no problem, as:
del file aixadmin /usr
However, trying to delete individual Windows filespaces causes probems.
All files can be deleted but individula filespaces
specified returns a not found
Roger,
I've seen this happen a couple of ways.
I doubt it really Expired, it's probably just corrupted.
I've seen it happen when someone applied maintenance to AIX that somehow
(we never figured out how) stomped around in /etc/password.
Also if you are using the new NIC with a new IP address,
Have you tried enclosing the UNC path within quotes? (), or if you don't
want to deal with that you can also delete the filespaces by filespace ID.
delete filespace {node} {filespaceid} nametype=fsid (delete filespace
AFSDBMS 3 nametype=fsid for example)
Worst comes to worst, you could try
Delete it using the FSID. del files nodename fsid# namet=fsid
Using your example, del file afsdbms 3 namet=fsid.
###
Joe Howell
Shelter Insurance Companies
(573)-214-6534
[EMAIL PROTECTED]
Lawrence Clark [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager
Use the filesystem number format instead:
del fi afsdbms 3 nametype=fsid
With Winders and unicode you may be running into codepage issues. Just use the
FSID insteadand make sure you type carefully!
Don't want to mistype the wrong number.
Bill Boyer
Some days you're the bug, some days
Hi Everybody!
My Environment is TSM V 5.1.1.6 on Win2k SP4.
Did you ever found fix to the problem below? I'm getting the same error
messages and won't let me edit the client nodes.
Please let me know! Any one please help!
Thanks,
Greetings all!
Environment: TSM V 5.1.1.0 on Win2k SP3
Backup is working fine, but to further avoid any errors I want to identify
the reason for the same.
We are working on TSM version 5.1.0.
Regards
Akash Jain
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Richard Sims
Sent: Monday, 16 May 2005 5:05
I had a similar problem, turned out to be the Qlogic card.
The machine had happily worked away with the same config for ages, then
started throwing anr errors. There was no indication in Windows or
the Dell logs of any problem, only in TSM. Turned out to be the Qlogic
card, updating the
29 matches
Mail list logo
