Checking the outcome of scheduled synchronizations, Security and authorization – HP Integrity NonStop H-Series User Manual

Page 67

Advertising
background image

Scheduled Synchronization

HP AutoSYNC User’s Guide522580-021

4-7

Checking the Outcome of Scheduled

Synchronizations

Checking the Outcome of Scheduled
Synchronizations

As mentioned above in the

AutoSYNC Users

paragraph, the outcomes of scheduled

synchronizations performed on behalf of Syncuser ggg,uuu are logged in file
SLggguuu. To display the content of the synchronization log file, use the LOG option of

INFO BATCHID

or INFO

INFO SYNCFILESET

.

Security and Authorization

A scheduled synchronization is managed by the AutoSYNC monitor process. The
monitor process starts ASYSYNCP processes for each AutoSYNC user who has been
added and who has configured synchronization file sets.

Initially, the ASYSYNCP process runs under the user ID of the authorizer, but when
accessing files, the ASYSYNCP process uses only the user ID and access rights of the
user who configured the file sets. When the process starts, it logs on as the user ID.
The change of user ID succeeds only when the authorizer is the Super user, the group
manager, or the AutoSYNC user. If the logon operation fails, ASYSYNCP terminates.

The syncuser must have appropriate remote passwords to any remote destination.
AutoSYNC can only synchronize files that are secured for read access by the user ID
and replace files that are secured for purge access by the user ID. If the destination is
remote, replaced files must be secured for remote purge access, unless the remote
ASYSYNC process is configured to run as a local process as described in

Licensing

Synchronization Processes

on page 2-11.

The syncuser gggg,uuu must also have the following access privileges to files and
tables in the MapDB subvolume:

WRITE access to the log file SLggguuu on the source and destination

WRITE access to file recovery index file AAINDEX on the destination

READ, WRITE, CREATE and PURGE to the temporary files created during
synchronizations in the MapDB subvolume and in subvolumes with the MapDB
name on any destination file set volume:

ZBKnnnnn on the source,

ZRSnnnnn on the destination,

AAnnnnn, ABnnnnn, ACnnnnn, etc on the destination.

The ownership of synchronized symbolic links is a special case. By default, the owner
of a synchronized symbolic link is the syncuser and not the owner of the source
symbolic link or the OWNER specified in the

ADD SYNCFILESET

or

ALTER

SYNCFILESET

command option.

To change this behavior, see

Changing Ownership of Symbolic Links

on page 5-7.

Advertising
This manual is related to the following products: