Create a NetApp File Catalog Data Policy

Cataloging objects located on a provider is required for browsing, searching, and reporting in ECX.

A NetApp File Catalog Data policy provides the framework to catalog and collect information about low-level NetApp objects. You can select one or more NetApp providers in a single policy for cataloging. NetApp 7-Mode and Cluster-Mode are both supported.

During cataloging, properties for NetApp files are collected and stored. Run a NetApp File Catalog Data policy to analyze your low-level NetApp environment in real time and navigate and correlate the objects from across the Enterprise in a single view. Additionally, you can infer snapshot sprawl, storage overutilization, and other storage inefficiencies.

Note: For cataloging high-level NetApp objects, create a NetApp Storage Catalog Data policy.

Tip: NetApp File Catalog Data jobs might take a long time to run because they catalog at a file level. Consider creating NetApp File Catalog Data policies that constrain the number of file system objects to catalog by limiting the number of storage systems and volume processed by a single policy. You can also stagger the scheduled run times of the policies to prevent them from running concurrently. Consider running NetApp File Catalog Data policies less frequently than you run NetApp Catalog Data policies.

Best Practice: Create a schedule before creating a policy so that you can easily add the schedule to the job definition in the New Policy editor.

To create a NetApp File Catalog Data policy:

1. Click the Plan tab. On the Views pane, select Policies .
2. Click the All Policies tab, select New , then select NetApp Files in the Catalog Data column. The NetApp File Catalog Data Policy editor opens.
3. Click the 1: Source tab. From the list of available providers, select one or more volumes to catalog. For Cluster-Mode providers, the SVM name appears in parentheses after the volume name. To view the number of files on the selected volume, hover your cursor over the volume name.
4. Click the 2: Options tab. Select the options for your policy.
5. Skip root volume
6. Select this option to avoid cataloging the root volume of your NetApp objects.
7. Skip unsupported volumes
8. Select this option to avoid cataloging unsupported volumes such as volumes that are offline. Selecting this option also avoids cataloging volumes with i2p disabled when Catalog all available snapshots is set to Yes and Traversal Method is set to Snapdiff.
9. Connection timeout (secs)
10. To run a catalog job, the application needs to connect with the resource. If there is no response within a certain time limit, it times out and the job session fails. Enter the number of seconds to wait before timing out.
11. Number of catalog instances to keep
12. After a certain number of job runs for a given policy, older low-level NetApp objects for that job are purged from the Catalog. Enter the number of job runs for which low-level NetApp objects are to be retained. Note that by default, the old data for the policy is purged from the ECX Catalog after the newer data is cataloged.
13. Condense catalog before run
14. Select this option to purge older low-level NetApp objects from the ECX Catalog before newer data is cataloged through a NetApp File Catalog Data policy.
15. Condense catalog after failed run
16. Select this option to purge NetApp objects from the ECX Catalog for the unsuccessful run of the NetApp File Catalog Data policy.
17. Traversal Method

18. This option indicates the methodology to employ when cataloging snapshots. ECX honors your preference if it is supported for the particular system configuration. If the selected preference is not supported for your system configuration, the operation fails.

    SnapDiff. ECX performs cataloging based on snapshot differences. If SnapDiff is selected, the default number of files requested in each query is 256 and the default maximum number of volumes that are simultaneously cataloged is 8.

    Filewalk. ECX retrieves owner information for files and folders for volumes that have CIFS shares. This option is used in conjunction with the ECX Filewalker tool. Once cataloging completes, searchable owner information is added to the Catalog. See the Filewalker documentation for more information.

5. Click the 3: Notification tab. Select the notification options for your policy.
6. SMTP Server
7. From the list of available SMTP resources, select the SMTP Server to use for job status email notifications. If an SMTP server is not selected, an email is not sent.
8. Email Address
9. Enter the email addresses of the status email notifications recipients. Click Add to add it to the list.
6. Click the 4: Schedule tab. Select Start job now to create a policy that starts the job immediately. Select Schedule job to start at later time to view the list of available schedules. Optionally select one or more schedules for the job. As each schedule is selected, the schedule's name and description displays. A policy paired with a schedule is a job.
7. Note: To create and select a new schedule, click Views, then select Schedules . Create a schedule, then return to the policy editor, refresh the Available Schedules pane, and select the new schedule.
7. Click the 5: Finish tab. Enter a name for your policy and a meaningful description. When you are satisfied that the policy-specific information is correct, click Finish.

Note: If you selected the Start job now option, the job runs.

8. Click the All Policies tab. Your new policy appears in the policy list.

 

---

Catalogic ECX™ 2.4

© 2016 Catalogic Software, Inc. | All rights reserved. | 7/15/2016

MySupport | Knowledge Base | Trademarks | info@catalogicsoftware.com