Kelly:
I had this same experience with Notes version 4.5.x so it is probably not
linked to the dot release of Notes
First question is how large is the existing NSF DB's that are appearing to
hang.
You may want to perform a Notes Archive ( or compacting) on these db's
and try your agent again. this will clean up any dead space the agent may
be hitting causing it to hang.
Are you using the latest ADSM agent for Notes v2.1.8
I have a explanation and futuristic informative memo direct form IBM
concerning the Agent hanging on certain databases that I would be glad to
forward you.
If you would like to contact me direct , give me a call, we were able to
get past the agent stoppage , it just required some fine tuning and
re-thinking.
Increasing the tcpbuffsize and tcpwindowsize in the DSM.opt file may be
another area to look at.
Here are some general considerations/suggestions for improving Lotus Notes
database backup performance with today's ADSM solution:
* Clean up the database by using Lotus Notes archiving before performing a
backup. In general, shrinking the size of a database both enhances
manageability as well as decreases backup time.
* If using the Agent for "small" database backup, consider staging the
initial backup so that it is done in several "pieces".
* Perform an off-line full backup of a replicated database using the ADSM
backup/archive client. This has minimal impact on the production system,
and
if used in conjunction with pre-backup archiving (suggested above), will
significantly enhance backup performance. This is IBM's recommended
solution
today. In addition, you can use multiple client sessions per Lotus Notes
server to backup "subsets" of the database, and if each client's backup
"subset" is sent to a separate tape drive, throughput will be improved.
Regards
John Stephens
813-222-6221
Date: Thu, 5 Nov 1998 00:20:52 -0700
From: "Kelly J. Lipp" <lipp AT STORSOL DOT COM>
Subject: Latest version of Notes and the Notes Agent: Problem!
We are having a problem with the Lotus Notes agent for ADSM
when running with Lotus notes V4.6.2a. The environment is a
two-node Windows NT cluster.
Several hundred .nsf files are saved successfully with the agent.
These have all just been created; they each have about 230
"documents" in them, and all save fine. However, there are three
.nsf files with some real messages in them. When the agent
hits these, it just "hangs". The session as viewed from the
server goes into an "IdleW" state. The client is consuming
no CPU or IO. It appears to be just waiting for something.
The only way to stop the agent is to ^C and then do an end
task via the taskmanager. And then, even if Lotus tries to
get into the file, it fails, saying the file is locked. Apparantly
the agent has set some sort of lock on the file, either
internally or externally, and it's not released.
When the client starts up, it prints a message stating that
it was built with the "Lotus Notes API V4.6.1". Is it possible
that this dot release to Lotus has broken the agent?
This problem is somewhat of a showstopper for this site's
rollout of ADSM. Can anybody offer any ideas on how
to deal with this
Kelly Lipp
Storage Solutions Specialists, Inc.
lipp AT storsol DOT com
www.storsol.com
(719) 531-5926
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
|
