Visara Master Console Center Administration Guide - Manual (Page 52)

Visara Master Console Center
52 © Visara International 2007
Moving Tasks between Operating Systems
TaskMan can move tasks from one OS to another. This feature is useful when a
particular task may be handled by more than one OS, and the OS currently
serving the task has failed in some way. Through careful setup and scripting, the
task can be moved automatically to another OS using TaskMan. The relevant
script(s) handle startup of the task on the new OS.
Configuring Movements of Tasks
To allow moving of tasks, several configuration conditions must be met:
ƒ All Operating Systems that tasks can move between must be defined as the
same type (the “type=” value).
ƒ The type definition must contain two list fields:
-
tmmode
-
moveable
ƒ Required tmmode list values must be set:
-
None
-
Zombie
-
At least one other value
ƒ Required moveable list values must be set:
-
No
-
Primary
-
Zombie
Moving Tasks
To move a task, the task on the original OS must have:
ƒ A tmmode status of neither None nor Zombie.
ƒ A moveable status of either Primary or Zombie.
When the move option is chosen for a selected task, the user is presented with a
list of Operating Systems of the same type as the original. Each of these
operating systems has a tmmode status of Zombie and a moveable status of
either Primary or Zombie. After the user selects the destination OS, TaskMan:
ƒ Sets the destination OS tmmode status for the selected task to the same as
the original OS tmmode status.
ƒ Sets the destination OS desired status to the same as the original OS desired
status.
ƒ Sets the original OS tmmode to Zombie.
The task automatically starts on the destination OS when the site-specific
TaskMan monitoring script detects a mismatch between the task’s desired status
and current status fields.