Features - SRM NAS Agent

Transcription

1 Page 1 of 41 Features - SRM NAS Agent Table of Contents Overview System Requirements - SRM NAS Agent Installation Install the SRM NAS Agent Configuration SRM Data Collection SRM Summaries SRM NAS Reports Management Admin Job History Data Collection Job History

2 Page 2 of 41 Overview - SRM NAS Agent Topics Related Topics Introduction Supported Job Types for Data Collection Analysis Job Discovery Job Tree Level in SRM NAS Agent Configuration Considerations License Requirement Introduction The SRM NAS Agent gathers statistics on the network interfaces, system infrastructure, disk and file system assets (CIFS and NFS shares) of the NAS File Server (both NetApp and EMC Celerra are supported). Data collected by the SRM NAS Agent is summarized by many types of reports that may be further customized with user-selected filters and charts in the Report Manager. For the SRM NAS Agent, the agent software is installed in a proxy client. For more information on installing the proxy client, see Deployment - SRM NAS Agent. Once the installation is complete, the agent and the NAS file server information must be configured from the client level in the CommCell Console. For step-by-step instructions see, Add NAS Filer. Supported Job Types for Data Collection This agent supports two job types for data collection: Analysis Discovery Analysis Job This job collects detailed file-level statistics including information about file sizes, types, owners, extensions and create access and modification times. Data collections using the Analysis level job should be run during off-peak hours because they require processing that is CPU- and disk-intensive on the proxy Agent computer. Discovery Job This job collects basic information about about network interfaces, system infrastructure, disks, file system and share details, CIFS and NFS performance statistics, quotas, NetApp qtrees and snapshots, EMC quota trees, quota configurations and checkpoints for the file server. Data collections using the Discovery level job require minimal processing on the proxy Agent computer and may be run throughout the day. If you select a Discovery level Data Collection Job, you will not receive meaningful data in certain of the more extensive reports. See Reports - SRM NAS Agent for more information about which reports require Analysis level data collection. Tree Level in SRM NAS Agent When the SRM NAS Agent is installed, the following levels are automatically created in the CommCell

3 Page 3 of 41 Browser. hct: NAS: default: Client Agent Subclients Network Shares:This level displays Network Shares information for the SRM NAS Agent's client computer. Logical Storage Volumes associated with the client computer are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. Data Movers: File Systems: This level displays Data Movers information for Celerra File Servers. Data Movers are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. This level displays File Systems information for Celerra File Servers. File Systems are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. Storage Pools: This level displays Storage Pools information for Celerra File Servers. Storage Pools are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. Storage Systems: Meta-Volumes: Logical Volumes: vfilers: Aggregate Volumes: This level displays Storage Systems information for Celerra File Servers. Storage Systems populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. This level displays Meta-Volumes information for Celerra File Servers. Meta-Volumes are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. This level displays Logical Volumes information for NetApp File Servers. Logical Volumes are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. This level displays vfilers information for NetApp File Server. vfilers are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries. This level displays Aggregate Volumes information for NetApp File Server. Aggregate Volumes are populated under this level after completion of the first Data Collection operation. For more information, see SRM NAS Agent in Summaries.

4 Page 4 of 41 Configuration Considerations Consider the following configuration requirements prior to using the SRM NAS Agent: The SRM NAS Agent functions as a proxy Agent and must be installed on a separate computer running one of the proxy Agent operating systems listed in System Requirements - SRM NAS Agent. The SRM NAS Agent, a proxy agent, cannot communicate with the NAS File Server across a firewall, so the agent and the NAS device must be on the same side of the firewall. In order to successfully start a migration archiving job, the NAS Filer name used in the SRM NAS Agent and in the subclient content path in the File Archiver Agent should exactly be the same (caseinsensitive) or resolve to the same IP address. Make sure that the subclient content path in the File Archiver Agent is not excluded from data collection. License Requirement To perform a data collection operation using this Agent, you need a SRM NAS Agent license, available in the SRM server. The license is consumed when this component is configured on the client computer. See License Administration for more details on license requirements. Back to Top

5 Page 5 of 41 System Requirements - SRM NAS Agent The SRM NAS Agent software is installed on a computer (Proxy Agent) that can access the file server from which you wish to perform data collection. The following requirements are for the SRM NAS Agent for Network Attached Storage. This feature/product/platform requires a special software installation package. Contact your software provider to obtain this package. Proxy Agent Operating System Microsoft Windows Server bit and x64 Editions with a minimum of Service Pack 1 Microsoft Windows Server bit and x64 Editions* Microsoft Windows Server 2008 R2 Editions* *Core Editions not supported File Server Data can be collected from file servers with the following Operating Systems: NetApp ONTAP versions through 8.0.x Celerra DART versions 5.5 through 5.6 Processor All Windows-compatible processors supported Memory 32 MB RAM minimum required beyond the requirements of the operating system and running applications Hard Disk 107 MB minimum of hard disk space for software/ 148 MB recommended 30 MB of additional hard disk space for log file growth 77 MB of temp space required for install or upgrade (where the temp folder resides) Peripherals DVD-ROM drive Network Interface Card Miscellaneous TCP/IP Services configured on the computer. Network connectivity between the proxy Agent and the NAS file servers that are configured as clients. These requirements are in addition to the disk requirements set for the operating system. Microsoft Visual C Redistributable Package is automatically installed. te that Visual C Redistributable Package can co-exist with other versions of this software.

6 Page 6 of 41 DISCLAIMER Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as supported in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system. Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.

7 Page 7 of 41 Install the SRM NAS Agent Click on a link below to go to a specific section of the software installation: Install Requirements Install Checklist Before You Begin Install Procedure Getting Started Select Components for Installation Firewall Configuration Configuration of Other Installation Options Client Group Selection Verify Summary of Install Options Schedule Automatic Update Install Remaining Cluster des Setup Complete Post-Install Considerations General Agent Specific Install Requirements The SRM NAS Agent is installed on the computer from which the Agent collects data for reporting purposes. (This computer is referred to as the Client computer in this install procedure.) Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - SRM NAS Agent. The following procedure describes the steps involved in installing the SRM NAS Agent. If you choose to install additional components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. te that when you install multiple components, the sequence of the install steps may vary. Review the following Install Requirements before installing the software: General Agents should be installed only after the CommServe and SRM Server has been installed in the CommCell. Also, keep in mind that the CommServe and SRM Server must be installed and running (on the same computer), before you can install the Agent. Close all applications and disable any programs that run automatically, including anti-virus, screen savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation. Ensure there is an available license on the CommServe for the Agent. Verify that you have the software installation disc that is appropriate to the destination computer s operating system. Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider. Firewall If the CommServe Server, MediaAgent and/or Clients communicate across two-way firewall(s):

