You will find the information you need more quickly if you are familiar with:
This book describes:
This publication presents commands, filenames, keystrokes, and other special elements in these typefaces:
Exit program?yesb_b.errno
New features in SCO ARCserve/Open Release 2.2.0
This chapter describes new features for SCO ARCserve/Open from Cheyenne Release 2.2.0 that are not discussed in the SCO ARCserve/Open documentation, including:SCO ARCserve/Open is now equipped to read bar code labels for tape cartridges that are accessed through tape autochangers. This feature helps reduce the initialization time that is typically associated with high capacity changers.
This section describes:
When bar code reading is enabled through the SCO ARCserve/Open Device Manager, the autochanger scans for labels on each loaded cartridge tape. When a new bar code label is encountered, the corresponding tape is inserted in the tape drive and the label and the tape's volume header are read.
This information is then stored in files in the bar code tape database directory, /usr/lib/ARCserve/tapedb. A separate file is created for each unique tape label that is read.
If the changer scans a tape label that has already been encountered, the tape information is extracted from the database, saving the need to insert the tape into the tape drive.
It you do not use the changer-specific Device Management menu in this case, the tape database is not updated to reflect the new state of the tape.
In addition, it is recommended that you only remove tapes from the changer using the changer-specific Device Management menu, so that the tapes' information is properly removed from the tape database.
To enable or disable bar code reading for an individual changer:
Simple Network Management Protocol (SNMP) traps are now supported in SCO ARCserve/Open. This feature allows warnings and error messages from SCO ARCserve/Open and Client Agent workstations to be ``trapped'' to a centralized network management console, allowing administrators to manage their systems more efficiently.
HP® OpenView® on both UNIX® and Microsoft® Windows® systems is certified for use with SCO ARCserve/Open. However, you should be able to send SCO ARCserve/Open message traps to any network management station on which you can load the SCO ARCserve/Open MIB.
See also:
To use SNMP to trap messages from SCO ARCserve/Open, you must:
To enable SCO ARCserve/Open to send SNMP traps, you must first configure the SNMP configuration files on your UnixWare 7 system to include:
An IP address or host name must be entered for each console on which you want to receive the messages.
To specify the network management station to which you want the SCO ARCserve/Open traps sent, edit the /etc/netmgt/snmpd.trap file. Supply the management station's IP address (or host name), using the format specified in the comments at the top of the snmpd.trap file.
The SCO ARCserve/Open MIB file is called ARCserve.mib and is located in the /usr/lib/ARCserve directory.
This MIB file must be loaded
onto your network management station before it can interpret
the SCO ARCserve/Open trap messages.
Refer to your network management station documentation
for information on how to do this.
Before SNMP messages can be sent to the network management console, you must enable them within SCO ARCserve/Open.
SNMP messages can be enabled (or disabled) for the Backup, Restore, Scan, and Merge Managers, on a per-manager basis:
To enable SNMP messages for all of these Managers, you must perform the above steps in each Manager window. Or, you can selectively enable traps for only the Managers you desire.
The SCO ARCserve/Open SNMP Configuration Manager allows you to change the severity level that is assigned to each trapped message.
The SNMP Configuration Manager is accessed from the Utility menu on the SCO ARCserve/Open Quick Access window.
See also:
Each SNMP message can be assigned one of four severity levels:
SCO ARCserve/Open allows you to configure messages on a module basis, where a module corresponds to a class of Client Agents associated with a particular platform.
Messages associated with a particular Client Agent can be configured using the Module menu in the SNMP Configuration Manager -- simply select the appropriate Client Agent. Client Agent modules are listed in this menu depending on whether or not the corresponding severity file exists in the /usr/lib/ARCserve/nls/C directory.
SCO ARCserve/Open is now capable of backing up and restoring NetWare® Directory ServicesTM (NDS) trees. This section describes how to:
The SCO ARCserve/Open server only permits the backup and restore of its own NDS tree -- and this is the only NDS tree that is visible from the Backup and Restore Managers.
For more information on NDS and how it is implemented within UnixWare 7, refer to ``Administering NetWare Services (NWS)'' in the SCOhelp online documentation.
Select the NDS tree for backup in the same way you would any other server or node.
The NDS tree (associated with the SCO ARCserve/Open server) is displayed within the server's directory tree, which is visible within the Source area of the Backup Manager window.
To back up an NDS tree:
The NDS tree is displayed along with the server's existing filesystems, as shown below:
Once selected, you see the Secured Object Login
dialog box.
The NDS user name is equivalent to the NDS context name. The NDS context name consists of the object's full path, starting with Admin leaf and ending at the root of the tree.
Given the NDS structure implemented below:
the syntax for entering a valid user name (NDS path) is:
.CN=Admin.0=Cheyenne
You can use either Tape View or Tape Session to restore your NDS trees. This section outlines the steps for restoring NDS objects using the Tape Session view. For information on using Tape View, see the SCO ARCserve/Open User Guide.
When using the Tape Session view, you are required to select the tape session that you want restored. To locate the correct session containing the NDS information:
To restore an NDS tree using the Tape Session view:
SCO ARCserve/Open reads directly from your tape devices and displays the tape groups that you are using.
In addition, you must have admin (or supervisor) rights to the NDS tree that you select as your restore destination.
Once selected, you see the Secured Object Login dialog box.
Installing and removing SCO ARCserve/Open products
This chapter describes:The following SCO ARCserve/Open products and product options are available:
You must have at least one SCSI tape drive attached to the SCSI port of your system to back up and restore data using SCO ARCserve/Open.
SCO ARCserve/Open allows you to ``group'' drives so that you can take advantage of Tape Cascading and Parallel Streaming:
Therefore, if you have two drives, one with SCSI ID 2 and one with SCSI ID 3, SCO ARCserve/Open sets up two groups called ``MARS'' and ``JUPITER''. You can then modify these tape group assignments and names using the SCO ARCserve/Open Device Manager.
For more information on tape groups, see ``Managing your Tapes and Tape Devices'' in the SCO ARCserve/Open User Guide.
Table 2-1 identifies the procedure to use to install the various SCO ARCserve/Open products:
| To install: | See: |
|---|---|
|
SCO ARCserve/Open Lite
or SCO ARCserve/Open |
``Installing SCO ARCserve/Open products from the Desktop''
or ``Installing SCO ARCserve/Open products from the command line'' |
| Client Agents | Appropriate SCO ARCserve/Open Client Agent Installation Guide (online) |
The Changer option for auto changer support and the client connections for managing data on remote systems are activated by adding the appropriate licenses to your system after SCO ARCserve/Open is installed.
See ``Licensing SCO ARCserve/Open products and options'' for information on licensing SCO ARCserve/Open products and options.
To install an SCO ARCserve/Open product from the UnixWare 7 Desktop:
Depending on the package you are installing, you may need to respond to some additional prompts. Answer these prompts as appropriate for your installation.
Repeat this step for each package you wish to install.
SCO ARCserve/Open is installed in the /usr/lib/ARCserve directory.
Note the following:
To install an SCO ARCserve/Open product from the UnixWare 7 command line:
where /mnt is the mount point directory
and t# is the SCSI ID of the CD-ROM
device. For example, if your CD-ROM drive is set
to a SCSI ID of 5, you would specify
/dev/cdrom/c0b0t5l0.
The available packages are:
For example, to install the ARCserve package, you would
enter:
pkgadd -d /mnt ARCserve.pkg
Depending on the package you are installing, you may need to respond to some additional prompts. Answer these prompts as appropriate for your installation.
SCO ARCserve/Open is installed in the /usr/lib/ARCserve directory.
Note the following:
Licenses are required to activate the functionality for the following SCO ARCserve/Open products and options:
To add licenses for your SCO ARCserve/Open products and options:
See also:
This section describes the two methods you can use to remove SCO ARCserve/Open products:
To remove an SCO ARCserve/Open product from the UnixWare 7 Desktop:
Do you want to remove this package [yes,no,?,quit]
Select y.
To remove an SCO ARCserve/Open product from the UnixWare 7 command line:
Do you want to remove this package [yes,no,?,quit]
Select y.
Configuring SCO ARCserve/Open
This chapter describes:
By default, SCO ARCserve/Open messages that
require a user to respond or perform an action (such as
insert a tape in a drive) are sent to the syslogd daemon.
If you want these messages to display on the system console instead,
add the following lines to the /etc/syslog.conf file:
user.alert /dev/console
This indicates that SCO ARCserve/Open uses the syslogd(1M) daemon at the ``user'' facility and sends messages at the ``alert'' priority level. For more information on syslogd(1M) and /etc/syslog.conf, see the syslog.conf(4bsd) manual page.
If your system has tape devices attached to multiple SCSI host adapters, the SCSI ID numbers used by all the tape devices must be unique or SCO ARCserve/Open will not be able to access them.
By default, the SCO ARCserve/Open database is located on the root filesystem. Over time, the database may grow to such a size that it starts creating space problems on the root filesystem.
You can move the database to a filesystem that has more available space:
Getting started with SCO ARCserve/Open
This chapter covers getting started with SCO ARCserve/Open from Cheyenne, including the minimum steps required to make a full backup of your system.Specifically, this chapter describes:
Full SCO ARCserve/Open documentation, including a copy of these Release and Installation Notes, is provided online and is accessible from the SCOhelp system.
To access the SCO ARCserve/Open online documentation, run SCOhelp and click on the ``Backup and Restore'' link in the left navigational frame. From here, you can access all of the SCO ARCserve/Open online documentation, including the User Guide and the Client Agent Installation Guides.
The installation procedure automatically creates a script file called S69ARCserve and places it in /etc/rc2.d. When the system is brought up in multi-user mode, this script is invoked and automatically starts all necessary daemons for the back-end.
In the event that your system appears to hang during the process of starting the SCO ARCserve/Open daemons, bring up the system in single-user mode. When the system is up, delete the S69ARCserve file and follow the instructions below for starting the back-end daemons manually:
To start the SCO ARCserve/Open front end:
The SCO ARCserve/Open Quick Access window displays. From here you select the SCO ARCserve/Open operation that you want to perform.
To stop the SCO ARCserve/Open back-end:
To stop the SCO ARCserve/Open front-end:
Following are the basic steps for making a backup -- that is, using the default backup options to back up your data to tape. Advanced backup options are covered in the SCO ARCserve/Open User Guide.
Using the above example, follow these directions to back up your files:
See
``Software Basics''
in the
SCO ARCserve/Open User guide
for more information on using the Browser
to select your sources.
Click the Run button to schedule and run the job.
Known limitations and workarounds
This release of SCO ARCserve/Open from Cheyenne for UnixWare 7 contains limitations, and where possible, workarounds in the following categories:By default, SCO ARCserve/Open locks all of the SCSI tape devices attached to your system. Because of this, your tape devices are unavailable for use by backup commands such as tar(1) or cpio(1), even if the devices are not currently being used for backup or restore operations by SCO ARCserve/Open.
Depending on the number of tape devices available on your system, there are two possible workarounds to this situation.
The following limitations apply when running backup jobs:
When you have finished editing the tapesvr.cfg file,
run astop to stop all SCO ARCserve/Open
processes then run astart to restart the server.
Failed to Access Source Directory
error in the activity log.
If, as is set by default, you do not want to back up NFS filesystems, you can safely ignore these error messages -- your backup jobs are complete. If, however, you want to include the NFS filesystems in your backup job, you will need to rerun the operation.
The workaround to this problem is to remove one of the tapes with the same name from the SCO ARCserve/Open database.
To avoid this, either make sure that all CD-ROMs are unmounted before starting a backup, or do not select the CD-ROM mount point(s) for backup.
See also:
The following limitations apply when using SCO ARCserve/Open Client Agents:
If the Remote Clients list does not display a system
that you expect to see, verify that the machine is
functioning properly and that the Client Agent is running.
If there are no physical reasons why the remote host should
be inaccessible by the SCO ARCserve/Open server,
close the Remote Clients list and display it again, repeating
this step until the desired remote host appears.
The workaround to this problem is to stop all SCO
ARCserve/Open daemons on the SCO ARCserve/Open
server by running astop,
then restart the daemons with astart.
Restoring files from multiple tape sessions is not a problem if you use Auto Pilot to back up your OS/2 clients.
After your backup job has completed, check the activity log and compare the number of files processed with the number of files actually written to tape for any discrepancies. There is no current workaround to this problem.
The following limitations apply when using SNMP message traps:
For example, if you want to generate SNMP message traps from a Windows 95 Client Agent system, copy the win95-30.sev severity file from the Client Agent distribution to the /usr/lib/ARCserve/nls/C directory on the SCO ARCserve/Open server. Then, in the same directory, make a copy of the severity file and name it win95-30.sev.default.
If you are using SCO ARCserve/Open Lite, you must use the arcserve.cmd utility (located in /usr/lib/ARCserve) to perform basic backup and restore operations from the command line. This utility is useful for scheduling SCO ARCserve/Open jobs from cron(1) or other such scheduling utilities.
The arcserve.cmd utility syntax is:
where -b is for backup and source_path is what you want backed up. You must specify the directory to back up in source_path.
where -r is for restore.
Troubleshooting
This appendix describes the most common problems that you might encounter while installing and starting SCO ARCserve/Open from Cheyenne and provides possible solutions.Most of the problems that you may encounter, especially when using SCSI host adapters, are hardware-related.
Two important points to consider when tracking down hardware problems are:
| Problem | Solution |
|---|---|
| During system startup, I get a SCSI bus selection timeout error. |
This message is normal during system startup. The software
scans the SCSI bus to look for tape drives and
changers. Some host adapter drivers report a NOTICE
or an error if there is no device attached to a particular
SCSI ID while scanning for devices.
If you see these messages scrolling by after the system is already up, immediately run astop. This condition usually occurs when someone has switched off a drive, disconnected a drive, or there is a loose SCSI cable.
NOTE: It is a good idea to run astop before disconnecting SCSI devices.
|
| When running the SCO ARCserve/Open front-end, my windows exceed the screen size. |
SCO ARCserve/Open's screens are designed
to display optimally on systems with a VGA
card capable of 256 colors and with a resolution of
at least 800x600.
If you want to change the graphics resolution, make sure your VGA card supports the above resolution, then run SCOadmin video configuration manager. |
| I've installed SCO ARCserve/Open, but I'm having trouble seeing my tape drive(s). |
Make sure that all cards, cables, and devices are connected
properly. If you installed a new card in your system before
installing SCO ARCserve/Open, make sure it is
seated properly in its slot. If that does not work, try
putting the card in a different slot.
Type astatus to see if the SCO ARCserve/Open tapesvr daemon is running. If you have multiple host adapter cards installed in your system, make sure your drive is connected to the first one. Make sure your SCSI bus is terminated properly. There must be two sets of terminating resistors, one at the beginning of the chain and one at the end. If you only have one drive connected to your machine, then you have two devices on the SCSI bus; the host adapter card and the tape drive. Both the host adapter card and the tape drive should be terminated. Make sure each SCSI device in the chain has a unique ID. If you have two tape drives attached to the SCSI bus, each with a SCSI ID of 2, chances are neither device will work. Set each drive to a unique SCSI ID. Make sure all the tape drives are turned on. Sometimes if you forget to turn on one device in a chain, the others will behave erratically. Make sure the jumper settings on your adapter board are correct. Check the documentation that came with the board to make sure the jumpers are set correctly for use with your hardware. Replace the cables you are using with ones you know are good. If the problem goes away, you know you had a bad cable. |
| The SCO ARCserve/Open database is getting very large. |
The ideal solution is to make sure your filesystem has plenty
of free space.
If you have tapes that are out of date, or that you no longer need, format them and re-use them. When you format a tape, the references to the files and sessions on that tape are removed from the database. You can calculate how much disk space you will need for the SCO ARCserve/Open database based on how much data you regularly back up. The information that SCO ARCserve/Open records about each file that is backed up requires about 80 bytes of space in the SCO ARCserve/Open database. If you back up 100,000 files every week, and re-use the same tapes each time you do it, you need about 8 MB of disk space (80x100,000) for the database. Another option is to relocate the database to a filesystem with more available disk space. See ``Relocating the SCO ARCserve/Open database'' for information on how to do this. |
©1994-1997 Cheyenne Software, Inc. All rights reserved.
©1983-1997 The Santa Cruz Operation, Inc. All rights reserved.
This publication is protected under copyright laws and international treaties.
Information in this document is subject to change without notice and does not represent a commitment on the part of The Santa Cruz Operation, Inc.
Argus, Business/21, dbXtra, DiSCOver, Internet Way of Computing, IWoC, Multiscreen, ODT, Open Desktop, Optimized For Internet Computing and its logo, Panner, SCO, SCO ACE, SCO CIFS Bridge, SCO Doctor, SCO Doctor for Networks, SCO Doctor Lite, SCO Global Access, the SCO logos, SCO MPX, SCO MultiView, SCO Nihongo OpenServer, SCO OK, the SCO OK logo, SCO OpenServer, SCO Open Server, SCO Portfolio, SCO POS System, SCO Premier Motif, SCO TermLite, SCO ToolWare, SCOtopia, SCO Vision 97, SCO VisionFS, SCO Visual Tcl, Skunkware, Tarantella, The Business Choice, The Santa Cruz Operation, UnixWare, Universal Server, VP/ix, and Zones are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. APC, SoftCare, and SoftTech are service marks of The Santa Cruz Operation, Inc. Deskterm, Deskworks, IXI, IXI Desktop, the IXI logo, IXI Panorama, Wintif, and X.desktop are trademarks or registered trademarks of IXI Limited, a subsidiary of The Santa Cruz Operation, Inc. X.tra is a service mark of IXI Limited. Codon, Devkit.Vision, Esprit, Kodon, PC-Connect, SQL-Retriever, SuperVision, Super.Vision, TermVision, Term.Vision, Vision Builder, Visionware, Visionware Direction, the Visionware logo, Visionware SQL-Retriever, Visionware Super.Vision, the XV logo, XVision, and X-Visionware are trademarks or registered trademarks of Visionware Limited, a subsidiary of The Santa Cruz Operation, Inc. X/Open and UNIX are registered trademarks and the X Device is a trademark of The Open Group in the United States and other countries. Cheyenne and ARCserve are registered trademarks of Cheyenne Software, Inc. Netscape, Netscape Navigator, Netscape Communications Server, Netscape Commerce Server, Netscape Proxy Server, Netscape FastTrack Server, Netscape Enterprise Server, Netscape SuiteSpot, Netscape Catalog Server, Netscape News Server, Netscape Mail Server, and Netscape Navigator Gold are trademarks of Netscape Communications Corporation. NFS was developed by Legent Corporation (formerly Lachman Associates, Inc.) based on LACHMAN SYSTEM V NFS. LACHMAN is a trademark of Legent Corporation. NFS is a trademark of Sun Microsystems, Inc. TCP/IP was developed by Legent Corporation (formerly Lachman Associates, Inc.) based on LACHMAN SYSTEM V STREAMS TCP, a joint development of Lachman Associates and Convergent Technologies. MPX was developed by Corollary, Inc. VP/ix is a product developed and licensed by Phoenix Technologies, Ltd/INTERACTIVE Systems Corporation. XRemote is a registered trademark of Network Computing Devices, Inc. Oracle is a registered trademark of Oracle Corporation, Redwood City, California. Java is a trademark of Sun Microsystems, Inc. Adobe is a trademark of Adobe Systems Incorporated and is registered in the U.S. Patent and Trademark Office. Reliant is a registered trademark of Siemens Pyramid Information Systems, Inc. (formerly Pyramid Technology Corporation). All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners. The Santa Cruz Operation, Inc. reserves the right to change or modify any of the product or service specifications or features described herein without notice. This document is for information only. SCO makes no express or implied representations or warranties in this document.
The Santa Cruz Operation, Inc. and SCO Skunkware are not related to, affiliated with or licensed by the famous Lockheed Martin Skunk Works®, the creator of the F-117 Stealth Fighter, SR-71, U-2, VenturestarTM, DarkstarTM, and other pioneering air and spacecraft.
The SCO software that accompanies this publication is commercial computer software and, together with any related documentation, is subject to the restrictions on US Government use as set forth below. If this procurement is for a DOD agency, the following DFAR Restricted Rights Legend applies:
RESTRICTED RIGHTS LEGEND: When licensed to a U.S., State, or Local Government, all Software produced by SCO is commercial computer software as defined in FAR 12.212, and has been developed exclusively at private expense. All technical data, or SCO commercial computer software/documentation is subject to the provisions of FAR 12.211 - "Technical Data", and FAR 12.212 - "Computer Software" respectively, or clauses providing SCO equivalent protections in DFARS or other agency specific regulations. Manufacturer: The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, California 95060.
The copyrighted software that accompanies this manual is licensed to the End User only for use in strict accordance with the two End User License Agreements. All such Agreements should be read carefully before commencing use of the software.
Document Version: SCO ARCserve/Open 2.2.0
December 1997