HP 3PAR StoreServ System Reporter Best Practices

Technical white paper

HP 3PAR StoreServ System Reporter Best Practices Table of contents Abstract...................................................................................................................................................................................... 2 External System Reporter vs System Reporter on-node................................................................................................. 3 System Reporter Excel Interface........................................................................................................................................... 4 System Reporter Configurations........................................................................................................................................... 5 Choosing the Appropriate Database................................................................................................................................. 5 Choosing the Appropriate configuration.......................................................................................................................... 7 Sizing the System Reporter server correctly.................................................................................................................. 9 System Reporter Maintenance............................................................................................................................................. 12 Checking sample status.................................................................................................................................................... 12 General System Reporter issues......................................................................................................................................... 14 Installation........................................................................................................................................................................... 14 AO configurations............................................................................................................................................................... 14 CPG name change with AO ............................................................................................................................................... 15 Other known issues........................................................................................................................................................... 15 Database Maintenance.......................................................................................................................................................... 15 Break large data files into smaller files.......................................................................................................................... 15 MSSQL Database initial setup best practices................................................................................................................ 16 MySQL Database initial setup best practices................................................................................................................ 16

Click here to verify the latest version of this document.

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Abstract HP 3PAR StoreServ Storage System is a highly virtualized, tightly clustered, and dynamically tiered Storage System built for utility computing. The HP 3PAR StoreServ greatly simplifies provisioning and management of storage in a consolidated environment. The Storage System also provides a high performance, scalable, virtualized environment in which separate departments or customers running differing workloads on multiple heterogeneous servers can effectively share the physical resources to attain greater levels of performance, efficiency and flexibility. System Reporter is optional software that samples the space and performance data, storing it in a database and providing historical capacity and performance reporting for collection of HP 3PAR StoreServ Storage Systems. These reports can be used for several purposes including: • Performance Analysis. Storage administrators must occasionally diagnose performance-related issues for the storage volumes for a particular application at some previous point in time. Using System Reporter, the storage administrator can provide detailed performance reports for the relevant time period and drill down to the various components to help analyze the performance issue. • Capacity Planning. Long term space and performance usage trends can be observed in historical charts to plan for growth and justify upgrades. • Active Monitoring. Email alerts can be configured so that administrators can actively monitor quality of service. • Scheduled reports. Storage administrators can schedule regular reports to monitor the growth and health of the monitored Storage Systems. This document describe some of the considerations Storage administrators should consider when planning to implement a Standalone System Reporter instance as well as some of the maintenance steps that should be implemented to ensure the System Reporter keeps on running and collecting data over time. This includes: • Selecting the appropriate Database • Selecting the appropriate server configuration for System Reporter • Sizing the storage requirements for the Database • Table maintenance

2

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

External System Reporter vs System Reporter on-node Before HP 3PAR OS version 3.1.2 the external System Reporter was the only option users had to collect and report historical performance data from one or more HP 3PAR StoreServ systems. The external System Reporter is installed on a standalone server and configured to collect and store performance data for all the storage servers in the environment in a local database. The external System Reporter was also used to manage the Adoptive Optimization (AO) functions for all storage servers monitored. With the introduction of HP 3PAR OS version 3.1.2 an instance of the System Reporter software is by default installed on the HP 3PAR StoreServ system, and will automatically collect performance data from the local system. The collected information is available through the Command Line Interface (CLI) using the “srstat*” commands. The on-node System Reporter is intended to manage Adoptive Optimization for the local system and configuring AO is made available in the Management Console (MC) interface. Later versions of the Management Console will include ability to view collected data and graphs for the system. The on-node System Reporter use a rolling database files system method and is limited in the amount of performance data that will be kept. Short term history information will be available from the on-node System Reporter using the CLI or eventually the MC. Note For any HP 3PAR StoreServ that is running OS version 3.1.1 or earlier the external System Reporter must be used for Adoptive Optimization management. The external System Reporter will not allow any AO operations for systems running OS version 3.1.2 and above, for those systems the on-node System Reporter have to be used for AO functions.

