Veritas CommandCentral Storage Release Notes

Transcription

1 Veritas CommandCentral Storage Release Notes for Microsoft Windows and UNIX 5.0 MP1

2 CommandCentral Storage Release Notes The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 5.0 MP1.1 Legal Notice Copyright 2008 Symantec Corporation. All rights reserved. Symantec, the Symantec logo, Veritas, CommandCentral, NetBackup, SANPoint, SANPoint Control, and Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying documentation. AIX is a registered trademark of IBM Corporation. HP-UX is a registered trademark of Hewlett-Packard Development Company, L.P. Linux is a registered trademark of Linus Torvalds. Solaris is a trademark of Sun Microsystems, Inc. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software - Restricted Rights" and DFARS , "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

3 Symantec Corporation Stevens Creek Blvd. Cupertino, CA

4 Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product feature and function, installation, and configuration. The Technical Support group also authors content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec s maintenance offerings include the following: A range of support options that give you the flexibility to select the right amount of service for any size organization A telephone and web-based support that provides rapid response and up-to-the-minute information Upgrade insurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week worldwide. Support is provided in a variety of languages for those customers that are enrolled in the Platinum Support program Advanced features, including Technical Account Management For information about Symantec s Maintenance Programs, you can visit our Web site at the following URL: Contacting Technical Support Select your country or language under Global Support. The specific features that are available may vary based on the level of maintenance that was purchased and the specific product that you are using. Customers with a current maintenance agreement may access Technical Support information at the following URL: Select your region or language under Global Support. Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to recreate the problem.

5 When you contact Technical Support, please have the following information available: Product release level Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Licensing and registration Customer service Router, gateway, and IP address information Problem description: Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: Select your region or language under Global Support, and then select the Licensing and Registration page. Customer service information is available at the following URL: Select your country or language under Global Support. Customer Service is available to assist with the following types of issues: Questions regarding product licensing or serialization Product registration updates such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade insurance and maintenance contracts Information about the Symantec Value License Program

6 Advice about Symantec's technical support options Nontechnical presales questions Maintenance agreement resources Additional Enterprise services Issues that are related to CD-ROMs or manuals If you want to contact Symantec regarding an existing maintenance agreement, please contact the maintenance agreement administration team for your region as follows: Asia-Pacific and Japan: Europe, Middle-East, and Africa: North America and Latin America: Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following: Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur. Managed Security Services Consulting Services Educational Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats. Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring and management capabilities, each focused on establishing and maintaining the integrity and availability of your IT resources. Educational Services provide a full array of technical training, security education, security certification, and awareness communication programs.

7 To access more information about Enterprise services, please visit our Web site at the following URL: Select your country or language from the site index.

8

9 Contents Technical Support... 4 Chapter 1 Overview of this release Introduction to Veritas CommandCentral Storage CommandCentral Storage installation options What s new in CommandCentral Storage Management and discovery Monitoring Reporting Other enhancements Chapter 2 System requirements Preinstallation configuration requirements Operating system requirements Solaris updates required Windows updates required HP-UX updates required AIX updates required Red Hat Linux updates required System resource requirements Solaris system requirements Windows system requirements HP-UX system requirements AIX system requirements Red Hat Linux system requirements CommandCentral Storage web browser requirements Co-existence of CommandCentral Storage components with other Symantec products Chapter 3 No longer supported Hardware changes OS and managed host (Agent) changes Install and supported configuration changes Console changes... 45

10 10 Contents Reporting changes Chapter 4 Software limitations Install, uninstall, and upgrade limitations NAT firewalls not supported Installation limitation for licensing options Discovery and management limitations bit MS-SQL application not discovered when co-resident with the 32-bit version Reports show incorrect capacity for NetApp LUNs with space reservation turned off Volume layout not discovered for LDM-managed volumes Capacity not discovered for LDM-managed volumes without file systems Restoring Brocade switch configuration may fail when reboot required Unable to remove disk groups via HP EVA SSSU version 4.0 and Detect Devices command applies only to objects that use device managers Console and report limitations Reports ToolTips are truncated in Firefox x Agent limitations Volumes and disk groups duplicated Incorrect data displayed for Oracle RAC applications Data displayed for unsupported applications VCS scripts must be installed on managed hosts Discovered objects deleted from the database after 24 hours Data not displayed in some performance reports Some Veritas NetBackup objects not displayed Directory Usage, Directory Aging, and Stale Directories reports not available for 4.x Agent hosts Data Module collection of all files not supported for 4.x Agent hosts Data Module Importer does not support secure (https) connection to 4.x Agent hosts Chapter 5 Known issues Install, uninstall, and upgrade issues Error message about VRTSweb during upgrade on Windows (542244)... 55

