VERITAS StorageCentral 5.2

Transcription

1 VERITAS StorageCentral 5.2 Release Notes Windows

2 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. VERITAS Legal Notice Copyright 2003 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, and all VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS and the VERITAS logo, Reg. U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. VERITAS Software Corporation 350 Ellis Street Mountain View, CA USA Phone Fax

3 Contents Introduction to StorageCentral New Features...1 Software and Hardware Requirements...2 Agents... 2 Collector... 3 Console... 3 Network Appliance Filer... 4 Remote Agent... 5 Operational Notes...6 Known Issues...6 No Longer Supported...18 Available Documentation...18 Documentation Addenda...18 Space Allocation and Network Appliance Filers Troubleshooting Uninstalling StorageCentral Upgrade Roadmap Getting Technical Support...21 i

4

5 Introduction to StorageCentral 5.2 VERITAS StorageCentral is a comprehensive storage capacity optimization solution. StorageCentral addresses the key storage management areas: controlling and monitoring disk space usage, reporting on storage content, and monitoring the health of your storage. It is a real-time storage resource management system for Windows NT and Windows 2000 (and above). StorageCentral: Limits the users' disk space by monitoring and enforcing disk usage policies in real time Generates detailed reports of space consumption Prevents unwanted files from being saved on the servers New Features StorageCentral 5.2 has a variety of new features and capabilities. They are summarized here; for more detail, read the What s New in StorageCentral 5.2 topic in the online User Guide. Features related to the Active Directory: StorageCentral presents information regarding the AD property level You can apply a computer policy stored in the AD to the copy of StorageCentral you are installing 1

6 Features related to Network Appliance Filers: StorageCentral presents new status information in the managed object grid for objects residing on a Network Appliance Filer You can issue simple Network Appliance Filer commands from StorageCentral StorageCentral provides user quota support for Network Appliance Filers Other new features and capabilities: The ability to run under Windows 2003 Unicode support Increased control over the amount of audit and trending data StorageCentral retains Two levels of access for non-administrative users Software and Hardware Requirements This section lists what you need to run StorageCentral on your system. Agents One of the following operating systems: o Windows XP Professional o Windows NT 4, service pack 6a 2 StorageCentral 5.2 Release Notes

7 o Windows 2000 Professional, Server, Advanced Server, or Datacenter Server o Windows Server 2003 Standard, Enterprise, or Datacenter Edition 128 MB RAM for Windows Professional or 256 MB for others 6 MB of disk space are required to install an agent, plus additional space to run StorageCentral Collector One of the following operating systems: o Windows XP Professional o Windows NT 4, service pack 6a o Windows 2000 Professional, Server, Advanced Server, or Datacenter Server o Windows Server 2003 Standard, Enterprise, or Datacenter Edition Internet Explorer 5.5 or later 256 MB RAM for Windows Professional or 512 MB for others 33 MB of disk space are required to install a collector, plus additional space to run StorageCentral Console One of the following operating systems: o Windows XP Professional 3

8 o Windows 2000 Professional, Server, Advanced Server, or Datacenter Server o Windows Server 2003 Standard, Enterprise, or Datacenter Edition Internet Explorer 5.5 or later 256 MB RAM for Windows Professional or 512 MB for others 50 MB of disk space are required to install the MMC console, plus additional space to run StorageCentral Network Appliance Filer This section applies only if you are installing a Network Appliance edition of StorageCentral. Data ONTAP version 6.4 (or later) from Network Appliance must be installed on the Filer to provide support for thirdparty products (such as StorageCentral). The CIFS protocol must be enabled on the Filer you want to manage. SNMP must be configured on both the Filer and remote agent to generate traps for your remote agent. You will configure SNMP to do this when you install StorageCentral. The StorageCentral remote agent and MMC must be installed and executed within the same domain as the Network Appliance Filer(s) that they are intended to manage. 4 StorageCentral 5.2 Release Notes