Note For customers that require longer data retention, performance alerting, scheduling of reports, and cross system reporting it is recommended to also have an instance of the external System Reporter installed and collecting performance data from all the systems in the environment. The external System Reporter can operate in parallel with the on-node System Reporter instance, although there is no existing method for transferring any collected data from the on-node System Reporter instance to the external System Reporter.

Note This document mainly addresses the options for the external System Reporter instance.

3

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

System Reporter Excel Interface The external System Reporter also supports web queries that will allow access to System Reporter data from within Microsoft® Excel software. To use the Microsoft Excel interface, download the “3PAR System Reporter.xls” file using the link on the top of the home page of the System Reporter interface. Figure 1. Download the Microsoft Excel client file from System Reporter

When opening the file in Microsoft Excel note the warning to enable Macros and ActiveX controls in order to be able to execute the web queries to System Reporter. Figure 2. Enable Macros and ActiveX in order to use web queries

Once that is enabled you can using the “Initialize” button to connect to the System Reporter server and from there you can create any of the System Reporter queries. The reports will be generated in a separate page, and at the bottom of each report will be the data used for the report. The Microsoft Excel client is an alternative way to execute and generate reports, but does not include the quick reports already defined in the System Reporter web interface.

4

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

System Reporter Configurations Choosing the Appropriate Database Although the System Reporter software comes standard with a SQLite database that enable the software to be used out of the box, the SQLite database might not be appropriate for large or multiple system use. It is important to give some thought about what database should be used, depending on the number of HP 3PAR StoreServ Storage systems to be monitored as well as the amount of data to be collected and kept in the system. Note For support of a single small HP 3PAR StoreServ and the fact that AO is handled by the on-node System Reporter instance the external System Reporter with out of the box a SQLite database can be an ideal solution for long term historic reports, scheduled reports and alarms. When cross system reporting is required it would be better to invest in one of the other more robust databases.

The options for databases are the following: SQLite SQLite is an embedded database that is included with System Reporter. It does not run as a separate application but rather as a module within the sampling tool and web server. Since it requires no installation or configuration, it is very simple to use but it has several limitations that make it only suitable for small database sizes and limited concurrency. SQLite supports only limited database concurrency because it relies on a single file lock for the entire database. The sampling process needs exclusive access to the database when inserting new samples. If the database is very large or if there are a large number of concurrent web requests, the sampler or the Web server can time out. Furthermore, database compaction cannot be done in parallel with sample insertion so there could be a large gap in samples during database compaction. Sampling of multiple HP 3PAR StoreServ Storage systems is not supported with a SQLite database, either the Microsoft SQL Server, MySQL or the Oracle database servers should be used instead. For large databases (over about 1 GB) or a large number of concurrent Web users, either the MySQL®, Microsoft SQL, or the Oracle database servers should be used instead. Note For PRE 3.1.2, the optionally licensed Adaptive Optimization feature is not supported with the SQLite database. Please consider another database if you plan on utilizing the storage optimization capabilities provided by Adaptive Optimization.

5

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

MySQL A MySQL database server can be used with System Reporter but is not included with it. You must purchase it separately. MySQL is a good choice for System Reporter because it supports MyISAM tables. These tables do not support transactions (which are not required for System Reporter) and are consequently somewhat higher performance than Oracle for sample insertion and deletion. Best practice: MySQL is the best choice for a database for its support of MyISAM tables and therefore have better performance than other databases. Microsoft SQL System Reporter supports Microsoft SQL version 2008 R2 database server but it is not included and must be purchased separately. The Microsoft SQL server is not supported on Linux and does not support data generated by System Reporter when installed on a Linux platform. Oracle System Reporter supports an Oracle 11g database server but it is not included with it. You must purchase it separately. Compared with MySQL, Oracle is slightly slower and more resource intensive for sample insertion and deletion. However, Oracle is also a good choice for large and active System Reporter installation. Note System Reporter does not currently support Oracle RAC implementations.

Note System Reporter requires the 32-bit Oracle client and does not support the 64-bit version.

Note If you choose Oracle as the database, you cannot install System Reporter on a 64-bit Linux system since it requires a 32-bit Oracle client which is not supported on 64-bit Linux. This limitation does not apply to the 64-bit Windows version since the 32-bit Windows version of Oracle Client works on 64-bit Windows platforms.

