If I remember correctly the TSM "service" process, which runs under a
"service context" has no visability to networked drives. This is a
Microsoft issue (I've had that problem with other products being run as a
service).

Drives are networked and visable in a "user" context.

To demonstrate, if you stop TSM and start it in CMD prompt (with the drive
mapped), it will see all local mapped drives, and your backup will
probably work.

This is one example where TSM would be better on Linux :-)

...deon
---
Have you looked at the A/NZ Tivoli User Group website?
http://www.tuganz.org

Deon George, Customer Support Account Engineer, IBM Australia
Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816,
IVPN +70 66058
mailto:dgeorge AT au1.ibm DOT com, http://www.ibm.com/tivoli

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 17/07/2003
05:30:59 AM:

> Have you checked the access permissions to F: ?
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Tae Kim
> Sent: Wednesday, July 16, 2003 11:55 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: backup of volhist and devconfig files
>
>
> I am currently trying to backup devconfig and volhist to a networked
> drive under windows
>
> Here is the command I use
>
> Backup volhist filenames=f:\test\volhist.out
>
> Backup devconfig filenames=f:\test\devonfig.out
>
> I always get the error
>
> ANR2391E BACKUP DEVCONFIG: Server could not write device configuration
> information to f:\test\devonfig.out.
>
> Are we not allowed to backup the volhist and devconfig to a networked
> drive?
>
> TIA
>
> Tae