Asigra backup service

This service monitors Asigra backup sets. You will need a separate instance of the Asigra Backup service to monitor each backup set.

You need to use a Windows probe when monitoring an Asigra backup set on a device using a Red Hat Enterprise or CentOS Linux operating system. To ensure the Windows probe successfully discovers the Linux device, you need to install the Microsoft Visual C++ 2010 Distributable Package on the device where the Windows probe is installed. For more information on the Microsoft Visual C++ 2010 Distributable Package, see http://www.microsoft.com/en-ca/download/details.aspx?id=5555.

After upgrading an agent that monitors the Asigra Backup service, you will need to stop the Windows agent services, place the Asigra .DLL files to the agent's bin directory and re-start the Windows agent services.

Asigra v12.x

For N-able N-central to monitor Asigra v12.x backup sets, you must redistribute the Asigra API bundle as well as the Microsoft Visual C++ 2010 Distributable Package, which includes the msvcp100.dll and msvcr100.dll files, as follows:

  • If you are using a previously-installed Probe and you are installing Asigra for the first time, you must store the API bundle and the MSVC .DLL files in the probe's bin directory.
  • If you are monitoring Asigra using a previously-installed agent, you must store the API bundle and the MSVC .DLL files in the agent's bin directory.
  • If you include an Asigra discovery during the installation of a probe, ensure the MSVC .DLL files are stored in the location configured in the DLL path field of the installation software.
  • If you are adding the API bundle and the new MSVC .DLL files to an existing agent or probe configuration, you need to re-start the agent or probe after storing the MSVC .DLL files so that N-able N-central can start using them.
Service TypeODBC
Instances on a Device100
Supported Systems/ApplicationsAsigra version 9.2 and newer.
Device ClassWindows server
Monitored ByWindows agent and Windows probe
Job TimeoutThe time in hours that the N-able N-central server waits for the backup job to report data. If the backup job has not reported data in the specified time, the service changes to a Failed state. The default is 24 hours.
Backup Set NamesThe identifying names of the discovered Asigra backup sets.
Scan Interval in MinutesThe time in minutes between each scan. The default scan interval is 30 minutes.
Repeat Weekly on DaysThe scan is repeated weekly on the specified days.
Repeat Monthly on DaysThe scan is repeated monthly on the specified days.

Metrics

Metric NameDescription
Last Attempted Backup Start Date and TimeThe last date and time that a backup was tried, whether successful or not.
Backup StatusThe current status of the backup set.
Backup Status DescriptionA description of the current status of the backup set.
Last Successful Backup Start Date and TimeThe last date and time that a backup was successful.
Last Sync TimeThe last time that the backup set was synchronized.
Backup DurationThe time it took for the backup to be completed.
Backup Data TypeThe type of data being backed up, for example, HyperV or Sybase.
Backup Set TypeThe type of backup set as either Local Only or Local and Offsite.
Stored SizeThe size of the backed up data in its stored location.
Protected SizeThe size of the backed up data prior to compression or encryption.
Native SizeThe size of the backed up data in its original location.