SearchFAQMemberlist Log in
Reply to topic Page 1 of 42
Goto page 1, 2, 3 ... 40, 41, 42  Next
No Title
Author Message
Post No Title 
I'd think you could kill the server (since you can't shut it down
nicely with halt), and then start up in console mode. That
should let you upd admin and change the password...

Pat Wilson
paw < at > dartmouth.edu

Apologies for the newbie ignorance in advance - I am a
recently appointed sysadmin (AIX v.4.3.2). The
previous sysadmin departed without turning over
selected passwords, including the ADSM admin password.
Is there any way of recovering this password, or
another password sufficiently powerful to change it,
short of re-installing the whole of ADSM on the
server?
I realize that this may seem like a crude attempt at a
hack, but any solution involving root password
knowledge would be just fine.

Thanks
_______________________________________________________
Do You Yahoo!?
Get your free < at > yahoo.ca address at http://mail.yahoo.ca

Post No Title 
Hi all,
I have a an issue on the expire inventory process. It take many time (>1day)
and hangs every time. I have this kind of error message. Does anybody have
any idea to solve it ?

01/05/2000 16:18:15 ANR0390W A server database deadlock situation has been
encountered: lock request for transaction 0:240857645
will be denied to resolve the deadlock.
01/05/2000 16:18:15 ANR9999D imutil.c(2893): Lock acquisition (xLock)
failed
for Inventory filespace 1427 1.
01/05/2000 16:18:15 ANR9999D imexp.c(1241): Could not lock filespace 1427 1
-
will retry on next expiration run.
01/05/2000 16:18:15 ANR0860E Expiration process 105 terminated due to
internal
error: examined 1376288 objects, deleting 386889
backup
objects, 0 archive objects, 0 DB backup volumes, and 0
recovery plan files. 1 errors were encountered.
01/05/2000 16:18:15 ANR0987I Process 105 for EXPIRE INVENTORY running in
the
BACKGROUND processed 386889 items with a completion
state
of FAILURE at 16:18:15.


Salutations / Best Regards
g GE Medical Systems
__________________________________
Eric Boireau GS
Server Architect

GE Medical Systems S.A
283, rue de la Minière
78533 BUC Cedex France
Tél: (33) 1 30 70 39 32, DC: 8*644 3932
Fax: (33) 1 30 70 42 30, DC: 8*644 4230
mailto:Eric.Boireau < at > med.ge.com



Post No Title 
Tons of possibilities off the top of my head...
1) have you tried bouncing adsm ?
2) is any other process running with expiration ? (dbbackup? migration?
reclamation? delete filespace?)
3) any client sessions ?
4) are you up to .40 and have you run the "cleanup archdir fix=yes" ?

Dwight


----------
From: Boireau, Eric (MED)[SMTP:BOIREER < at > EUROMSX.GEMSE.FR]
Reply To: ADSM: Dist Stor Manager
Sent: Thursday, January 06, 2000 6:32 AM
To: ADSM-L < at > VM.MARIST.EDU

Hi all,
I have a an issue on the expire inventory process. It take many time
(>1day)
and hangs every time. I have this kind of error message. Does anybody have
any idea to solve it ?

01/05/2000 16:18:15 ANR0390W A server database deadlock situation has
been
encountered: lock request for transaction
0:240857645
will be denied to resolve the deadlock.
01/05/2000 16:18:15 ANR9999D imutil.c(2893): Lock acquisition (xLock)
failed
for Inventory filespace 1427 1.
01/05/2000 16:18:15 ANR9999D imexp.c(1241): Could not lock filespace 1427
1
-
will retry on next expiration run.
01/05/2000 16:18:15 ANR0860E Expiration process 105 terminated due to
internal
error: examined 1376288 objects, deleting 386889
backup
objects, 0 archive objects, 0 DB backup volumes, and
0
recovery plan files. 1 errors were encountered.
01/05/2000 16:18:15 ANR0987I Process 105 for EXPIRE INVENTORY running in
the
BACKGROUND processed 386889 items with a completion
state
of FAILURE at 16:18:15.


Salutations / Best Regards
g GE Medical Systems
__________________________________
Eric Boireau GS
Server Architect

GE Medical Systems S.A
283, rue de la Minière
78533 BUC Cedex France
Tél: (33) 1 30 70 39 32, DC: 8*644 3932
Fax: (33) 1 30 70 42 30, DC: 8*644 4230
mailto:Eric.Boireau < at > med.ge.com




Post No Title 
Hello,

There are some APARs that describe deadlock during expire inventory :

ERROR DESCRIPTION:
Deadlock situation during expiration may occur when processing
archive objects of converted nodes. If the DeleteFilesThread

deletes a batch of files it holds a xlock on the according
filespace. This prevents the ExpirationSearchThread from
obtaining a slock on that filesspace to report it's position.
While it has to wait to get the slock granted it holds an islock
on the according node id. If now, the DeleteFilesThread processe
s an archive object of a converted node it want to get a xlock
on this node id which results in a deadlock.