11 Contents 11 Cannot connect to Veritas Enterprise Administrator Console after installing managed host on Linux (865052) addresses for configured users not upgraded if 4.x hotfix not applied ( ) Shared components restarted during CommandCentral Storage install ( ) Install or upgrade of managed hosts using push install hangs on Solaris in a VCS environment ( ) CIMVAILExplorer does not run after upgrade from 5.0DCAP to 5.0 MP1 on Solaris ( ) Default agent password cannot be changed using CommandCentral Storage product installer on UNIX (859670) Erroneous messages during CommandCentral Storage managed host installation on AIX cluster nodes with Storage Foundation Cluster File System ( ) Upgrade on Windows does not restart Alarm Service ( ) Incorrect SAN Access Layer data export failure message while upgrading Management Server from 4.x to 5.0 MP1 on Solaris (962734) Upgrade to CommandCentral Storage 5.0 MP1 on Windows does not allow new Agent Push Install utility install ( ) Agent Push Install Utility cannot be uninstalled separately on Windows ( ) Patch fails to install during Management Server or managed host install/upgrade on Solaris ( ) Managed host fails to install when shell on remote UNIX managed host is configured as tcsh or csh ( ) Summary file not created during managed host installation on UNIX ( ) Erroneous reference to response file at end of Management Server install on Solaris ( ) CommandCentral Storage installations fail on UNIX hosts with auto-mounted volumes ( ) CommandCentral Storage installations on Windows fail while configuring SICL ( ) Server and database issues Management tasks not terminated when Server can no longer contact managed host (604446) JavaScript error when viewing charts in reports (623475)... 65

12 12 Contents PBX startup and kill script issue on Solaris and HP-UX (574983) Operations fail with authentication error on Windows bit managed host ( ) Shared components stop-start order (856750) DB server fails to stop after issuing commands ( ) Console and report issues LUN capacity displayed as "Assigned to VM" for Sun VM disk slice (637435) ed report does not reflect column sorting (615330) Incorrect name displayed for file systems on unmounted or unnamed volumes (864757) Change History Detail shows object keys for deleted objects (630154) Extended attributes irregularity in Change History Detail (862576) No validity checking for dates in Filter Table dialog (423406) Dialogs overwritten when new dialogs are opened (606871) Mismatch between time on Server and time displayed in scheduling dialogs (851525) Testing lengthy SQL query for custom table appears to fail ( ) Host volume sets displayed in Volume Sets and Volumes tables ( ) Port Bundle Builder Tool displays only one fabric (629557) Numeric precision adjustment required before creating virtual disks on IBM DS8000 storage arrays ( ) Unhandled exception error in CLARiiON array adapter overview ( ) No online help for user-created reports ( ) After upgrade, duplicate objects for NetApp unified storage systems display in the Console ( ) Viewing Explorer Status on user-created hosts creates an error ( ) Device and device configuration issues Device configuration name does not change after modification (853400) Console does not validate application explorer configuration entry (854436) Do not use an existing IP address for array configuration (582094) Stale device configuration names present in the Configured Devices Summary window (832583)... 75

13 Contents 13 Visualization issues Incorrect LUN capacity estimates when CX Meta LUNs created from mixed RAID groups ( ) Attributes and group memberships not migrated for Hitachi RAID groups (859638) Incomplete information displayed for newly discovered objects (539046) McDATA SMI-S explorer does not refresh zoning changes made on the EFCM ( ) Monitoring issues Monitoring data not displayed for SnapMirror destination (621024) Monitoring status not available for ESX server ( ) Monitoring of McDATA switch is not automatically enabled after the switch is added to CommandCentral Storage ( ) Discovery and management issues Disk state not discovered (859207) Incomplete discovery when two versions of DB2 are on the same host (605860) HP EVA: Disabling discovery of Management Appliance does not disable discovery of arrays (614523) HP EVA: Inactive arrays are selectable in management dialogs (615368) Manually configured database instances not coming up automatically after upgrade (900677) ESX Server no longer discovered after modifying shared storage pool ( ) Discovery failure of NFS-based storage pools ( ) Discovery failure for storage arrays configured as SMI-S managed arrays ( ) CommandCentral Storage 5.0 or 5.0 RP1 managed hosts on VMware ESX servers must be upgraded to 5.0 MP1 ( ) Chapter 6 Getting help Using the product documentation Commenting on product documentation Displaying online help Contacting Symantec Using the support web site Subscribing to notification service... 83

14 14 Contents Accessing telephone support Obtaining support by Obtaining license information Purchasing products... 84