Table 1 provides a comparison of features for the various database choices.

6

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Table 1. Database Comparison Comment

SQLite

Microsoft SQL

MySQL

Oracle

Included with System Reporter

Yes

No

No

No

Operating system supported

Windows or Linux

Windows

Windows or Linux

Windows or Linux(32 bit only)

Sample more than one HP 3PAR StoreServ

No

Yes

Yes

Yes

Support Adaptive Optimization (AO)

No

Yes

Yes

Yes

Can have remote database server

No

Yes

Yes

Yes

Scale to large database size?

No, recommend less than 1GB

Yes

Yes

Yes

Scale to a large number of concurrent users

No

Yes

Yes

Yes

Performance for sample insertion and deletion?

Adequate for small databases

Good

High

Good

Choosing the Appropriate configuration System Reporter is designed to run on a separate server and can collect data from one or several HP 3PAR StoreServ Storage systems. The server designated to run System Reporter can be a physical server or a virtual server as long as it is sized sufficiently for the intended load. The administrator also has the option to run the database on a remote server or on the same server than the System Reporter software. The administrator can choose between running System Reporter on a Windows based server or on a Linux server. System Reporter can be installed on Red hat Enterprise Linux 5.6 32- or 64-bit OS, but when used with Oracle only 32-bit OS is supported. System Reporter requires a 32 bit library to connect to the database, and Oracle only has a library for the 32-bit OS. The database can be on a separate server running on 64 bit platform.

7

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Figure 3. System Reporter configurations

System Reporter SQLite DB No AO support

Single Array

System Reporter MSSQL, MySQL, Oracle Support AO

Multiple Arrays

System Reporter

Database Server

OS

OS

Virtual Servers or Physical System Reporter Remote database server MSSQL, MySQL, Oracle Support AO

Multiple Arrays With Remote Database Servers

Figure 3 above show 3 different possible configurations for a System Reporter environment. On the left we have a single array with the default out-of-the-box System Reporter installation using the SQLite database. This database is only recommended for a single 3PAR StoreServ and does not support AO operations. Note With FW version 3.1.2 and the on-node System Reporter functions the AO operations can be controlled using the on-node System Reporter and the historical information collection can be done by the System Reporter with SQLite database.

In the middle picture we have a System Reporter with a MSSQL, MySQL, or Oracle Database. This installation monitors multiple storage systems and can also perform the AO operations for these storage systems that are still on the older FW versions. For all storage systems with FW version 3.1.2 or higher the AO operation will be performed by the on-node System Reporter. When monitoring multiple storage systems the default SQLite database is not recommended. On the right side of the picture we have an installation using Virtual Server hosts with a separate server for the database and the System Reporter tools. This is recommended for larger installations that demand high performance and quick response from the System Reporter. Using an existing database with sufficient storage space can eliminate additional license fees for high end databases. Note The diagram on the right of figure 3 is also the recommended configuration when using System Reporter with Linux operating system and a 64bit database. System Reporter software can be installed on Red Hat Enterprise Linux 5.6 (32bit only if using Oracle), 32- or 64-bit otherwise.

8

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Sizing the System Reporter server correctly There are a number of parameters that affect the size of the System Reporter database as well as the performance of the report generation. It is very important to know and plan for the correct amount of storage space required for the system reported database, and to size the server with enough memory and CPU to provide the required performance. A sizing tool is provided with the System Reporter software to assist in determining the required size. The sizing tool does have a number of parameters settings and it is important to understand how each of these setting affects the size and performance of the database. The following are important settings to manage in the sizing tool: Database type The database type determines what functionalities will be available in System Reporter. When selecting the SQLite database, the application will be restricted to only one storage array to be monitored. Depending on how the database stored the data internally will depend on the actual storage space required for the larger tables listed in the sizing tool. Sampling Parameters Table 2 describe several of the collection settings that will affect the size and also performance of the System Reporter setting. Table 2. Collection settings for System Reporter Parameter

Description

Default

Hi-resolution interval (minutes):

The minutes between taking a Hi resolution (very detailed) performance measurement. The shorter the interval the more information will be collected. For larger systems it’s recommended to have a larger interval time to accommodate for collection time.