9 Remote Agent This section applies only if you are installing a Network Appliance edition of StorageCentral. One of the following operating systems: o Windows XP Professional o Windows 2000 Professional, Server, Advanced Server, or Datacenter Server o Windows Server 2003 Standard, Enterprise, or Datacenter Edition Internet Explorer 5.5 or later 128 MB RAM for Windows Professional or 256 MB for others 6 MB of disk space are required to install a remote agent, plus additional space to run StorageCentral Simple Network Management Protocol (SNMP) support must be operational on the remote agent so that StorageCentral can report on space allocation violations on the Filer. The StorageCentral remote agent and MMC must be installed and executed within the same domain as the Network Appliance Filer(s) that they are intended to manage. Note: Installing the remote agent on a Windows 2000 (or above) cluster is not supported. 5

10 Operational Notes You will find installation and upgrade instructions in the User Guide. The installation instructions are also presented in a standalone document, titled Installation Instructions, which is available as a PDF located in the \docs folder of the installation CD. Known Issues The chart below summarizes the known issues with StorageCentral. These issues, and their resolutions or workarounds, are presented in greater detail after the chart. Issue Number Incident Number Description Space by Space Allocation Report Definition is Wrong Space by Space Allocation Report Definition Shows Incorrect Columns Space Allocation Summary Report Set Fields That Are Not Supported for a Filer Do Not Show N/A (Not Applicable) Report Sets Run Slowly Chargeback Report Has Errors Space By Partition Report Figures Are Different in Drill Down Object Failed to be Scanned on a Remote Server in the Space Allocation Summary Report 6 StorageCentral 5.2 Release Notes

11 Issue Number Incident Number Description Sometimes a Scheduled Report Never Runs If a Volume That Has Quotas is Offline, Restarting Quotas on Other Volumes Causes Quota Off on Other Volumes Trending Does Not Work for User Quotas on Filer No Unicode Support for the SNMP Trap MMC Cannot Connect to a Remote Domain on Windows XP Drilldown Results are Inconsistent Virtual Memory May be Exceeded When Running a Report WQRptServer and WQFileSvr Running as "Launching User" Information is Missing After an Upgrade Reports Against an Entire Filer Do Not Work New Auto Detect Objects for Subfolders or Users Use the Old Policy Settings Scrolling the Rows in Active Reports Does Not Work the Way You Expect in Windows XP 7

12 Issue Number Incident Number Description Active Directory Properties Are Not Propagated Correctly for a Domain Controller Icons Do Not Render Correctly ComputerList Gets Removed from AD When You Modify the Setup Space Allocation Objects Not Associated with Policy Cannot Save SQL Server Properties for a Filer 1. Problems with Reports Incident number: Space by Space Allocation Report Definition is Wrong Description: The report definition shows the selection as <1MB but the report selects all objects with a space limit >1MB. The registry/ad has a value of 5 for scope which is not supported. Workaround: Use the user interface to change the report definition so that the selection is All Quotas. Follow these steps: 1. Right-click the Space by Space Allocation report definition and select Properties. 2. Select the Settings tab. 8 StorageCentral 5.2 Release Notes

13 3. Select All Quotas from the Range drop-down list. 4. Click OK to save the report definition. The product does not ship with any report sets that use this definition. To use the new definition in user-created report sets, right-click the report set and select Properties. Select the Content tab and uncheck the Space by Space Allocation. Then click OK. Right-click the report set and select properties. Select the Content tab and check the Space by Space Allocation. This report set will now use the new Space by Space Allocation report definition. 1.2 Space by Space Allocation Report Definition Shows Incorrect Columns Description: The Space by Space Allocation report definition s IsQuotaAbsolute column always shows N/A, Threshold1 always shows 0, and Threshold2 always shows N/A. These are all incorrect. This only occurs on a Network Appliance Filer. Workaround: If reporting against a Network Appliance Filer, use the Space Allocation Summary report set instead. Issue 1.3 Space Allocation Summary Report Set Fields That Are Not Supported for a Filer Do Not Show N/A (Not Applicable) Description: This only occurs on a Network Appliance Filer. Resolution: Unsupported fields will be 0 for numeric values, disabled for bit values, and 0 for numeric values. 9