8 Page 8 of 41 Ensure port 8400 is allowed connections through the firewall. In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall. For information on configuring the range of ports, see Port Requirements for Two-way Firewall. If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s): Identify a range of outbound ports (consecutive or discrete) for use by the software. For information on configuring the range of ports, see Port Requirements for One-way Firewall. If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer. Multi Instancing By utilizing the Multi Instancing feature, the same Agent and MediaAgent software can be installed on a computer multiple times, but not all components support Multi Instancing. This limitation can apply to the component you are installing, or to one already installed on the computer. Prior to installing multiple instances of a software component on the same computer, carefully review the information contained in Multi Instancing, and follow the instructions in the How to Use Multi Instancing section for the additional screens that will appear during the installation process. Install Checklist Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder. 1. Install folder location for SRM software: See Select Components for Installation for more information. 2. If the CommServe Server and the client computer communicate across a firewall: Firewall ports: Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall: Keep Alive Interval minutes: Hostname for outgoing tunnel connections: Tunnel Initialization Interval seconds: See Firewall Configuration for more information. 3. CommServe Host Name or the CommServe IP address: See Configuration of Other Installation Options for more information. 4. Client computer's Host name (NetBIOS name) or IP address See Configuration of Other Installation Options for more information. 5. Job result folder location:

9 Page 9 of 41 If necessary, Name and Password for the specified folder: See Configuration of Other Installation Options for more information. 6. Client Group to which this Client will be associated: See Client Group Selection for more information. 7. Time and frequency for Install of Automatic Updates: See Schedule Automatic Update for more information. Before You Begin Log on to the client as local Administrator or as a member of the Administrators group on that computer. Install Procedure Getting Started 1. Place the software installation disc for the Windows platform into the disc drive. After a few seconds, the installation program is launched. If the installation program does not launch automatically: Click the Start button on the Windows task bar, and then click Run. Browse to the installation disc drive, select Setup.exe, click Open, then click OK. NOTES If you are installing on a x64 version of Windows 2008 Server Core R2, go to the AMD64 folder and run Setup.exe. 2. In this screen, you choose the language you want to use during installation. Click the down arrow, select the desired language from the pull-down list, and click Next to continue. 3. Select the option to install software. NOTES This screen will only appear when the ballow32bitinstallon64bit registry key has been created and enabled on this computer. 4. Select the option to install software on this computer. NOTES The options that appear on this screen depend on the

10 Page 10 of 41 computer in which the software is being installed. 5. Read the Welcome screen. Click Next to continue, if no other applications are running. 6. Read the virus scanning software warning. Click OK to continue, if virus scanning software is disabled. 7. Read the license agreement, then select I accept the terms in the license agreement. Click Next to continue. Select Components for Installation 8. Select the component(s) to install. NOTES Your screen may look different from the example shown. Components that either have already been installed, or which cannot be installed, will be dimmed. Hover over the component for additional details. The Special Registry Keys In Use field will be enabled when GalaxyInstallerFlags registry keys have been enabled on this computer. Hover over the field to see which keys have been set, as well as their values. For more information, see Registry Keys. Click Next to continue. To install the SRM NAS File System Agent, expand the SRM folder and then select SRM NAS Agent. 9. Specify the location where you want to install the software. NOTES Do not install the software to a mapped network drive. Do not use the following characters when specifying the destination path: / : *? " < > It is recommended that you use alphanumeric characters only. If you intend to install other components on this computer, the selected installation directory will be automatically used for that software as well. If a component has already been installed, this screen may not be displayed if the installer can use the same install location as previously used. If you intend to use the SnapProtect feature for Windows File System idataagent, the agent

11 Page 11 of 41 should be installed on a non-system drive and not a filer volume. Click Browse to change directories. Click Next to continue. Firewall Configuration 10. Select from the following: If this Client communicates with the CommServe Server and/or MediaAgent across a firewall, select, configure firewall services, and then click Next to continue. Proceed to the next Step. If firewall configuration is not required, click, do not configure firewall services and then click Next to continue. Proceed to the next section. NOTES Operating systems, such as Windows 2008 and Windows Vista, may have more than one profile present. When you select to configure firewall services, verify that firewall settings are not enabled in the profile(s). If the system detects firewall settings are present in the profile(s), you must select from the following: Disable firewall for ALL profiles: Employ caution when choosing this option; firewall settings will be disabled in all profiles. This requires a system reboot; installation automatically resumes after reboot., Firewall is not enabled: Select this option if your firewall settings allow communication with the CommServe computer. Click Back to configure firewall services. 11. Click the Specify list of machine across the firewall option and then specify the list of hosts separated from this computer by a firewall. Make sure you correctly describe whether the firewall allows two-way communication (but on a limited range of ports), or one-way communication (with either only remote host being able to make connections to this computer, or vice versa). For all one-way firewalls allowing incoming connections and those one-way firewalls allowing outgoing connections without additional port filtering, skip this step. Click Next to continue. NOTES Consider the following:

12 Page 12 of 41 On the CommServe Server, this list should include all the MediaAgents and Clients that are on the other side of the firewall. On the MediaAgents/Clients this should include the CommServe computer, and any other Clients/MediaAgents on the other side of the firewall with which communications will be established. For each machine on the other side of the firewall that you want to configure, choose the type of firewall configuration based on the firewall setup in your environment. Choose from the following options: Click on 2-way firewall if you can open certain ports as bi-directional ports. Click 1-way firewall; host is reachable from this machine on the machine that is on the secure side of the firewall. Click 1-way firewall; host is NOT reachable from this machine on the machine that is on the public / DMZ side of the firewall. If you wish to communicate with computers in a clustered environment, ensure that you add the Host Name/IP Address of all physical nodes in the cluster (even if no CommCell components are installed) and all the virtual nodes in which CommCell components are installed. Type the host name or the IP address and the GxCVD port number of the host name, and click Add to place it in the Host Name/IP Address List. 12. Click the Specify list of restricted open ports option and then specify the port range. Add the starting and ending port range and then click Add to place it in the Open Port List. Repeat as needed. If firewall separating this computer from others allows incoming connections, but these connections can be made only on a limited set of ports, then configure the appropriate port range here. For all other scenarios, skip this step. te that if you do not specify hostname(s) as well as port number(s), then the firewall services will not be configured. NOTES Typically in a two-way firewall, the open ports must be indicated for all computers. In a oneway firewall, the ports must be specified on computers in the open side, if they are open in a restricted way. te that the port ranges are not required for computers that are fully closed in the one-way firewall. For example, laptops which are configured as clients in the Workstation Backup Agent.

13 Page 13 of 41 In a clustered environment, make sure the firewall ports specified here are open for communication on all the physical nodes as well as the virtual nodes. Click Next to continue. 13. If desired, modify the Keep Alive interval. Click Next to continue. 14. Optionally, select Advanced Firewall Configuration and specify a local host name interface to use for outgoing tunnel connections through the firewall. Otherwise, the interface and port is automatically selected for you by the OS. Click Next to continue. 15. If desired, modify the Tunnel Initialization interval. Click Next to continue. Configuration of Other Installation Options 16. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com) NOTES

14 Page 14 of 41 Do not use spaces when specifying a new name for the CommServe Host Name. If a component has already been installed, this screen will not be displayed; instead, the installer will use the same Server Name as previously specified. Click Next to continue. 17. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell. NOTES This window is only displayed when the Require Authentication for Agent Installation option is selected in the CommCell Properties. Users must belong to a User Group with Administrative Management capabilities to enable this feature. For more information, see Authentication for Agent Installs. Click Next to continue. 18. Enter the following: The local (NetBIOS) name of the client computer. The TCP/IP IP host name of the NIC that the client computer must use to communicate with the CommServe Server. NOTES Do not use spaces when specifying a new name for the Client. The default network interface name of the client computer is displayed if the computer has only one network interface. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server. If a component has already been installed, this screen will not be displayed; instead, the install program will use the same name as previously specified. Click Next to continue. 19. Specify the following and click Next to continue: Type the location of the client's job results directory, or click Browse. NOTES

15 Page 15 of 41 The Agent uses the job results directory to store the client's backup and restore job results. UNC paths are supported for Windows and Exchange Database 2007 idataagents with Cluster Continuous Replication (CCR), but cannot be specified on this screen. After the installation completes, you can change the Job Results path to a UNC path. For comprehensive information on UNC paths, see Using UNC Paths for Job Results Directory. UNC paths are supported for job results directory by the Exchange Database idataagent 2007 and above when configured in Cluster Continuous Replicator environment. Also note that Windows idataagent is also supported when configured in this environment. Client Group Selection 20. Select a Client Group from the list. Click Next to continue. NOTES This screen will be displayed only if Client Groups are configured in the CommCell Console. For more information, see Client Computer Groups. 21. Select Download Pack(s) and Install to download and install the latest service packs and post packs from the software provider. NOTES Internet connectivity is required to download updates. This step is applicable when installing on the first instance. Updates are downloaded to the following directory: <software installation>/base/temp/downloadedpacks. They are launched silently and installed automatically for the first instance. Click Next to continue. Verify Summary of Install Options 22. Verify the summary of selected options. NOTES

16 Page 16 of 41 The Summary on your screen should reflect the components you selected for install, and may look different from the example shown. Click Next to continue or Back to change any of the options. The install program now starts copying the software to the computer. This step may take several minutes to complete. 23. The System Reboot message may be displayed. If so, select one of the following: Skip Reboot This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As these files are not critical for this installation, you may skip the reboot and continue the installation and reboot the computer at a later time. Reboot w If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot w is displayed without the Skip Reboot option, reboot the computer at this point. The install program will automatically continue after the reboot. Exit Setup If you want to exit the install program, click Exit Setup. Schedule Automatic Update 24. If necessary, select this option to schedule an automatic installation of software updates. NOTES Install Updates Schedule allows automatic installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console. To avoid conflict, do not schedule the automatic installation of software updates to occur at the same time as the automatic FTP downloading of software updates. You may be prompted to reboot the computer before restarting services. If a component has already been installed, this screen will not be displayed; instead, the installer will use the same option as previously

17 Page 17 of 41 specified. Click Next to continue. Install Remaining Cluster des 25. If you are installing/upgrading the software on the physical node in a clustered environment, use this option to install/upgrade the software on the remaining physical nodes of the cluster. To install/upgrade the software on the remaining nodes of the cluster, click. To complete the install/upgrade for this node only, click. See Install/Upgrade Remaining Cluster des for step-by-step instructions. Setup Complete 26. Click Next to continue. NOTES Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling. 27. Setup displays the successfully installed components. NOTES The Setup Complete message displayed on your screen will reflect the components you installed, and may look different from the example shown. If you install an Agent with the CommCell Console open, you need to refresh the CommCell Console (F5) to see the new Agents. If Reboot w button is displayed make sure to reboot the computer before performing any other operations from the computer. Click Finish to close the install program. The installation is now complete. Post-Install Considerations General

18 Page 18 of 41 Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component. Agent Specific After installing the SRM NAS Agent, you need to add a SRM NAS Filer that has the required data. For step-by-step instructions, see Add NAS Filer. If you configure the same NAS filer multiple times, with different names, SRM will treat them as separate filers, as long as the names are resolvable Valid CIFS credentials are required for data archiving.

19 Page 19 of 41 Data Collection Topics How To Troubleshoot Related Topics Overview Scheduling Data Collection jobs Considerations Best Practices Overview After installing the SRM Server, the SRM Agent software must be installed on your selected client computers before you can collect data from them. When data collection is performed, this information populates the SQL database on the SRM Server's repository with current statistics, for the purpose of generating summaries and reports. When you configure data collection for a client, from the SRM node you have the options of choosing which Agent(s) to use (if more than one is available on the client), the type of data collection to be performed (determined by selecting either an Analysis or Discovery Job Type), a Schedule Policy, and a start date. You can exclude volumes and directories from the data collection process for Subclients filters. You can also balance the collection load across different subclients, each with a different schedule policy. Data collection jobs run automatically according to the parameters you have selected, and will appear in the Job Controller as a scheduled job. The system can also be configured to generate advisories, a brief text message describing an actual or potential problem and the suggested corrective action. Reports and SRM Summaries viewed through the console are generated from the data collected and stored on the SRM Server. Schedule your first reports to run after your first data collection jobs have completed. te that data collection and Report Generation jobs are scheduled independently, at different times and intervals. Thus, you can, for example, collect data nightly, hourly, or on-demand, but generate reports only once per week if desired. For more information about summaries, see SRM Summaries. For more information about running and viewing reports, see Reports. Scheduling Data Collection jobs Data Collection jobs can be scheduled to regularly collect data at specified intervals. Data Collection jobs can be scheduled from the SRM agent level in the CommCell Browser. In addition, Analysis Data Collection jobs can be scheduled for the individual subclients at the subclient level. When the Data Collection job is scheduled the job will be displayed in the Job Controller. After the successful completion of the Data Collection job, the client information is gathered at the SRM Server and the job status is shown as completed in the Job Controller. For more information on scheduling, see Scheduling. For stepby-step instructions on scheduling a Data Collection job see Run/Schedule Data Collection. Considerations Data Collection is not performed for mounted network drives, volumes, or directories. If you want to collect data for network file systems, install the appropriate SRM Agent on the local computer for those file systems. SRM Exchange Agent based Analysis Data Collection job will report storage groups only if the storage groups are mounted. For NAS Data Collection, all CIFS and NFS content will be included as content in the default subclient, unless some or all of it is specifically listed as content in a user-defined subclient. For NAS Data Collection, if subclient SubB is child of subclient SubA meaning that SubB's paths are

