Thanks, that did the trick. However, now when ADSM starts, it tries to do a
database backup (I have a backup trigger set), but it fails with the error:
ANR1405W Scratch volume mount request denied - no scratch volume
available.
It then issues a database backup failure message and retries again every 60
seconds. I found the scratch volume it was looking for, which was marked as
private, not scratch. It wouldn't let me convert it to a scratch volume, so
I deleted it. Then, the database backup worked. I have about 8 or 9 other
volumes that should be all scratch. Will I have to delete those as well?
Any information would be greatly appreciated.
Thanks,
--------------------------------------------
Jeff Richmond - MCP, CCSA
Jeff Richmond - MCP, CCSA
Systems Administrator
Sharp Labs of America
5750 NW Pacific Rim Blvd.
Camas, Washington 98607
(360) 817- 8463 Phone
(360) 817- 8436 Fax
(360) 910 - 2775 Cell
--------------------------------------------
-----Original Message-----
-----Original Message-----
From: Hilton Tina [mailto:HiltonT AT TCE DOT COM]
Sent: Wednesday, March 17, 1999 9:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: crash on Solaris 2.6
You ran out of log space. You'll need to format a new
volume and then start
dsmserv with: dsmserv extend log new.log.file nn
---> where
new.log.file is the name of your new log file and nn is the
new.log.file is the name of your new log file and nn is the
size. That's
what the book says for AIX, so I assume it's the same or
similar for
Solaris.
> -----Original Message-----
> From: Richmond, Jeff [SMTP:richmond AT SHARPLABS DOT COM]
> Sent: Wednesday, March 17, 1999 12:45 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: crash on Solaris 2.6
>
> All,
>
> I have had another ADSM crash of sorts on Solaris 2.6. I
was backing up a
> small number of clients (4 or 5 servers) with ease, and
all seemed to be
> going well. However, after setting the server to
automatically back up 20
> servers, it crashed sometime the following day. Now when I
attempt to
> start
> ADSM, I get the following messages:
>
> ANR7800I DSMSERV generated at 11:19:12 on Aug 28 1998.
> ANR7801I Subsystem process ID is 15229.
> ANR0900I Processing options file dsmserv.opt.
> ANR0990I ADSM server restart-recovery in progress.
> ANR0200I Recovery log assigned capacity is 596 megabytes.
> ANR0201I Database assigned capacity is 2000 megabytes.
> ANR0306I Recovery log volume mount in progress.
> ANR0353I Recovery log analysis pass in progress.
> ANR0354I Recovery log redo pass in progress.
> ANR0355I Recovery log undo pass in progress.
> ANR9999D logseg.c(493): Log space has been overcommitted
(no empty segment
> found) - base LSN = 3088.0.0.
> ANR7824S Server operation terminated.
> ANR7823S Internal error LOGSEG871 detected.
> ANR9999D Trace-back of called functions:
> ANR9999D 0x000639BC AbortServer
> ANR9999D 0x00060D60 pkAbort
> ANR9999D 0x00534F70 LogAllocSegment
> ANR9999D 0x0052EE54 ForceLogPages
> ANR9999D 0x0052C5C0 LogWriterThread
> ANR9999D 0x00063BA8 StartThread
> ANR9999D 0xEF75501C *UNKNOWN*
> ANR9999D 0x00063AD0 StartThread
>
> In case anyone is interested, I have the client sending
their backup data
> directly to a storage pool called autopool, which is an
IBM 3575 Tape
> Library with a single Magstar "C" drive and 60 Magstar
tapes. I am using
> scratch volumes exclusively.
>
> I am at a complete loss. This is the second time I have
had an ADSM crash
> when setting it to backup more than 3 to 5 clients. Does
anyone have any
> thoughts or ideas? And I was the one who pitched to
management how crappy
> ArcServe was and that we should switch to ADSM...
>
> Thanks in advance!
> --------------------------------------------
> Jeff Richmond - MCP, CCSA
> Systems Administrator
> Sharp Labs of America
> 5750 NW Pacific Rim Blvd.
> Camas, Washington 98607
> (360) 817- 8463 Phone
> (360) 817- 8436 Fax
> (360) 910 - 2775 Cell
> --------------------------------------------
|
