Re-Install Backup Manager in Command Line/Terminal Emulator

Reinstalling a device using the Command Line/Terminal Emulator can be done on devices using Windows and Linux or macOS operating systems.

All devices installed, or re-installed which use the Managed encryption method are installed silently, meaning no additional parameters are required. It is, however, possible to include additional optional parameters to any install for Windows or Linux devices for either Managed or Self-Managed devices.

Windows and Linux

To perform the silent re-installation of the Backup Manager on Windows and Linux devices:

  1. Download the Backup Manager installer for the device from Device Properties in the Cove Management Console
  2. Open the command line/terminal on the device as an Administrator/Root user
  3. Navigate to the folder where the installer file is located
  4. Run the installer command:
    1. On devices installed using Managed encryption:

      Windows:

      cove#vi#abb751eb-123a-456b-78ef-9g0123hi4jk5#.exe -silent

      Linux:

      cove#vi#abb751eb-123a-456b-78ef-9g0123hi4jk5#.run --

      On devices that use Managed encryption, the passphrase is automatically pulled alongside the Device Name and Installation Key

    2. On devices installed using Self-Managed encryption:

      Windows:

      cove#vi#abb751eb-123a-456b-78ef-9g0123hi4jk5#.exe -silent -encryption-key "encryption-key-used-when-device-installed"

      Linux:

      cove#vi#abb751eb-123a-456b-78ef-9g0123hi4jk5#.run -- --encryption-key="encryption-key-used-when-device-installed"

      3. Where cove#vi#abb751eb-123a-456b-78ef-9g0123hi4jk5# is replaced with the name of the downloaded installation file and encryption-key-used-when-device-installed is replaced with the Encryption Key/Security Code you provided when the device was originally installed

      On devices that use Self-Managed encryption, the Encryption Key/Security Code is not pulled with the Device Name and Installation Key and so must be provided in the installer command, otherwise you will be prompted to enter this on the terminal

macOS

To perform the silent re-installation of the Backup Manager on macOS devices:

  1. Download the Backup Manager installer for the device from Device Properties in the CoveManagement Console
  2. Open the terminal on the device as an Administrator user
  3. Navigate to the folder where the installer file is located
  4. Run the installer command:
    1. On devices installed using Managed encryption:

      sudo installer -pkg cove#24.10.102#ab1234c5-67d8-9ef0-g1h2-i34j56k789lm#.pkg -target

      On devices that use Managed encryption, the passphrase is automatically pulled alongside the Device Name and Installation Key

    2. On devices installed using Self-Managed encryption:

      sudo installer -pkg cove#24.10.102#ab1234c5-67d8-9ef0-g1h2-i34j56k789lm#.pkg -target -encryptionKey=encryption-key-used-when-device-installed

      3. Where cove#24.10.102#ab1234c5-67d8-9ef0-g1h2-i34j56k789lm# is replaced with the name of the downloaded installation file and encryption-key-used-when-device-installed is replaced with the Encryption Key/Security Code you provided when the device was originally installed

      On devices that use Self-Managed encryption, the Encryption Key/Security Code is not pulled with the Device Name and Installation Key and so must be provided in the installer command, otherwise you will be prompted to enter this on the terminal

  5. Confirm installation has been successful by viewing the system installation logs

    The system installation log files can be found on the machine by browsing in the file explorer to OS/private/var/log/install.log

It is possible to create a script that references the configuration file (config.ini) containing the device name, installation key and Encryption Key/Security Code which updates the config.ini file after a successful installation and then restart the Backup Service Controller.

This would reload the system with the new configuration updates, however a pre-existing script is not available so you would have to write this manually.

The config.ini file can be found in this location:

/Library/Application Support/MXB/Backup Manager/config.ini

Once you have updated the configuration file, you will need to restart the internal backup process for all changes to take effect.