20 Page 20 of 41 contained in paths of SubA, then when collecting SubA none of the contained paths of SubB will be collected. Instead they will be collected by Data Collection of SubB. For UNIX file systems, all mount points (comprised of a logical volume or partition) will be included as content in the default subclient, unless they are specifically listed as content in a user-defined subclient. Consider this example: You have created a subclient named sub1. You have defined a directory named /mount_points as contents for sub1. Within /mount_points there are three mount points, mnt1, mnt2, and mnt3. Data will not be collected on those three mount points as part of sub1; instead, they are part of the content of the default subclient. To collect data on those mount points as part of sub1, you must specify each mount point, /mount_points/mnt1, /mount_points/mnt2, and /mount_points/mnt3, as content for sub1. If you would like to configure the SRM Exchange Agent for cross-domain mailbox access for data collection purposes, this can be accomplished by creating the AdServerList key in the registry. After adding, editing or removing a subclient, you must run an Analysis data collection job on all subclients associated with an agent for reports to reflect the changes. For the SRM Agent for SharePoint only - ensure that all necessary SharePoint services are running and that the configuration and content databases are online; otherwise, installation may appear successful, but a subsequent Data Collection will fail. Best Practices Oracle Consider the following configuration items before running data collection from the Oracle Agent: Verify that Oracle databases are in OPEN status before running a data collection job. Verify that the Oracle databases are running properly, and that there are no database-related memory issues. Verify that the shared_pool_size parameter in the init<sid>.ora file is set to the maximum valid value so that SQL queries can run successfully for data collection. Data collection by the appropriate file system SRM Agent must be scheduled to occur before data collection by the SRM Oracle Agent. SharePoint "Usage Analysis" must be enabled in SharePoint for SRM to collect data about hits, for those reports that include this information. Refer to Microsoft SharePoint documentation for information about enabling "Usage Analysis". Solaris Ensure that the NFS client specifies the soft option when mounting NFS shares, or else data collection for NFS data will hang whenever the NFS server is down or not accessible. Also, increase the value for the retrans and timeo options; this will compensate for the soft option limiting the number of retries that the client can attempt to access the NFS server. Windows File System Activating Data Classification will decrease the amount of time required to perform an Analysis level data collection job for the SRM Windows File System Agent. NAS Configure NAS filer (including NetApp vfiler, EMC Celerra CIFS Servers and Data Movers) with DNS server in a way that reverse DNS lookup (from NAS filer to SRM NAS proxy) is resolved. If that is not the case then CIFS connection or NFS mount from SRM NAS proxy to NAS filer will fail. Back to Top

21 Page 21 of 41 Data Collection - How To Topics How To Troubleshoot Related Topics Run/Schedule a Data Collection Job for an SRM Instance, Agent or Subclient Required Capability: See Capabilities and Permitted Actions To run/schedule a Data Collection job for an SRM instance, agent or subclient: 1. From the CommCell Browser, right-click the SRM instance, agent or subclient, and then click Data Collection from the short-cut menu. 2. From the Schedule Data Collection Job dialog box, select the agent for which you want to run the Data Collection job from the Agent list. (This option is not applicable at the SRM agent and subclient levels.) 3. Choose the Job Type. (This option is not applicable at the SRM subclient level.) 4. If you selected "Analysis" in the previous step, and if the agent has more than one subclient, click the name of the subclient you want from the Subclient list. (This option is not applicable at the SRM subclient level.) 5. Choose Schedule or Run Immediately from the Job Initiation area. 6. Configure any other options as appropriate. 7. Click OK. If you have selected the Run Immediately option, you can track the progress of the job from the Job Controller window. For more information on Scheduling, see Scheduling.

22 Page 22 of 41 SRM Summaries Topics How To Related Topics Overview Accessing Summaries SRM Exchange Agent SRM NetWare Proxy Agent SRM NAS Agent SRM Oracle Agent SRM SharePoint Agent SRM SQL Agent SRM UNIX File System Agent SRM Windows File System Agent Enterprise Viewer Overview When you select an SRM entity in the CommCell Console, its summary information appears in the main window. The summary information depends on the selected entity as follows: SRM Agent level Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. For more information, see Advisories. Properties: For some of the agents physical information including name, state (enabled or disabled) last modification time and last analysis times, etc. are displayed. Charts: Some of the agents also display unique charts that include statistics, tabular data, and images such as bar graphs. See Accessing Summaries section below. SRM Subclient level Charts: Each agent display unique charts that provide statistics, tabular data, and/or images such as bar graphs of all subclients within the specific Agent. See Accessing Summaries section below. Default and user defined Subclient level Properties: Physical Information including name, state (enabled or disabled) last modification time and last analysis times, etc. are displayed. Charts: Each agent display unique charts that include statistics, tabular data, and images such as bar graphs and pie charts. See, Accessing Summaries section below. Depending on the selection of Agent, summary on various levels are displayed like: Volumes, Shares, Devices, Pools, etc. For more information see, Accessing Summaries section below. Accessing Summaries While viewing summary, data rows in tables can be sorted by any one of the columns listed in that summary. A major information section can be expanded or closed by clicking the expand button. The following section describes the available summary types for each agent at different levels in the CommCell Console: SRM Exchange Agent Agent - Summary information includes Properties and Advisories at the agent level. Subclient level - Charts: Current Capacity by Exchange Subclient

23 Page 23 of 41 For more information on the Report Name associated with the displayed charts, see SRM Exchange Agent Reports. User defined or default Subclient level - Properties are included in summary information at this level. Storage Groups level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Current Capacity by Exchange Storage Group are also available in summary information. Each storage group also display Properties including physical information like Name, Transaction Log, System Path, Circular Logging, etc. Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Storage Group Storage Usage History. Each store also displays Properties including Name, Database Path, Mount status, warning quota, etc. Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Unique charts that include statistics, tabular data, and images such as bar graphs on the basis of the type of database are displayed, e.g. for Mailbox Databases, the charts would be displayed on the basis of Mailbox Storage Database Usage History and Mailbox Distribution by Size however for Public Folder databases it would be Public Folder Database Storage Usage History and Public Folder Distribution by Size. The storage group level may display Physical devices if available. For step-by-step instructions, see View Summaries. SRM NetWare Proxy Agent Agent - Summary information includes Advisories at the agent level. Subclient level - Charts: NetWare Volume Usage by Subclient For more information on the Report Name associated with the displayed charts, see SRM NetWare Proxy Agent Reports. User defined or default Subclient level - Properties and Charts including File Distribution by Size, File Distribution by Type, File Distribution by Access Time and File Distribution by Modification Time are available in summary information at this level. Devices level - Charts: Storage Capacity per NetWare Device. Each Device also displays Properties including physical information like Name, Sector Count, Sector Size, Capacity, etc. in addition to Charts displaying Storage Capacity per Partition. The device level may also display Physical devices if available. Pools level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Storage Pool Capacity are available in summary information. Each pool also displays Properties including physical information like Name, Used Space, Free Space, Cost Category, etc. Volumes level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Storage Usage per NetWare Volume are available in summary information. Each volume also displays Properties including physical information like Name, NDS Location, Status, Used Space, etc. Advisories: Advisory information including severity level, time stamp, and a brief description is also displayed. Unique charts that include statistics, tabular data, and images such as bar graphs on the basis of Usage History, File Distribution by Size, File Distribution by Type, File Distribution by Access Time, File Distribution by Modification Time are displayed. The volume level may also display Physical devices if available. For step-by-step instructions, see View Summaries. SRM NAS Agent Agent - Summary information includes Properties, Advisories and Charts such as NAS Filer Usage

