BE9 and two VXA drives - show up swapped around - Veritas Backup Exec
This is a discussion on BE9 and two VXA drives - show up swapped around - Veritas Backup Exec ; Hi,
Have a NW51sp6 server with BE9 (4175). Attached are a standalone Ecrix VXA-1
drive and an Exabyte Autopak 1 x10 containing a single VXA-2 drive. Both
drives work when a job is submitted, but the standalone drive appears under
...
-
BE9 and two VXA drives - show up swapped around
Hi,
Have a NW51sp6 server with BE9 (4175). Attached are a standalone Ecrix VXA-1
drive and an Exabyte Autopak 1 x10 containing a single VXA-2 drive. Both
drives work when a job is submitted, but the standalone drive appears under
the Autopak robot and the VXA-2 drive appears as standalone, so I can't use
the autoloader.
Does Backup Exec assign the first (lowest SCSI ID number) drive it finds to
the autoloader? VXA-1 is ID-1 and VXA-2 is ID-4. Autoloader is ID-6.
I don't think I need the library expansion option as there's only one drive
in the auto loader.
Thanks
-
Re: BE9 and two VXA drives - show up swapped around
Jim
> Does Backup Exec assign the first (lowest SCSI ID number) drive it finds to
> the autoloader? VXA-1 is ID-1 and VXA-2 is ID-4. Autoloader is ID-6.
How BE interprets the devices is down to how they're presented when the
SCSI bus is scanned. In the majority of cases, the loader should be on a
lower SCSI ID than any drives that it contains, and those drives should
be ID'd consecutively. Also, in addition to not using 0 ID, I usually
avoid using 1 as well (just my habit & preference) - so, if I were in
this situation, I'd probably put the standalone on 2, the loader on 3
and the drive within the loader on 4.
> I don't think I need the library expansion option as there's only one drive
> in the auto loader.
Correct - it's free for the first drive
Michael
--
"If it jams, force it. If it breaks,
you probably needed a new one anyway"
* Please post replies via the newsgroup *
