You are here:

Create an Inventory Job Definition - NetApp ONTAP Storage

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

A NetApp ONTAP Storage Inventory job provides the framework to catalog and collect information about high-level NetApp ONTAP objects. You can select one or more NetApp ONTAP cluster or non-cluster providers in a single job definition for cataloging. NetApp ONTAP 7-Mode and Cluster-Mode are both supported.

Run a NetApp ONTAP Storage Inventory job to analyze your NetApp ONTAP 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 low-level NetApp ONTAP objects, create a NetApp ONTAP File Inventory job definition.

BEFORE YOU BEGIN:

At least one NetApp ONTAP provider must be associated with a NetApp ONTAP Storage Inventory job definition. Before defining an Inventory job definition, add NetApp ONTAP providers. See Register a Provider.
For email notifications, at least one SMTP server must be configured. Before defining a job, add SMTP resources. See Register a Provider.

CONSIDERATIONS:

One or more schedules might also be associated with a job. Job sessions run based on the triggers defined in the schedule. See Create a Schedule.

To create a NetApp ONTAP Storage Inventory job definition:

Click the Jobs tab. Expand the Storage Controller folder, then select NetApp ONTAP.
Click New , then select Inventory NetApp ONTAP Storage . The job editor opens.
Enter a name for your job definition and a meaningful description.
From the list of available sites, select one or more providers to catalog.
To create the job definition using default options, click Create Job. The job can be run manually from the Jobs tab.
To edit options before creating the job definition, click Advanced. Set the job definition options.
Maximum concurrent tasks
Set the maximum number of concurrent cataloging tasks that can be performed on the provider.
Connection timeout (secs)
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.
Number of catalog instances to keep
After a certain number of job runs for a given job, older NetApp ONTAP objects for that job are purged from the Inventory. Enter the number of job runs for which high-level NetApp ONTAP objects are to be retained.
Optionally, expand the Notification section to select the job notification options.
SMTP Server
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.
Email Address
Enter the email addresses of the status email notifications recipients. Click Add to add it to the list.
Optionally, expand the Schedule section to select the job scheduling options. Select Start job now to create a job definition 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.
Note: To create and select a new schedule, click the Configure tab, then select Schedules . Create a schedule, return to the job editor, refresh the Available Schedules pane, and select the new schedule.
When you are satisfied that the job-specific information is correct, click Create Job. The job runs as defined by your schedule, or can be run manually from the Jobs tab.

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

NEXT STEPS:

If you do not want to wait until the next scheduled job run, run the job session on demand. See Start, Pause, and Hold a Job Session.
Track the progress of the job session on the Jobs tab. See Monitor a Job Session.
If notification options are enabled, an email message with information about the status of each task is sent when the job completes.