Re: ANS4147E invalid device error on nt volume set

Alex,

  We have seen this problem, and I have no explanation.  I scheduled a
backup of the "bad" drive via a bat file and the NT scheduler service.  We
intended to research the problem, but the machine was slated for
upgrade/rebuild and the problem was gone after this was done.  I could see
no discrepancy on the drive when looking with performance monitor, srvinfo
or disk administrator.

We have never had a chance to resolve the problem by using the ADSM v3
client.  If your server is v2, you can run the v3 client to see if it fixes
the problem, so why not do it?

good luck,
  Dan T.

----------
> From: Alex Mounayar <Alex.Mounayar AT SMED DOT COM>
> From: Alex Mounayar <Alex.Mounayar AT SMED DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ANS4147E invalid device error on nt volume set
> Date: Wednesday, January 07, 1998 3:20 PM
>
> We are having a problem backing up a nt volume set with the
> scheduler.  We are running the version 2 nt client on a nt 4.0 intel
machine.
>  The following error logs to schedule log:
>
> 12/30/1997 02:16:52 ANS4147E Drive E: is an invalid drive specification
>
> The E: drive is a multi-volume volume set made up of 3 whole disks and
1/2 of
> another disk.
> The ba  gui client does not give the error message and backs up the
volume.
>
> Has anyone else seen this problem or have a fix?
>
> Also does anyone know if the v3 nt scheduler would work?
>
> Thanks
>
>
>
> *