HP NonStop AutoSYNC

From a disaster-recovery viewpoint, the role of RDF and

Shadowbase is to maintain an accurate and current image of

audited databases on a backup system. However, this role is not

sufficient to ensure reliable takeover by a backup system if the

primary system fails. There are numerous other files that define

the application environment, and these files must all be mapped

accurately to the backup system. They include unaudited data files,

configuration files, and program executables.

Typically, when a critical file is changed on the primary system,

manual operations must be executed to move a copy of the file to

the backup system. This procedure is subject to human error and

can lead to configuration drift. If the configuration of the backup

system is not identical to that of the primary system, a failover fault

is likely if the primary system fails. The backup system may refuse

to come up or be restarted with an incorrect version of software.

HP AutoSYNC addresses this challenge.

It automatically ensures that the application environment on the

backup system is identical to that of the primary system.

Using a configured list of files that are important to the
application environment, AutoSYNC

monitors these files on the primary system and immediately

replicates changed files to the backup system. The backup system

configuration is therefore always synchronized with the primary

system, thereby guaranteeing a successful failover. AutoSYNC can

be configured to replicate files to any number of target systems.

Add caption

Virtually all file types are supported, including audited

and unaudited NonStop SQL tables; audited and unaudited

structured files; unstructured files such as edit files, OSS files,
and directories; and partitioned files. Files necessary to start and
maintain applications also are handled by AutoSYNC. Included are
configuration files, batch files, object/source files, OSS files, BLOBs,
TACL macros, and Obey files.

AutoSYNC supports triggers that can initiate any function

whenever a file is changed. Triggered functions can include
executing a TACL command, compiling a SQL program, or starting
a program such as a batch job. AutoSYNC also supports automatic
software distribution and can be used to initially load systems being
brought online by synchronizing the files of the new systems with
those of a primary system.