I resolved this issue with this command:

ip addr del 10.10.122.13/24 dev enp3s0

Hello @ZakariyaKhalaf

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

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

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

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

Hello @Tommaso

This error indicates insufficient privileges to execute this command. You probably need to use an account with higher privileges.

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

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 @centrisag

I am sorry for late response. I must to ask, do you mean OLVM (Oracle Linux VM, ovirt based hypervisormanager) or OVM (which is older solution from Oracle)? It is important in meaning of choose strategy.

At this moment we do not make another HA feature, then in our documentation, but I think, that we could handle your environment in other way:

Our software is build in architecture Server+Nodes. You could use many Nodes with own config (for example for Main and External site) Server could be in completly another place than worker nodes (for example in another hypervisor) You can restore VM from Main to external site only choosing where this vm should be restored (if you have Node configs, we choose based on assinged Node config to hypervisor) You can use guide for Disaster Recovery if you want to arise server in another location.

If you need additional information, the best option will be contact with our PreSales Team (presales@storware.eu) where my coworkers could make meeting where they could show you how we handle similar cases.

Regards
Krzysztof Szawara
IT Systems Specialist

Hello @kirkscollision

Sorry for the late response time, I hope you are still interested in our solution.

I'm not sure what installation you're asking about. The error occurs while installing our software or XCP? Please provide more information and we will try to help.

Hello @branes

What do your backup retention settings look like? With what parameters is NFS shared? Does the storware node have full access to this NFS resource? You are sure that nothing changed in the DataDomain settings in the meantime?

Hello @sangram

If you select an interval schedule, the backup will be performed only at selected hours in accordance with the frequency.
For example:
Window start: 6:00AM
Window end: 10:00AM
Frequency: 60min
The backup will be performed at 6,7,8,9,10.

Perhaps the Time type with specific hours when the backup must be performed will be better in your case? You can set specific times when the backup should be performed.

Hello @sangram

Yes, this is expected behavior, we can create only full backups of Apps.You can save space on Backup Destination using some of deduplication types (like synthetic BD)

Regards

Hello @jguilford81

Please go to the Virtual Environments -> Virtualization Providers -> click your vCenter -> Certificates tab. Then select "Trust all certificates" and save. Perform inventory synchronization again and check the backup.