First, try to find out why you're running out of space. Lots of apps
and Windows keep logs, and it's possible that by pruining logs you can
recover enough space to operate normally.

If log prunning doesn't clear enough, you can send the ADSM log to
another drive: The folowing is clipped from the Using the Microsoft
Windows Backup-Archive Clients online book.



The schedlogname option specifies the path and file name where you want
schedule log information stored.
When you run the schedule command, output from scheduled commands
displays on your screen. It is also
sent to the file you specified with this option.

Use this option only when you run the schedule command.


Syntax

>>--SCHEDLOGName filespec-----------------------------------------------><
Parameters

filespec
     Specifies the path and file name where you want ADSM to store
schedule log information when it
     processes scheduled work. If you specify a file name only, ADSM
stores the file in your current directory.
     The default is the installation directory with a file name of
dsmsched.log.



Examples

Options file:   schedlogname c:\mydir\schedlog.jan

Command line:   -schedlog=c:\mydir\schedlog.jan



Jack Xu wrote:
>
> ADSM client is installed on the C drive of an NT server. For some reason,
> the C drive is out of space later, will this cause the NT server failed to
> backup to ADSM because it can't write to the log which is located on the C
> drive?
>
> Thanks
> Jack