HP NonStop G-Series - Manual (Page 53)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-016
3-15
Changing File Ownership
starts, it checks the last modified timestamp for the file and synchronizes the file only if
the OPENUPDATE interval has elapsed since the last update.
In addition to specifying the OPENUPDATE option, the following conditions must be
met:
°
The file must not be audited.
°
The file cannot be opened for exclusive access.
°
Recovery must be enabled for the fileset.
Changing File Ownership
By default, the ownership of each synchronized file is preserved. You may specify the
OWNER option to give the files to any user ID, including your own user ID.
Note that for OSS files, only SUPER.SUPER can change the ownership of a file on the
destination. Moreover, using the OWNER option does not change the group id of the
file. To change the group id, the user must also specify the OWNERGROUP option.
Synchronizing Based on Ownership
By default, source files owned by all user can be candidates for synchronization,
provided the security settings allow it.
You can restrict the source file set to files owned by a specific user ID, by using the
FROMOWNER option. Files owned by other users are skipped.
Note that for OSS, if a directory that is not owned by the FROMOWNER user ID is not
synchronized, even if it contains files or subdirectories that are owned by the
FROMOWNER user ID.
Synchronizing based on REDEFINITION timestamp
By default, AutoSYNC compares source and destination MODIFICATION timestamps
to decide if the destination table needs to be replaced.
Users might want to synchronize tables after performing certain types of DML
operations on SQL tables, such as adding a column or a partition or creating an index.
However these operations leave the MODIFICATION timestamp unchanged and
update only the REDEFINITION timestamp, causing AutoSYNC to overlook the
change that occurred on the table.
To synchronize tables based on differences in the REDEFINITION timestamp, use the
SQLREDEF option. AutoSYNC then compares the source and destination
REDEFINITION timestamps of the table, in addition to the MODIFICATION
timestamps, to decide if a table requires synchronization.
Note that a SQL index is synchronized automatically with the primary partition of the
base table. If the redefinition date of an index in the source subvolume is newer than in