5

Hi-resolution perf-space sampling ratio

Ratio of Hi-Resolution performance samples to Hi-Resolution space samples. For each x Hi-Res performance collection 1 Hi Res space collection will be performed. Example: with Hi Res interval = 5 and Ratio = 6, a Hi-res space sample will be taken every 30 minutes

6

Retain hi-res samples for hours

Default number of hours to keep hi-resolution samples

24

Retain hourly samples for days

Default number of days to keep hourly samples

7

Retain daily samples for days

Default number of days to keep daily samples

366

Retain Adaptive Optimization samples for days

Default number of days to keep Adaptive Optimization hourly samples

7

Perform Compression of the database (Only for versions 2.9 and earlier)

Frequency of performing the database compression operation.

Daily

On SQLite systems sampling will be stopped during database compression and can take several minutes where the system would be unavailable.

All settings are by default enforced for all systems unless specified otherwise on an individual storage system basis.

9

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Storage system size Besides the collection parameters it is also important to keep in mind the size of the storage system and the number of objects that will be tracked in the System Reporter database. The Sizing tool allow for the user to specify the number of objects in each Storage System that will be monitored. For new systems it might not be possible to specify exact number for these settings, and it is recommended rather over estimate the number of objects than to underestimate them. Table 3 gives an overview of the Storage System objects that contribute the most to the database space. Table 3. Storage System object settings Parameter

Description

Example value

# of Physical Devices (PDs)

The number of Physical Devices in the system. This will add to the Physical device stats

Small - 16 Medium - 480 Large - 960

# of Logical Devices (LDs)

Number of Logical Devices in the system for Logical Device stats

Small - 512 Medium - 1024 Large - 2048

# of Virtual Volumes (VVs)

Number of Virtual Volumes in the system

Small - 512 Medium - 1024 Large - 2048

# of Virtual Luns (VLUNs)

Number of presentation to hosts for Virtual Volumes

Small - 2048 Medium - 4096 Large - 8192

# of ports

Total number of ports in the system for the ports performance stats

Small - 12 Medium - 170 Large - 340

Logical disk space in TiB

Logical disk pace to be managed

Small - 7 Medium - 170 Large - 340

Enable LD performance stats

Set to 1 if you want to collect performance stats for Logical Devices. Set to 0 if not

0 or 1

Enable Adaptive Optimization stats

Set to 1 if AO information will be collected for this system. Set to 0 for no AO information. If set to 1 then user cannot select SQLite database.

0 or 1

Note The values in the “Example value” column are just examples of what a small/medium/large system might look like. Each storage system will be different and depending on your specific use and configuration you should adjust these values.

10

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Example configurations Table 4 shows some sample configurations obtained from the System Reporter Sizing tool for a small, medium and large as well as a combination of all 3 systems. Configuration A and B have the same Storage System parameters, but Sampling retention was doubled from the default. The Sizing is for a System Reporter with MySQL database. Table 4. Example sizing results for System Reporter database and server A Small

B Small

C Medium

D Large

B+C+D Multiple

Hi Res interval (minutes):

5

5

5

5

Hi-res perf-space sampling ratio:

6

6

6

6

Retain hi-res samples for hours:

24

48

48

48

Retain hourly samples for days:

7

14

14

14

Retain daily samples for days:

366

366

366

366

Retain AO data for

n/a

7

7

7

# of Physical Devices (PDs):

16

16

480

960

# of Logical Devices (LDs):

512

512

1024

2048

# of Virtual Volumes (VVs):

512

512

1024

2048

# of Virtual Luns (VLUNs):

2048

2048

4096

8192

# of ports

12

12

24

96

Logical disk space in TiB:

7

7

170

340

Enable LD perf stats:

1

1

1

1

Enable Adaptive Opt stats:

0

1

1

1

DB GB inserted (deleted)/day:

0.85

1.2

10.25

20.51

31.96

DB Total table space (GB):

2.5

6.3

67.1

134.2

207.6

Total System Reporter Server Memory(GiB):

2.11

2.27

6.21

10.40

14.88

Total CPU Cores:

2

2

2

4

5

Sampling Parameters:

Storage system size:

Results:

