WVP NonStop Storage Analyzer Plug-in User Guide Version 1.0 Part Number 536988-001 Abstract This manual describes the installation, configuration, and usage of Web Viewpoint (WVP) NonStop Storage Analyzer Plug-in Software Version V01 (i.e. H01) on a HP NonStop™ system. Supported Release Version Updates (RVU’s) This publication supports H06.10 and J06.03 all subsequent H & J-series RVUs until otherwise indicated by a replacement publication.
Introduction Table of Contents Version 1.0 ........................................................................................................................................................... 1 Part Number............................................................................................................................................. 1 Abstract...................................................................................................................................................
Introduction 2-3-5 Work Files............................................................................................................................................ 36 2-3-6 Daily processing overview ................................................................................................................... 37 3 Administration............................................................................................................................................. 38 3-1 Overview ............
Introduction Table of Figures Figure 1-1 High-level architecture (WVP and NSA) ..................................................................................................... 7 Figure 1-2 High-level architecture (NSA Components)................................................................................................ 8 Figure 1-3 Functional Diagram ..................................................................................................................................
Introduction Figure 4-54 Command - Properties ........................................................................................................................... 71 Figure 4-55 Command - OBEY .................................................................................................................................. 72 Figure 4-56 Command - Run .....................................................................................................................................
Introduction 1 Introduction NonStop Storage Analyzer (NSA or SA) is a plug-in to Web ViewPoint. NonStop Storage Analyzer is a powerful and feature rich tool for the management, analysis and monitoring of Disks & Files on hp NonStop Servers. This document explains how to use NonStop Storage Analyzer. The first section provides an overview of the product which includes its architecture, functional description, and UI components.
Introduction 1-1-1 Architecture The NonStop Storage Analyzer (NSA) is plug-in the Web Viewpoint. The following reflects the Web Viewpoint and NSA Plug-in relationship and also how alerts are routed.
Introduction The NonStop Storage Analyzer (NSA) main data collection and management module is SA Host. Runtime controls and configuration parameters for the SA Host module are stored in the SACNFG file. The SA Client module supports the user interface functions and features. to display the data and trend information based on them. The SA Alert module is used to set the alert definitions.
Introduction Processing 1. Enscribe files are used to store all data managed on the NonStop (i.e. Main DB, Daily DB, Misc DB, and Alert Def DB). 2. The scheduled SA Host scans through the node and gathers all required file and disk information. The software includes optimization techniques, which allows the user to run the SA Host data collections as several concurrent sub processes each of which can be set to run in a specific CPU and priority.
Introduction 1-1-2 Functional Overview The following figure displays the different components of NonStop Storage Analyzer and how they interact with each other. There are two main user modules namely the SA Client and SA Host. There are three main admin modules namely SA Log, SA Admin, and SA Alert. Figure 1-3 Functional Diagram The SA Host uses the following four modules: o SAMGR This is the main process which runs on the NonStop. It uses the file SACNFG as its configuration file.
Introduction the SACNFG file, it will be applied on the second collection run after the changes have been applied. o SAPROC This is the sub process which runs whenever a collection is being started by the SAMGR process. Based on the number of CPU(s) to use in the SACNFG file, SAMGR creates the same number of processes each running in their own CPU. This makes the host module act like a distributed process making the collection faster and more efficient.
Introduction 1-1-3-1 Overview When NonStop Storage Analyzer is installed, a link will be added to the Web ViewPoint Operations menu namely ‘Storage Analyzer’ which links directly to the main NonStop Storage Analyzer screen. Two links will be added to the Admin menu namely ‘SA Runtime Admin’ and ‘SA Alert Admin’.
Introduction 1-1-3-2 Toolbars Storage Analyzer uses a common toolbar in most of its windows. Figure 1-5 displays the common toolbar shared by most of the windows. Figure 1-6 Common Toolbar The first icon is used to access the NSA Trend features. Clicking the Trend icon displays a new window to which users can trend data based on a selected profile attribute of a disk or file. This icon does not appear in some views. The last three icons correspond to the print, export to excel, and help functions.
Introduction 1-2 Install Process Overview 1-2-1 General There are three ways to install the product, they are: wizard installation, manual installation and through IPSETUP. Wizard Installation is the recommended install process; see section 2-2-5 on Wizard Installation for details. Wizard Installation will guide you through a step by step process allowing you to set parameters as you move along the installation. Refer to Section 2-2-6 for manual installation.
Installation and Configuration 2 Installation and Configuration Installation can be done either using the Wizard Installation, Manual Installation or IPSETUP. The Wizard Installation automates most of the install steps but requires Java Run Time on the PC where the installer is run. Configuration data is collected through user input and then the particular configuration files of WVP are updated and pushed to the NonStop server. This process greatly simplifies and streamlines the EA install process.
Installation and Configuration 2-1-2 Licensing The SA plug-in requires a runtime license key. If the PC from where SA is being accessed (via IE browser) has Internet access then the license key retrieval is completely automated. If no Internet access is available then instructions for retrieving a license key via email will be provided. When SA is initiated and no license file or key is found, the user is provided instructions on how to register and obtain a product license key.
Installation and Configuration 2-2 Installation There are 3 different ways to install Storage Analyzer: o NSA Install.exe: The PC –based wizard installer for Storage Analyzer. (This is the recommended installation process.) o Manual Installation: (This is not a recommended procedure.) o IPSetup.exe : The IPSetup(DSM/SCM) installer for Storage Analyzer 2-2-1 Install Basics 2-2-1-1 Overview NonStop Storage Analyzer consists of one host component installation pack.
Installation and Configuration 2-2-2-1 Command & Obey Files Table 1 Command & Obey Files - NonStop File Name Type/Code RWEP Description SABAMIMP 101 NUNU Obey file to import SA BAM entries to Web Viewpoint BAM MAKEWSA 101 NUNU Obey Script to create key sequenced files LICSADLL 101 NUNU Obey Script to license SADLL INSTSA 101 NUNU Obey Script to manually install Files located at $Volume.
Installation and Configuration 2-2-3 File List - Windows Client NonStop Storage Analyzer’s windows client file is the install package. 2-2-3-1 Object & Executable Files Table 3 Object & Executable Files – Windows Client File Name Type/Code Location Description SAInstall Exe User specified Wizard Install package for Windows 2-2-4 Configuration Defaults/Initial Settings At initial run, SA host runs in the first available CPU with priority 142. It is set to run each day of the week at 23:59.
Installation and Configuration 2-2-5 Wizard Install NonStop Storage Analyzer comes with a powerful, flexible and smart PC based installer. The PC based installer provides a comprehensive wizard that guides the user through the install process. Install options provide paths for different possibilities like default installation or single-resident installation.
Installation and Configuration 2-2-5-2 Process a. Double Click on the saInsall.exe file. This is a self extracting executable that will ask the user to extract the contents to a folder on the PC. Once extracted, the installer will be launched and the following screen will be presented. Figure 2-7 Installer welcome screen Clicking on ‘No’ brings up a dialog box asking the user to install Web ViewPoint first. The installer will then shut down. b.
Installation and Configuration Figure 2-9 Wizard Installation – Single-node configuration Alternately, if multiple-node installation is selected, users are presented with a form to; you can choose the ‘Multi-node’ option. This screen will accept address of multiple nodes/residents.
Installation and Configuration Figure 2-11 User logon information e. Clicking on NEXT brings up the following form. This form lets you verify Web ViewPoint files that will be downloaded and modified by the Storage Analyzer installation wizard.
Installation and Configuration f. Clicking on NEXT brings up the following form. This form lets you verify the TCP/IP process name. Figure 2-13 TCP/IP Process Name g. Once the environment is verified, the transfer of files begins which include the configuration, binary and OBEY files. A detailed progress of the whole process is shown Figure 2-14 Wizard Installation – File Transfer h.
Installation and Configuration i. If the installation is successful, the following screen shows up. If an error occurs during any step of the process, the same screen displays with details of the error: Figure 2-16 Installation Complete j.
Installation and Configuration 2-2-6 Manual Install This section describes the manual installation steps for Storage Analyzer. 2-2-6-1 Overview For performing manual install, user will need to FTP some files and follow the installation procedure described below. This is not a recommended process. 2-2-6-2 Process For the Manual Installation, use the WS_SW\Manual Install\ascii and \binary folders from the CD as specified bellow.
Installation and Configuration Figure 2-18 Installation of Storage Analyzer Each of the configuration parameters from 1 -6 can be changed by entering the number against it and then entering the corresponding value. When ready to install, enter ‘7’ and the installer will modify the necessary files and set the defaults for the Alerts and Runtime configuration. It then notifies the user whether the installation was successful or not. To start Storage Analyzer, Web ViewPoint must be started manually.
Installation and Configuration 2-2-7-2 Process o The following files need to be transferred in ‘BINARY ‘ mode to $volume.sub volume o Change the file code for RMVSA to 800 by issuing the following TACL command: o o RMVSA FUP ALTER RMVSA , CODE 800 Stop Web ViewPoint, if already running Set your working volume to $system.zwvps (or to $volume.sub volume where you have installed Web ViewPoint) Issue ‘Obey STOPWVP’ Run the Uninstall program, RMVSA Set your working volume to $system.
Installation and Configuration 2-2-8 IPSETUP Option (DSM/SCM) NonStop Storage Analyzer can be installed using DSM/SCM tool. 2-2-8-1 Overview NonStop Storage Analyzer is packaged on a CD as an independent product. To install Storage Analyzer on a NonStop server, proceed as shown in the following section using the product CD. 2-2-8-2 Process a. Run the IPSetup program to begin installation, and follow the on-screen prompts to copy the files to the NonStop system. b.
Installation and Configuration d) Volume to $SYSTEM.ZTEMPL. This is the sub volume where the individual product templates are located. e) Move the new Storage Analyzer template file (ZWSATMPL) from the sub volume where Storage Analyzer is installed. For example, if you installed the Storage Analyzer software on $SYSTEM.ZWVPSA, then enter the following command. > FUP DUP $SYSTEM.ZWVPSA.
Installation and Configuration 2-3 Configuration Options This section explains the configuration options available for Storage Analyzer and the files that are affected in the process 2-3-1 Overview The configuration for Storage Analyzer is spread over Web ViewPoint configuration files (STRTWVP & WVPCONF) as well as ENSCRIBE files that are created and modified during installation and also during the daily collection based on the settings defined in Storage Analyzer’s Admin interface.
Installation and Configuration *Note: The file ALDEF FH is used in relation to the Hourly alerts which is not currentl y being support ed in Storag e Analyz er. It’s reserve d for future release . [Back to TOC] Table 4 Data files Name Enscribe File Type Purpose SACNFG K Used to store the Runtime settings for the SA Host process as described in the Runtime Admin section. Parameters such as collection time, collection days, CPU(s) etc.
Installation and Configuration 2-3-3 Updating Configuration This section lists the configuration options that exist in the ENSCRIBE files which can be modified via the Storage Analyzer Runtime Admin & Alert Admin interface. Table 5 Configuration Options and Descriptions Item UI Reference Possible Values Description Run time Runtime Admin Hour (00-23) and Minute (00-59) (Default is 23:59) This defines in hour and minute of the day when the collection will start running.
Installation and Configuration Table 5 Configuration Options and Descriptions Item UI Reference Possible Values Description Generate EMS Event or not Alert Admin YES / NO - by This indicates if an EMS Event must be generated checking or unwhen any of the alert criterions matches. checking the option.(Default is NO) Run days Alert Admin One checkbox for each of the days in the week (Default all 7 days are checked). Days when alert threshold should be checked.
Installation and Configuration Table 5 Configuration Options and Descriptions Item UI Reference Possible Values Description File(s) to be included in the alert definition. Alert Admin All Files or Specific filename (Maximum 8 character alphanumeric string). (Default is All Files) This is used to indicate if all files will be checked for meeting the alert criteria or just a specific file. Also, the severity level for this alert criterion could be specified. File security & severity level.
Installation and Configuration 2-3-4 Web ViewPoint configuration files This section lists the configuration assigns that exist in the Web ViewPoint configuration files that are either added during the install or are important for the product activation. Table 6 ASSIGNS Name Location Possible Values Description LICENSE-FILE WVPCONF LICFILE This is a shared Assign file. Storage Analyzer uses the same license file as is used by Web ViewPoint by appending its license to the existing license file.
Installation and Configuration FCRPT K Used to store corrupted file info. FDEALOC K Used to store deallocatable file info. FLIC K Used to store licensed file info. FLICN K Used to store newly licensed file info. FNEW K Used to store newly created file info. FPART K Used to store primary partitions info. FPARTS K Used to store partitioned file info. FPID K Used to store PROGID file info. FPIDN K Used to store all the newly PROGID’d files on disks in that system.
Administration 3 Administration NonStop Storage Analyzer has two main admin screens namely the Runtime Admin screen and Alert Admin screen. These views are accessible from the Web ViewPoint admin menu. 3-1 Overview The SA Admin screen is accessed from the Web Viewpoint Admin as reflected below.
Administration 3-2 Functions and Settings 3-2-1 Runtime Admin The Runtime Admin settings can be changed by accessing the configuration screen via Web Viewpoint by clicking on the Admin-> SA Runtime Admin and selecting the Runtime tab (selected by default) as shown below: Figure 3-21 RunTime Admin The Runtime Admin lets the user with admin privilege change the runtime configuration of the SA Host. The runtime configurations are stored in SACNFG file, located in the Storage Analyzer sub volume.
Administration to 365 days. The value for this field is used to determine what files will be included in the old file count (i.e. those files that do not have a used date within the number of days specified). Note: It is recommended that the value used be reasonable because depending on the number of files on the node, if this value is set to a low value (e.g. 10), may result in the SA Host running longer than normal.
Administration Note1: The changed settings do not come into effect until after the next run of the collector. In other words, the SA Host reads the configuration file after it has finished collecting for that day and it only runs once every day. So, if the user changes the run time the following are possible scenarios: Table 8 Collector run scenarios Original Run time New Run time Has run today? Effect on Collection 1:00 pm 8:00 pm (later than the original schedule) No (i.e.
Administration 3-2-2 Runlog Admin The Runtime Log screen can be accessed via Web Viewpoint by clicking on the Admin-> SA Runtime Admin and selecting the Runlog tab as shown below: Figure 3-23 RunLog Admin The Runlog Admin displays a calendar which highlights (in green) a date if a collection was run for that date and therefore the data should be available for analysis. The maximum numbers of days marked as green depend on the “retention days” field specified in the Runtime Admin.
Administration Figure 3-25 Runlog Calendar Year Menu When a highlighted date is clicked, the collection details and the CPU/Process busy details are displayed. The collection details display the following information: Figure 3-26 Runlog Collection Details Start Time – the date and time at which the collection started to run Stop Time – the date and time at which the collection stopped Status – an indicator stating if the collection finished completely or not.
Administration The CPU/Process busy details displays the CPUs utilized during the collection and the CPU Busy statistics that were measured during the collection. This information can be used to fine tune the runtime parameters for SA.
Administration Figure 3-28 Alert Admin Note: Please refer to Table 9 for the definition of commonly used disk and file attributes used in setting the Alerts.
Administration 3-2-3-3 Disk Daily Alerts The Disk Daily Alerts displays the disk alert definitions set by the user. It has the following fields: Disk – name of disk Run Days – days at which alert should be checked. At least one day should be selected.
Administration e) Severity Level = (Critical) f) EMS Event number = 101 g) Generate EMS Event = No Simply stated, it means ‘report all the disks whose usage falls within 90%-99% range’ will be reported as an Alert and a corresponding EMS event will be generated. Users can click on the following icons/links: Add new alert – add a new alert definition – delete alert definition – edit alert definition When the ‘add new alert’ link is clicked, the following window is shown.
Administration At least one of the alert criteria must be specified. Multiple criterions from the above can be specified for an Alert definition. If at least one of them is satisfied, an alert will be reported for that particular disk. Note: Please refer to Table 5 or Alert Admin error messages for a description about the permissible values for each of these fields.
Administration When the edit icon is clicked, the disk alert definition window is displayed with values populated as per the Alert definition. Figure 3-31 Edit Disk Daily Alert Users can edit one or more fields and save the new definition or Cancel if they change their mind. The alerts definitions will not be updated in the SA Collector until the next run. Note: This means that alert changes are always going forward and do not associate with data that has already been collected.
Administration 3-2-3-4 File Daily Alerts The File Daily Alerts displays the file alert definitions set by the user. It has the following fields: File – location and name of file Run Days – days at which alert should be checked Enabled – flag indicating whether alert should be checked or not Used % – threshold value for the used % of the file; if used % is equal or greater than this value, alert is generated; alert severity is also shown beside threshold value.
Administration Run Days – days at which alert should be checked % Used – threshold value for the used % of the file; dropdown box containing alert severities is beside the input field. Index Level – threshold value for the Index Level of the file; trigger a notification if greater; dropdown box containing alert severities is beside the input field.
Administration When the edit icon is clicked, the file alert definition window is displayed with the populated values. Figure 3-34 Edit File Alert Users can edit one or more fields and save the new definition or Cancel if they change their mind. The alerts will be generated during the next run of the SA Host.
Administration 3-2-3-5 File Exclude Alerts The exclusions can be used on files where the alert criteria should not be applied. For example, you may want to exclude files that are static and although are over 80 or 90% full are not a concern. The File Exclude Alerts displays the exclude file definitions set by the user.
Administration In this example, all the files in $SYSTEM.STARTUP will be excluded from being reported, even if they match the criteria set in File Alert definition. Figure 3-37 File Exclude Example In this example, the file, ADMCONF in $GUEST.TEST will be excluded from being reported, even if it matches the criteria set in File Alert definition.
Using NonStop Storage Analyzer 4 Using NonStop Storage Analyzer This section provides the operational details on the command and control of NonStop Storage Analyzer. 4-1 NonStop Storage Analyzer Activation Once installed, NonStop Storage Analyzer is automatically started or stopped whenever Web ViewPoint is started or stopped. When stopped, the SA Collector(s) is also stopped, which means no storage data will be collected.
Using NonStop Storage Analyzer Central Display Panel on the right – This section is used to display information (e.g. grids, lists, details) based on the current selection on the tree. By default, it displays the Utilization charts, Volumes details and Physical disk usage summary, spawned into three tabs viz. Utilization, Volumes and Summary, for the given node. This section also displays detailed information about a particular disk and their sub volumes.
Using NonStop Storage Analyzer The following features are common for Volumes and Summary display: Alert Icons – These are alert indicators displaying if a disk has an alert. These are displayed based on user alert settings, as well as default alert settings which are shipped with the product (e.g. full or corrupt files). Users can define their own alerts or modify the existing ones.
Using NonStop Storage Analyzer Below the charts, a table is displayed which summarizes the file and size usage for each group. The first column in this table is the group ID, the second column displays the corresponding group name, third column displays the total size (in MB) consumed by that group and the fourth column displays the number of files that are owned by that group.
Using NonStop Storage Analyzer 4-2-2-2 Volumes The second tab displays Storage Analyzer’s Volumes screen. This contains details about all the volumes/disks that are present in the system. The default display displays all the disks, irrespective of the Alerts, but users can filter the display based on alerts. This information comes from the data collected and stored as per the settings in Runtime Admin. The Volumes tab has the following elements: Disk – name of the disk.
Using NonStop Storage Analyzer Figure 4-42 Archived Volumes display [Back to TOC] 4-2-2-3 Physical Disks Summary The third tab displays the Physical Disks Summary. It displays information about physical disks only. The following information is collected and exhibited: Disk – name of Physical disk. This is a clickable link, leading to detailed Disk properties upon clicking. Size (GB) – total size of disk (GB) at the time of collection.
Using NonStop Storage Analyzer Note: There might be some discrepancies in the values of the Disk Growth, Days to 90% and Days to 100% due to rounding off. E.g: Growth might have a value of 0 (rounded off from a very small number such as 0.003) but Days to 90% and Days to 100% might have some actual integral values. Also, if the Growth is 0 or negative, Days to 90% and Days to 100% columns will display ‘N/A’.
Using NonStop Storage Analyzer 4-3 Filtering based on Alerts This section explains how to filter the display using the various alert levels. 4-3-1 Overview Selecting alerts from the Alert Filter will update the Central Display. Users can check the alert level(s) they wish to view and click on the Apply button. Description of these Alert icons can be found here.
Using NonStop Storage Analyzer 4-4 Filtering based on User This section explains how to filter the display based on a particular user on the current node. 4-4-1 Overview When the user filters are applied, the Tree Hierarchy and Central Display are updated based on the selected filter. 4-4-2 Description Clicking on the User Filter brings up a small window wherein user options are displayed. Figure 4-45 User Filter View By default, option “All” is chosen.
Using NonStop Storage Analyzer Figure 4-46 User Filter Archive [Back to TOC] WVP NonStop Storage Analyzer User Guide – 536988-001 - 64 -
4-5 Disk Analysis This section explains the information that users can gather about a particular disk on the current node and its sub volumes. 4-5-1 Overview Users can drill down to a particular disk and monitor its usage. The Disk property page gives an expanded view of the various disk attributes and the alerts generated by it. It also displays information about sub volumes belonging to the disk. 4-5-2 Description Clicking on a disk in the Tree Hierarchy changes the Central Display.
Figure 4-47 Disk Properties When the “Show Physical link(s)” button is clicked, a window displaying the Pool information of the disk is displayed. This window displays the Pool, physical disks belonging to that pool, and logical disks belonging to that pool.
Figure 4-48 Show Physical link(s) [Back to TOC] 4-5-2-2 Sub Volumes The next tab is the “Sub Volumes” tab. This tab displays the following information about the disks sub volumes: Sub Volume – name of sub volume. This is a clickable link, leading to Sub volume Info for the selected disk upon clicking.
New File Count – number of files created in the sub volume between 0000 hrs and the start time of the collection New Size – size (MB) of the files created in the sub volume volume between 0000 hrs and the start time of the collection.
4-6 File List Window This section explains the pop-up window that displays files information for a particular disk/sub volume on the current node. 4-6-1 Overview Users can click on the file numbers displayed on the Central Display. This brings up a window which contains a list of files for that file category.
4-6-2 Description A file list window is opened when a user clicks on a file count hyperlink for different categories of files (e.g. corrupt files, Over 90% full files) in the Central Display of Archive View. All files, when clicked, have a link which opens a CCM Menu of available commands (applicable commands are based on the file type).
Clicking on a file enables the user to select from a set of commands: Figure 4-53 Command List The following commands are shown for all types of files: Properties – Displays the file properties such as file code, format, owner etc.
The following command is shown only for files with code 101: Obey – Obeys a file. The result of this operation is displayed in a separate window Figure 4-55 Command - OBEY TACL OBEY command is used to execute the OBEY operation. E.g. the above is equivalent to the following TACL command: -- OBEY $IDEL4.KENFILL.
The following command is shown only for files with code 101, 700, 800 and 100 files as shown: Run – Runs a macro/program file The result of this operation is displayed in a separate window Figure 4-56 Command - Run WVP NonStop Storage Analyzer User Guide – 536988-001 - 73 -
Run “Now” will run the file as-is.
Additional arguments, such as output file, no wait parameter etc. could be specified by opening the Run Dialog via Run > Open Dialog as shown: Figure 4-58 Command – Run File Options TACL RUN command is used to execute the RUN operation. E.g. the above is equivalent to the following TACL command: -- RUN $IDEL4.KENPRG.HELLO Duplicate – Duplicates/copies a file to a specified location. The user can specify the destination as either $volume.sub volume.filename or sub volume.
TACL FUP DUP command is used to execute the DUPLICATE operation. E.g. the above is equivalent to the following TACL command: -- FUP DUP $IDEL3.DEV1.COMPILE, SAHOST.COMPILE1 Move – Moves (copies to the destination and removes from the source) a file to a specified location. The user can specify the destination as either $volume.sub volume.filename or sub volume.filename (volume of the source file is used in this case) or just the filename (volume.sub volume of the source file is used in this case).
Figure 4-61 Command - Rename TACL FUP RENAME command is used to execute the RENAME operation. E.g. the above is equivalent to the following TACL command: -- FUP RENAME $IDEL3.AAIQA2.SMGR, $IDEL3.AAIQA2. SMGR1 Alter – Alters file code, maximum extents, security, and owner of the selected file as specified by the user. Result of the operation is displayed in a separate popup.
TACL FUP ALTER command is used to execute the ALTER operation. E.g. the above is equivalent to the following TACL command: -- FUP ALTER $IDEL3.AAIQA2.STOPWVP, CODE 100 Delete – Deletes the selected file after confirmation from the user. TACL FUP PURGE command is used to execute the DELETE operation. E.g. -- FUP PURGE $IDEL3.AAIQA2.FILENAME Download – downloads the selected file to users’ local machine as binary/ascii.
Figure 4-64 Command - Dealloc TACL FUP DEALLOCATE command is used to execute the Dealloc operation. E.g. the above is equivalent to the following TACL command: -- FUP DEALLOCATE $IDEL3.PVPOSAUR.WDSM001 The Contents display a table containing the following information: Code – file code. Used % - used % of the file. Partition – number of file partitions. Size (MB) – size in mb of the file. Max (MB) – maximum size in mb of the file. Owner – file owner (groupID.userID).
A – audit flag (Y/N value) Last Modified – last file modification date Created – file creation date Pri. Ext – number of primary file extents (in pages). Sec. Ext – number of secondary file extents (in pages). Max Ext – number of maximum file extents (in pages). Deallocatable Space – The amount of space (MB) that can be deallocated (only for Deallocatable Files.) Physical File –name of the physical file for logical disks, N/A for physical disks.
Table 9 Commonly used disk / file attributes. Attribute Name Description Primary Extents. The first extent is called the primary extent and can differ in size from the remaining secondary extents. It is used to contain all the data to be initially placed in the file. It defaults to one page. Secondary Extents The extent size beyond the primary extents. It defaults to one page.
Figure 4-65 Disk Trend Window [Back to TOC] WVP NonStop Storage Analyzer User Guide – 536988-001 - 82 -
Figure 4-66 Disk Trend Categories Users can trend the following disk attributes: Used (GB) – storage used (GB) on the disk (Physical files only) Free (GB) – unused storage (GB) on the disk (Physical files only) Fragmentation Free – number of fragments in the Free space on the disk Files Count – number of files on the disk Over 90% Count – number of 90% - 99% full files on the disk 100% Count – number of full files on the disk Corrupt Count – number of corrupt files on the disk
4-8 Sub Volume Trending This section explains the graphical trending of sub volume attributes belonging to a particular disk on the current node. 4-8-1 Overview Similar to disks, sub volume attributes can be analyzed by charting them over a period of time. The users can then see the trend for its utilization. 4-8-2 Description The Sub volume trending window is similar to Disk trending with regards to functionality.
Figure 4-67 Sub volume Trending Charts can be plotted for the following sub volume attributes: Total Size (GB) – total size (GB) of files in sub volume.
New Count – total number of newly created files for that date in the sub volume Growth (MB) – growth rate of the total size of files in the sub volume Figure 4-68 Chart Settings Selecting an attribute will draw the graph for the selected sub volume(s). The graph legend displays the name of the selected sub volume(s). Users can click on the “eye” icon next to the sub volume name to remove that sub volume from the graph and the icon will change. Clicking on it will display the sub volume again.
4-9 Fragmentation This section explains the data collection about free fragments available in Physical Disks on the current node. 4-9-1 Overview NonStop Storage analyzer reports the fragmentation information by finding out the various free extent sizes and the number of free extents on a disk. The size of each extent is reported as a page consisting of 2048 bytes (2 KB).
<= 1 GB 0 0.0 > 1 GB 2 99,564.4 (1608.286208 + 97956.12467) Total 18 99,674.
4-9-3 Description Clicking the Fragmentation Free value from the Central Display in the Storage information under the “Properties” tab at the disk level displays the fragmentation window. This window displays the breakdown of fragments in the Free space of the disk. Figure 4-69 Fragmentation The fragmentation window has the following information/components: Disk – name of disk Date Navigation – Enables the user to display the fragmentation information on a given date.
Fragmentation Table – Displays the breakdown of fragments in the free space. It also displays the fragment count and total size of those fragments per category.
4-10 Fragmentation Trending This section explains the graphical trending of Physical Disks from the collected fragmentation details. 4-10-1 Overview When the “Trend” icon is clicked in the Fragmentation Window, the Fragmentation Trend Window is shown. This lets users trend the fragmentation of the disk for a specified time period.
The fragmentation trending window displays a bar graph for the total number of fragments of different size on the disk. It also displays a bar graph for the different sized fragments present on the disk. All this information is shown for the number of days selected (as long as there is data for the days) The legend for both the graphs displays the different fragments. The same information is displayed in the form of a table below the graphs.
4-11 Partition Window This section explains the information collected and shown about primary partitioned files. 4-11-1 Overview A partitioned file is a file that resides on multiple volumes. A file can span up to 16 volumes. Moreover, the disk volumes can be connected to the same or different controllers, on the same or different processing modules, or can even span multiple systems. To the user the file seems contiguous.
Figure 4-71 Partition Window The bar chart displays the size of various partitions across the disks where they reside. The graph legend for file partitions display the various disks across which that file is spanned.
The Partition Detail Window displays the secondary partitions of a partitioned file. It displays the following information: Volume – volume of the file Partial Key – partial key of the file.
4-12 Alerts 4-12-1 Overview There are two different alerts being generated, namely daily disk alerts and daily file alerts. These alerts are based on the values set by the user in the Alert Definitions Admin. Additionally, users with admin rights for Alerts can edit the generated alerts.
Alert Table – This contains the following fields o o Severity Icon – Displays the severity of the alert. Possible icons are: - Critical - Major - Minor - Warning - Information Alert – Displays the alert generated.
Figure 4-73 File Alerts The following is shown in the daily file alert window: Path – path of file Date Navigation – Enables the user to display alerts based on a given date. Next or Previous buttons are available to allow the user to move to alerts for next or previous day. Alert Table – This contains the following fields o Severity Icon – Displays the severity of the alert.
Corrupt – if file is corrupt, alert notification is generated Missing – if file is missing, alert notification is generated. Reload – if file is a reload candidate(Index Level criteria); alert notification is generated o Value – This is the value of the alert which triggered it to be generated o EMS # – This is the EMS # for the alert Print – Prints the contents of table. Export to Excel – Transfers data from currently displayed table to MS Excel.
5 Appendix A 5-1-1 Software Support Support for Web ViewPoint is available through HP's 24-hour Global Mission Critical Support Centers (GMCSC) throughout the world. In the U.S. call 1-800-255-5010. International numbers see: http://h71014.www7.hp.com/gcscphone.html [Back to TOC] 5-1-2 Error and Advisory Messages (EMS Events) This section lists all EMS Events that can be generated specifically from the Storage Analyzer application conditions and processing. Storage Analyzer EMS SSID: TANDEM.
NSSTORA 103 : Decompose Error: Relating to function or activity: Primary or backup SAMGR process trying to retrieve process information from the process handle. Cause: Occurs on the “PROCESSHANDLE_DECOMPOSE_” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, for e.g. non-existent process (Error 14).
Recovery: Recovery will depend on the specific Guardian error returned. Make sure that the file exists before being opened. If the max numbers of File Opens have been reached, then close all open file handles and then try again. NSSTORA 110 : Pair Info Error Relating to function or activity: SAMGR attempting to communicate with the primary. Cause: Occurs on the “PROCESS_GETPAIRINFO_” Guardian procedure call.
NSSTORA 114 : READUPDATEX error : Relating to function or activity: Reading from some process and replying to that process failed Cause: The process with which communication was being attempted has expired. The EMS Event indicates the error value returned by the Guardian Procedure call READUPDATEX Effect: Any future I/O Operations with the deceased process will fail. Recovery: The parent process should restart the child process that died prematurely.
Cause: The file could not be created using the Guardian Procedure call FILE_CREATE_. The EMS Event indicates the file name and the corresponding Guardian Error returned by the Guardian Procedure Call. Effect: Any succeeding operation (READ/ WRITE) on the file will fail. Recovery: If the file is corrupted, then try to recreate the file with the same parameters. Please consult the INSTSA file to check whether the file is created at startup.
Relating to function or activity: Positioning the file pointer within a key-sequenced file (database file) to access contents. Cause: Occurs on the “FILE_SETKEY_” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, for e.g. non-existent record (Error 11).
Effect: Properties about the file cannot be reported Recovery: N/A NSSTORA 203 :File search error: Relating to function or activity: Searching for a particular file failed. Cause: Occurs on the “FILENAME_FINDSTART_” procedure cal. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, e.g. file missing etc.
5-1-3 Error & Advisory Messages (Pop-up Messages) This section lists important Pop-up Events that display various Storage Analyzer application conditions. Storage Analyzer Processing Errors - Pop-up Messages If a database interaction error (on a procedure call) occurs, an EMS event is generated as explained in the previous section.
Cause: Trying to update the Runtime settings without selecting any days to run. Effect: If Ok is pressed, the SA Host process (SAPROC) will never run, if Cancel is pressed, the runtime settings will not be changed. Recovery: None Microsoft Excel not found on your machine. Cause: ‘Export to Excel’ was clicked but no instance of Excel is present on the system from which Storage Analyzer is being viewed.
Enter correct Extents (0- 10000000) Cause: Adding or editing a disk alert when Extents checkbox is checked but an invalid value is entered for that field. Recovery: Enter a valid Extents value (0- 10000000). Enter correct Index (0- 255) Cause: Adding or editing a disk/file alert when Index checkbox is checked but an invalid value is entered for that field. Recovery: Enter a valid Index value (0- 255).
Alert already exists. Cause: An alert definition for disk (Disk Alerts) or disk-sub volume / disk-sub volume-file (File Alerts) combination being added exists already. Recovery: Either cancel the addition or add the alert for another disk (Disk Alerts) or disk-sub volumefile (File Alerts). Alert Definition has been deleted. Cause: Informational message that comes up after the alert definition is successfully deleted. Alert exclusion rule has been added.
Function or activity: Storage Analyzer – User Filter View Please input a user. Cause: Clicking on the User filter icon, checking the Only User option and clicking Submit without entering in the text field. Recovery: Enter a user that already exists on the node. Please enter a user / Invalid User / Please enter a valid user (Group.User/Alias name/GroupID.UserID) Cause: Clicking on the User filter icon, checking the Only User option and clicking Submit after entering an invalid user.format.
No data available for Capacity chart. Cause: No data exists since the plug-in just got installed and hence the capacity chart will not be displayed. Recovery: None. To determine the days for which data exists, users can view the grid displayed in Runlog Admin. Function or activity: Storage Analyzer – File list window. File database has been deleted. Cause: Trying to get detailed information about a particular file (e.g. Over 90% Full, Old Files etc.
Please select 1 or more disks. Cause: In the disk trend window, when no disk is selected from the list of Available Disks and the Chart button is clicked. Recovery: Select at least one disk for which the trend graph is to be displayed. Please select up to 25 disks or less. Cause: In the disk trend window, when more than 25 disks are selected from the list of Available Disks and the Chart button is clicked. Recovery: Select up to 25 disks for which the trend graph is to be displayed.
Recovery: None At least one alert severity level (or "None" option) must be selected.' Cause: None of the alert checkboxes were selected and the Apply button was clicked Recovery: At least one of the alert checkboxes must be selected before clicking ‘Apply’ Function or activity: Storage Analyzer Disk/Sub volume trending. No data exists for yyyy-mm-dd. Do you wish to see the trend from the beginning (yyyymm-dd)? Cause: The user selected a date in future for which there is no data.