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.

@krzysztof-sz Yes, I tried that, didn't work. Could do 1 backup, the next one failed. I think I'll just reinstall it all.

@a-spinek Thank you, that works!

@djaw Yes it is a stand alone host

Hi @mario-krizan, Also, is it possible to migrate a virtual machine from OVM to OLVM with Stormware? Unfortunately, we do not support this type of migration. Failed to collect file system information: [Command execution failed: [/usr/bin/virt-filesystems, --filesystems, -l, --csv, -a, /vprotect_data/abc_fmo_pool_01/A22000A0__0004fb00000600007ee414f01ab0c9f5/0004fb00001200002bb2cfe407f43a53.img] Return code: 1 output: [] error: [libguestfs: error: force_kvm supplied but kvm not available. ]] Please provide a log with DEBUG mode enabled. Instructions how to do this: https://storware.gitbook.io/backup-and-recovery/troubleshooting/how-switch-vprotect-to-debug-mode

Hello! Sorry for late response. Please tell me at first, did you tried to update to version 6.2.0 and then restore backup? If problem still occurs we need to look into log f backup and restore. Before you generate it please follow this guide: DEBUG MODE Regards Krzysztof

@carl-ceriola Hi, what backup method do you use?

@vguillard Hi, no Storware is not capable of backuping/restoring user-data yet.

Scratch that, was able to modify some S3 settings and it now shows as a destination. Now my issue is that all backup jobs including internal db show queued and not doing anything.

@krzysztof-sz Finally last week I had some spare time to do some tests, I wasn't able to import the old database because after the import the service storware-server stopped to work, anyway I built from the ground up a new VM with Storware 6.1.0-25, and so far it is working fine (except two minor issues that I'll now discuss here). Hope it will not broke in the next days. Regards, Cristian

Hello @victors, This new limitation was introduced in the 6.2 version of Storware Backup & Recovery. In this strategy, you can make only full backups of OpenStack instances because every time a snapshot is kept on the VM, the disk type changes to QCOW2. Incremental backups are only available for CEPH volumes in SSH/libvirt strategy, https://storware.gitbook.io/backup-and-recovery/changelog

Hi! I am sorry for delay, but could you tell me more about your environment? Where is server and node (inside/outside VMWare)? Regards

Hello @ZakariyaKhalaf Could you show some logs for task? Do you have DNS with resolve of this name?

@andreargamgroup I can confirm that the same behavior occurs when you are using a password with UTF-8 characters. I will let you know when the fix for this problem will be ready.

Hello @user If you still have this problem, please send us the full DEBUG logs of this operation (server and node logs). If you cannot attach logs to this thread, you can put them somewhere, e.g. OneDrive or similar, and send the link. Here is the documentation on how to switch logs to debug: Logs in DEBUG

@VP Please also try to restart service, it might help. systemctl restart vprotect-server && systemctl restart vprotect-node Best regards Jan Leszczyński

@a-spinek thanks for your fast answer. This explains all.

I resolved this issue with this command: ip addr del 10.10.122.13/24 dev enp3s0

Hi, I can't see the images you uploaded. Storware had some issues with duplicated rules. It was already fixed so I would recommend updating to the latest version 6.1.0 (6.0.0 will also be fine).

Hi! After deep analysis we found, that issue is caused by deleting of snapshots files without merging it to vm. We do not this kind of operation, so it could be done only by user itself. Regards