11

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Note If using FW 3.1.2 or higher with on-node System Reporter for AO then the standalone System Reporter does not have to have AO stats active. With AO turned off for scenario B+C+D the GB inserted/deleted per day = 6.54GB and the total database table space = 29.7GB.

Note For any database over 100MB the administrator might want to consider splitting tables into multiple files.

Best practice: Always over size the Database to accommodate and server to accommodate for future growth and setting changes. Best practice: Sampling parameters can be set for individual arrays or for all systems. Consider setting specific sampling parameters for a single storage system rather than for all systems, and always check the effect of specific settings with the sizing tool to ensure sufficient space and performance for database and server. Best practice: If the System Reporter server and database are running on the same host, double the values found by the sizing tool. Running System Reporter in virtual machines is acceptable as long as the VMs are sized correctly. Best practice: Rather than increasing the default retention times for High resolution and Hourly data schedule automatic reports to be created every day. This will allow the data to be viewed for a long time without requiring a lot of CPU, memory and disk resources.

System Reporter Maintenance Besides selecting the correct database and sizing the space and performance required for the database, the administrator must also periodically check that System Reporter is still collecting data and not running into any issues.

Checking sample status Checking the sample status on a regular interval will alert the administrator to any potential issues. From the main System Reporter page select the Sampling Status menu. Figure 4. System Reporter main page

The Sample status page will show the last time a sample was successfully collected from each storage system. If this status is more than the sample interval set for the system (5 minutes by default) then the administrator should start to look at the System Reporter log files to see why a sample was not collected for a specific system.

12

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

Figure 5. Collection status report

If the collection status is more than the collection interval (default 5 minutes) then there is possibly an error with the collection processes. Look in the “C:\Program Files (x86)\3PAR\System Reporter\log” directory on the System Reporter server for the “sampleloop.log” file. This is the main processes controlling the collection or sampling processes. This file will have entries for each Storage System configured and will report any connection errors for a Storage System. Note Each time the System Reporter is restarted a new log file will be created and the older log files will be renamed with a “.x” where x is number 1 to 5. Sometimes the errors will be in the older log files.

For errors collecting data from a specific Storage System look at the “inservsample_10.195.*.*.log’ file, where the IP address is that of the Storage System collection is performed on. Monitor the “TrimDB.log” for any errors for the trim processes responsible to delete old data from the database. The “sysrdtsched.log” and “schedrptlog_cleanup_thread” will log any errors in the report scheduler processes. Sometimes old reports can cause some errors and this will be reported in these logs.

13

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

General System Reporter issues Installation Follow the installation manual closely and perform all the recommended steps in the correct order. Basic install is to install the HP 3PAR CLI software first, then the HTTP server. The next step is to install the database you selected to use. If using the SQLite database that will be installed with the main System Reporter install. After installing the database create the users for the System Reporter account and allocate the correct database space to these users. The actual database schemas will be created during the main System Reporter install. Install any ODBS connections to the database and only then run the main System Reporter install. Monitor the install.log file for any installations issues from the main install program. Remember to check for the latest updates to System Reporter. Besides some bug fixes the updates might include new sample reports that can be very useful. Best practice: Do not use a Super user (such as ‘3paradm’) for the System Reporter user. Use a Browse user if Adaptive Optimization is not required or a 3PAR_AO user if Adaptive Optimization is required. Best practice: Secure access to the System Reporter web server. The easiest way of securing a System Reporter server is to enable the local firewall and prevent remote access to the HTTP port 80. This will ensure than only users that can connect locally to the System Reporter server will be able to access the System Reporter web server it is also possible to configure Apache to require password authentication. See the following link for a quick tutorial on how to do so: sniptools.com/vault/windows-apache-and-htaccessauthentication. Best practice: Schedule high resolution reports every day for VLUN, PD, CPU and port performance. This will make detailed performance analysis possible long after the high resolution data has been purged by System Reporter. For every 3PAR StoreServ system managed by System Reporter, schedule high resolution scheduled reports (through the Policy Settings page), to be executed every day at the same time and kept (Retention) for the length of the support period of the system. These scheduled reports should cover: VLUNs, Ports (Hosts, Disks and Remote Copy), PDs (individual reports for SSD, FC and NL), CPU, CMP, as well as Adaptive Optimization (Region density, space moved and VV tiers).

