Technical article 100083

I can only back up or restore UNIX clients from the command line with ARCserve/Open 2.2.0.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5UnixWare 7.0.0UnixWare 7.0.1

Written · Last revised

Problem

After installing SCO ARCserve/Open and licensing remote clients,
I can back up or restore all of my clients when using the menu
options.  However, I can only back up and restore my UNIX clients
using command line options.  All other clients fail to back up or
restore using the command line options.

Cause

The current version of ARCserve/Open uses push technology for the
remote agents.  It is not possible to use command line utilities
to back up or restore these remote clients without providing a
user account and password.  This would present a possible security
problem.

Solution

There are two workarounds to this issue.

One solution is to use the menu options when doing a backup or restore of a non-UNIX remote client.

Another solution would be to use the menu to set up a backup or restore of a non-UNIX client and then save that session to a file. Using the command line, it would be possible to use the saved session to run a backup or restore of a non-UNIX client.

Below is an example of how to create and save a backup session for
a remote client and then use the saved session to run the backup
from the command line.  The same steps could be used to create a
restore session for a remote client.
EXAMPLE BACKUP PROCEDURE

1. Start SCO ARCserve/Open from the main desktop by selecting the ARCserve/Open icon.

2. Select the Backup icon from the ARCserve/Open Main Menu.

3. Select the Remote Hosts icon from the Backup Menu.

4. Select the desired remote machines from the available choices that are listed.

5. After all of the remote machines and source options have been chosen, select the File option from the top bar Backup Menu.

6. Select the Save option from the choices and provide a name
   for the saved file.  The default filename will be .as5; however,
   it would be more practical to choose names that would be more
   descriptive of the backup session. For instance, if you save a
   session that will back up a remote Windows 95/98 machine, give the
   saved file the same name as the remote machine.

7. The saved file (by default the file will be saved in the /usr/lib/ARCserve/jobs directory) can be used to perform a backup from the command line.

8. The command line to use a saved file would use the following syntax:

as_qmgr -load /usr/lib/ARCserve/jobs/.as5
where:
as_qmgr equals command line interface to the job queue;
-load   equals command option to load a script file;
/usr/lib/ARCserve/jobs/.as5 is the default script file
to load.
The above example would immediately execute a backup of a remote
machine using the information in the .as5 script file.  Note that
the full path to the saved script file must be specified on the
command line.

It should be noted that although the saved job file is referred to as a "script" file, it is a data file and is not viewable with standard viewers like more(C), pg(C) or cat(C) and cannot be edited with a standard ASCII text editor like vi(C).

Additional help for the command line options can be found by using
the man(C) command.  The following manual pages can be referenced
with the man command: as_backup, as_restore, as_dbmgr, as_qmgr,
as_devmgr, as_scan, as_merge.

See also

Appendix A, Command Line Options, SCO ARCserve/Open from Cheyenne User Guide.

Chapter 3, page 33, Creating scripts for your jobs, SCO ARCserve/Open from Cheyenne User Guide.

From the Xinuos technical article database, record 100083. Reproduced with permission. The original is at www.sco.com/ta/100083, 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.