HP MPX200 Multifunction Router - Manual (Page 23)

Table 2 Possible data migration job states (continued)
Description Job State
A running job has been paused by the user. You can resume or stop a paused job. A paused job that
is resumed continues running from the point where it was paused. Paused
A running, scheduled, failed, or pending job has been halted. You can restart or remove a job in the
stopped state. A stopped job that is restarted begins at the job start. Stopped
Sync up errors caused the online local migration job to fail, or a lost or full data management LUN
caused the online remote migration to fail. Failed
A job goes into a suspended state when access to either the source or destination LUN is lost. Suspended
A job has been created with the Configure Only option without a specified start time. Configured
A job goes into this state when a data migration copy is completed and the router is synchronizing the
DRL blocks with the destination. Synchronizing
Job failover and failback
Data migration job failover and failback extends the current support for high availability. The
feature adds a new infrastructure for moving the migration job between blades. Utilizing this
infrastructure, migration jobs can be failed over and fail back between blades.
Migration job failover is a process of moving a migration job from its owner blade to a peer blade.
Migration job failback is a process of returning a previously failed over job to its original owner
when that job is restored after a failure. Both failover and failback virtually use the same process
and can be done manually by changing the migration ownership.
The feature also adds support for automatic failover. Automatic failover enables the second blade
to automatically take over the migration jobs of its peer when the peer goes down.
To configure automatic failover using mpx Manager:
1.
In the left pane, select the Services tab, and then click Blade 1.
The Data Migration Info page appears in the right pane.
2. Under Migration Parameters:
a.
Enter a value in the Job Auto-failover Timer (Seconds) box that indicates the number of
seconds that the MPX200 waits for the source or destination LUN to come up after the
job owner blade is powered down or the source or destination LUN becomes unavailable
on the owner blade. The default value is 600.
b. Select the Job Auto-Failover Enable check box.
3. Click Set.
4. Repeat the preceding steps for Blade 2.
To set automatic failover parameters using the CLI, issue the migration_params set command.
For example:
MPX200 <1> (admin) (miguser) #> migration_params set
Local Migration Periodic Flush Interval (Secs, Min=30 ) [30 ]
Remote Migration Periodic Flush Interval (Secs, Min=300 ) [900 ]
Job Auto-failover Timer (Secs, Min=600 ) [900 ]
Job Auto-failover Policy (1=Disabled, 2=Enabled) [2 ]
Successfully Modified Migration Global Parameters
NOTE: You must change the Job Auto-failover Timer value before you make a destination or
source LUN unavailable. The timer value change applies only to the currently running job.
Data migration jobs 23