14 Issue 1.4 Report Sets Run Slowly Description: When a report definition has a data source of Active File System and reports on space allocation fields, any report sets based on it can take a long time to run. This only occurs when there are a large number of files. Workaround: Do not use these fields on reports with a large number of files. 2. Chargeback Report Has Errors Incident number: Description: The Chargeback Summary report set is sorting on the Threshold1 field which is incorrect. The Chargeback Summary report set should sort on the Department field. Also, the break on Threshold1 should be changed to Department. Also, there seems to be a problem running the Chargeback Summary report set on a Network Appliance Filer. Workaround: Change the report definition so that the report sorts on ChargebackAccount (ascending) and the report breaks on ChargebackAccount. Do not run this report on a Network Appliance Filer unless the file ownership is Windows domain users. 3. Space By Partition Report Figures Are Different in Drill Down Incident number: Description: The Used Space column in the Space By Partition report definition does not match similar columns reported if you drill down on an individual partition listed in the report. Workaround: The Space by Partition report definition does not use the global filtering settings used by the other report definitions 10 StorageCentral 5.2 Release Notes

15 because it displays volume information about each volume, rather than totaling file usage statistics on all the files on a volume. To make the totals match, using the MMC, right-click the computer where the server totals are different, or in the AD version, right-click the root. Then select the Reports tab and uncheck Exclude OS Files, Exclude DLL Files, and Exclude Administrators. 4. Object Failed to be Scanned on a Remote Server in the Space Allocation Summary Report Incident number: Description: When the Space Allocation Summary report set is run against multiple servers it will intermittently fail to scan one of the servers. The failure seems to be caused by a Quota Server object instantiation failure. Workaround: Limit this report set to a single server or rerun the report set if it fails. 5. Sometimes a Scheduled Report Never Runs Incident number: Description: In some instances when a report is scheduled, the report never runs in the task scheduler and shows there forever as having never completed. Resolution: Verify that the task scheduler is logging on as a domain-level user and not the system account. Also make sure that the path environment variable points to <install-directory>\bin and that the user can execute the SCReport command. 11

16 6. If a Volume That Has Quotas is Offline, Restarting Quotas on Other Volumes Causes Quota Off on Other Volumes Incident number: Description: Network Appliance API "quota-on" returns success, even though the quota is not turned on. Workaround: Turn the volume online from the Filer view. 7. Trending Does Not Work for User Quotas on Filer Incident number: Description: QAServer does not write Filer user quotas to the trend database. Workaround: None. 8. No Unicode Support for the SNMP Trap Incident number: Description: You selected the Send SNMP trap check box when you created or changed a file blocking policy, but the notification message in the SNMP trap contains garbage text. Explanation: The StorageCentral SNMP trap only reads ANSI characters; Unicode support is not provided. Workaround: None. 12 StorageCentral 5.2 Release Notes

17 9. MMC Cannot Connect to a Remote Domain on Windows XP Incident number: Description: The problem only occurs when the MMC is executed on a Windows XP machine in a multiple domain environment. Workaround: Use the MMC UI in the same domain to manage servers. 10. Drilldown Results are Inconsistent Incident number: Description: When the Large Users Summary report set is run on a Windows NT object and the ensuing drilldown report is launched, the results do not match. Workaround: Do not drill down on the Large Users Summary report set. 11. Virtual Memory May be Exceeded When Running a Report Incident number: Description: Reports are memory-intensive. There are times when a report can use up all of a CPU's remaining virtual memory. Workaround: Use Task Manager to ensure that you still have virtual memory available. If you are running a report and either the WQRptSvr.exe or the Iexplore.exe process is using up all of the CPU and thus using up all of the virtual memory, kill the process in the Task Manager. 13