24 Page 24 of 41 History, File Distribution by Size, File Distribution by Access Time, File Distribution by Modification Time at the agent level. Subclient level - Charts: File System Usage by Subclient For more information on the Report Name associated with the displayed charts, see SRM NAS Agent Reports. User defined or default Subclient level - Properties and Charts: File Distribution by Size, File Distribution by Access Time, File Distribution by Modification Time are included in summary information at this level. Network Shares level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying NAS Usage Statistics are available in summary information. Each Share also displays Properties including physical information like Path, Protocol, Free Space on Volume, etc. apart form Advisories. Data Movers level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying NAS Usage Statistics and Data Mover Uptime Statistics are available in summary information. This level will only be visible for Celerra filers. Each Data Mover has various severs that display different summary information. Summary includes - Properties including physical information like Name, EMC ID, Status, Type, etc. Advisories including severity level, the time stamp, and a brief description is displayed. Charts displaying Usage History, NAS Usage Statistics, File Distribution by Size, File Distribution by Access Time and File Distribution by Modification Time are available in summary information. Data Mover summary also includes the available CIFS Servers, Mount Points, Hostnames, and Network Shares. File Systems level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying NAS Usage Statistics File Distribution by Size, File Distribution by Access Time and File Distribution by Modification Time are available in summary information. Each File System also displays Properties including physical information like Name, EMC ID, Status, Type, etc. apart form Advisories and Charts at the File System level. Quota Trees and Auxiliary Information is also available as summary at this level, depending upon the availability. Storage Pools level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Storage Pool Capacity are available in summary information. Each pool also displays Properties including physical information like Name, EMC ID, Type, Description, etc. Volumes, File Systems and SnapSure SavVol is also displayed as summary at this level depending on the availability. Storage Systems level - Displays summary in tabular format showing Name, EMC ID, Status, Type, Model, Serial Number, Disk Count for the storage system. Meta Volumes level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. For step-by-step instructions, see View Summaries. SRM Oracle Agent Agent - Summary information includes Properties, Advisories and Charts such as Storage Usage per Oracle Database at the agent level. Subclient level - Charts: Storage Usage by Subclient For more information on the Report Name associated with the displayed charts, see SRM Oracle Agent Reports. User defined or default Subclient level - Properties and Charts including Storage Usage per Oracle Tablespace are available in summary information at this level. Instances level - Advisories: Advisory information including severity level, the time stamp, and a brief

25 Page 25 of 41 description is displayed. Charts displaying Storage Usage per Oracle Instance are available in summary information. Each Instance also displays Properties including physical information like Name, Hostname, Startup Time, Redo Log Size, etc. as summary at this level. Tablespaces level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Storage Usage per Oracle Tablespace are available in summary information. Users level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Storage Usage per Oracle User are available in summary information. For step-by-step instructions, see View Summaries. SRM SharePoint Agent Agent - Summary information includes Advisories at the agent level. Subclient level - Charts: Storage Utilization per Subclient For more information on the Report Name associated with the displayed charts, see SRM SharePoint Agent Reports. User defined or default Subclient level - Properties and Charts: Storage Utilization per Virtual Server are included in summary information at this level. Virtual Servers - Advisories: Advisory information including level, the time stamp, and a brief description is displayed. Charts displaying Virtual Server Alias Usage and Storage Utilization and Site Count per Virtual Server are available in summary information. For step-by-step instructions, see View Summaries. SRM SQL Agent Agent - Summary information includes Advisories and Charts such as Current Utilization by SQL Server Instance at the agent level. Subclient level - Charts: Current Utilization by Subclient For more information on the Report Name associated with the displayed charts, see SRM SQL Server Agent Reports. User defined or default Subclient level - Properties and Charts: Current Utilization by SQL Server Database is included in summary information at this level. Instance level - Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Usage History are available in summary information. Databases level - Advisory information including severity level, the time-stamp, and a brief description is displayed. Charts displaying Current Utilization by SQL Server Database are available in summary information. Each database also displays Properties including physical information like Name, Owner, Creation Date, Status, etc. Unique charts that include statistics, tabular data, and images such as bar graphs on the basis of Usage History, Largest Table, Largest Indexes, Largest Files are displayed. The databases may also display Physical devices and Mirror Snapshots if available. For step-by-step instructions, see View Summaries. SRM UNIX File System Agent Agent - Summary information includes Advisories at the agent level. Subclient level - Charts: File System Usage by Subclient. The chart displays details like Name, Average Tree Depth, Maximum Tree Depth, File Count, Directory Count, Average File Size, etc about the selected subclient. For more information on the Report Name associated with the displayed charts, see SRM UNIX File System Agent Reports.

26 Page 26 of 41 User defined or default Subclient level - Properties and Charts including File Distribution by Size, File Distribution by Type, File Distribution by Access Time, File Distribution by Modification Time are available in summary information at this level. Volume Groups level - Summary information includes Advisories and Charts displaying Current Capacity by Volume Group at this level. The chart displays detail like Name, Volume Group Manager, Capacity, Allocated Space, Unallocated Space, Access Mode, Logical Volume Count, Physical Volume Count, Physical Extent Count for the selected volume group. Each volume also displays Properties including physical information like Name, Volume Group Manager, Capacity, Allocated Space, etc. are displayed. Advisories: Advisory information including severity level, time stamp, and a brief description is also displayed. Unique charts that include statistics, tabular data, and images such as bar graphs on the basis of Logical Volume Distribution by Size are also displayed. The volume level may also display Physical Devices and Logical Volumes if available. File Systems level - Advisories: Advisory information including severity level, the time stamp, and a brief description is displayed. Charts displaying Current File System Usage and File System Capacity are available in summary information. The Current File System Usage chart displays detail like Name, Type, Average Tree Depth, Maximum Tree Depth, File Count, Directory Count, Average File Size, Maximum File Size, Average Directory Count and Sparse File Count for the selected volume group. The File System Capacity chart displays detail like Name, Type, Mount Point, Used Space, Free Space, Capacity, Percent Used and Percent Free for the selected volume group. Each File System also displays Properties including physical information like Name, Type, Mount Point, Used Space, etc. apart form Advisories and Charts including Usage History, File Distribution by Size, File Distribution by Type, File Distribution by Access Time, File Distribution by Modification Time are available in summary information at the this level. The file system level may also display Physical Devices if available. Shares level - Summary information includes Advisories with severity level, the time stamp, and a brief description. The summary includes Name, Path and Used Space of the selected shares. For step-by-step instructions, see View Summaries. SRM Windows File System Agent Agent - Summary information includes Advisories at the agent level. Subclient level - Charts: File System Usage by Subclient For more information on the Report Name associated with the displayed charts, see SRM Windows File System Agent Reports. User defined or default Subclient level - Properties and Charts including File Distribution by Size, File Distribution by Type, File Distribution by Access Time and File Distribution by Modification Time are available in summary information at this level. Volume level - Summary information includes Advisories and Charts including Current file System Usage and File System Capacity at this level. Shares level - Summary information includes Advisories with severity level, the time stamp, and a brief description. For step-by-step instructions, see View Summaries. Enterprise Viewer The Enterprise Viewer displays the physical assets of SharePoint and NAS File Server Clients in a single location. Summaries can be viewed by expanding the nodes and clicking the assets displayed in the Enterprise Viewer. Larger enterprises with many NAS File Servers will find it convenient that the Enterprise Viewer

27 Page 27 of 41 displays all NAS assets in one place. A SharePoint Farm can have multiple Web Servers and thus multiple Agents and Clients, unlike other SRM Clients which typically involve a single computer. Rather than searching the Client Manager for every involved Agent and Client, the Enterprise Viewer allows you to review all assets and Summary information for the entire SharePoint Farm in one place. Back to Top SRM Summaries - How To Topics How To Related Topics View Summaries Required Capability: See Capabilities and Permitted Actions To view summaries: 1. From the CommCell Browser, select the SRM entity for which you want to view summaries. You may expand an entity to view the summary associated with the next level. Summary information is available for client, agent, subclient, volumes, shares, devices, etc. For more information on available summaries for each agent see, Accessing Summaries. 2. The summary information associated with the selected entity will appear in the main window.

28 Page 28 of 41 SRM NAS Agent Reports Topics How To Related Topics Several reports are available for NAS File Servers, which are categorized as follows: NetApp EMC Celerra Vendor Independent The following table enumerates the reports, along with a short description. It also indicates whether an Analysis level Data Collection Job is required to produce complete and accurate data for each report. For step-by-step instructions, see Run/Schedule a Report. NetApp Report Name Description Is Analysis level Data Collection Required? Aggregate Volumes Capacity History [NetApp] Aggregate Volumes Current Capacity [NetApp] Aggregate Volumes Virtual Capacity [NetApp] File Distribution by Access Time by vfiler [NetApp] File Distribution by Modification Time by vfiler [NetApp] File Distribution by Size by vfiler [NetApp] File Distribution by Type by vfiler [NetApp] Historical view of capacity of all aggregate volumes (total, used, free), %used, and includes aggregate name and type (traditional or aggregate). Similar to Aggregate Volumes Current Capacity [NetApp] report, but tracks changes in free and used space over time. Use to predict future use patterns for capacity planning. Capacity of all aggregate volumes (total, used, free) and includes aggregate name and type (traditional or aggregate). Use to report on current capacity of a NetApp filer. A list of aggregate volumes on NAS filers that displays used space, and total, virtual, and remaining capacity for each aggregate. Use to identify overcommitted aggregate volumes with virtual capacity that exceeds physical capacity. For each NAS file server and file system, categorization of files per vfiler based on their size and age (by last access time). Use it to identify file systems, on a per vfiler basis, with many unused files; these are good candidates for migration archiving tools such as File Archiver for Windows Agent. For each NAS file server and file system, categorization of files per vfiler based on their size and age (by modification time). Use it to identify file systems, on a per vfiler basis, which should be backed up frequently (i.e., those with many recently modified files). Files in each NAS file server, per vfiler, by size. This information may be useful when tuning file system or RAID parameters (such as block size), or when planning for backups. Files on each vfiler by File Category. Use it to identify vfilers with many multimedia, archive, or document files or applications (e.g., executables).

29 Page 29 of 41 File Systems Current Capacity [NetApp] Qtrees [NetApp] RAID Disks [NetApp] Snapshots [NetApp] vfilers [NetApp] vfilers Current Used Space [NetApp] vfilers Used Space History [NetApp] File system capacity on each logical and aggregate volume of NetApp filer, and aggregate capacity on each filer level -- total, used, free, %used, %free space. The report includes flexible logical volumes contained in the aggregate and traditional logical volumes. Use it to identify logical volumes that require additional storage. A list of Qtrees on NetApp filers and their properties. That includes Qtrees on the logical volume level. Properties show qtree security style (Unix, NTFS, or Mixed), and whether Opportunistic Locking is enabled. A list of RAID disks on NAS filers that displays disk volume, pool the disk is in, RPM (5400, 7200, 10000, or N/A), checksum compatibility (zoned, zoned/block, or none), disk size in bytes, and RAID state (e.g., partner, broken, zeroing, spare, copy, pending, reconstructing, present, etc.) for each. Use to identify spare disks, which are disks not currently used in any aggregate, and disk parameters. Describes the volume snapshots present on NetApp filers. Displays the logical volume, snapshot name, date snapshot was created, snapshot status (normal or busy), and cumulative/incremental used and total spaces. Used space is expressed as a % of overall spaced used on the volume. Total space is expressed as a % of total volume size. Cumulative space is calculated from spaces of all snapshots, including this one. Incremental space is based on space of only this snapshot. Lists vfilers of NetApp filers with MultiStore license. Displays the vfiler name, vfiler status (running, stopped, inconsistent, defunct), indication of whether the vfiler is default vfiler, and IPspace to which the vfiler belongs. Lists the amount of used space (in MB) for each vfiler. Used space is calculated as the amount of space used by the vfiler's storage resources (logical volumes and Qtrees). Historical view of used space for all vfilers. Similar to vfilers Current Used Space [NetApp] report, but tracks changes in used space over time. Use to predict future use patterns for capacity planning. EMC Celerra Report Name Description Is Analysis level Data Collection Required? Checkpoints [Celerra] Lists the File System checkpoints that are present on an EMC Celerra. Displays the control station name, production file system, checkpoint name, name of SnapSure SavVol, when checkpoint was created, percentage of SavVol space used by checkpoints, status showing whether checkpoint is being used, and full mark SavVol-usage point (when reached, sends a warning message to system log and auto-extends the SavVol as space permits).

30 Page 30 of 41 Data Movers [Celerra] Disk Volumes [Celerra] File Distribution by Access Time by VDM [Celerra] File Distribution by Modification Time by VDM [Celerra] File Distribution by Size by VDM [Celerra] File Distribution by Type by VDM [Celerra] File Systems Current Capacity [Celerra] Metavolumes [Celerra] Quota Configuration [Celerra] Lists the physical Data Movers that are present on an EMC Celerra. Displays type of Data Mover (NAS, Standby, RDF), its role (primary or standby; primary Data Mover must have NAS type and standby can be Standby or RDF), model, status (enabled or disabled), OS version, failover policy of primary Data Mover (n/a, local, auto, retry), and date of last reboot. Lists the disk volumes that are present on an EMC Celerra. It identifies disks not currently used by any Meta Volume that are created by an administrator or by AVM. Displays the name of control station, name, type, and capacity of disk volume, and if the disk volume is in use. Files in each NAS file server and file system, categorization of files per VDM based on their size and age (by last access time). Use it to identify NAS file servers, on a per VDM basis, with many unused files. These are good candidates for migration archiving tools such as File Archiver for Windows Agent. Files in each NAS file server and file system, categorization of files per VDM based on their size and age (by modification time). Use it to identify NAS file servers, on a per VDM basis, which should be backed up frequently (i.e., those with many recently modified files). Files in each NAS file server, per VDM, by size. This information may be useful when tuning file system or RAID parameters (such as block size), or when planning for backups. Files in each NAS file server, per VDM, by File Type. Use it to identify NAS file servers, on a per VDM basis, that contain many multimedia, archive, or document files or applications (e.g., executables). File system capacity on each EMC file system and Storage Pool of Celerra, and aggregate capacity on each Celerra level -- total, used, free, %used, %free space. The report includes EMC file systems contained in the Storage Pool and EMC file systems created from Meta Volumes. Use it to identify EMC file systems that require additional storage. Lists the Meta Volumes and Pool volumes that are present on an EMC Celerra. Displays the control station name, name and capacity of the volume, type and name of volume's client (volume or File System). Meta Volumes that have no clients are not listed. Displays quota configurations of file systems and quota trees on an EMC Celerra. Displays the file system, quota tree path, quota policy (blocks or filesize), user and group quotas (on or off), block and inode grace periods (time when users/groups can exceed soft limits before hard-limit behavior takes effect), user and group block soft and hard limits, user and group inode soft and hard limits, deny disk space state to enforce hard user or group quotas; not applicable to quota tree quotas (enable or disable), state of logging of system events when a hard or soft block limit is reached (enable or disable), logging of system events when quota checks starts or ends (enable or disable).

31 Page 31 of 41 Quota Trees [Celerra] Storage Pools Capacity History [Celerra] Storage Pools Current Capacity [Celerra] Storage Pools Virtual Capacity [Celerra] VDM Capacity History [Celerra] VDM File Systems Current Capacity [Celerra] Virtual Data Movers [Celerra] Lists the Quota Trees that are present on an EMC Celerra. Displays the control station name, name of file system, and quota tree path. Historical view of capacity of all storage pools (total, used, free), and remaining potential capacity. Similar to Storage Pools Current Capacity [Celerra] report, but tracks changes in free and used space over time. Use to predict future use patterns for capacity planning. Displays storage pool name, type (system-defined or userdefined), automatic extension, obtain unused disk volumes, current capacity (total, used, free), and remaining potential capacity (available space that can be added to the storage pool) of an EMC Celerra. Use to report on current capacity of a storage pool. A list of system-defined storage pools of an EMC Celerra that displays used space, total capacity, virtual capacity (sum of max capacity of file systems created from this storage pool), and remaining capacity (aggregate of unused disk and nondisk volumes), remaining post-committed (remaining capacity of storage pool after virtual capacity is fully used; can be negative when there is not enough remaining capacity to fulfill storage commitment), and percent committed (% of virtual capacity relative to physical capacity). Use to identify the storage pools with virtual capacity that exceeds physical capacity. Historical view of capacity of all file systems (total, used, free) mounted on VDMs of an EMC Celerra. Similar to VDM File Systems Current Capacity [Celerra] report, but tracks changes in free and used space over time. Use to predict future use patterns for capacity planning Capacity of all file systems (total, used, free) mounted on VDMs of an EMC Celerra, including file systems created from Storage Pool and from Meta Volume. For each VDM File System displays File System name, total space, used space, free space, % of file system currently in use and the % that is free is displayed. For file systems created from Storage Pool displays Storage Pool name and type (for file systems created form Storage Pool), total space, used space, free space, and percent used and percent free. Use to report on current capacity of file systems mounted on VDMs. Lists the VDMs that are present on an EMC Celerra. Displays the physical data mover that hosts it and its status (enabled or disabled). Vendor Independent Report Name Description Is Analysis level Data Collection Required? Capacity History Historical view of space (total, used, free), %used, %free per Enterprise, Client Group, and Filer that is attached to this

32 Page 32 of 41 CIFS Statistics Current File System Usage by Subclient Exchange Personal Folders File Distribution by Access Time File Distribution by Access Time by Subclient File Distribution by Modification Time File Distribution by Modification Time by Subclient File Distribution by Size File Distribution by Size by Subclient File Distribution by Type File Distribution by Type by Subclient File Shares client. Use to predict future use patterns for capacity planning. Lists the various CIFS request types that have been processed since the last time CIFS services were restarted on the NAS file server (NetApp), Data Mover (EMC Celerra), or VDM (Celerra). Space used per subclient on each NAS file server. Use it to analyze NAS file server usage patterns, on a per subclient basis. Shows file statistics for Exchange PST files. Displays number of PST files, total average, and max file size of the PST files. For each NAS file server and file system, categorization of files based on their size and age (by last access time). Use it to identify file systems with many unused files; these are good candidates for migration archiving tools such as File Archiver for Windows Agent. For each NAS file server and file system, categorization of files per subclient based on their size and age (by last access time). Use it to identify NAS file servers, on a per subclient basis, with many unused files; these are good candidates for migration archiving tools such as File Archiver for Windows Agent. For each NAS file server and file system, categorization of files based on their size and age (by modification time). Use it to identify file systems which should be backed up frequently (i.e., those with many recently modified files.) For each NAS file server and file system, categorization of files per subclient based on their size and age (by modification time). Use it to identify NAS file servers, on a per subclient basis, which should be backed up frequently (i.e., those with many recently modified files.) Files for each NAS file server and file system, categorized by size. This information may be useful when tuning file system parameters (such as block size), or when planning for backups. Files in each NAS file server, per subclient, by size. This information may be useful when tuning file system or RAID parameters (such as block size), or when planning for backups. Files for each NAS file server by File Category. Use it to identify NAS file servers that contain many multimedia, archive, or document files or applications (e.g., executables). Files in each NAS file server, per subclient, by File Category. Use it to identify NAS file servers, on a per VDM basis, that contain many multimedia, archive, or document files or applications (e.g., executables). For each NAS file server, share name, path, space used by each share, and total space on hosting storage (e.g., logical volume, aggregate volume), and file system protocol (CIFS, NFS). and *

33 Page 33 of 41 File System Usage by User Group per File System File System Usage by User per File System File Systems Capacity History Filers Files by Extension Junk Files Largest Files Least Recently Used Files NFS v2 Read Distribution by Size NFS v2 Statistics NFS v2 Write Distribution by Size NFS v3 Read Distribution by Size NFS v3 Statistics NFS v3 Write Distribution by Size Summarizes file system usage, highlighting the usage patterns of different user groups and NAS file servers on a per-file system basis. Use this report to identify heavy disk consumers for capacity management and planning purposes. Summarizes file system usage, highlighting the usage patterns of different users and NAS file servers on a per-file system basis. Use this report to identify heavy disk consumers for capacity management and planning purposes. Historical view of space (total, used, free), %used, %free per Enterprise, Client Group, and Filer that is attached to this client. Similar to File Systems Current Capacity [NetApp] or File Systems Current Capacity [Celerra] report, but tracks changes in used, available space, and spare/unused capacity over time. Use to predict future use patterns for capacity planning. A list of NAS filers (NetApp filers and EMC Celerra) and their properties. Displays NAS file servers' operating system, firmware version, model number, and type. Use filters to group NAS file servers by important characteristics, such as OS or type. Displays file statistics for each file extension of non-directory files that are collected on NAS filers. Statistics for other files are displayed. Each file extension and the number of files with that extension are displayed, as well as the total and average file size. Displays a list of files with junk file extensions. Report includes properties of these files, such as client group, filer, group, owner, file system, file name, and details. Displays a list of largest files based on their size. Report includes properties of these files, such as client group, filer, group, owner, file system, file name, and details. Displays a list of files that are least recently used based on their access time. Report includes properties of these files, such as client group, filer, group, owner, file system, file name, and details. The distribution, by size, of NFS Read requests processed by each NAS filer (NetApp). Enumerates the various NFS v2 request types that have been processed since the last time NFS services were restarted on the NAS filer (NetApp) or Data Mover (EMC Celerra). The distribution, by size, of NFS v2 Write requests processed by each NAS filer (NetApp). The distribution, by size, of NFS v3 Read requests processed by each NAS filer (NetApp). Enumerates the various NFS v3 request types that have been processed since the last time NFS services were restarted on the NAS filer (NetApp) or Data Mover (EMC Celerra). The distribution, by size, of NFS v3 Write requests processed by each NAS filer (NetApp).

