If this option is selected, Movere will capture Actual Resource Consumption (ARC) data from each server being targeted. Unlike inventory data, which is typically captured every few days or once a week, resource consumption (CPU, memory, disk) is constantly changing and must be captured frequently to fully understand how a device is being used.
Selecting the ARC option will reveal the ARC tab in the Movere Console:
The ARC tab is used to specify the ARC collection frequency (5, 10, 15 minutes etc.) and duration (1, 3, 7 days etc.).
Question: Is an ARC scan just like an Inventory scan?
Answer: No. Inventory scanning cycles are typically scheduled to occur according to timelines measured in days or weeks, i.e. every 1, 3, 5, 7 days. As the Movere inventory bot is only 2MB in size and produces an output file which on average is less than 10KB, there is no need to leave the inventory bot in place. This not only avoids the need to install a persistent agent on each endpoint, it gives the user access to new Movere features by simply clicking the ‘Update’ button when the Movere Console notifies them that newer version is available:
An ARC scan is focused on gathering consumption data which is constantly changing. Collecting processor, memory and disk usage on the same schedule as an inventory scan would be of limited value. To fully appreciate how usage changes and accurately calculate peak workloads, data needs to be captured on a far more frequent basis, i.e. every 5, 10, 15 minutes over multiple days or weeks.
The need to capture consumption data on such a frequent basis over days, weeks or even months means that, unlike an inventory scan, the ARC bot needs to remain running as stopping and deleting itself after each scan would create a lot of unnecessary load on both the device and the network. This is the key difference between inventory and ARC when it comes to how scans are run.
When performing an inventory scan, the inventory bot is copied to the device to be inventoried, it runs once, produces an output file, then stops and deletes itself. Movere then leverages three different techniques to retrieve the inventory payload. These techniques, outlined above under the heading Operation, were developed so that customers, in most situations, can deploy Movere in minutes without having to make any changes to their existing environment.
When performing an ARC scan, the user is asked to specify a collection frequency (i.e. 5, 10, 15 minutes) and duration (i.e. 1, 3, 7 days). The ARC bot and collection configuration is then sent to the device to be monitored. Unlike an inventory bot which will delete itself after each scan, the ARC bot will capture usage data at that point in time then attempt to upload it straight to the cloud. If the cloud upload fails, then it will attempt to send the payload to the device the Movere Console is being run from. If this fails, the ARC bot will wait 30 seconds (to allow for any network congestion to clear) then it will attempt both methods again. If both fail a second time, the ARC bot will wait for a further 5 minutes before attempting both upload methods a third time. If both fail again, the ARC bot will terminate and delete itself.
If any of these uploads are successful, then the ARC bot will simply wait for the next specified collection time in accordance with the frequency and duration specified by the user. The ARC bot will remain in place throughout this time. Once the specified duration (e.g. 7 days) has passed, then just like the inventory bot, the ARC bot will terminate and delete itself.