15 Chapter 1 Overview of this release This chapter includes the following topics: Introduction to Veritas CommandCentral Storage CommandCentral Storage installation options What s new in CommandCentral Storage Introduction to Veritas CommandCentral Storage Veritas CommandCentral Storage by Symantec represents an entire storage resource management (SRM) solution, giving you what you need to manage your storage infrastructure more effectively. It gives you the following capabilities: Offers a single console from which data center administrators deploy, manage, and expand a multi-vendor networked storage environment. The CommandCentral Storage Console seamlessly integrates performance and policy management, storage provisioning, and zoning capabilities to ensure that the storage infrastructure runs as efficiently as possible. The Console enables users to set policies that automate notification, recovery, and other user-definable actions. Discovers and tracks the utilization and allocation of storage resources down to the disk level. The reporting features in CommandCentral Storage provide a complete and detailed view into precisely how and where storage for office documents, files, applications, , and databases is used in your enterprise. Shows usage trends and makes forward projections. You can gather data both locally and remotely (through a managed host). This means you can get baseline information without huge deployment costs. Armed with this data, you can do predictive modeling to analyze the return on your storage investment. You also have what you need to implement a program of departmental chargeback.

16 16 Overview of this release CommandCentral Storage installation options Using CommandCentral Storage together with other Symantec software, IT managers have the tools they need to perform real, active, end-to-end storage resource management and make strategic decisions about their future storage needs. CommandCentral Storage installation options You can install CommandCentral Storage in the following ways: Standard (both Data Module and Operations Module): All product features. Operations Module only: Users can view detailed discovery data for storage objects, switches, fabrics, applications, and databases; provision storage; and create and manage policies. Data Module only: Users can view objects, display storage and consumption reports, and track specialized data such as storage consumption by application, by file system, and on a per-file and per-user basis. With each installation option, you can establish user credentials such that authorized users can access the product to perform sensitive management tasks and other users can perform only a more basic set of functions. Table 1-1 summarizes the features you get with each of the CommandCentral Storage installation options: Table 1-1 CommandCentral Storage Data Module (DM) and Operations Module (OM) features Feature Discover and visualize disk arrays; discover and create storage enclosures Discover and visualize NetApp devices as unified storage devices Discover and visualize NetApp replication features Discover and display database instances: Oracle, Sybase, DB2, and SQL Server Discover and display applications: Veritas NetBackup, Veritas Cluster Server, Exchange Server DM OM

17 Overview of this release CommandCentral Storage installation options 17 Table 1-1 CommandCentral Storage Data Module (DM) and Operations Module (OM) features (continued) Feature Discover and display physical disks and disk characteristics associated with specific LUNs Discover hosts and file systems associated with a given application Discover and visualize storage network elements such as switches and fabrics Display usage projections for hosts, databases, and NetApp storage devices Provide application health views, utilization details, and notifications for storage resources associated with specific hosts and applications Display largest files, file types breakdown, directories size, number of files, owner, and file aging Perform centralized policy management Monitor network activity using collectors Provision storage by binding LUNs to hosts and applications Change impact analysis: identify how changes will affect resource availability for a given application Construct LUNs from physical disks Select multiple LUNs and perform masking and binding on them Organize storage resources by defining groups Create and manage zones to enhance network security DM OM

18 18 Overview of this release What s new in CommandCentral Storage Table 1-1 CommandCentral Storage Data Module (DM) and Operations Module (OM) features (continued) Feature Create object dependency groups with associated resources; display rolled-up status of an application based on status of dependent storage components Make paths available to Veritas Volume Manager hosts for Dynamic Multipathing Display reports showing storage capacity Display reports showing storage consumption Display reports showing alerts Display reports showing port usage and performance for switch ports, hosts, and arrays Save reports to file; reports to designated users Push install managed host code to remote hosts, either individually or in batch DM OM What s new in CommandCentral Storage Management and discovery Veritas CommandCentral Storage 5.0 MP1 contains and builds upon CommandCentral Storage 5.0 functionality, providing several new features. CommandCentral Storage 5.0 MP1 introduces the following management and discovery features. VMware support CommandCentral Storage now provides expanded support for VMware. Combining VMware with CommandCentral Storage, you can reclaim unclaimed storage across

19 Overview of this release What s new in CommandCentral Storage 19 your ESX server, storage pools, virtual hosts, and virtual machines. You can analyze infrastructure dependencies for applications that span these layers, and increase your storage environment's efficiency and capacity planning. NEC support CommandCentral Storage now supports discovery and environmental monitoring of NEC storage arrays (NEC Storage family and istorage family arrays). Additional device support CommandCentral Storage 5.0 MP1 now discovers and manages the following arrays: HDS USP-V HP XP For the latest support information, see the CommandCentral Storage Hardware and Software Compatibility List. This document is updated regularly at: Remote EMC Symmetrix/DMX Discovery CommandCentral Storage 5.0 MP1 now discovers EMC Symmetrix and DMX arrays without in-band connectivity. Monitoring CommandCentral Storage 5.0 MP1 introduces the following monitoring features. Improved self-monitoring CommandCentral Storage now includes enhanced self-monitoring in the Console. These new features monitor the CommandCentral Storage infrastructure on both the Management Server and the managed hosts. Environmental monitoring support In CommandCentral Storage 5.0 MP1 environmental monitoring via SMI-S has been added for the following arrays: 3PAR arrays Engenio arrays Fujitsu arrays

