NEC 320Fc - Manual (Page 62)

Configuring Custom Actions
3-12 Express5800/320Fc: Active Upgrade™ User’s Guide
Configuring Custom Actions
Use the Custom Actions page to customize the way that the Active Upgrade process
runs in your environment. You can create custom actions to perform the following types
of tasks:
• Specify how a critical application is stopped and started during the upgrade
process.
For example, if you use special executable files to start and stop your applications,
you can use the controls on the Custom Actions page to specify when these
executable files will run during the upgrade process, and, if you have several files,
you can specify the order in which they will run.
•
Check if a certain condition exists before starting the upgrade process.
For example, you can write a program to verify that a critical backup has completed,
if the load on the system is acceptable, or if it is a certain time of day before starting
the upgrade process.
•
Back up files during the upgrade process.
Any files that are modified on the Production Side system disks while the system
is in split mode are lost during the commit process, when the RDR mirrors are
resynchronized. If applicable, you can write a program to save copies of important
files before you commit an upgrade. For example, you can save a copy of an
application-specific log file that does not appear in the system Event Viewer. (For
information about saving Event Viewer logs, see
“Selecting Event Log Files to Back
Up” on page 3-10 .)
By default, the Custom Actions page supports executable files that are batch files
(.bat), application files (.exe), or Visual Basic scripts (.vbs). For other types of
executable files, see
“Executing Visual Basic Scripts and Other Types of Executable
Files” on page 3-18 .
N O T E S
1. Custom actions run consecutively when called. If one
action fails to terminate, it might prevent the next
action from executing, and, ultimately, prevent the
upgrade process from continuing. When you specify
an executable file for a custom action, verify that it
runs successfully outside of the Active Upgrade
process, and ensure that it completes in a timely
manner.