The following limitations apply when using
SCO ARCserve/Open Client Agents:
-
When expanding the list of Remote Clients in either the
Backup or Restore Manager windows, it is possible that
the list may not display all of your active remote clients.
This is due to an inherent limitation in the design
of UDP, one of the underlying network protocols on which
SCO ARCserve/Open relies. This problem tends
to occur most often with Macintosh systems, but may be
experienced for any remote host.
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.
-
If a UNIX system Client Agent (uagent) on
a remote system is stopped while an SCO ARCserve/Open
server is running a backup job on that system, the backup job
will never complete. Consequently, the tape device performing
the backup remains inaccessible indefinitely.
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.
-
To back up a Windows NT 4.0 system, you must use the
Windows NT Client Agent provided with the 2.2 release of
SCO ARCserve/Open. The 2.1 release of the
Windows NT Client Agent does not work on an NT 4.0 platform.
-
The Macintosh and OS/2 Client Agents can only
be used with an SCO ARCserve/Open Release 2.2
server -- the 2.1 release of SCO ARCserve/Open
cannot back up these platforms. All of the other supported
Client Agents work with both SCO ARCserve/Open
Release 2.1 and 2.2.
-
If you run custom incremental backups on an OS/2
client, restore operations that require files from more than one
tape session may fail to recover files from any session other
than the most current. To work around this problem, we suggest
that you limit restore operations to a single tape session
at a time. You can view the SCO ARCserve/Open database
to see the files that are contained on the tape session that you want
to restore.
Restoring files from multiple tape sessions is not a problem
if you use Auto Pilot to back up your OS/2 clients.
-
There are certain types of files on
NetWare systems that you can view
and select in the Backup Manager browser but which
do not actually get backed up. Testing seems to
indicate that this is a function of a file having
both the ``hidden'' and ``system'' attributes.
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.