On Dec 20, 2006, at 10:02 AM, Kerry Campbell wrote:
...As a second question the report tells me that
the "% of diskpool utilization is at 99.8%" should I be concerned
about this?
Do storage pool queries. It's only an issue if Migration isn't
happening, to drain that disk pool to the next st
Yes. Check if the scheduler is running on that system and review the
dsmsched.log on the system that missed the backup.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kerry Campbell
Sent: Wednesday, December 20, 2006 8:59 AM
To: ADSM-L@VM.MARIST.E
, September 04, 2006 5:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: missed backups oddity
Maybe you could try running a shell script
that does a 'query session' every 5 minutes
and redirects the output to a log file.
That should tell you where all the sessions
come from.
Something like th
l
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Verkooijen
Sent: Monday, September 04, 2006 5:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: m
Maybe you could try running a shell script
that does a 'query session' every 5 minutes
and redirects the output to a log file.
That should tell you where all the sessions
come from.
Something like this should work:
--- CUT HERE ---
#!/usr/bin/ksh
while true
do
/usr/bin/dsmadmc -id="xxx"
We have >1% miss rate on Win2k and higher running 5.2.2.10 agent or
higher. We use the CAD to manage the scheduler. Many failures have
been traced to the scheduler hanging on agents lower than 5.2.2.10 (not
saying this one is perfect) so we have standardized on this version for
now. 5.2.4.0 look
On Jan 4, 2006, at 12:50 PM, John Monahan wrote:
I've noticed a dramatic increase in reliability/stability in
letting the
client acceptor daemon (CAD) control the scheduler. In many cases you
don't have to restart services every time you make a options file
change
with this method either. ...
I've noticed a dramatic increase in reliability/stability in letting the
client acceptor daemon (CAD) control the scheduler. In many cases you
don't have to restart services every time you make a options file change
with this method either.
The only time I notice missed backups nowadays is when t
For Windows clients:
I had a lot of problems with the service stopping using 5.1 TSM clients
on Win2K.
Sometimes it just died, all would die about once a month. I think at
5.1 there was a known memory leak; got better with 5.2, even better with
the 5.3 client.
What I recommend is setting the Win
It's definitely not supposed to happen. I have it happen occassionally
on a lesser scale than what you're describing, and it's almost always
Windows clients. Some of them I tracked to oddities that occur when you
install the client through rdp session instead of at the console. Some
of them I st
Maybe you don't have stopped and started the ADSM Scheduler Service on WNT since those
days. Once you have a modification in the disks configuration, you have to stop and
start the service to let the ADSM to know about taht.
Angel Antón
IZFE. S.A.
Plaza de Pinares, 1-3
Donostia 20001
Tlf.: +34
you need to check the permissions on the E_Drive...
-Original Message-
From: Thomas Denier [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 01, 2000 4:59 PM
To: [EMAIL PROTECTED]
Subject: Missed backups on Windows NT
We have a Windows NT client with C, D, and E drives. The central s
12 matches
Mail list logo