AO configurations AO operations are not supported with the default SQLite database and the user will not be able to enable AO collection when using SQLite. Make sure the “Skip LD collection” box is un-clicked. System Reporter has to collect LD information in order to do AO operations. Best practice: With FW version 3.1.2 or higher use the on-node System Reporter for all AO operations.

14

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

CPG name change with AO When a customer change the names of CPG used in AO configurations, the administrator would have to go and modify the AO configurations in System Reporter to reflect the new names, or create new AO schedules. It can take up to 30 minutes for new CPG names to be reflected in the System Reporter.

Other known issues a. SSL option to register the HP 3PAR StoreServ in System Reporter will not succeed if customer has Inform OS 3.1 MU1. ––FIX: Upgrade the command line interface on the System Reporter server to version 3.1.1 (MU2) b. Trimdb row lock errors on MSSQL Setups only. ––FIX: Dedicated Database server with memory at 32 GB will fix this issue for up to 3 Inservs. c. Slow response from MySQL and Sampling timeouts ––FIX: Run myisamchk with following parameters. myisamchk --key_buffer_size=512M --sort_buffer_size=512M --read_buffer_size=8M --write_buffer_size=8M –r *.MYI d. Scheduled reports fail or report errors. ––FIX: Upgrade to System Reporter 2.9 MU1-P02.

Database Maintenance The administrator will have to monitor the database and database usage, and from time to time some database maintenance would be required to keep the System Reporter process running and to ensure the fastest response time for creating reports.

Break large data files into smaller files When collecting data from very large StoreServ systems or from more than 3 HP 3PAR StoreServ systems using MSSQL the size of the database files can easy grow larger than 100GB and at this point dramatically affect the performance of data inserts as well as running reports. Current recommendation is to break data files into multiple files when size of data file reaches 100GB There is an MSSQL script available to assist with splitting the database tables for System Reporter. The script can be used as a basis for starting the processes of splitting the table, but the actual script is not supported by HP support. Ask your HP representative for detail on the script.

15

Technical white paper | HP 3PAR StoreServ System Reporter Best Practices

MSSQL Database initial setup best practices a. If the Inform OS is 3.1.1 or lower and AO is required then it is recommended to have a dedicated database server with sufficient memory and space to handle hi resolution sampling. b. Size the Server according to the System Reporter sizing spread sheet. Recommendation is to have at least 40 % more memory than the memory suggested by sizing sheet as MSSQL can use only 60 % of the memory for row locks. c. Separate the tables and indexes on two separate file groups. Each file group with 30 files each with 1 GB size, growth rate of 10%. d. Configure the following Database settings. i. Index creation memory set at 0. (Server/Instance level setting) ii. Maximum server memory set at maximum value possible iii. Boost SQL Server Priority Check this setting. ( Server/Instance level setting) iv. Cost Threshold for parallelism set at 30. ( Advanced tab on MSSQL Server/Instance properties) v. Value of locks set at 0. (Advanced tab on MSSQL Server/Instance properties.) vi. Database properties--> options set Recovery model to “Simple” I developed and tested SQL Script that we can use to split the tables and indexes to two separate file groups as specified in step “c” above. Can we have this script approved by Engineering to use at customer sites?

MySQL Database initial setup best practices a. Add the following parameter in the my.ini file under server section max_allowed_packet=128M. (The file is located at C:\ProgramData\MySQL\MySQL Server 5.5 for Mysql 5.5) b. Run the following command to fine tune the MySQL parameters once the System Reporter is installed. ––Stop the sampling and kill all the System Reporter related child process. ––Run “myisamchk” with following parameters. “myisamchk --key_buffer_size=512M --sort_buffer_size=512M --read_ buffer_size=8M --write_buffer_size=8M –r *.MYI”

Learn more at hp.com/go/storage hp.com/go/StoreServ

Sign up for updates hp.com/go/getupdated

Share with colleagues

Rate this document

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft is a U.S. registered trademark of Microsoft Corporation. Oracle is a registered trademark of Oracle and/or its affiliates. 4AA4-6829ENW, May 2013