Arctera InfoScale™ Operations Manager 9.0 User's Guide
- Section I. Getting started
- Introducing InfoScale Operations Manager
- Using the Management Server console
- About selecting the objects
- About searching for objects
- Examples for using InfoScale Operations Manager
- Example: Cluster Server troubleshooting using InfoScale Operations Manager
- Example: Ensuring the correct level of protection for volumes controlled by Storage Foundation
- Example: Improving the availability and the disaster recovery readiness of a service group through fire drills
- Examples: Identifying and reducing storage waste using InfoScale Operations Manager
- Section II. Managing InfoScale Operations Manager
- Managing user access
- Creating an Organization
- Modifying the name of an Organization
- Setting up fault monitoring
- Creating rules in a perspective
- Editing rules in a perspective
- Deleting rules in a perspective
- Enabling rules in a perspective
- Disabling rules in a perspective
- Suppressing faults in a perspective
- Using reports
- Running a report
- Subscribing for a report
- Sending a report through email
- Managing user access
- Section III. Managing hosts
- Overview
- Working with the uncategorized hosts
- Managing File Replicator (VFR) operations
- Managing disk groups and disks
- Creating disk groups
- Importing disk groups
- Adding disks to disk groups
- Resizing disks in disk groups
- Renaming disks in disk groups
- Splitting disk groups
- Moving disk groups
- Joining disk groups
- Initializing disks
- Replacing disks
- Recovering disks
- Bringing disks online
- Setting disk usage
- Evacuating disks
- Running or scheduling Trim
- Managing volumes
- Creating Storage Foundation volumes
- Encrypting existing volumes
- Deleting volumes
- Moving volumes
- Renaming volumes
- Adding mirrors to volumes
- Removing the mirrors of volumes
- Creating instant volume snapshots
- Creating space optimized snapshots for volumes
- Creating mirror break-off snapshots for volumes
- Dissociating snapshots
- Reattaching snapshots
- Resizing volumes
- Restoring data from the snapshots of volumes
- Refreshing the snapshot of volumes
- Configuring a schedule for volume snapshot refresh
- Adding snapshot volumes to a refresh schedule
- Removing the schedule for volume snapshot refresh
- Setting volume usage
- Enabling FastResync on volumes
- Managing file systems
- Creating file systems
- Defragmenting file systems
- Unmounting non clustered file systems from hosts
- Mounting non clustered file systems on hosts
- Unmounting clustered file systems
- Mounting clustered file systems on hosts
- Remounting file systems
- Checking file systems
- Creating file system snapshots
- Remounting file system snapshot
- Mounting file system snapshot
- Unmounting file system snapshot
- Removing file system snapshot
- Monitoring capacity of file systems
- Managing SmartIO
- About managing SmartIO
- Creating a cache
- Modifying a cache
- Creating an I/O trace log
- Analyzing an I/O trace log
- Managing application IO thresholds
- Managing replications
- Configuring Storage Foundation replications
- Pausing the replication to a Secondary
- Resuming the replication of a Secondary
- Starting replication to a Secondary
- Stopping the replication to a Secondary
- Switching a Primary
- Taking over from an original Primary
- Associating a volume
- Removing a Secondary
- Monitoring replications
- Optimizing storage utilization
- Section IV. Managing high availability and disaster recovery configurations
- Overview
- Managing clusters
- Managing service groups
- Creating service groups
- Linking service groups in a cluster
- Bringing service groups online
- Taking service groups offline
- Switching service groups
- Managing systems
- Managing resources
- Invoking a resource action
- Managing global cluster configurations
- Running fire drills
- Running the disaster recovery fire drill
- Editing a fire drill schedule
- Using recovery plans
- Managing application configuration
- Multi Site Management
- Appendix A. List of high availability operations
- Section V. Monitoring Storage Foundation HA licenses in the data center
- Managing licenses
- About Arctera licensing and pricing
- Assigning a price tier to a host manually
- Creating a license deployment policy
- Modifying a license deployment policy
- Viewing deployment information
- Managing licenses
- Monitoring performance
- About InfoScale Operations Manager performance graphs
- Anomaly detection and monitoring
- Managing Business Applications
- About the makeBE script
- Managing extended attributes
- Managing policy checks
- About using custom signatures for policy checks
- Managing Dynamic Multipathing paths
- Disabling the DMP paths on the initiators of a host
- Re-enabling the DMP paths
- Managing CVM clusters
- Managing Flexible Storage Sharing
- Monitoring the virtualization environment
- About discovering the VMware Infrastructure using InfoScale Operations Manager
- About the multi-pathing discovery in the VMware environment
- About discovering Solaris zones
- About discovering logical domains in InfoScale Operations Manager
- About discovering LPARs and VIOs in InfoScale Operations Manager
- About Microsoft Hyper-V virtualization discovery
- Using Web services API
- InfoScale Operations Manager command line interface
- Appendix B. Command file reference
- Appendix C. Application setup requirements
- Application setup requirements for Oracle database discovery
- Application setup requirements for Oracle Automatic Storage Management (ASM) discovery
- Application setup requirements for IBM DB2 discovery
- Application setup requirements for Sybase Adaptive Server Enterprise (ASE) discovery
- Application setup requirements for Microsoft SQL Server discovery
Viewing graphs and faults for anomalies
You can view the trend graphs and faults in real time in the UI and receive email notifications for the detected anomalies.
You can view the graphs for entropy changes and for the anomalies that are detected during the read, write, and rename operations performed on a file system.
To view graphs:
- In the Management Server console, go to the Server perspective and expand Manage in the left pane.
- Search or locate the host in the left pane.
- Expand the host and expand Volumes.
- Click the volume that has the file system on which anomaly detection is enabled.
- Click Anomaly Watch.
The following trend graphs are shown:
Rename Count: Shows measure of rename operations analyzed over a time series.
Green contours: Represent the count of actual rename operations.
Blue contours: Represent the count of rename operations predicted by the ML engine.
Blue range: Represents the accepted range of rename operations predicted by the ML engine. Any count beyond this threshold is considered a deviation and shown as an anomaly indicated in red.
Read Count: Shows measure of read operations analyzed over a time series.
Green contours: Represent the count of actual read operations.
Blue contours: Represent the count of read operations predicted by the ML engine.
Blue range: Represents the accepted range of read operations predicted by the ML engine. Any count beyond this threshold is considered a deviation and shown as an anomaly indicated in red.
Write count: Shows measure of write operations analyzed over a time series.
Green contours: Represent the count of actual write operations.
Blue contours: Represent the count of write operations predicted by the ML engine.
Blue range: Represents the accepted range of write operations predicted by the ML engine. Any count beyond this threshold is considered a deviation and shown as an anomaly indicated in red.
High Entropy: Shows the entropy levels analyzed over a time series.
Green contour: Represents the entropy level for the actual data.
Blue range: Represents the accepted entropy range that is predicted by the ML engine.
Faults are generated if the count for file system attributes deviates from the ML engine predicted range. If a fault occurs and rule is set with the fault topic event.alert.vom.fs.anomaly, email notification is sent to the recipients for the generated faults. Ensure that you provide the details for the SMTP settings before setting the email notification for a fault.
The following fault is generated if an anomaly is detected:
The monitored-attributes patterns observed on the file-system-name file system indicate a few anomalies. Verify the data on the file system. Note: This alert originates from an early-stage ML model and may produce false positives if it has not yet fully learned the relevant patterns.