The data collection from all endpoints is scheduled to run at default intervals. However you can modify the intervals by updating the respective job properties in the itfm.properties file.

Following table lists the jobs from all endpoints, its default intervals for data collection and the job property that you can use to modify the interval.

Note:

You can modify these intervals by updating the respective job property in the itfm.properties file present at the /usr/local/tcserver/vfabric-tc-server-standard/sharedconf location. For example, to run the storage data collection every one hour, update the storage job property to dc.job.interval.vc.storage = 60.

Table 1. Data Collection Jobs

Endpoint

Jobs

Default Intervals

Job Property

vCenter Server

Inventory

Immediately after an inventory update

Not applicable

Tags

Every 6 hours (360 minutes)

dc.job.interval.vc.tags

vRealize Operations Manager

Every 30 minutes

dc.job.interval.vc.vcops

Storage

Every 12 hours (720 minutes)

dc.job.interval.vc.storage

Usage Statistics

Every 24 hours (1440 minutes)

dc.job.interval.vc.stats

EMC SRM

Every 24 hours (1440 minutes)

dc.job.interval.srm

vRealize Automation

Every 2 hours (120 minutes)

dc.job.interval.vra

Public cloud

AWS

Every 24 hours (1440 minutes)

dc.job.interval.aws

vCloud Air

Every 24 hours (1440 minutes)

dc.job.interval.vca

Azure

Every 24 hours (1440 minutes)

Note:

You cannot configure Azure interval. You can manually trigger the job when required.

vCloud Director

Every hour (60 minutes)

dc.job.interval.vcd

Note:

To run a data collection process immediately, click Status and click the Update Now option next to the respective process.

If a failure occurs during the data collection process, vRealize Business for Cloud retries to run the process maximum of five times, by default. You can modify the retry value by updating the dc.failed.job.max.retry.count parameter in the itfm.properties file.

For example, dc.failed.job.max.retry.count = 3.

And by default, vRealize Business for Cloud takes two minutes interval to retry the process. You can modify this value by updating the dc.failed.job.retry.period parameter in the itfm.properties file.

For example, dc.failed.job.retry.period = 1.