20 20 Overview of this release What s new in CommandCentral Storage IBM DS6000 and DS8000 arrays IBM Shark arrays IBM DS4000 arrays (previously called IBM FastT arrays) STK arrays CommandCentral Storage 5.0 MP1 also includes environmental monitoring for HDS USP-V and HP XP arrays. For the latest support information, see the CommandCentral Storage Hardware and Software Compatibility List. This document is updated regularly at: Performance monitoring support CommandCentral Storage 5.0 MP1 now includes performance monitoring via SMI-S for the following arrays: Engenio arrays IBM DS4000 arrays STK arrays CommandCentral Storage 5.0 MP1 also includes performance monitoring for HDS USP-V arrays. For the latest support information, see the CommandCentral Storage Hardware and Software Compatibility List. This document is updated regularly at: Reporting CommandCentral Storage 5.0 MP1 introduces the following reporting features. New VMware reports With the addition of enhanced VMware support in CommandCentral Storage 5.0 MP1, new Host Virtualization Summary and Detail reports, and the Virtualization Capacity Trending report have been added to increase your knowledge of storage utilization and server virtualization. Array scoping In CommandCentral Storage 5.0 MP1, you can scope Data Module reports by array. Array scoping allows you to understand use of expensive array storage based on

21 Overview of this release What s new in CommandCentral Storage 21 Other enhancements content residing on individual arrays. This feature increases the accessibility of file type and aging data for arrays. Discovered arrays now appear individually in the Data Module Rollup Configuration table. Enhanced DM reports CommandCentral Storage 5.0 MP1 includes modifications to the Data Module File and Directory Aging reports. File Aging and Directory Aging now include summary reports with pie charts to give you a quick graphical representation of this important data. CommandCentral Storage 5.0 MP1 introduces the following features. Addition of array and LUN objects to object dependency groups In CommandCentral Storage 5.0 MP1, you can view object dependency groups for array and LUN objects. Now you can quickly determine the applications, hosts, file systems, and other objects that are dependent upon a specific array. SSL support for SMI-S arrays CommandCentral Storage 5.0 MP1 adds Secure Socket Layering (SSL) support for SMI-S arrays. CIMVAIL providers will now be able to communicate with CIMOM using these ecrypted streams. McDATA v2.0 CIMOM support CommandCentral Storage 5.0 MP1 supports the McDATA v2.0 CIMOM, which provides greater stability and syncing capability for your zoneset information.

22 22 Overview of this release What s new in CommandCentral Storage

23 Chapter 2 System requirements This chapter includes the following topics: Preinstallation configuration requirements Operating system requirements System resource requirements CommandCentral Storage web browser requirements Co-existence of CommandCentral Storage components with other Symantec products Preinstallation configuration requirements The largest share of configuration occurs prior to installing CommandCentral Storage. This configuration typically comprises a number of activities performed in this order: Making sure that your storage network devices and their firmware levels are supported by CommandCentral Storage Verifying that the device is physically connected to the storage network in a supported manner Configuring the device to the vendor s specifications and making any additional modifications required by CommandCentral Storage For the latest support information, see the CommandCentral Storage Hardware and Software Compatibility List. This document is updated regularly at:

24 24 System requirements Operating system requirements Operating system requirements Table 2-1 provides operating system requirements for CommandCentral Storage hosts. Table 2-1 Component CommandCentral Storage Management Server CommandCentral Storage operating system requirements Operating systems supported Solaris 8, 9, 10 Windows Server bit (Xeon/Opteron): Datacenter Edition Enterprise Edition Windows Server bit: Standard Edition Web Edition Datacenter Edition Enterprise Edition Windows Server 2000 (Service Pack 3): Server Advanced Server Datacenter Server

25 System requirements Operating system requirements 25 Table 2-1 Component CommandCentral Storage managed host CommandCentral Storage operating system requirements (continued) Operating systems supported Solaris 8, 9, 10 with GSS package (SUNWgss) HP-UX 11i v1 (no array management support) 11i v2 AIX 5.2, 5.3 Red Hat Linux 3.0 and 4.0 (32-bit): Advanced Server Enterprise Server Note: The product cannot be installed on a Red Hat Security-Enhanced Linux (SELinux) system. Itanium processor not supported for Red Hat Linux. On a Red Hat Linux managed host, we recommend that you create the maximum allowable number of /dev/sgn device paths (255) using the following command: dev/makedev -v -m 255 sg. The host uses these device paths to gather information about LUNs. By changing the setting before you install CommandCentral Storage, you enable the host to gather information for more LUNs than the default number of paths (15). Windows Server bit (Xeon/Opteron): Datacenter Edition Enterprise Edition Windows Server bit: Datacenter Edition Enterprise Edition Standard Edition Web Edition Windows Server 2000 (Service Pack 3): Server Advanced Server Datacenter Server