18 12. WQRptServer and WQFileSvr Running as "Launching User" Incident number: Description: The silent install utility accepts the local system account. After generating the batch file and installing the product, WQRptSvr and WQFileSvr will be running as "Launching User". Resolution: WQRptSvr and WQFileSvr can be configured using the DCOMCNFG utility. In the Identity tab, if WQRptSvr and WQFileSvr are set to the "Launching User," you must change them to "This User" and enter the domain-level user account you specified for StorageCentral services. Note: In this case even WQQASvr and WQFSSvr will also be running as system account services. Even this should be changed to domain-level user account. 13. Information is Missing After an Upgrade Incident number: Description: The retention period values on the Trending and Audit tabs, and file blocking settings on the Event Log tab, are missing after an upgrade from StorageCentral 5.2 Standard edition to 5.2 Active Director edition. Explanation: When you upgrade the product, the registry values are not saved and retained. Workaround: Before doing an upgrade, make a note of the retention period values on the Trending and Audit tabs, and the file blocking settings on the Event Log tab. After upgrading, enter the retention period values on the Trending and Audit tabs and the file blocking settings on the Event Log tab. 14 StorageCentral 5.2 Release Notes

19 14. Reports Against an Entire Filer Do Not Work Incident number: Description: When a report is run against a Filer UNC (universal naming convention) such as \\Netapp, StorageCentral produces a blank report. An error message such as the following appears in the report: Error Scanning \\netapp: NetShareGetInfo Result=%d This appears to be an intermittent problem. Workaround: Rerun the report. 15. New Auto Detect Objects for Subfolders or Users Use the Old Policy Settings Incident number: Description: If the policy associated with an auto detect object is modified after the initial auto detect object is created, any new objects created for a user or subfolder retain the old policy settings, thereby ignoring the updated policy. Workaround: Reapply the policy against the newly created auto detect objects that exhibit the old policy settings. 15

20 16. Scrolling the Rows in Active Reports Does Not Work the Way You Expect in Windows XP Incident number: Description: This seems to be a GUI issue with Windows XP and not the report components. Workaround: None. 17. Active Directory Properties Are Not Propagated Correctly for a Domain Controller Incident number: Description: When the global properties are changed in Active Directory, they are not propagated down to the local machine correctly on a domain controller after reboot. Workaround: Restart the StorageCentral services. 18. Icons Do Not Render Correctly Incident number: Description: While running in High Contrast mode, certain icons (for example, Move Up and Move Down) do not display correctly. Workaround: Switch back to Normal Contrast mode. 16 StorageCentral 5.2 Release Notes

21 19. ComputerList Gets Removed from AD When You Modify the Setup Incident number: Description: When you modify the setup by adding a component that was not selected during install, StorageCentral deletes the ComputerList from the Active Director. Workaround: After modifying the setup, you must manually add the machine to the AD. From the command prompt go to the <install-directory>\bin directory and type the following command: AddComputerToAD.exe Add computer-name Space Allocation Objects Not Associated with Policy Incident number: Description: When you create multiple Space Allocation objects (for example, c:\test1, c:\test2, and c:\test3), only the first object (c:\test1) will have the policy association. The rest of the objects will have the policy properties in them but are not associated with the policy that was used to create them. Workaround: Select all of the objects that show no policy association and apply the policy that was originally selected when the objects were created. 21. Cannot Save SQL Server Properties for a Filer Incident number: Description: You can enter a value for SQL Server user and password on the SQL Server tab of a Filer s global properties. 17

22 However, QAServer does not save these values. The Filer instead uses the user and password values for SQL server associated with the remote agent Workaround: The SQL Server tab will be removed for Filers in the future. For now, use the values in the remote agent. No Longer Supported StorageCentral no longer supports the Web user interface (UI) and Explorer Snapin feature. Available Documentation There are two documents that come with StorageCentral: The User Guide explains how to install the product, use it to monitor your storage, and produce reports. This document also provides reference material, a list of best practices, and troubleshooting advice. The Tutorial provides step-by-step instructions in using StorageCentral to quickly begin gathering information about the way your computer storage is being used. These documents are available online. They are also available as PDFs located in the \docs folder of the installation CD. Documentation Addenda This section identifies late-breaking additions and corrections to topics in the online User Guide. 18 StorageCentral 5.2 Release Notes

