Technical article 109464

What is SCO ARCserve/Open from Cheyenne Release 2.2.0k?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

What are the new features in SCO ARCserve/Open from Cheyenne Release 2.2.0k and how can I obtain it?

Solution

SCO ARCserve/Open from Cheyenne Release 2.2.0k combines the functionality of the previous version (2.2.0f) with the SCO ARCserve/Open 2.2.0 Maintenance Supplement Release 1.0.0 in the same package.

SCO ARCserve/Open from Cheyenne 2.2.0k is included on the OpenServer June 1998 Optional Services CD-ROM and on the UnixWare December 1997 Optional Services CD-ROMs. These can be purchased as the currently shipping ARCserve/Open from Cheyenne Release 2.2 Base Product, and ARCserve Upgrade Media Kit Version 2.2 product.

The features of the new version are described in the following SCO ARCserve/Open from Cheyenne Release 2.2.0k cover letter:

Dear SCO ARCserve/Open customer,

This letter provides important information about SCO ARCserve/Open from Cheyenne 2.2.0k for both SCO OpenServer Release 5 and SCO UnixWare Release 2.1 platforms, including new features, upgrade information, and limitations and workarounds not included in the SCO ARCserve/Open from Cheyenne Release and Installation Notes.

We would also like to encourage you to check the SCO World Wide Web home page (http://www.sco.com/) for future developments regarding the SCO ARCserve/Open products and options.

Thank you,
SCO Product Management
A. SCO ARCserve/Open product options

There are several optional products available for the fully licensed SCO ARCserve/Open product, including:

- the SCO ARCserve/Open Changer option, to support leading 4mm (DAT), 8mm, Quarter-Inch Cartridge, and Digital Linear Tape (DLT) changers.

- the SCO ARCserve/Open Database Agent for Informix, for performing online backups of your Informix databases from within SCO ARCserve/Open, using the ON-bar system. (Currently available for SCO OpenServer platforms only.)

- SCO ARCserve/Open Database Agent for Oracle, so you can perform online backups of your Oracle databases. (Currently available for SCO OpenServer platforms only.)

- 1, 5, 10, 25, and 100 client connection licenses, so you can use your Client Agents with SCO ARCserve/Open to back up and restore remote systems.

- the SCO Doctor Solution Pack for SCO ARCserve/Open from Cheyenne, for monitoring the performance of SCO ARCserve/Open from the SCO Doctor product.

If you are interested in obtaining more information about these products, contact your authorized SCO Reseller or Distributor.

B. New features in SCO ARCserve/Open Release 2.2.0k

In addition to the new features described in Chapter 1, "New features in SCO ARCserve/Open Release 2.2.0" of the SCO ARCserve/Open from Cheyenne Release and Installation Notes, this release also provides:

- support for the new SCO ARCserve/Open Database Agent for Informix (on SCO OpenServer Release 5 platforms only).

- support for new tape devices, including:

HP Colorado T4000s (Travan), firmware rev. 1.06/1.07

- support for new tape libraries, including:

Exabyte 18D DLT library (SCO OpenServer Release 5 platforms only)

- Exabyte 220 8mm library
- HP C5153 DLT library

- Philips LMS BlackJack (SCO OpenServer Release 5 platforms only)

- SpectraLogic 10000
- StorageTek 9724/9734

- WangDAT LD-8 DAT Autochanger (SCO UnixWare Release 2.x platforms only)

NOTE: The functionality and enhancements provided by the SCO ARCserve/Open 2.2.0 Maintenance Supplement Release 1.0.0 are now included in SCO ARCserve/Open Release 2.2.0k.

C. Installing and upgrading SCO ARCserve/Open:

If you are installing SCO ARCserve/Open for the first time, see the installation instructions in the SCO ARCserve/Open Getting Started document on the SCO ARCserve/Open Download page.

If you are upgrading from an earlier release of SCO ARCserve/Open, including Release 2.2.0f, see one of the following sections in this letter:

Upgrading to SCO ARCserve/Open Release 2.2.0k on SCO OpenServer Release 5 systems Upgrading to SCO ARCserve/Open Release 2.2.0k on SCO UnixWare Release 2.x systems

These installation and upgrade sections supersede the information provided in your SCO ARCserve/Open from Cheyenne Release and Installation Notes.

D. Upgrading to SCO ARCserve/Open Release 2.2.0k on SCO OpenServer Release 5 systems.

The following scenarios for upgrading to SCO ARCserve/Open Release 2.2.0k on an SCO OpenServer Release 5 system are supported:

--------------------------------------------
From:               To:
--------------------------------------------
ARCserve/Open       SCO ARCserve/Open Lite
Release 2.0x        Release 2.2.0k
or
SCO ARCserve/Open
Release 2.2.0k
--------------------------------------------
SCO ARCserve/Open   SCO ARCserve/Open Lite
Lite                Release 2.2.0k
Release 2.1.0          or
or               SCO ARCserve/Open
SCO ARCserve/Open   Release 2.2.0k
Release 2.1.0
--------------------------------------------
SCO ARCserve/Open   SCO ARCserve/Open Lite
Lite                Release 2.2.0k
Release 2.2.0f         or
or               SCO ARCserve/Open
SCO ARCserve/Open   Release 2.2.0k
Release 2.2.0f
--------------------------------------------

E. Upgrading from ARCserve/Open Release 2.0x or Release 2.1.0

Upgrading from ARCserve/Open Release 2.0x or SCO ARCserve/Open Release 2.1.0 Lite or Full versions preserves the following data:

- the ARCserve/Open database (/usr/lib/ARCserve/dbase)

- all configuration information (except for changes made to the /usr/lib/ARCserve/tapesvr.cfg and /etc/conf/pack.d/chey/space.c files on Release 2.0x installations)

- all ARCserve/Open jobs

To upgrade from these versions of ARCserve/Open:

1. Log in as root.

2. It is recommended that you back up these files and directories before starting the actual upgrade:

/usr/lib/ARCserve/dbase
/usr/lib/ARCserve/tapesvr.cfg
/etc/conf/pack.d/chey/space.c

3.Install the Full or Lite SCO ARCserve/Open Release 2.2.0k product, as described in "Installing SCO ARCserve/Open products" in the SCO ARCserve/Open from Cheyenne Release and Installation Notes.

You do not need to remove the old version of ARCserve/Open first; it is automatically removed for you.

If you are upgrading from the Full version of the 2.1.0 product
to the Full version of Release 2.2.0k, your Certificate of License
and Authenticity (COLA) has not changed, so you do not need to
re-license the new version of SCO ARCserve/Open during the
installation procedure.  However, you are still prompted for the
COLA information during the installation. Select 'Defer' in the
License Manager. Your new product is correctly licensed at this
point.

If an ARCserve/Open database is detected, you are prompted to upgrade the database to the new Release 2.2.0 format. SCO ARCserve/Open Release 2.2.0k cannot use the database until you perform this update.

4. Reboot the system.

5. If, during the upgrade installation you performed in Step 3, you were not prompted to update your ARCserve/Open database, you must now run /etc/as_dbupgrade to upgrade the database to the new Release 2.2.0 format. SCO ARCserve/Open cannot use the database until you have performed this step.

You can skip this step if you updated the database during the upgrade installation.

6. If you are upgrading from a Release 2.0x product and you made modifications to the tapesvr.cfg and space.c files, you may want to incorporate your changes into the 2.2.0k versions of the files.

If you are upgrading from a Release 2.1.0 product, any changes to these files are automatically preserved.

F. Upgrading from SCO ARCserve/Open Release 2.2.0f

Upgrading from SCO ARCserve/Open Release 2.2.0f (Lite or Full versions) to the Lite or Full version of Release 2.2.0k preserves the following data:

- the SCO ARCserve/Open database (/usr/lib/ARCserve/dbase)

- all configuration information, including changes made to the /usr/lib/ARCserve/tapesvr.cfg and /etc/conf/pack.d/chey/space.c files

- all SCO ARCserve/Open jobs

To upgrade from an SCO ARCserve/Open Release 2.2.0f product:

1. Log in as root.

2. Remove the SCO ARCserve/Open 2.2.0 Maintenance Supplement Release 1.0.0 if it is installed on your system. You cannot upgrade to SCO ARCserve/Open Release 2.2.0k until the Maintenance Supplement has been removed.

3. Install the Full or Lite SCO ARCserve/Open Release 2.2.0 product, as described in "Installing SCO ARCserve/Open products" in the SCO ARCserve/Open from Cheyenne Release and Installation Notes.

You do not need to remove the old version of SCO ARCserve/Open first; it is automatically removed for you.

NOTE: If you are upgrading from the Full version of the 2.2.0f product to the Full version of Release 2.2.0k, your Certificate of License and Authenticity (COLA) has not changed, so you do not need to re-license the new version of SCO ARCserve/Open during the installation procedure.

However, you are still prompted for the COLA information during
the installation. Select 'Defer' in the License Manager.  Your
new product is correctly licensed at this point.
4. Reboot the system.

G. Upgrading to SCO ARCserve/Open Release 2.2.0k on SCO UnixWare Release 2.x systems

The following scenarios for upgrading to SCO ARCserve/Open Release 2.2.0k on an SCO UnixWare Release 2.x system are supported:

--------------------------------------------
From:               To:
--------------------------------------------
SCO ARCserve/Open   SCO ARCserve/Open Lite
Lite                Release 2.2.0k
Release 2.2.0f
--------------------------------------------
SCO ARCserve/Open   SCO ARCserve/Open
Release 2.2.0f      Release 2.2.0k
--------------------------------------------

NOTE: If you want to upgrade from Lite to Full functionality at the same time you are upgrading to SCO ARCserve/Open Release 2.2.0k, simply perform the upgrade installation, then run /etc/licenseMgr to add the license data from the SCO ARCserve/Open Certificate of License and Authenticity (COLA).

Upgrading to SCO ARCserve/Open Release 2.2.0k preserves the following data:

- the SCO ARCserve/Open database (/usr/lib/ARCserve/dbase)

- all configuration information, including changes made to the /usr/lib/ARCserve/tapesvr.cfg file

- all SCO ARCserve/Open jobs

To upgrade from SCO ARCserve/Open Release 2.2.0f (Lite or Full versions):

1. Log in as root or owner.

2. Remove the SCO ARCserve/Open 2.2.0 Maintenance Supplement Release 1.0.0 if it is installed on your system. You cannot upgrade to SCO ARCserve/Open Release 2.2.0k until the Maintenance Supplement has been removed.

3. Install the Full or Lite SCO ARCserve/Open Release 2.2.0k product, as described in "Installing SCO ARCserve/Open products" in the SCO ARCserve/Open from Cheyenne Release and Installation Notes.

You do not need to remove the old version of SCO ARCserve/Open first; it is automatically removed for you.

4. Reboot the system.
H. Additional limitations and workarounds:

In addition to the limitations and workarounds described in the SCO ARCserve/Open from Cheyenne Release and Installation Notes, the following SCO ARCserve/Open limitations and workarounds exist:

It is not possible to upgrade the Release 2.0 Client Agent
(uagent) for SCO OpenServer Release 5 systems to the Release
2.2 version of the uagent provided on this media. If you want
to upgrade to the new version of the uagent Client Agent, you
must first remove the old Client Agent and then install the
Release 2.2 Client Agent.  See the online SCO ARCserve/Open
Client Agents for UNIX Installation Guide for uagent installation
instructions.

For SCO OpenServer Release 5.0.4 systems only:

When creating an SCO ARCserve/Open disaster recovery floppy
set, a  "File not Found" error message is generated for the
/usr/lib/mkdev/perms/DKINIT file. You can safely ignore this
message.

For SCO OpenServer Release 5.0.4 systems only:

A new alad device driver is provided with SCO OpenServer Release 5.0.4. If you are using the new alad driver with an Adaptec 2940 host adapter, there is a chance that your tape devices will be unavailable to SCO ARCserve/Open. If you experience this problem, there are two possible workarounds, which you should try in this order:

1. Edit the /usr/lib/ARCserve/tapesvr.cfg file and comment out
all DEVICE entries for non-tape drive  SCSI IDs (that is, any
SCSI hard disks, CD-ROM drives, and so forth).

Then run astop and astart to restart the SCO ARCserve/Open tape server.

2. If the previous step did not fix the problem, you will need to change to an older version of the alad driver, which is provided on the SCO OpenServer Release 5.0.4 CD-ROM.

The instructions for making this change are also provided on the CD-ROM. To access this information, mount the CD-ROM:

mount -r /dev/cd0 /mnt

Read the section entitled "Conflicts with the Adaptec alad driver" in the /mnt/latenews/latenews.htm or /mnt/latenews/latenews.txt files.

For SCO OpenServer Release 5 systems only:

If your system contains a BusLogic SCSI host adapter that is emulating an Adaptec 154x series host adapter using the ad device driver, there are two scenarios in which changing to the BusLogic-specific device driver, blc, may also require modifications to the SCO ARCserve/Open device driver configuration:

- You install AHS 5.2 on an SCO OpenServer Release 5.0.0 or 5.0.2 system that also has SCO ARCserve/Open (Lite or Full) installed, then switch to the BusLogic-specific driver (blc) provided with AHS.

- SCO ARCserve/Open (Lite or Full) is installed on an SCO OpenServer Release 5.0.0 or 5.0.2 system. Then you upgrade to a future release of SCO OpenServer and select to use the BusLogic-specific device driver (blc).

If you upgrade to the blc BusLogic device driver in either of these cases, it is important to check the /etc/conf/pack.d/chey/space.c file and make sure that the SCSI host adapter entry point field is set to the correct value: blc_entry.

From the Xinuos technical article database, record 109464. Reproduced with permission. The original is at www.sco.com/ta/109464, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.