26 26 System requirements Operating system requirements Table 2-1 Component CommandCentral Storage virtual managed hosts CommandCentral Storage operating system requirements (continued) Operating systems supported ESX virtualization server: ESX server ESX server Note: If the virtualization server uses QLogic's HBA, install the VMware version of Qlogic's HBA. The virtualization server also requires installation of VMware Tools. Virtual managed hosts are supported on the following guest operating systems: Red Hat Linux 3.0 and 4.0 Windows Server bit (Xeon/Opteron) Windows Server bit Windows Server 2000 (Service Pack 3) Note: The virtual machine does not require any FibreChannel HBA drivers. CommandCentral Storage Console Any platform with network access to the Management Server host and a supported web browser. The minimum recommended resolution for the Console is 1024 x 768. See CommandCentral Storage web browser requirements on page 40. Agent Push Install Utility Windows Server bit: Datacenter Edition Enterprise Edition Standard Edition Web Edition Windows Server 2000 (Service Pack 3): Server Advanced Server Datacenter Server Solaris updates required This section lists patches required to run CommandCentral Storage on Solaris.

27 System requirements Operating system requirements 27 In addition to the required patches listed here, you may want to install the latest full patch cluster for your version of Solaris. Patch clusters include additional recommended and security patches. Download Solaris patches and patch clusters from the following Web site: The GSS package (SUNWgss) is required on all CommandCentral Storage Management Servers running on Solaris. To list the patches currently installed on your Solaris system Use the showrev command: showrev -p To check whether a particular patch is installed, use the command as follows: showrev -p grep patch-id where patch-id is the patch number in the format xxxxxx-xx. When updating Solaris patches, you should apply the Libthread patch last. Solaris 8 Following are the required patches to run CommandCentral Storage on Solaris 8: Note: An asterisk (*) indicates that the patch is required for array management functionality * * * Solaris 9 Following are the required patches to run CommandCentral Storage on Solaris 9 required for array management:

28 28 System requirements Operating system requirements Increasing semaphore limits on Solaris The Veritas Provider Access Layer (VxPAL) and the Veritas Enterprise Administrator Service require more operating system semaphores than are usually set by default on Solaris. This can also be a problem on the other UNIXs; however, the Solaris default semaphore limit is small. To increase semaphore limits on Solaris 1 Open a UNIX console and log in as root on the target host. 2 Using a text editor, open: /etc/system 3 Locate a line similar to the following. If the line is not there, add it: set semsys:seminfo_semmni=0x10 Windows updates required 4 Make sure that the value is something larger than what is currently there. For example, set sminfo_semmni to 0x10. 5 Save the file and reboot the host. Download and apply Windows updates from the following Web site: Windows 2000 Table 2-2 Required Updates for Windows 2000 Component CommandCentral Storage Management Server CommandCentral Storage managed host Agent Push Install Utility Required Updates Windows 2000 Service Pack 3 Windows 2000 Service Pack 3 Windows 2000 Service Pack 3

29 System requirements Operating system requirements 29 HP-UX updates required This section lists the patches required to run CommandCentral Storage on different versions of HP-UX. Only the CommandCentral Storage managed host is supported on HP-UX. You can download HP-UX patches from the following Web site: admit= HP-UX 11i v1 Following are the required patches to run the CommandCentral Storage managed host on HP-UX 11.i v1: Note: An asterisk (*) indicates that the patch is required for array management functionality. PHSS_31326 PHSS_28509* PHSS_28880* PHSS_30968* HP-UX 11i v2 Following are the required patches to run the CommandCentral Storage managed host on HP-UX 11.i v2: PHSS_34859 PHSS_36336 PHSS_35055 PHSS_34853 PHSS_34444 PHSS_34445 PHSS_35528 PHSS_33903 PHSS_35978 PHSS_32231 AIX updates required Increase the stack size for the vxpal process by following the procedure for increasing the application stack size at the following Web site: This section lists the patches required to run CommandCentral Storage on different versions of AIX. Only the CommandCentral Storage managed host is supported on AIX.

