HP Integrity NonStop H-Series - Manual (Page 38)

Installation
HP AutoSYNC User’s Guide—522580-021
2-10
Running Different Versions of AutoSYNC
Running Different Versions of AutoSYNC
If you need to run different versions of AutoSYNC on the same system, for example to
test a new version of the product, you must configure an alternate AutoSYNC
environment (Monitor and MapDB) and install the test software in a different location.
For details on configuring and using an alternate environment, see
Configuring and
Using an Alternate AutoSYNC Environment on page A-7.
Special Cases: Licensed Synchronization
Processes
In order to perform certain operations that would otherwise be prohibited, AutoSYNC
requires the ASYSYNC and ASYSYNCP object files to be licensed. Those operations
include:

If Safeguard's PASSWORD-REQUIRED ON is set on the source system,
AutoSYNC is not able to manage scheduled synchronizations for multiple
SYNCUSERs because it cannot "log down" from the Authorizer to another
SYNCUSER. Licensing ASYSYNCP on the source system bypasses this
restriction.

For synchronizations over TCP/IP, Safeguard's PASSWORD-REQUIRED ON
setting on the destination system causes the same “log down” problem as
described above. Licensing ASYSYNCP on the destination system bypasses this
restriction.

If files on a remote destination are secured for “local-only” access (A, G, or O
security), security errors may prevent replacing the existing files. Licensing
ASYSYNC on the destination (or ASYSYNCP if the synchronization is over
TCP/IP) enables local access to the destination files.

Preserving ownership of OSS file sets and symbolic links:
When a syncuser synchronizes OSS files or symbolic links, the syncuser becomes
the owner of the files on the destination, regardless of the owner on the source.
Only SUPER.SUPER can preserve (or change) the ownership of OSS files or
symbolic links on the destination, with the following requirements:

To preserve the ownership of the OSS files, the destination ASYSYNC (or
ASYSYNCP if synchronizing over TCP/IP) must be licensed. This allows
ASYSYNC(P) to run as a local process.

To preserve the ownership of a symbolic link, or to give the link to a different
user ID through the OWNER or OWNERGROUP option, the destination
ASYSYNC process (or ASYSYNCP if synchronizing over TCP/IP) must be
licensed to allow SUPER.SUPER to log down to the specified user.

Synchronizing licensed and progid'ed files to a remote destination requires the
following: