Symantec Enterprise Vault Technical Note

Transcription

1 Symantec Enterprise Vault Technical Note FSA Reporting deployment guidelines 8.0 Symantec Information Foundation

2 Symantec Enterprise Vault: FSA Reporting deployment guidelines 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. Last updated: July 15, Legal Notice Copyright 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Veritas, and Enterprise Vault 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. This Symantec product contains third party software for which Symantec is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Software file accompanying this Symantec product for more information on the Third Party Programs. 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. Symantec Corporation 350 Ellis Street Mountain View, CA

3 Technical Support Symantec Technical Support maintains support centers globally. Technical Support s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates 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 Telephone and Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers automatic software upgrade protection Global support that is available 24 hours a day, 7 days a week Advanced features, including Account Management Services For information about Symantec s Maintenance Programs, you can visit our Web site at the following URL: Contacting Technical Support Customers with a current maintenance agreement may access Technical Support information at the following URL: 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 replicate the problem. 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

4 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: Customer service information is available at the following URL: 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 assurance and maintenance contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals

5 Maintenance agreement resources 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 Additional enterprise services 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 Managed Security Services Consulting Services Educational Services These solutions provide early warning of cyber attacks, comprehensive threat analysis, and countermeasures to prevent attacks before they occur. 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 is 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. 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.

6

7 FSA Reporting deployment guidelines This document includes the following topics: About FSA Reporting deployment Assumptions, notes, and recommended settings Deploying FSA Reporting with NTFS file servers Deploying FSA Reporting with NetApp and EMC Celerra file servers Changing the number of simultaneous target volume scans About FSA Reporting deployment This technical note contains guidelines on how to deploy FSA Reporting. It provides advice on: The factors that affect how many file servers you should attempt to scan simultaneously. How to configure Enterprise Vault for improved performance with FSA Reporting. The figures quoted in this technical note are based on practical experience, but they can only provide approximate guidelines. Every customer has different needs and different environments. Many factors influence the performance of an archiving system, including the type and size of data that is archived, the file types, and so on. In addition, most systems expect growth in both volume and size of data. These factors lead to the need to be very cautious when you deploy a system.

8 8 FSA Reporting deployment guidelines Assumptions, notes, and recommended settings Assumptions, notes, and recommended settings Note the following: The information in this technical note is based on an environment that uses Enterprise Vault 8.0 Service Pack 2 (SP2). We recommend that you install or upgrade to Enterprise Vault 8.0 SP2 if you intend to use FSA Reporting. Some of the procedures in this technical note refer to the Enterprise Vault server that runs the proxy FSA Agent for NetApp and EMC Celerra file servers. If you have more than one Enterprise Vault server in a site, you may need to determine which Enterprise Vault server or servers run the proxy FSA Agent. See Determining the location of the proxy FSA Agent on page 8. The guidelines assume that you use the default values for FSA Reporting's settings, unless otherwise advised. If you upgrade to Enterprise Vault 8.0 SP2, we recommend that you modify two registry values to use the new SP2 default values. See Resetting the WebServiceTimeout and FilePartSize values after upgrading on page 9. The guidelines assume that data collection for FSA Reporting's duplicate files reports is disabled. See Data collection for the Duplicate Files reports on page 10. We recommend that you change the default storage location for FSA Reporting's temporary files on the file server. See Changing the storage location for temporary files on the file server on page 10. Determining the location of the proxy FSA Agent Some of the procedures in this technical note refer to the Enterprise Vault server that runs the proxy FSA Agent for NetApp and EMC Celerra file servers. If you have more than one Enterprise Vault server in a site you can examine the FSA Reporting database to determine which Enterprise Vault server or servers run a proxy FSA Agent.

9 FSA Reporting deployment guidelines Assumptions, notes, and recommended settings 9 To determine which Enterprise Vault servers run a proxy FSA Agent 1 Start Enterprise Manager for Microsoft SQL 2000, or SQL Server Management Studio for SQL Server 2005 or Expand the container for the EnterpriseVaultFSAReporting database. 3 Right-click the FileServerConfiguration table and select Open Table. An entry in the ProxyServerName column of the table indicates the name of an Enterprise Vault server that runs a proxy FSA Agent. Resetting the WebServiceTimeout and FilePartSize values after upgrading The default values for some FSA Reporting registry settings changed at Enterprise Vault 8.0 SP2. If you upgrade to Enterprise Vault 8.0 SP2, Enterprise Vault retains the old values. We recommend that after the upgrade you modify the following values to use their new SP2 defaults: WebServiceTimeout. This value sets the timeout period for the FSA Reporting Web service. FilePartSize. This sets the maximum chunk size that FSA Reporting uses when it sends the scan data from the file server to the Enterprise Vault server. To modify the FSA Reporting Web service timeout and File Part Size values 1 On the NTFS file server, or on the Enterprise Vault server that runs the proxy FSA Agent for NetApp and Celerra, start the registry editor. 2 Navigate to the following registry key: HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \FSA \Reporting 3 Change the value of WebServiceTimeout to the decimal value This sets the timeout value to 9999 minutes. 4 Change the value of FilePartSize to the decimal value This sets the maximum file chunk size to 2048 KB.

10 10 FSA Reporting deployment guidelines Assumptions, notes, and recommended settings 5 Exit from the registry editor. You must now edit the FSA Reporting Web.config file to reflect the new WebServiceTimeout value, as described in the following steps. 6 On the Enterprise Vault server, navigate to the FSAReporting folder under the Enterprise Vault installation folder. 7 Open the Web.config file with a text editor. 8 Search for executionttimeout and change its value to This value must match the WebServiceTimeout value, but it is expressed in seconds, not minutes is 9999 x Save the changes to the Web.config file. Data collection for the Duplicate Files reports If you install or upgrade to Enterprise Vault 8.0 SP2, data collection for the three Duplicate Files reports is disabled by default. Data collection for these reports incurs a performance overhead that is best avoided unless you require the reports. If you enable data collection for these reports, FSA Reporting's scan times may be significantly longer, depending on the number of files in the target volume. The guidelines in this technical note assume that data collection for the Duplicate Files reports is disabled. To enable or disable the data collection for the Duplicate Files reports you must edit the Properties table of the EnterpriseVaultFSAReporting database. For more details, see the section "Changing parameter values for the File Collector service" in the Enterprise Vault 8.0 SP2 Reporting guide. Changing the storage location for temporary files on the file server FSA Reporting creates temporary files on the file server to hold the scan data. On a file server with a large number of files, these temporary files can become very large. FSA Reporting stores its temporary files by default in the FSAReports subfolder of the Enterprise Vault installation folder. The installation folder is often on drive C, which typically has limited space. If the temporary files fill up all the space on the installation drive, the computer may suffer performance problems or stop responding. If there is likely to be insufficient space for the temporary files on the installation drive, relocate the storage location to an existing path on a drive that has sufficient free space.

11 FSA Reporting deployment guidelines Deploying FSA Reporting with NTFS file servers 11 To change the storage location for temporary files 1 On the NTFS file server, or on the Enterprise Vault server that runs the proxy FSA Agent for NetApp and Celerra, start the registry editor. 2 Navigate to the following registry key: HKEY_LOCAL_MACHINE \Software \KVS \Enterprise Vault \FSA \Reporting 3 Specify a suitable existing path using the TempFilePath registry value. Enterprise Vault creates a subfolder named FSAReports under the path that TempFilePath defines, in which to hold the temporary files. 4 Exit from the registry editor. 5 On NTFS file servers, restart the Enterprise Vault File Collector Service. For Celerra and NetApp file servers, restart the Enterprise Vault Admin service on the Enterprise Vault server that runs the proxy FSA Agent. Deploying FSA Reporting with NTFS file servers As an approximate guide, you may configure FSA Reporting to scan up to ten file servers simultaneously if your configuration does not exceed any of the following limits: 500 archive points per target volume. 3 million archived files per target volume different file types per target volume different file owners per target volume. These limits assume that FSA Reporting scans no more than five target volumes simultaneously, which is the default setting. If your configuration exceeds one or more of these limits, we recommend that you reduce the number of simultaneous target volume scans. See Changing the number of simultaneous target volume scans on page 12. If you have more than ten file servers on which you want to run FSA Reporting scans, we recommend that you schedule no more than ten file server scans to run concurrently.

12 12 FSA Reporting deployment guidelines Deploying FSA Reporting with NetApp and EMC Celerra file servers To improve performance in any configuration we also recommend that you use a dedicated SQL Server or SQL Server instance for the FSA Reporting database. Deploying FSA Reporting with NetApp and EMC Celerra file servers The guidelines for NTFS file servers apply equally for NetApp file servers and EMC Celerra file servers, or a mix of file server types. See Deploying FSA Reporting with NTFS file servers on page 11. However, there is an additional factor to consider for NetApp and EMC Celerra file servers: For NTFS, an FSA Agent is present on each target file server. By default, the FSA Agents scan up to five volumes simultaneously on each file server. For NetApp and Celerra, a single proxy FSA Agent on an Enterprise Vault server performs the scans for all of the target NetApp and Celerra file servers in the Enterprise Vault site. By default, the proxy FSA Agent scans no more than five NetApp and Celerra target volumes simultaneously in the site. This difference has the following consequences for NetApp and Celerra file servers: FSA Reporting takes proportionately longer to scan multiple volumes on multiple file servers, compared with NTFS. The resource demand is focused on the Enterprise Vault server that runs the proxy FSA Agent. For improved performance, we recommend that you do not run any Enterprise Vault archiving tasks on an Enterprise Vault server that runs the proxy FSA Agent. Changing the number of simultaneous target volume scans The FSA Agent scans a maximum of five target volumes simultaneously, by default. You can reduce this number by changing the ScanThreads registry value. For example, if twenty volumes are enabled for FSA Reporting and you set ScanThreads to 3, only three volumes are scanned initially. FSA Reporting does not start to scan another volume until the scan completes on one of the three initial volumes. By reducing this value you reduce the resource demand, although you lengthen the time for multiple FSA Reporting scans to complete.

13 FSA Reporting deployment guidelines Changing the number of simultaneous target volume scans 13 To change the number of simultaneous target volume scans 1 On the NTFS file server, or on the Enterprise Vault server that runs the proxy FSA Agent for NetApp and Celerra, start the registry editor. 2 Navigate to the following registry key: HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \FSA \Reporting 3 Change the value of the DWORD registry value ScanThreads. This value sets the maximum number of simultaneous target volume scans. The default value of ScanThreads is 5, and the maximum value is Exit from the registry editor. 5 On NTFS file servers, restart the Enterprise Vault File Collector Service. For Celerra and NetApp file servers, restart the Enterprise Vault Admin service on the Enterprise Vault server that runs the proxy FSA Agent.

14 14 FSA Reporting deployment guidelines Changing the number of simultaneous target volume scans