30 30 System requirements Operating system requirements To list the patches currently installed on your AIX system Use the instfix command: instfix -ia To check whether a particular patch is installed, use the command as follows: instfix -ia grep patch-id where patch-id is the patch number in the format IYxxxxx. AIX 5.2 Following are the required patches to run the CommandCentral Storage managed host on AIX Version 5.2 with Maintenance Level 7 (ML7) or higher: xlc.rte xlc.aix50.rte AIX 5.3 Following are the required patches to run the CommandCentral Storage managed host on AIX Version 5.3 with Technology Level 3 (TL3), Technology Level 6 (TL6) or higher. CommandCentral Storage does not support the managed host on AIX 5.3 with Technology Level 4 (TL4) and Technology Level 5 (TL5). xlc.rte xlc.aix50.rte Red Hat Linux updates required This section lists the patches required to run CommandCentral Storage on different versions of Red Hat Linux. Only the CommandCentral Storage managed host is supported on Red Hat Linux. Advanced Server 3.0 Following are the required patches to run the CommandCentral Storage managed host on Red Hat Linux Advanced Server 3.0: openssl096b-0.9.6b-16 (Data Module) libstdc++-libc6.2-2.so.3

31 System requirements System resource requirements 31 Advanced Server 4.0 Following are the required patches to run the CommandCentral Storage managed host on Red Hat Linux Advanced Server 4.0: openssl096b-0.9.6b-16 (Data Module) libstdc++-libc6.2-2.so.3 Enterprise Server 3.0 Following are the required patches to run the CommandCentral Storage managed host on Red Hat Linux Enterprise Server 3.0: openssl096b-0.9.6b-16 (Data Module) libstdc++-libc6.2-2.so.3 Enterprise Server 4.0 Following are the required patches to run the CommandCentral Storage managed host on Red Hat Linux Enterprise Server 4.0: openssl096b-0.9.6b-16 (Data Module) libstdc++-libc6.2-2.so.3 System resource requirements The tables below provide memory and disk space specifications for CommandCentral Storage components. The amounts of memory and disk space are in addition to the resources already consumed by other software on the host. Note: Disk space requirements are only for installation of the product itself. On the Management Server, disk space requirements (as well as memory and CPU) increase as you add switches, storage devices, and file usage information to the CommandCentral Storage database. On managed hosts, used disk space increases as the number of files that you scan with the Data Module increases. For the latest Management Server and managed host processor requirements, see the CommandCentral Storage Hardware and Software Compatibility List. This document is updated regularly at:

32 32 System requirements System resource requirements Note: On UNIX hosts, although you can specify user-defined install directories for CommandCentral Storage components, you cannot specify user-defined install directories for shared components. The CommandCentral Storage installer installs shared components (such as the Authentication Service and the Authorization Service) under the /opt directory only. Approximately 160MB of free disk space is required for these components. Solaris system requirements Windows system requirements HP-UX system requirements AIX system requirements Red Hat Linux system requirements Solaris system requirements Table 2-3 provides memory and disk space specifications for installing CommandCentral Storage 5.0 MP1 components. Table 2-4 provides memory and disk space specifications for upgrading CommandCentral Storage 5.0 components to 5.0 MP1. The amounts of memory and disk space are in addition to the resources already consumed by other software on the host. Disk space requirements for the CommandCentral Storage Management Server are only for installation of the component itself. Disk space, CPU, and memory requirements increase as you add switches, storage devices, and file usage information to the CommandCentral Storage database. Note: When you install or upgrade to CommandCentral Storage 5.0 MP1, you need to ensure that there is sufficient space to create a backup of the binaries. On Solaris, the backups are created in /var/sadm/patch and /var/sadm/pkg. Table 2-3 System resources for installing CommandCentral Storage 5.0 MP1 on Solaris hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Management Server 2GB (4GB recommended) Total MB Relocatable MB Non-relocatable - 600MB Binaries backup - 490MB 420MB Yes

33 System requirements System resource requirements 33 Table 2-3 System resources for installing CommandCentral Storage 5.0 MP1 on Solaris hosts (continued) Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB Total - 543MB 420MB No Relocatable - 405MB Non-relocatable - 67MB Binaries backup - 71MB Managed host (with array management) 256MB (512MB recommended) Total MB Relocatable - 654MB Non-relocatable - 324MB Binaries backup - 159MB 420MB No Table 2-4 System resources for upgrading CommandCentral Storage 5.0 to 5.0 MP1 on Solaris hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Management Server 2GB (4GB recommended) Total - 525MB Relocatable - 5MB Non-relocatable - 5MB Binaries backup - 515MB 420MB Yes Managed host 256MB Total - 152MB 420MB No Relocatable - 10MB Binaries backup - 142MB Managed host (with array management) 256MB (512MB recommended) Total - 172MB Relocatable - 7MB Non-relocatable - 2MB Binaries backup - 163MB 420MB No Temporary space shows the additional space that must be in /var/tmp for tar.gz packages. Consider the following calculations:

