How can we help?

Should I back up the Auvik collector?

Follow

Auvik has two primary components:

  • The Auvik collector, a lightweight piece of software deployed on a client’s network
  • The Auvik cloud, data processing engine, and data storage platform

The Auvik collector doesn’t store any data. All the data it collects is immediately sent to the cloud where it’s securely processed and stored in our cloud environment. Since there’s no data on the collector itself, it’s not necessary to back it up.

If an Auvik collector becomes corrupt (due to a corrupted file system, for example), we recommend deploying a new collector rather than restoring a backup. Deploying a new collector is faster.

If a collector does need to be redeployed or reinstalled, it won’t collect or send data to the cloud from the time the collector is disconnected to the time the new collector starts running. If a redundant secondary collector is scanning the same subnets as the failed collector, the secondary collector takes over and those subnets continue to be monitored.

If your MSP has recovery point objectives and recovery time objectives in place, the recovery time will be the amount of time it takes to deploy a new collector—typically minutes. The recovery point is the time the collector failed and data stopped being sent to the cloud (unless you have a redundant collector on the same subnets, in which case data continues to be sent to the cloud).

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request
Powered by Zendesk