|
This area contains questions and answers for the AutoSYNC product. It is currently undergoing revisions and updating.
For further assistance please contact us. |
1) I have AutoTMF. Why do I need AutoSYNC?
A) AutoTMF allows you to audit database files and use
RDF or other third party tool such as Shadowbase to keep files synchronized
between systems. But many files cannot be audited (object files, OSS files
and directories) or do not lend themselves to auditing (edit files).
AutoSYNC automates the synchronization of these files between NonStop
servers. AutoSYNC synchronizes files that are not audited.
2) Can I use AutoSYNC to synchronize audited files?
A) Yes you can, if you specify that you want to
synchronize audited files and if the audited file is not opened for update.
3) Can I synchronize files that are opened for read only access?
A) Yes, AutoSYNC synchronizes files that are opened
for read-only access.
4) What happens if the object file I am trying to synchronize is currently
running on the destination?
A) You can tell AutoSYNC to rename the destination
file prior to replacing it.
5) Can I synchronize my OSS files?
A) Yes you can synchronize OSS files, directories and
links.
6) Can AutoSYNC synchronize SQL/MP tables?
A) Yes it can.
---------------
7) Can AutoSYNC synchronize partitioned files and tables?
A) Yes, it can. You can use the MAPNAMES option to
tell AutoSYNC where the secondary partitions will go on the destination
system.
8) Is there a way to SQL compile my object files after they have been
synchronized?
A) Yes. AutoSYNC has a trigger mechanism that allows
you to execute a TACL
script or command or an OSS shell command after a file has been
synchronized.
9)What happens if the synchronization of a file fails?
A) AutoSYNC saves a copy of the file on the
destination system before it is attempts to replace it. If the
synchronization fails for any reason, the original file is restored. The
synchronization is retried at the next interval.
10) Can I do synchronizations on the fly and if so, what is the advantage of
using AutoSYNC to do this instead of FUP?
A) AutoSYNC can synchronize files over TCP/IP as well
as Expand. AutoSYNC does extensive error reporting. AutoSYNC
synchronizes Enscribe files and SQL tables. The user can specify a mapping
file to move alternate key files, partitions and SQL indexes to different
locations on the destination. AutoSYNC synchronizes only the files
that have changed, according to the options the user specifies (AUDITED,
TIMEEXACT, so on)
AutoSYNC synchronizes OSS files A trigger command can be executed after the
file has been moved, such as SQL compilation of SQL programs.
11) How do I make sure that files that do not belong to a user are not moved
by AutoSYNC?
A) AutoSYNC follows the Guardian and OSS and Safeguard
rules as configured on the source and destination systems. The
synchronization processes run under the userid of the syncuser and do not
have additional access privileges.
12) We are installing a new system in our data center. Can I use AutoSYNC to
move the files over?
A) Yes you can. In fact, since you can move the files
over TCP/IP, the new system can have the same Expand node name as your
current system.
13) I don't have any idea how much change there is in my environment. How do
I know how dynamic my environment is?
A) AutoSYNC has a reporting function that tells you
how many files will require synchronization and the amount of data that will
be moved. You can run the report as often as you like on any file set
and evaluate the amount of change your files are undergoing.
------------
14) When the synchronization occurs automatically, how do I know it worked?
A) A log file is configured for each user. The details
of each synchronization are stored in the user's log file. Errors and
catastrophic events are sent to an EMS collector. An EMS filter is supplied
with the product to assist the operator in displaying only AutoSYNC events.
|
