Skip to main content
NetApp Knowledge Base

What is the "_ocs_vserver" workload in qos statistics?

Views:
1,424
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
Perf
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP Copy Subsystem (OCS)

Answer

  • _ocs_vserver is a QoS internal workload ID for Copy Offload, known as VAAI, ODX
    • Copy offload is a process of copying data blocks without sending the data, only metadata/control data across the network
    • This may be copied from one part of a volume to another of the same volume, or another volume on the same ONTAP node/cluster
    • This is done to optimize a slow client or network by making all the computation occur on storage (ONTAP)
  • This may be identified from a Performance case, or from the command qos statistics workload resource cpu show.
  • Example:

cluster1::> qos statistics workload resource cpu show -node nodeB
Workload            ID   CPU
--------------- ------ -----
-total- (100%)       -   30%
_ocs_vserver_a3      -   20%
vs0-wid101         101   12%
file-1-wid121      121   10%
vol0-wid1002      1002    8%
_DEDUP               -    7%
-total- (100%)       -   30%
vs0-wid101         101   12%
file-1-wid121      121   10%
_ocs_vserver_a3      -   10%
vol0-wid1002      1002    8%
_DEDUP               -    7%

  • Offloading the reading of data from a source and the writing to a destination via the use of an in-band SCSI command known as EXTENDED_COPY
    • This mainly includes Storage vMotions (VMware initiated data migration)
  • For Copy Offload work, OCS creates a default QoS workload per destination vserver
  • These workloads follow a well-defined naming scheme; each workload name is of the form _ocs_vserver_<vserver UUID>, where the vserver ID is the UUID of the destination vserver.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.