If you are running ADSM in AIX, the apar number is IY05562
and the solution is to apply U468795 (service level 3.1.2.50)

Adriana M. Sanchez Abouchar
IBM Brazil
email: adrianas < at > br.ibm.com

Post No Title 
For a similar group of filesystems

/
/usr
/var
/tmp
/home
/DIR1
/DIR2
/DIR3
/usr/lpp/adsmserv
/ADSM_AIX

i´ve defined the following dsm.sys file (on aix)

include /DIR1 mg_aix_s
include /DIR2 mg_aix_s
include /usr/lpp/adsmserv/bin/d*dsm mg_aix_s
include /usr/lpp/adsmserv/bin/log*dsm mg_aix_s
include /usr/lpp/adsm/bin/dsm.sys mg_aix_s
include /usr/lpp/adsm/bin/dsm.opt mg_aix_s
include /home/.../* mg_aix_s
include /home mg_aix_s

include /DIR2

What i want to get is just /DIR2 to be backuped every day, and the other
filesystems on the weekend. But when i start the backup via a schedule job,
it backups everything.

Could someone pls. send me the correct structure for include/exclude? that
i should use?

TIA.
Regards,

Post No Title 
Hi Maria,

as far as you are on AIX I suggest to create an external include/exclude-file
for your contents
and instead of using Domain all-local (default) define only those filesystems
you need.

Regards
Meckï

"María Fernanda YÊpez" <mfyepez < at > BELLSOUTH.COM.EC> on 06.01.2000 23:30:19

Please respond to "ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>

To: ADSM-L < at > VM.MARIST.EDU
cc: (bcc: Ralf Meschonat/Germany/IBM)
Subject:




For a similar group of filesystems

/
/usr
/var
/tmp
/home
/DIR1
/DIR2
/DIR3
/usr/lpp/adsmserv
/ADSM_AIX

i´ve defined the following dsm.sys file (on aix)

include /DIR1 mg_aix_s
include /DIR2 mg_aix_s
include /usr/lpp/adsmserv/bin/d*dsm mg_aix_s
include /usr/lpp/adsmserv/bin/log*dsm mg_aix_s
include /usr/lpp/adsm/bin/dsm.sys mg_aix_s
include /usr/lpp/adsm/bin/dsm.opt mg_aix_s
include /home/.../* mg_aix_s
include /home mg_aix_s

include /DIR2

What i want to get is just /DIR2 to be backuped every day, and the other
filesystems on the weekend. But when i start the backup via a schedule job,
it backups everything.

Could someone pls. send me the correct structure for include/exclude? that
i should use?

TIA.
Regards,

=

Post No Title 
Yes i did, the problem i have is that i have not been able to backup (daily)
JUST the data marked by DIR1

-----Original Message-----
From: Wolf, Stefan [mailto:S.Wolf < at > HZD.HESSEN.DE]
Sent: Friday, January 07, 2000 1:58 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: AW:


Did you restart the scheduler? The scheduler reads the inclexcl file on
startup.

-----Ursprüngliche Nachricht-----
Von: Marma Fernanda Yipez [mailto:mfyepez < at > BELLSOUTH.COM.EC]
Gesendet am: Donnerstag, 6. Januar 2000 23:30
An: ADSM-L < at > VM.MARIST.EDU
Betreff:

For a similar group of filesystems

/
/usr
/var
/tmp
/home
/DIR1
/DIR2
/DIR3
/usr/lpp/adsmserv
/ADSM_AIX

i´ve defined the following dsm.sys file (on aix)

include /DIR1 mg_aix_s
include /DIR2 mg_aix_s
include /usr/lpp/adsmserv/bin/d*dsm mg_aix_s
include /usr/lpp/adsmserv/bin/log*dsm mg_aix_s
include /usr/lpp/adsm/bin/dsm.sys mg_aix_s
include /usr/lpp/adsm/bin/dsm.opt mg_aix_s
include /home/.../* mg_aix_s
include /home mg_aix_s

include /DIR2

What i want to get is just /DIR2 to be backuped every day, and the other
filesystems on the weekend. But when i start the backup via a schedule job,
it backups everything.

Could someone pls. send me the correct structure for include/exclude? that
i should use?

TIA.
Regards,

Post No Title 
ADSMers,
We are beginning the evaluation process of ADSM V3.7.1 Server and Client.
I have seen an e-mail or 2 on the list server regarding V3.7.1 as buggy.
There's a lot of ADSM admins planning the upgrade in the next few months,
could those of you who have, please share any confirmed bugs or issues?

We have had the client running on 6 NT servers in test for over 2 months.
We have also had the Server running on an NT Server in test for a month. We
have found no bugs.

We have been told that HPUX V10 is not supported for the V3.7.1 client.
Not all of our HP boxes are at 11 yet. Can anyone confirm or deny this?

On a separate note:
We are going to be performing a series of tests to see how much data we can
push through NT. We have been told of the limits with NT4.0. We also plan
to test Windows 2000 to see if it has the same limits. We believe the OS
will be the bottle neck on NT4.0 and that the PCI bus will be the limit on
Windows 2000. If anyone has any suggestions for this test please through
them my way.

Environment for Test:
1) Compaq 6400
A. 2 100/Mbs Full Duplex Dual Cards with all 4 ports bound together
B. 3 SCSI cards
C. 90 GB for the Disk Pool
D. First PCI bus
1. RIB card
2. 1 100/Mbs Full Duplex Dual Card
3. Disk Controller
C. Second PCI bus
1. 1 100/Mbs Full Duplex Dual Card
2. 3 SCSI cards
3) StorageTek 9738
A. 3 9840 Drives
B. 28 9840 Tapes
4) Software
1. NT 4.0
2. NT 2000 when gold CD is out.
3. ADSM V3.7.1

Thanks,
Kyle
payne < at > berbee.com

Post No Title 
Hello All

We are running the Oracle connect agent, and the log file continues to grow.
Is there a way to set a log file retention for the connect agent?

Thanks in advance.
Ray Baughman
National Machinery Co.
Phone: 419-443-2257
Fax: 419-443-2376
Email: rbaughman < at > nationalmachinery.com

Post No Title 
SET REPro

Post No Title 
We have been doing some disaster recovery testing of restoring Novell data
servers.
These are all restartable restores and we often see ANR0480W messages eg.
Session 4000 for node PORSD1 (NetWare) terminated - connection with client
severed.
during the restore after which a session restarts and the restore eventually
completes see example stats below.

31-01-2000 05:49:59 ANE4955I (Session: 4068, Node: PORSD1) Total
number of objects restored: 1,941,868
31-01-2000 05:49:59 ANE4959I (Session: 4068, Node: PORSD1) Total
number of objects failed: 0

31-01-2000 05:49:59 ANE4961I (Session: 4068, Node: PORSD1) Total
number of bytes transferred: 15.60 GB

31-01-2000 05:49:59 ANE4963I (Session: 4068, Node: PORSD1) Data
transfer time: 11,704.13 sec

31-01-2000 05:49:59 ANE4966I (Session: 4068, Node: PORSD1) Network
data transfer rate: 1,398.46 KB/sec

31-01-2000 05:49:59 ANE4967I (Session: 4068, Node: PORSD1) Aggregate
data transfer rate: 266.70 KB/sec

31-01-2000 05:49:59 ANE4964I (Session: 4068, Node: PORSD1) Elapsed
processing time: 17:02:50

I have 2 questions really

1) Why do we see these session dropouts average 5 per DR restore.
The restore is taking place from an mvs os390 adsm v3.2.40 server to a
dedicated netware test box on the same subnet as the host, using tcpip 3.2
The netware box is version4, adsm 3.1.06.
Immediately before the dropout query session will show the client in sendw state
for two or three minutes.

2) Why is the restore performance so slow.
We are using STK 9840 tapes (so only 4 tapes mounted)
db cache hits are 99%
Looking through the IBM MVS performance monitor it shows minimal cpu delay, but
some device delay primarily against the database volumes.
When I raise this with IBM they always say its the network, but in this case the
stats
show we are achieving 4.8gb hour network transfer rate.
We are trying for under 10 hours, so we have a way to go and I suspect that we
may need to look at TSM and logical dump/restore to achieve this, but this is
some months away.
In the meantime if anyone else has experience with large netware server restores
and got any ideas how we can improve restore time, I would be very grateful.

Thanks,
John






**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric and Southern Electric are trading names of
Scottish and Southern Energy Group
**********************************************************************

Post No Title 
Apparently, the HP-UX 11 client for ADSM is a 32-bit client. Can anyone
confirm this? If so, has anyone heard when (or if) ADSM will have a HP-UX
11 64-bit client? Does TSM have a HP-UX 11 64-bit client available yet?

IF I can't get a 64-bit client soon, I'll have to SERIOUSLY consider a
switch to LEGATO to back up my Informix databases.


J. Douglas Agnew
Database Administrator
Charlotte Pipe & Foundry

Email: dagnew < at > charlottepipe.com

Post No Title 
Is there an ADSM Server for LINUX?

Fred Dann
Penn Mutual Life

Post No Title 
UNSUBSCRIBE ADSM-L

Post No Title 
Hi folks,
Can someone tell me the meaning of the msg below when we have several tape drives
available for use and no mount messages outstanding ?? We are using an ATL.

Waiting for multiple mount points in device class TAPECLASS (28141 seconds).

Any and all help appreciated.
Larry
larry_heath < at > shawinc.com

Display posts from previous:
Reply to topic Page 1 of 42
Goto page 1, 2, 3 ... 40, 41, 42  Next
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB