Business Neue Version 3.0.0-24631 veröffentlicht...

[Adama]

Moin, es gibt eine neue Version von ABfB: 3.0.0-24631

Hier die Release Notes:

Version: 3.0.0-24631
(2025-04-07)

Compatibility and Installation

    Active Backup for Business 3.0.0 and above requires DSM 7.2 or above.
    Active Backup for Business 3.0.0 and above requires installing Container Manager.
    The following models are not supported in Active Backup for Business 3.0.0 or above:

    DS214play
    DS216play
    DS415play
    DS416play
    DS418play

Important Note

    Daily backups previously scheduled to run every hour will change to hourly backups.
    To back up a custom volume on Mac, you only need to specify the volume name instead of the entire path. However, if your device has multiple volumes with the same name, all of them will be backed up. Backups configured before the update will continue using the full path unless modified.
    Active Backup for Business tasks will no longer appear in the Task Scheduler in DSM.

What's new

    Added support for centralized management via ActiveProtect appliances. [Learn about package features, requirements, and limitations here].(https://sy.to/abfbcentralizedmanagement)
    Updated OpenSSL to version 3.0.0 to enhance connection security. This update applies to personal computers, physical servers, file servers, and virtual machines.
    Added support for throttling failure notifications when the server reaches its storage limit or encounters hypervisor connection issues, preventing excessive notifications.

Fixed Issues (General Issues)

    Fixed an issue where reaching the storage limit might cause backups to freeze and prevent the status from updating.

Fixed Issues (Physical Server)

    Fixed an issue where the system might fail to boot after an instant restore to VMware when the disk was not 4K-aligned.

Fixed Issues (Virtual Machines)

    Fixed an issue where backing up VMware to encrypted or compressed storage might cause a boot failure during instant restores.
    Fixed an issue where Hyper-V backups might fail if the snapshot contains inaccessible virtual disks not directly related to the backup task
    Fixed an issue where restoring multiple virtual machines to different ESXi hosts within the same vCenter might fail.
    Fixed an issue where restores might fail if the selected vSwitch name conflicted with another on the same Hyper-V host.

Anmerkungen:

    This version is released in a staged rollout.

https://www.synology.com/de-de/releaseNote/ActiveBackup?model=DS918+&os=DSM&version=7_x_series

 

[Adama]

Ich hab - natürlich - schon upgedatet, wieder mal keine Selbstbeherrschung gehabt...

Grundsätzlich läuft alles. Wer sich fragt, warum brauche ich jetzt den Container Manager dazu, siehe folgendes:







Und edit sagt, schau mal ins Menü:

 

[Adama]

Spassige Nebenerscheinung: Watchtower fällt natürlich bei all den Containern auf die Schnauze.

Als Beispiel:

Unable to update container "/apm-centralized-service": Error response from daemon: error parsing HTTP 403 response body: invalid character 'F' looking for beginning of value: "Forbidden". Proceeding to next.

Was kann man tun? All den Containern, die upgedatet werden sollen und die ich bearbeiten kann, hab ich folgendes Label mitgegeben:

    labels:
      - "com.centurylinklabs.watchtower.enable=true"

Dem Watchtower-Container gibt man folgende Environment-Variable mit:

      - "WATCHTOWER_LABEL_ENABLE=true"

Das hat Watchtower dann so interpretiert:

Watchtower 1.7.1
Using notifications: smtp
Only checking containers using enable label
Scheduling first run: 2025-04-07 16:00:00 +0200 CEST
Note that the first check will be performed in 1 hour, 46 minutes, 7 seconds

Damit sollte dann hoffentlich alles wieder richtig laufen. Schauen wir mal...

 

[plang.pl]

Das mit Docker wäre da auch meine erste Frage gewesen. Danke für die Erfahrungen