Without Recovery Log free space, ADSM/TSM can't have any other
transactions allowed. Do one of these :

1) backup db devclass=... type=...

When you backup ADSM/TSM's database, recovery log is cleaned
up. You can run incremental backups as long as your log is in
rollforward mode (what looks like it is).

2) extend log

Allocate more log space, so you won't run out of log space
again in little time.

3) Set backupdbtrigger

Based on log usage, automatically runs backup db. See 1.

If you don't enough disk space for the recovery log, set it
to normal mode (circular area) and give up incremental db
backups.

regards,
Rodrigo

From: "Jeffus, Dan" <Dan.Jeffus AT FLHOSP DOT ORG>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: FW: TSM errors
Date: Fri, 10 Dec 1999 09:16:18 -0500

> We got this message on several  Novel servers tring to backup with TSM
> last night. Any ideas what this means?
>
>
> ANS1364E Session Rejected: The server does not have enough recovery log
> space to allow a connection to be established.
>
>
> Dan Jeffus
> Intel Systems
> Florida Hospital
> 407-303-5600-5491
>

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com