34 Page 34 of 41 Oldest Files Prohibited Files Quotas Displays a list of oldest files that are based on their access time. Report includes properties of these files, such as client group, filer, group, owner, file system, file name, and details. Displays a list of files with prohibited file extensions. Report includes properties of these files, such as client group, filer, group, owner, file system, file name, and details. A list of quotas configured on NAS filers. Quotas are defined per logical volume or qtrees (NetApp), per file system or quota tree (EMC Celerra), type, scope, default quota for all users and groups, disk space soft and hard limits, percent used, space remaining, disk space threshold, file count soft and hard limits, and files used. * A Discovery level Data Collection Job is adequate to produce a complete File Shares report, but if a report for used space on the subclient with content residing on that share is desired, then an Analysis level Data Collection Job is required. Back to Top SRM NAS Agent Reports - How To Topics How To Related Topics Run/Schedule a Report View Report Details Run/Schedule a Report Required Capability: Capabilities and Permitted Actions To schedule a report: 1. In the CommCell Browser, expand Report Manager, right-click a report, and select Schedule Report. 2. In the Schedule Details dialog box, select a Report Name and Schedule and Start Time for the report. 3. To create a custom schedule for this report, click Edit, and enter the appropriate parameters in the Schedule Details dialog box. 4. If Predictive Trending is available for the report, you can optionally select Trending. 5. Click OK. Only if you select the One Time Schedule Policy do you need to specify a Date and Time. To run it immediately, accept the default start time. View Report Details Required Capability: Capabilities and Permitted Actions To view details of a report:

35 Page 35 of In the CommCell Browser, expand Report Manager and select a report. 2. The Report History window displays the copies of that report which have been run. 3. Select a report, and click View. 4. At the prompt, enter the User Name and Password configured in Reporting Server Credentials for viewing reports. The report will be displayed in your web browser. For help when viewing the report details in a browser, which are generated by Microsoft SQL Server Reporting Services, click the Help icon in the report window.

36 Page 36 of 41 Admin Job History Topics How To Related Topics The Admin Job History Filter dialog box allows you to view detailed, historical information about the following administration job types: All Data Aging Export Media Auxiliary Copy Inventory Disaster Recovery Backup Data Verification Offline Content Indexing Erase Media Erase Backup/Archived Data Drive Validation Drive Cleaning Stamp Media Install Updates Download Updates Magnetic Library Maintenance SRM Reports Information Management Once chosen, your filter options are then displayed in the Admin Job History window. From this window you can view more detailed information such as the: Details of the administration job. Events of the administration job. Log files of the administration job. For information on Job Details displayed in the Job History, see Viewing Job Information. Back to Top Admin Job History - How To Topics How To Related Topics View Admin Job History View Job History Details View the Events of a Job History Viewing the Log Files of a Job History View Admin Job History

37 Page 37 of 41 Required Capability: See Capabilities and Permitted Actions To view admin job history: 1. From the CommCell Browser, right-click the CommServe, click View, and then click Admin Job History. 2. From the Admin Job History Filter dialog box, select the filter options that you want to apply and click OK. 3. The Admin Job History dialog box displays with the specified filter options. 4. Click Close. View Job History Details Required Capability: See Capabilities and Permitted Actions To view the details of a job history: 1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click job history. 2. From the Job History Filter dialog box, select the filter options that you want to apply and click OK. 3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Job Details. 4. The Job Details dialog box appears, displaying detailed job history in General, Details, Phase Details and Attempts tabs for the selected job. 5. Click OK. If viewing the details of a job with a pending or failed status, the Reason for Job Delay field will contain an Error Code, which, if clicked, will launch the customer support website displaying troubleshooting article(s) related to the specific issue. View the Events of a Job History Required Capability: See Capabilities and Permitted Actions To view the events associated with a job: 1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click Job History. 2. From the Job History Filter dialog box, select the filter options that you want to apply and click OK. 3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Events. 4. The All Found Events window gets displayed. If no events where found for the back up, a message is displayed to that effect. 5. Click Close. View the Log Files of a Job History Required Capability: See Capabilities and Permitted Actions To view the log files of a Job History:

38 Page 38 of From the CommCell Browser, right-click the entity whose job history you want to view, and then click to view a job history. 2. From the job history filter window select the filter options, if any, that you want to apply, and then click OK. 3. From the job history window, right-click the job whose log files you want to view, and then click View Logs. 4. The contents of the log file related to the selected job history are displayed in the Log File for Job n window.

39 Page 39 of 41 SRM Data Collection Job History Topics How To Related Topics The Data Collection History Filter dialog box allows you view detailed, historical information about data collection jobs for the selected SRM entity. Data collection jobs run automatically according to the parameters you have selected, and appear in the Job Controller as a scheduled job. After the successful completion of the Data Collection job, the client information is gathered at the SRM Server and the job status is shown as completed in the Job Controller. For information on Job Details displayed in the Job History, see Viewing Job Information. Once chosen, your filter options are then displayed in the Data Collection Job History Window of the SRM entity. From this window you can view more detailed information such as: Viewing the Events of a Job History Viewing the Log Files of a Job History SRM Data Collection Job History - How To Topics How To Related Topics View Job History Details View the Events of a Job History View the Log Files of a Job History View Job History Details Required Capability: See Capabilities and Permitted Actions To view the details of a job history: 1. From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click job history. 2. From the Job History Filter dialog box, select the filter options that you want to apply and click OK. 3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Job Details. 4. The Job Details dialog box appears, displaying detailed job history in General, Details, Phase Details and Attempts tabs for the selected job. 5. Click OK. If viewing the details of a job with a pending or failed status, the Reason for Job Delay field will contain an Error Code, which, if clicked, will launch the customer support website displaying troubleshooting article(s) related to the specific issue. View the Events of a Job History Required Capability: See Capabilities and Permitted Actions To view the events associated with a job:

40 Page 40 of From the CommCell Browser, right-click the entity (e.g., subclient, client computer, etc.) whose job history you want to view, click View, and then click Job History. 2. From the Job History Filter dialog box, select the filter options that you want to apply and click OK. 3. From the Data Management Job History window, right-click the job whose job details you want to view, and then click View Events. 4. The All Found Events window gets displayed. If no events where found for the back up, a message is displayed to that effect. 5. Click Close. View the Log Files of a Job History Required Capability: See Capabilities and Permitted Actions To view the log files of a Job History: 1. From the CommCell Browser, right-click the entity whose job history you want to view, and then click to view a job history. 2. From the job history filter window select the filter options, if any, that you want to apply, and then click OK. 3. From the job history window, right-click the job whose log files you want to view, and then click View Logs. 4. The contents of the log file related to the selected job history are displayed in the Log File for Job n window. Back to Top

41 Page 41 of 41