HP NonStop G-Series User Manual
Page 129
Command Interpreter
HP AutoSYNC User’s Guide—522580-015
8-41
ALTER SYNCFILESET
If OWNER is omitted, the owner of the source file is retained.
PRI[ORITY] priority | NO PRI[ORITY]
the process priority at which the ASYSYNC process is to run when processing
this syncfileset.
If priority exceeds the value of MAXPRIORITY set with the
command, it is overridden by the syncuser's
MAXPRIORITY.
If this option is omitted, the priority of ASYSYNC is set to the priority of the
syncuser.
PURGE | NO PURGE
specifies that any file that is in the destination file set but is not in the source
file set will be (or will not be) purged. By default AutoSYNC does not purge any
file in the destination file set.
Guardian file sets:
°
If PURGE is specified, the subvolume portion of the source and destination
file sets must be fully qualified (no wild-card characters or "*").
°
Purging of files occurs on a subvolume by subvolume basis. A destination
file is not purged if it does not exist in a corresponding source subvolume,
unless the SUBVOLPURGE option is also specified.
°
Extra SQL objects in the destination like tables, views and indexes are
purged. Catalog files are not supported and they are not synchronized or
purged by Autosync.
Extra SQL tables and views are purged explicitly, indexes and secondary
partitions are purged implicitly, with the main table.
OSS files and directories:
°
If PURGE is specified, subordinate directories not present in the source file
set are purged on the destination. Note that this is different than the
processing of Guardian subvolumes. Guardian subvolumes are not purged
unless SUBVOLPURGE is specified.
An entry is written into the log file for each file or OSS directory that is purged
as a result of the synchronization.
PURGE is not supported for SQL tables.
Note for OSS file sets. If OWNER is specified and OWNERGROUP is omitted, the
OWNERGROUP of the file set is set to the group of the source file, not the group
specified by OWNER.
Note. Be aware that running ASYSYNC at high priority may impact system
performance as the process is CPU bound.