Log details question

[gfarcas]

Hello everyone,

I was wondering if you can explain to me the following log line, it would help me troubleshoot my setups:

Code: Select all

 <  9400> cli|     - 5%, workload src: 99/10/0, ntf: 93/10/1

Also it would help if you know somewhere where I can find more resources about logs.

Best regards,
George

[PetrM]

Hi George,

Kindly please include support case ID for the issue.
I don't think you should waste time on logs analysis so please let our support team to find more hints there.

Looks like this line is taken from source Data Mover log and corresponds to some data processing step.
It means that 5 % of data has already been processed and most of time of Data Mover activity is spent on reading data blocks from source (src: 99, ntf: 93).

By the way, would you be so kind to clarify the issue that you're trying to troubleshoot?

Thanks!

[gfarcas]

No issue at the moment. We have a lot of Cloud Connect clients that we support and many times I want to detect where the bottleneck is when it comes to performance without opening a ticket and have several replies to find out. I know there is some information about this in VBR in the job log but I know this line is more granular in showing that.

The log is taken from a datamover inside a proxy

Thanks!

[PetrM]

I'd suggest to use this statistics in order to detect bottleneck.
Logs are required for support team when working with sophisticated issues.

Thanks!

[Netrepid]

workload src: 99/10/0, ntf: 93/10/1

src: 99% Source Storage, 10% CPU, 0% Network

ntf: 93% Network, 10% CPU, 1% Storage

Your bottlenecks are Source Storage and Target Network

[PetrM]

Hi Robert,

The best option to detect "bottleneck" is to examine job/task session statistics.

Metrics shown in logs can be interdependent and analysis is usually performed by support team.
Sometimes additional Data Mover performance statistics (enabled by registry key) is required to get clear interpretation.

By the way, every system has only one "bottleneck" (99 is on the source in our case).

Thanks!