ADSM-L

Re: ADSM Problems

1997-11-17 14:12:26
Subject: Re: ADSM Problems
From: Daniel Thompson <thompsod AT USAA DOT COM>
Date: Mon, 17 Nov 1997 13:12:26 -0600
Richard,

 We had an identical problem.  This server was due to be upgraded so I
simply
ran a bat file via AT until that time.  After the upgrade (memory, NT, hard
drive) the problem was gone.

I would try the standard "I don't know whats causing the problem but I'm
trying stuff to fix it anyway" solutions.
.reboot
.uninstall-reinstall ADSM
.run registry checking programs
.Run disk utilities etc.

Hopefully, someone has actually figured this problem out and responds.

Good luck,
 Dan T.

----------
> From: Smith, Richard <smithrr AT MARITZ DOT COM>
> From: Smith, Richard <smithrr AT MARITZ DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ADSM Problems
> Date: Friday, November 14, 1997 1:13 PM
>
>         I am trying to backup a NT server with ADSM.  The problem I am
> having is that I can't backup the F: drive.  This drive is a RAID disk
> drive.  The lettering sequence is a little different also, we have
> drives C:, D:, then D: is mirrored where E: would be, then we have the
> F: drive.  We run the scheduling service as a system account and it
> backs up the C and D drives fine, however, it says that F is an invalid
> drive specification.  All of the drives are labeled in the same manor:
> Servername-driveletter.  If we run the Scheduler service under the
> administrators ID, which is God to the machine, it sees the F: drive and
> tries to back it up, however, we get access denied errors.  Not only do
> we get this error on F: when we do this, but we get the same errors on
> C: and D: which work fine the other way.  If we run a manual backup
> through the backup client we can back it up fine also.
>
> Thanks,
> Rick Smith
> Maritz, Inc.
> Storage & Security Administration
> smithrr AT maritz DOT com
> (314) 827-1584
<Prev in Thread] Current Thread [Next in Thread>