23 Space Allocation and Network Appliance Filers Add this section before the Limitations section: Requirements A volume root share is required to manage quotas on a Network Appliance Filer. If the Administrator neglects to set a share on the volume root, but has created shares on qtrees, no folders appear in the New Object Wizard even though qtrees and shares exist on the filer, and you are unable to create managed objects. There is a section that lists StorageCentral space allocation features not available for Filer support. Change the Notify user bullet to read: Notify user (an action option) is not supported for qtree limits, but it is supported for user limits Troubleshooting There are several additions and corrections for the online help Troubleshooting topic: There are several typos in Step 4 of the entry titled User Account is Marked Safe for Delegation Differently. Step 4 should read like this: If you cannot see the Delegation tab, set the SPN first using the Setspn command. Use the syntax: Setspn /a servicename/servername domain\user. Type the following: Setspn /a WQQASvr/servername domain\user Setspn /a WQFSSvr/servername domain\user 19

24 Add this troubleshooting entry: A Report Fails to Run as Expected Problem: A report may not behave as you expect. For example, you may be unable to drill down on an ActiveX report or you get an unexpected error message. Explanation: You may have encountered one of the StorageCentral limitations regarding reports. Solution: Read the Limitations section in the Introduction to Reports online help topic. If you still have questions, contact VERITAS technical support. Add this troubleshooting entry: The object exporter specified was not found Error Message Displays Problem: The The object exporter specified was not found error message displays. Explanation: This message displays under one of several conditions: (1) The DNS on the remote agent and management workstation (that is, where you run the MMC from) are not equal. (2) The IP address of the management workstation is wrong or missing. Suggested solutions: (1) Use statically configured IP addresses for both the remote agent and management station, and ensure that the IP addresses for the Filer, remote agent, and management station are correct and present in the DNS. (2) If the error message displays when you are managing a remote Windows server, make sure the IP addresses for the remote server and management station are present in the DNS. 20 StorageCentral 5.2 Release Notes

25 Uninstalling StorageCentral This topic has been expanded to be more complete and renamed StorageCentral Maintenance. The PDF file containing the enhanced documentation is located in the \docs folder of the installation CD. Upgrade Roadmap In this topic s table there is a row with a value of 5.0 (builds 220 and 230) Standard in the Upgrade From column, and a value of 5.2 Standard in the Upgrade To column. The first numbered step in the Instructions column should read: On the StorageCentral management pane, highlight My Computer or a preferred machine, right-click, and choose Properties. The Properties dialog box displays. In this topic s table there is a row with a value of 5.0 (builds 220 and 230) AD in the Upgrade From column, and a value of 5.2 AD in the Upgrade To column. The first numbered step in the Instructions column should read: On the StorageCentral management pane, highlight the StorageCentral icon, a computer, an OU, or preferred machine. Then right-click and choose Properties. The Properties dialog box displays. Getting Technical Support VERITAS Software Corporation offers you a variety of support options. 21

26 Accessing the VERITAS Support Web Site The VERITAS Support Web site allows you to: Contact the VERITAS Support staff and post questions to them Get the latest patches, upgrades, and utilities View the StorageCentral Frequently Asked Questions (FAQ) page Search the knowledge base for answers to technical support questions Receive automatic notice of product updates Find out about StorageCentral training Read current white papers related to StorageCentral The address for the VERITAS Support Web site is Subscribing to VERITAS Notification Service Subscribe to the VERITAS notification service to be informed of software alerts, newly published documentation, Beta programs, and other services. Go to Select a product and click Notifications on the right side of the page. Your customer profile ensures you receive the latest VERITAS technical information pertaining to your specific interests. 22 StorageCentral 5.2 Release Notes

27 Accessing VERITAS Telephone and Fax Support Telephone support for StorageCentral is only available with a valid support contract. To contact VERITAS for technical support, go to Specify StorageCentral as the product and click Contact Support on the right side of the page. Find the appropriate phone number in the list that displays. Contacting VERITAS Licensing For license information, call or fax