I had that happen to my production machine.  However, I could not get the
following command to execute without placing single quotes around the last
two options.  Then it worked just fine.

dsmserv extend log -m 'temporary logfile' 'size'

Anthony Jones
Koch Industries, Inc.
Platform Technologist
316-828-2432

> -----Original Message-----
> From: Lloyd Dieter [SMTP:dieter AT SNRGY DOT COM]
> Sent: Friday, October 23, 1998 9:03 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Recovery log full, Can I get back up?
>
> Hi all-
>
> I've been experimenting with ADSM V3.1.1.0 on an NT machine, and I
> deliberately let my recovery log fill up (I'm experimenting...this is a
> crash & burn machine).  Not surprisingly, the server will not start now.
>
> In the event that this happened on a live machine, is there a way to force
> the server to start, such that the database or recovery logs could be
> expanded?
>
> Also:
>
> With a server which has two drives defined in a manual library, is there a
> way to either tell ADSM which drive to use for a particular operation,
> (i.e. labelling tapes), or perhaps some way to at least determine which
> drive it intends to use for a particular operation?
>
> TIA-
>
> Lloyd Dieter
> dieter AT snrgy DOT com