Storware update went wrong
-
Hi,
Few months ago I've installed Storware on a WMWare host, the actua version is 5.2.0-45, today I had check if there's an update and I've followed this guide:
But I've some trouble to update:
Activate the web console with: systemctl enable --now c**kpit.socket Last login: Thu Sep 14 11:53:21 2023 from 192.168.192.32 [root@STORWARE ~]# dnf clean all 39 files removed [root@STORWARE ~]# yum update sbr-endpoints-server CentOS Stream 8 - AppStream 22 MB/s | 33 MB 00:01 CentOS Stream 8 - BaseOS 52 MB/s | 47 MB 00:00 CentOS Stream 8 - Extras 46 kB/s | 18 kB 00:00 CentOS Stream 8 - Extras common packages 26 kB/s | 6.9 kB 00:00 MariaDB 53 kB/s | 615 kB 00:11 vProtect 167 kB/s | 24 kB 00:00 Package sbr-endpoints-server available, but not installed. No match for argument: sbr-endpoints-server Error: No packages marked for upgrade. [root@STORWARE ~]# su kodo su: user kodo does not exist [root@STORWARE ~]# cd /opt/storware/kodo-server/api-core/bin/ -bash: cd: /opt/storware/kodo-server/api-core/bin/: No such file or directory [root@STORWARE ~]#
What I'm doing wrong?
Thanks and regards,
Cristian -
@Cristian-Eglue
Could I ask for the result of the cat command from the created repo for the SBR Endpoints product?
Should be located in /etc/yum.repos.d dir -
Hi Djaw,
Here are:
[root@STORWARE yum.repos.d]# cat vProtect.repo # Storware Backup & Recovery - Enterprise backup solution for virtual environments repository [vprotect] name = vProtect baseurl = http://repo.storware.eu/storware/5.2.0/el8/ gpgcheck = 0 [root@STORWARE yum.repos.d]# cat MariaDB.repo # MariaDB 10.6 CentOS repository list - created 2023-02-14 09:39 UTC # https://mariadb.org/download/ [mariadb] name = MariaDB # rpm.mariadb.org is a dynamic mirror if your preferred mirror goes offline. See https://mariadb.org/mirrorbits/ for details. # baseurl = https://rpm.mariadb.org/10.6/centos/$releasever/$basearch baseurl = https://ftp.icm.edu.pl/pub/unix/database/mariadb/yum/10.6/centos/$releasever/$basearch # gpgkey = https://rpm.mariadb.org/RPM-GPG-KEY-MariaDB gpgkey = https://ftp.icm.edu.pl/pub/unix/database/mariadb/yum/RPM-GPG-KEY-MariaDB gpgcheck = 1[root@STORWARE yum.repos.d]# pin
There are also the CentOS repos:
CentOS-Stream-AppStream.repo
CentOS-Stream-BaseOS.repo
CentOS-Stream-Debuginfo.repo
CentOS-Stream-Extras-common.repo
CentOS-Stream-Extras.repo
CentOS-Stream-HighAvailability.repo
CentOS-Stream-Media.repo
CentOS-Stream-NFV.repo
CentOS-Stream-PowerTools.repo
CentOS-Stream-RealTime.repo
CentOS-Stream-ResilientStorage.repo
CentOS-Stream-Sources.repoPlease let me know if you need these too.
-
Hi Cristian,
Repo looks fineIf you want to update the server hosting UI Storware Backup & Recovery, use the yum update vprotect-server command
yum update sbr-endpoints-server refers to the application component used to backup computers in the organization.
Please also remember to update vprotect-node along with server update
-
@djaw said in Storware update went wrong:
yum update vprotect-server
Hi Djaw
Thank you, I was able to update both with the commands:
- yum update vprotect-server
- yum update vprotect-node
Thanks and regards,
Cristian -
When a Storware update goes wrong, here's how to handle it:
- Stay Calm: These issues can be fixed.
- Check Logs: Look for error messages in the update logs.
- Rollback if Needed: Revert to the previous version if the update caused major problems.
- Contact Support: Reach out to Storware support for help.
- Verify Compatibility: Ensure the update is compatible with your system.
- Backup Data: Securely back up your data before making further changes.
- Check Dependencies: Make sure all necessary components are installed and updated.
- Consider a Clean Install: Uninstall and reinstall the latest version if problems persist.
- Review Documentation: Check Storware’s documentation for any known issues and solutions.