34 34 System requirements System resource requirements Disk space calculation: The disk space required varies depending on the number of components you choose to install. The installer sums the space required for all the components you are installing. Temp space calculation: The installer copies all tar.gz files to /var/tmp from where it installs the component and then deletes the tar.gz files. The temp space required equals the size of the largest component package you are installing, plus the size of the associated tar file. The install script calculates the package and the tar file sizes and reports this sum as the required temp space. Windows system requirements Table 2-5 provides memory and disk space specifications for CommandCentral Storage components. The amounts of memory and disk space are in addition to the resources already consumed by other software on the host. Disk space requirements for the Management Server are only for installation of the component itself. Disk space, CPU, and memory requirements increase as you add switches, storage devices, and file usage information to the CommandCentral Storage database. Consider the following while provisioning disk space: When you install CommandCentral Storage 5.0 MP1, the non-relocatable space is required on the system drive where the operating system is installed. If you are upgrading to 5.0 MP1, the non-relocatable space is required on the drive where CommandCentral Storage is installed. When you upgrade CommandCentral Storage 5.0 to 5.0 MP1, you need to ensure that there is sufficient space to create a backup of the binaries. On Windows, the backup is created on the system drive. Table 2-5 System resources for installing CommandCentral Storage 5.0 MP1 on Windows hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Management Server 2GB (4GB recommended) Total - 850MB Relocatable - 705MB Non-relocatable - 145MB 224MB Yes

35 System requirements System resource requirements 35 Table 2-5 System resources for installing CommandCentral Storage 5.0 MP1 on Windows hosts (continued) Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host (local install) 256MB Total - 231MB Relocatable - 196MB Non-relocatable - 35MB 115MB No Managed host (remote install using Agent Push Install Utility) 256MB Total - 231MB Relocatable - 196MB Non-relocatable - 35MB 170MB No Managed host with array management (local install) 256MB (512MB recommended) Total - 357MB Relocatable - 243MB Non-relocatable - 114MB 115MB No Managed host with array management (remote install using Agent Push Install Utility) 256MB (512MB recommended) Total - 357MB Relocatable - 243MB Non-relocatable - 114MB 170MB No Agent Push Install Utility 256MB (512MB recommended) Total - 202MB Relocatable - 190MB Non-relocatable - 12MB 150MB No

36 36 System requirements System resource requirements Table 2-6 System resources for upgrading CommandCentral Storage 5.0 to 5.0 MP1 on Windows hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Management Server 2GB (4GB recommended) Total - 440MB + twice the database size 224MB Yes Relocatable - 140MB + database size Non-relocatable - 80MB + database size Binaries backup - 250MB Managed host (local install) 256MB Total - 103MB Non-relocatable - 14MB 115MB No Binaries backup - 95MB Managed host (remote install using Agent Push Install Utility) 256MB Total - 103MB Non-relocatable - 14MB Binaries backup - 95MB 170MB No Managed host with array management (local install) 256MB (512MB recommended) Total - 144MB Non-relocatable - 19MB Binaries backup - 130MB 115MB No Managed host with array management (remote install using Agent Push Install Utility) 256MB (512MB recommended) Total - 144MB Non-relocatable - 19MB Binaries backup - 130MB 170MB No Agent Push Install Utility 256MB (512MB recommended) Total - 172MB Non-relocatable - 54MB Binaries backup - 120MB 150MB No

37 System requirements System resource requirements 37 HP-UX system requirements Table 2-7 provides memory and disk space specifications for installing CommandCentral Storage 5.0 MP1 components. Table 2-8 provides memory and disk space specifications for upgrading CommandCentral Storage 5.0 components to 5.0 MP1. The amounts of memory and disk space are in addition to the resources already consumed by other software on the host. Note: When you install or upgrade to CommandCentral Storage 5.0 MP1, you need to ensure that there is sufficient space to create a backup of the binaries. On HP-UX, the backup is created in /var/adm/sw/save. Table 2-7 System resources for installing CommandCentral Storage 5.0 MP1 on HP-UX hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB Total - 884MB 255MB No Relocatable - 456MB Non-relocatable - 117MB Binaries backup - 311MB Managed host (with array management) 256MB (512MB recommended) Total MB Relocatable - 723MB Non-relocatable - 658MB Binaries backup - 534MB 255MB No Table 2-8 System resources for upgrading CommandCentral Storage 5.0 to 5.0 MP1 on HP-UX hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB Total - 317MB 255MB No Relocatable - 6MB Binaries backup - 311MB

