May 6, 2009

iTERA HA v6.0 Monitoring Checklist

IMPORTANT

This checklist provides only a brief description for most items. For instructions on any step of this checklist, consult the iTERA HA Training Guide (Monitoring section). For additional information consult the section of the Reference Guide that corresponds to the menu option listed. For instructions on common procedures, refer to the User and Troubleshooting Guide.

Daily System Tasks

The following procedures should be performed on a daily basis.

System Monitor (1.1, Primary and Backup)

Press F7=E2SBS to verify that the iTERA HA Subsystem is active (all nodes). On the Primary, press F10=Update Monitor.
Note the last update time for the Primary: ________________

Indicate the % Total Disk Storage Used.

Primary: _____________ Backup: _____________

Indicate the % Total Used By Receivers.

Primary: _____________ Backup: _____________

Local/Remote Journals Active? Indicate YES or NO. (If Remote Journal is inactive,
press F16=Process Monitor.) Primary:______/______ Backup: ______

Apply Job Active? (If not active, then troubleshoot via 1.1 F16=Process Monitor,
F9=Apply Jobs from the Backup node.) Backup: ______

Network/Subsystems Active?
Backup: ______/______

Vision Solutions, Inc. 15300 Barranca Parkway Irvine, CA 92618 USA Copyright 2008 VISION SOLUTIONS, INC. All rights reserved.

May 6, 2009

If Journal Entries Not Applied is larger than usual press F16=Process Monitor on the
Primary to investigate. Indicate number: __________

Objects Requesting Sync (F6=Objects Requesting Sync, Backup). Indicate number:

____________ If OSR excessive, submit additional sync jobs from F16 on the Primary. If tape sync is required, execute using F20=Tape Sync from the Primary.

Review Object Sync History log (F6=Objects Requesting Sync, F17=History, Backup
only).

Optional: Clear Object Sync History log (F6=Objects Requesting Sync, F17=History,
F20=Clear History Log, Backup only).

Review Message Log (F11=E2MSGLOG, all nodes). Clear Message Log (F16=Clear Info Messages, all nodes). This moves all messages
from the Message Log to history; view history via F18=History.

Check Role Swap Readiness status. If status is OK for all nodes, skip the Role Swap
Readiness section.

Role Swap Readiness Monitor (1.1, F14 - Primary)

Review the Role Swap Readiness Monitor Summary Status results. If Summary Status
indicates OK/OK, continue with the next section. If any tests indicate an ERR status, investigate and resolve as necessary, using the steps on the last page of this checklist and/or the User and Troubleshooting Guide. Press F18=Submit All Tests to retest, as needed.

Review Record Count Audit (Option 1 on RCDCNT test in the Role Swap Readiness Monitor or 1.22, Backup)
Set the Filtering I/O field to O, enter an asterisk in the Alloc State and RSync
Y/N fields, as indicated:

For objects that display errors, select option 8=Audit, then F5=Refresh (after a few
moments). Select option 6=Resync for objects that reappear.

Press F21=Clear Audits.

Review Object Attribute Audit (E2MSGLOG and 1.23, Backup)

Messages generated by the Object Attribute Audit will be displayed in the iTERA HA
Message Log. Select option 5 for the most recent audit (highest Audit ID number). Select option 5 for a library to view object detail.

Vision Solutions, Inc.

May 6, 2009

Object Monitor (1.4, Primary)

Wait five minutes then press F5=Refresh. Check the Object Monitors Process Status
(field displays the status of the OBJMON job). If the Present Delay field is excessively high (relative to your system), indicate the number, investigate and resolve as necessary: __________

Indicate the Process Difference for IFSMON: __________

Spool File Monitor (1.6, Primary)

If replicating spool files, review the number of entries to be processed: __________

IFS Audit Review (Audit Console [6], opt 1 on IFS_Review; Backup)

If replicating IFS, check the following:

Verify the audit ran. Indicate the End Date of the most recent audit: ______ View details of each audit. Select the audit to review with option 1, followed by the
function key of the failure type. Use option 5 to display and review details. Indicate number of Authority Failures (opt 1 w/F8; opt 5): __________ Indicate number of Attribute Failures (opt 1 w/F9; opt 5): __________ Indicate number of Data Failures (opt 1 w/F10; opt 5): __________

