Table of Contents

Backing up a DataMiner Agent in DataMiner Cube

In the System Center module, you can configure automatic backups that will run at regular intervals, and execute an immediate backup when necessary.

Configuring the DataMiner backups

The following steps can be taken to configure the backups for a DMA:

  1. Go to Apps > System Center.

  2. In System Center, select the Backup tab.

  3. In the General tab, under Location, optionally configure local or network path(s) where the backups should also be stored.

    • If you select the Local paths option, all Agents in the Local paths list will automatically be selected, but you can clear the selection for some Agents if necessary. For the selected Agents, the backup package will be placed both in the default local folder C:\Skyline DataMiner\Backup and in the folder specified in the Local path box (on the same Agent).

    • If you select the Store the backups on a network path option, you can either use one network path for all DMAs, or a different network path for each DMA.

      If Use a different network path for each Agent is selected, you can select for which Agents this applies. For the selected Agents, the backup package will be placed both in the default local folder C:\Skyline DataMiner\Backup and in the folder specified in the Network path box. From DataMiner 10.3.11/10.3.0 [CU8]/10.2.0 [CU20] onwards, the backups for each DataMiner Agent in the DMS will be stored in a dedicated subfolder of this folder. The subfolder will have the DMA ID as its name.

      Note

      Only SMB file shares are supported for network backups. It is not possible to back up to e.g. (S)FTP shares.

  4. In the General tab, next to Number of backups to keep, enter the number of backups that should be kept.

    Note

    Prior to DataMiner 10.2.0 [CU20], 10.3.0 [CU8], and 10.3.11, this number determines the number of backups kept in the entire system. From those DataMiner versions onwards, it determines the number of backups per DMA or Failover setup. As older systems are often configured with a higher number of backups because of this, upgrading to these DataMiner versions will adjust the number of backups to keep if necessary. If the number is set to more than 3, there are 2 or more DMAs in the system, and the backups are not saved to the same network path, the number of backups to keep will automatically be divided by the number of DMAs in the system during the upgrade.

  5. In case the system uses an indexing database, in the Indexing Engine Location section of the General tab, the backup path can be modified if necessary.

    Note

    For more information on indexing backups, see Configuring OpenSearch backups or Configuring Elasticsearch backups.

  6. In the Schedule tab, select when the backup should be executed: monthly, weekly, daily, or only when it is manually initiated.

  7. In the Content tab, determine the backup type:

    • If you select Use predefined backup, indicate the type of backup in the drop-down list.

      • Full Backup: Backup containing all data necessary to restore the entire DataMiner Agent (default).

      • Full Backup without Database: Similar to the full backup, but does not include the database. If you are using STaaS, you can choose this option, as you do not have a self-hosted database in that case.

      • Configuration Backup: Backup containing all data necessary to restore the configuration of the DataMiner Agent. This also contains parameter values saved in the database, but not alarm or trending data.

        Note

        The configuration backup does not include DataMiner Files and Logging.

      • Configuration Backup without Database: Similar to the configuration backup, but does not include any information from the database. If you are using STaaS, you can choose this option, as you do not have a self-hosted database in that case.

      • Visual Configuration Backup: Backup containing all protocols (including Visio files, WFMs, and the production protocol), all Visio files linked to views, and the contents of the folder C:\Skyline DataMiner\Webpages.

    • If you select Use custom backup, in the table below, select what is to be included in the backup.

      Note
      • In case an MSSQL general database is used, in the Options section, an extra option is available that allows you to back up the transaction log as well. This option can be of use in order to allow MSSQL to shrink the log file. However, note that MSSQL is no longer supported as the general database as from DataMiner 10.3.0.
      • While changes are being made to a backup configuration, no backup can be taken.

  8. Click the Save button to save the settings.

Note

If during a backup operation DataMiner fails to take a backup of the general database, an information event will be generated.

Taking an instant backup

To take an immediate backup of a DMA:

  1. Go to Apps > System Center.

  2. In System Center, select the Backup tab.

  3. Check whether the backup configuration is correct, and adjust it if necessary. (See above.)

  4. Click the Execute backup button.

  5. Select the DMAs to back up, and click Start backup.

Propose changes