Solaris 7, DDS3 Autochanger, and Solstice Backup 5.1(.1)

Solaris 7, DDS3 Autochanger, and Solstice Backup 5.1(.1)

Post by Peter Schwen » Fri, 24 Nov 2000 04:00:00



Hello:

I'm having major problems with getting Solstice Backup 5.1 (and 5.1.1)
with Autochanger module working on a Sun Ultra 5 running Solaris 7
(32-bit mode only).  The software was working fine under Solaris 2.6.
I went from Solaris 2.6 to Solaris 7 using a complete installation (not
upgrade), and I only installed the 32-bit stuff because I figured that
it would avoid some incompatibility issues because Solstice Backup 5.1
is older than Solaris 7.

After installing Solaris 7 and Solstice Backup 5.1, the software
appeared to be working on the face of it because it was reading the
media database fine and the indices, but when it came to actually making
the autochanger jockey tapes around, all I would get is a "File not
found"-type message.  The one big difference that I can see is that

under Solaris 2.6.  I have no idea if Solaris 2.6 was responsible for
those files being created or if the kernel driver, lus, supplied by
Solstice Backup, was responsible.

In the mean time, I found the Solaris Data Backup 5.1.1 in the Easy
Access Server 2.0 kit that came with an older Solaris 7 media kit, and
it looks like it is just a re-named Solstice Backup because all the
package names were the same.  I removed Solstice Backup 5.1 and
installed Solaris Data Backup 5.1.1, and it seemed to be okay with my
enabler codes for Solstice Backup 5.1.  Even though it alleges to not
support autochangers, the jb_config and nsrjb utilities exist, but the
same "file not found" messages occur when I try to operate the
autochanger.  The jb_config utility cannot find any autochangers.

At this point, I'm guessing that the device files are different than
they used to be, and the software isn't finding the autochanger.  This
is odd because Solaris Data Backup 5.1.1 claims to support Solaris 7.
It doesn't claim to handle autochangers, but it really seems to be
Solstice Backup in disguise because all the autochanger utilities are
present and my autochanger module enabler code works.

Does anyone have any ideas on what I might do to get this working?  I'm
backup-less until I do.

Any help will be greatly appreciated.

- Peter Schwenk
- Campus Information and Technology Associate 3
- Mathematical Sciences
- University of Delaware

- 302-831-0437

 
 
 

Solaris 7, DDS3 Autochanger, and Solstice Backup 5.1(.1)

Post by Allen Wittenaue » Sun, 03 Dec 2000 04:00:00



> I'm having major problems with getting Solstice Backup 5.1 (and 5.1.1)
> with Autochanger module working on a Sun Ultra 5 running Solaris 7
> (32-bit mode only).  

Upgrade to 5.5.1.  I'm fairly certain that 5.1.x isn't supported under
Solaris 7.

 
 
 

Solaris 7, DDS3 Autochanger, and Solstice Backup 5.1(.1)

Post by Darren Dunha » Tue, 05 Dec 2000 04:00:00




>> I'm having major problems with getting Solstice Backup 5.1 (and 5.1.1)
>> with Autochanger module working on a Sun Ultra 5 running Solaris 7
>> (32-bit mode only).  
> Upgrade to 5.5.1.  I'm fairly certain that 5.1.x isn't supported under
> Solaris 7.

The software may have other problems, but Solaris 2.6 and 7 both run SBU
5.1.x.  I ran 5.1 and 5.1.1 on a Solaris 7 machine.

If anyone's interested, there is a mailing list for Legato Networker
administrators.  Solstice Backup is the same thing, so autochanger
questions would be the same...

send a 'subscribe networker' to

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
      < Please move on, ...nothing to see here,  please disperse >

 
 
 

1. Solstice Backup 5.1 / DMO 2.1/Oracle 8.1.5: Tape backup failed : Need of 5.5 Upgrade ?

Hi,

we have the following installation:

Backup Server with

Solaris 2.5.1
Solstice Backup  Server 5.1

Backup client with

Solaris 2.6
Solstice backup Client 5.1

DMO (Database modules for Oracle) 2.1 with the last Patches, which
should give the possibility of scheduled backups

Oracle 8.1.5

Our Problem is:

we cant make a tape-backup with allocate ...'sbt_tape'  startet over
rman. backups to disk are running fine.

Starting a backup over nwadmin we get an error, because there is no
given a user.

Has anybody made a tape-backup from rman or nwadmin, without upgrading
to Solstice Backup 5.5?

TIA,

Nele

2. register_inet6addr_notifier

3. Solstice Backup 5.1: can't do level or incremental backups

4. PCI+Pentium+Linux+X?

5. Does Solstice Backup 5.1 work with Solaris 7?

6. Modem in a Sambaserver

7. Q: Is Solstice Backup 5.1 Compatible with Solaris 7?

8. Pushd, popd, dirs for stock SysV.3 Bourne shell

9. Solstice backup 5.1 - speed issues

10. Solstice Backup 5.1 and two tape drives

11. Solstice Backup 5.1

12. solstice backup 5.1 nwadmin puzzle! any help/suggestions?

13. Solstice Backup 5.1 server edition