38 38 System requirements System resource requirements Table 2-8 System resources for upgrading CommandCentral Storage 5.0 to 5.0 MP1 on HP-UX hosts (continued) Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host (with array management) 256MB (512MB recommended) Total - 668MB Relocatable - 5MB Non-relocatable - 124MB Binaries backup - 539MB 255MB No Temporary space shows the additional space that must be in /var/tmp for tar.gz packages. CommandCentral Storage managed hosts require minimum values for the following HP-UX variables: maxssiz 80MB (process maximum stack size) maxdsiz 1.9GB (data segment) For more information about these variables, refer to your HP-UX documentation. AIX system requirements Table 2-9 provides memory and disk space specifications for installing CommandCentral Storage 5.0 MP1 components. Table 2-10 provides memory and disk space specifications for upgrading CommandCentral Storage 5.0 components to 5.0 MP1. The amounts of memory and disk space are in addition to the resources already consumed by other software on the host. Note: When you install or upgrade to CommandCentral Storage 5.0 MP1, you need to ensure that there is sufficient space to create a backup of the binaries. On AIX, the backup is created in /usr/lpp.

39 System requirements System resource requirements 39 Table 2-9 System resources for installing CommandCentral Storage 5.0 MP1 on AIX hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB Total MB 670MB No Non-relocatable - 912MB Binaries backup - 750MB Managed host (with array management) 256MB (512MB recommended) Total MB Non-relocatable MB Binaries backup MB 670MB No Table 2-10 System resources for upgrading CommandCentral Storage 5.0 to 5.0 MP1 on AIX hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB Total - 660MB 670MB No Non-relocatable - 23MB Binaries backup - 637MB Managed host (with array management) 256MB (512MB recommended) Total MB Non-relocatable - 33MB Binaries backup MB 670MB No Temporary space shows the additional space that must be in /var/tmp for tar.gz packages. Red Hat Linux system requirements Table 2-11 provides memory and disk space specifications for installing CommandCentral Storage 5.0 MP1 components. Table 2-12 provides memory and disk space specifications for upgrading CommandCentral Storage 5.0 components to 5.0 MP1. The amounts of memory and disk space are in addition to the resources already consumed by other software on the host.

40 40 System requirements CommandCentral Storage web browser requirements Table 2-11 System resources for installing CommandCentral Storage 5.0 MP1 on Red Hat Linux hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB Total - 271MB 40MB No Relocatable - 206MB Non-relocatable - 65MB Managed host (with array management) 256MB (512MB recommended) Total - 509MB Relocatable - 291MB Non-relocatable - 218MB 40MB No Table 2-12 System resources for upgrading CommandCentral Storage 5.0 to 5.0 MP1 on Red Hat Linux hosts Component Physical memory required Disk space required Temp space required Dual CPU required? Managed host 256MB 2MB relocatable space 40MB No Managed host (with array management) 256MB (512MB recommended) 2MB relocatable space 40MB No Temporary space shows the additional space that must be in /var/tmp for tar.gz packages. CommandCentral Storage web browser requirements One of the following Web browsers is required to run the Console: Microsoft Internet Explorer 6.x or later (Windows only) Mozilla 1.7 (Solaris only) Mozilla Firefox 1.07, 1.5, or x (Windows only) Your browser must support either JScript 5.5 (provided with Microsoft Internet Explorer 6 or later) or JavaScript 1.2. Additionally, for Internet Explorer, Secure Sockets Layer (SSL) 3.0 ActiveX scripting must be enabled.

41 System requirements Co-existence of CommandCentral Storage components with other Symantec products 41 If you are using pop-up blockers, either disable them or configure them to accept pop-ups from the CommandCentral Storage Management Servers to which you will connect. To display the CommandCentral Storage Topology Map in a Web browser, your workstation must have at least Java 5 (version 1.5) installed. Note: For Internet Explorer 6.0 on Windows 2000 (Server, Advanced Server, or Datacenter Server) and Windows 2003 Server (Standard Edition, Datacenter Edition, Enterprise Edition, or Web Edition), set the default Intranet zone security level to MEDIUM or lower. Co-existence of CommandCentral Storage components with other Symantec products Several Symantec products may be required in a typical data storage management environment. Table 2-13 describes the products (or product components) that can co-exist on a host where CommandCentral Storage components are installed. Note: Co-existence between Management Servers has been tested on Solaris with SF 5.0MP1. Co-existence of Management Servers and managed hosts has been tested on Solaris with SF 5.0MP1/SFRAC 5.0MP1. Table 2-13 CommandCentral Storage co-existence with other Symantec products Component Management Server Management Server Management Server Management Server Management Server Symantec product component Veritas SF Manager 1.1 Management Server Veritas SF Manager 1.1 managed host Symantec License Inventory Manager 4.0 agent Veritas NetBackup 6.5 agent Veritas Backup Reporter Co-install possible? No Yes Yes Yes No