ADSM-L

Re: WinNT 32 bit client v2r1.3 Invalid Drive ANS4147E

1996-11-14 19:33:09
Subject: Re: WinNT 32 bit client v2r1.3 Invalid Drive ANS4147E
From: Jim Larson <jalarson AT MICRON DOT COM>
Date: Thu, 14 Nov 1996 17:33:09 -0700
Make sure that the SYSTEM account has access at the root of your NTFS
partition.  That is the account that your service is using.

        Jim Larson

>-----Original Message-----
From:           Eric LEWIS
Sent:           Wednesday, November 13, 1996 1:07 PM
To:             Multiple recipients of list ADSM-L
Subject:        WinNT 32 bit client v2r1.3 Invalid Drive ANS4147E
     We find that the GUI client sees drives C: D: and E:, highlights
them
     as candidates for backup, and backs them up when an incremental
backup
     menu pick is made.

     However, the dsmc client does not see the E: (NTFS) drive and thus
     does not back it up.  We added a Domain statment to make the drives
     explicit and when a scheduled backup next occurred the ANS4147E
     message appeared instead of the backup we had hoped for.  E: drive
is
     is seen by NT as an extended partition drive, drive D: is the first
     partition on the physical volume.

     We have tested extended partition drive backups on other
     configurations.  Our problem occurs on an HP Netserver 5/133 LS2.
The
     DASD configuration includes a Mylex Raid controller card and that
may
     be a clue to our problem solution.  The Mylex controller specifies
to
     NT two drives (C; and (D:, E:)).  (Once a LISP programmer . . .)

     We feel that the problem lies with the DSMC code, rather than the
     Mylex controller because the Backup GUI does work as expected and
we
     feel that both pieces of code should be able to see the same
drives.
     Can someone offer any help or clues?  Thanks for your help.

     Eric Lewis - Univ. of Wis-Mad.  eric.lewis AT doit.wisc DOT edu
608-263-1652
<Prev in Thread] Current Thread [Next in Thread>