Understanding the Monitoring Tab within the Veritas Alta SaaS Protection Connector Service

Article: 100050128
Last Published: 2023-04-18
Ratings: 1 0
Product(s): Veritas Alta SaaS Protection

Description

This article describes how to make use of the Monitoring Tab within the Veritas Alta SaaS Protection Connector Service.  

 

 

 

There are two sections in the Monitoring Tab.  The first being the top section of the window as seen below: 

 

 

 

 

This section contains the following status elements:

 

Current upload speed:  This shows the upload speed of data to Veritas Alta SaaS Protection measured in Megabits (Mbps). This number fluctuates slightly during the initial phase of the crawl, but in time it stabilizes.

 

Uploaded since service started:  Indicates the amount of data sent over the wire since the last time the Veritas Alta SaaS Protection Connector Service was started.  The Veritas Alta SaaS Protection Connector service can be started and stopped through the Windows service control manager.  Please note that closing this user interface does not impact this number as the Veritas Alta SaaS Protection Connector Service remains running.  

 

  • This is the compressed size as the data is compressed prior to transmission.
  • This number is cumulative across all connectors. 
  • It is measured in Megabytes (MB).

 

The bottom section of the window shows activity for the connector threads.  The default number of threads per connector is 10.  

 

 

 

 

In this example, the connector crawl was only utilizing one thread as the amount of data crawled was very small.  Generally, all threads are utilized unless the crawl is stopping or nearing the end of a run.   

 

This section is an excellent reference to monitor a connector crawl after pressing the 'Stop Crawl' button.  The status of each thread is displayed until the crawl has completed.  A stopping crawl completes once every thread finishes the current item in progress.  In other words, all threads show 'None.'

 

If you don't want to wait for each thread to complete the current item, restarting the Connector service forces all work to stop without completing.  Please note that a service restart affects all active crawls.

 

 

 

 

 

Was this content helpful?