Updating Smart Beat Manager and Smart Beat

danger

Smart Beat Manager must be updated first. After that, you can proceed to update Smart Beat agents. Smart Beat Manager maintains backward compatibility with previous agent versions.

Conventions:

• SM_INSTALLER - the directory where the Smart Monitor installation package is unpacked
• SBM_HOME - the installation directory of Smart Beat Manager
• SB_HOME - the installation directory of Smart Beat

Updating Smart Beat Manager

Updating Smart Beat Manager and its configurations is only available manually.

1. Back up the certificates and configuration of the current installation, for example, to the /app/backup directory:

mkdir -p /app/backup/$(date +%Y%m%d)/sbm/
cp -r $SBM_HOME/etc/ssl /app/backup/$(date +%Y%m%d)/sbm/
cp $SBM_HOME/etc/*.yml /app/backup/$(date +%Y%m%d)/sbm/

2. Stop the service and remove the existing version of Smart Beat Manager:

systemctl stop smartBeatManager
rm -f $SBM_HOME/smartBeatManager*

3. Delete the old files:

cp $SM_INSTALLER/utils/smartBeatManager/smartBeatManager-* $SBM_HOME/smartBeatManager
chmod +x $SBM_HOME/smartBeatManager
rm $SBM_HOME/etc/smartBeatManager.yml
rm $SBM_HOME/etc/config.yml

4. After extracting the Smart Monitor installer, copy the installation file and make it executable:

$SBM_HOME/smartBeatManager remove
$SBM_HOME/smartBeatManager install
systemctl restart smartBeatManager
systemctl stop smartBeatManager

warning

Starting from version 4.2.0, the configuration file name has changed from smartBeatManager.yml to config.yml. If config.yml exists, it will be used. If it doesn't exist, smartBeatManager.yml might be used. The configuration syntax has changed; it is recommended to transfer the settings to the new configuration file.

5. Compare the old configuration file smartBeatManager.yml and the new config.yml:

diff /app/backup/$(date +%Y%m%d)/sbm/smartBeatManager.yml $SBM_HOME/etc/config.yml

6. Transfer the necessary settings from the old file to the new one and restart the service:

systemctl restart smartBeatManager

---

Updating Smart Beat for Linux

1. Back up the certificates and configuration of the current installation, for example, to the /app/backup directory:

mkdir -p /app/backup/$(date +%Y%m%d)/sb/
cp -r $SB_HOME/cert /app/backup/$(date +%Y%m%d)/sb/
cp $SB_HOME/config/*.yaml /app/backup/$(date +%Y%m%d)/sb/

2. Stop the service and remove the existing version of Smart Beat:

systemctl stop smartBeat
rm -f $SB_HOME/smartBeat*

3. After extracting the Smart Monitor installer, copy the installation file and make it executable:

cp $SM_INSTALLER/utils/smartBeat/smartBeat-linux-x64-* $SB_HOME/smartBeat
chmod +x $SB_HOME/smartBeat
rm $SB_HOME/config/config.yaml

4. Install Smart Beat and restart the service, then stop it immediately:

$SB_HOME/smartBeat remove
$SB_HOME/smartBeat install
systemctl restart smartBeat
systemctl stop smartBeat

5. Compare the old configuration file config.yaml and the new one:

diff /app/backup/$(date +%Y%m%d)/sb/config.yaml $SB_HOME/config/config.yaml

6. Transfer the necessary settings from the old file to the new one and restart the service:

systemctl restart smartBeat

---

Updating Smart Beat for Windows

danger

To update the agent on Windows, you must first uninstall it. However, uninstalling will affect the entire installation directory, so back up all necessary files beforehand. When installing from the command line or PowerShell, the installation command with the list of parameters can be left unchanged.

1. Back up the certificates (usually C:\Program Files\smartBeat\cert\) and the configuration of the current installation (usually C:\Program Files\smartBeat\config\config.yaml)

2. Uninstall the old agent through "Add/Remove Programs" in Windows Control Panel

3. Install Smart Beat. Pay attention to the SSL/TLS settings window; you can specify the certificates copied before the update. If you check the Generate self-signed certificate box, new self-signed certificates will be generated (if none exist)