|
Brian, After you edit the st.conf and sgen.conf
make sure you do a ‘reboot –r’ so that Solaris will
reconfigure your devices and add any new devices found. We have been running it for about 10
months now and it has been a very good for us. The only maintenance we need to
do is updating the database after removing the monthly tapes that go to
off-site storage (mostly because I just haven’t created an automated
script to update the database when the tapes are pulled) and keeping an eye on
storage to make sure we have enough tapes to do our monthly full backups. Here is the stuff I changed in the
sgen.conf: # #device-type-config-list="scanner",
"ocrw"; device-type-config-list="changer"; inquiry-config-list=
"QUALSTAR", "RLS-8236"; # # After configuring the
device-type-config-list and/or the inquiry-config-list, # the administrator must uncomment those
target/lun pairs at which there are # devices for sgen to control. If it
is expected that devices controlled by # sgen will be hotplugged or added into
the system later, it is recommended # that all of the following lines be
uncommented. name="sgen" class="scsi" target=0 lun=0; Here is what I added to st.conf: name="st" class="scsi"
target=0 lun=0; name="st" class="scsi"
target=0 lun=1; name="st" class="scsi"
target=1 lun=0; name="st" class="scsi"
target=1 lun=1; name="st" class="scsi"
target=2 lun=0; name="st" class="scsi"
target=2 lun=1; name="st" class="scsi"
target=3 lun=0; name="st" class="scsi"
target=3 lun=1; name="st" class="scsi"
target=4 lun=0; name="st" class="scsi"
target=4 lun=1; name="st" class="scsi"
target=5 lun=0; name="st" class="scsi"
target=5 lun=1; name="st" class="scsi"
target=6 lun=0; name="st" class="scsi"
target=6 lun=1; name="st" parent="fp"
target=0; I hope this helps. Tom. From: Waldock, Brian
[mailto:[EMAIL PROTECTED] Tom, Thanks for your response. I did try the
procedure for updating sgen.conf (for the autochanger), but it did not
create a scsi device in the device tree. I guess I’m not sure if this is
the correct procedure to follow for a fibre attached autochanger, as compared
to scsi attached. Would you mind sending me what your file edits so I can
compare? How is bacula working for you? Thanks Brian From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Hello Brian, I have a Solaris 9 system on a SunFire
v240 running a Qualstar RLS8232 SCSI Attached with 2 LTO1 tape drives. It is a little different – but
similar enough to demonstrate what needs to be done. I edited the /kernel/drv/st.conf to make
sure the tape devices would get recognized and then I added an entry into
/kernel/drv/sgen.conf so that Solaris would recognize and create a device for
changer. Then I installed mtx to work the changer
and I use 0cbn and 1cbn for my devices. Use the btape test program to make sure
you have the correct tape definitions – I didn’t and caused myself
some grief until I tested the tape devices and used the correct devices. Before I go any further in building this environment, I
wanted to see if anyone has any experience with the following configuration or
similar. Sun e480 running Solaris 10 OS Sun storedge L180 fiber attached autochanger with 6 LTO2
fibre attached drives. The 6 drives are connected though brocade 3850 switches The robot is directly connected to fibre hba I’m not entirely sure how to configure Solaris to
control the autochanger and tape drives. I’m assuming I can use MTX, but
I can’t seem to find any documentation on how to set this up in Solaris.
The sun documentation mostly refers to legato and veritas procedures and they
are not helping at all. Any help would be greatly appreciated. Tom. |
- [Bacula-users] bacula on solaris 10 with fibre attached li... Waldock, Brian
- Re: [Bacula-users] bacula on solaris 10 with fibre at... Sebastian Stark
- RE: [Bacula-users] bacula on solaris 10 with fibre at... tom.boyda
- RE: [Bacula-users] bacula on solaris 10 with fibre at... tom.boyda
- RE: [Bacula-users] bacula on solaris 10 with fibre at... Waldock, Brian