Resolve audit failures.

NOTE

Verify E2IFSPRGA runs regularly in the job scheduler to purge audit data.

Heal Monitor (3.7, Backup)

Review the number of pending Heal records. Record the number here: __________

Non-Mirrored Object Replication Check (4.30, Primary)

Verify that all objects that need to be replicated are being replicated. The Last Sync
Date/Time data should be current.

Weekly System Tasks

The following tasks should be executed, at minimum, on a weekly basis.

Review locked object list (4.22; Primary). For objects that do not have current locks,
either start journaling and replication on them, or remove the filter (F15=Filters),

Vision Solutions, Inc.

May 6, 2009

resync the objects (9=Sync Object), verify the objects are synced, then remove them from the list (4=Delete Lock Record).

Check Data Queues (1.50.1; Primary). If not empty, check E2MSGLOG (not
necessary if running V5R4 or higher).

Run the User Profile Component Checker (1.50.2, F18=Submit Info Build; all
nodes). Resolve warnings and errors.

Run the Job Description Component Checker (1.50.3, F18=Submit Info Build; all
nodes). Resolve warnings and errors.

Check for new libraries (1.50.4, F7, F7; Primary). Use option 21=Quick NetSync for
new libraries you want to replicate. Use option 16=Clear New Status for libraries that you do not want to replicate.

Verify sync status for active libraries (1.50.4, F6) Ensure all libraries have a status of
syncing and review cross-library dependencies.

User Profile Replication (1.50.5.1; Primary). Verify the map is correct (F16=Dft
Map). If modifications are needed, use F8=Update Remote Maps to modify the remote map then F13 to trigger profiles.

IFS (1.50.5.2; Primary): Verify that all necessary directories and/or folders are
replicated.

Spool File Replication (1.50.5.3; Primary): Select F7 twice to review new output
queues and replicate as needed.

Configuration Replication (1.50.5.4; Primary): Select F16=Expand/Compress to

expand the view. Review for new items and replicate as needed. Review Configuration Replication errors in 5.4 on the Backup.

Job Scheduler Replication (1.50.5.5; all nodes): Ensure that everything that should be
replicating is. Errors can be fixed through 5.5 on the Backup.

MQSeries (1.50.5.6; Primary): If replicating MQSeries, ensure that all queue

managers are replicating.

Directory Entry Replication (1.50.5.7; all nodes): Ensure that everything that should
be replicating is. Errors can be fixed through 5.7 on the Backup.

Update Non-Mirrored Library Sync status (4.30, [Library = *ALL, Target System =
*ALL]; Primary).

Monthly System Tasks

The following tasks should be performed, at minimum, on a monthly basis. For complete instructions, refer to the guide How to Get and Apply iTERA HA 6.0 PTFs.

Load and apply PTFs for XP (Cross Product) using menu option 10.46 (specifies
product ID 7PA2K02; release V4R3M0).

Vision Solutions, Inc.

May 6, 2009

Load and apply PTFs for iTERA HA using menu option 10.45 (specifies product ID
7PA2K05; release V6R0M0).

If using iTERA Alert, load and apply PTFs using menu option 10.47 (specifies
product ID 7PA2K25; release V6R0M0).

Troubleshooting Steps
Option 1 on OBJSNCSTS test from the Role Swap Readiness Monitor (1.7; all nodes)
Set the Filtering I/O field as follows on all nodes:

This filter will display all objects for which journaling is not active. An object that displays an X in the JRN column (the first filter column) indicates that it has been manually omitted and you may disregard it. Any object that appears with a value other than X needs to be investigated in order to determine why it is not being journaled. Set the Filtering I/O field as follows on all nodes:

This filter will display all objects that are not being replicated by the system. For any objects displayed, verify that they should not be synced (i.e., that they were omitted from replication on purpose).

Set the Filtering I/O field as follows on all nodes:

This filter will display all objects that are marked to be omitted. For any objects displayed, verify that the objects should be omitted. (You may want to set up an audit exclusion filter to exclude them from the audit so that the objects dont appear in this list on a daily basis. To do so from this screen, press F7, then F6.)

Vision Solutions, Inc.