Posts made by krzysztof.sz

Hello

It looks that you do not clear certs and not set after that Trust All Certificates

It should be looked like this in tab Certificates:

you also should set same in all hypervisors inside hvm:

After clear certs, and set up TCA please rerun Inventory Sync and run backups.

If you tried it, you could clear all info about HVisors removing them from that tab. Please be careful about that, that you should check that you switched off autoremove non-present vms in Backup Policy:

Regards

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

Hi!

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

Regards

@Cristian-Eglue

You can try jump from version 6.1.0, but in this case I recommend to make backup of database (after stop the server use /opt/vprotect/scripts/backup_db.sh, it will create backup of db in /tmp), After that you could restore it to clean install like in our documentation: Recovery.

Regards

Hi!

Sorry for delay.

This error is mostly depend on connectivity issues. When we receive information from Manager and not correct information from host. The information of file to transfer is first which we check.

It could be affected by SSL chain. When we could communicate by SSL to Manager but not for all hosts.

You can go to setup of Virtual provides, and clear all certs, and switch on "Trust all Certificates" on Manager and each of hosts. Then run Sync and try to backup.
Regards

Hello @ZakariyaKhalaf

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

Hi!

I am sorry for delay!

To check your issue we need to look deeper. Could you tell me some information about your environment (Do you use All-in-one installation, How many resources do you have for our software).

You also have old, not fully supported version. Version 6.1.0 have many changes in area of M365 backup.
Regards
Krzysztof

Hi!

After deep a**lysis 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

Hi @KLM

Error which you sent is known and is in under development. We will update you when fix will be available.

Regards

Hi! @user

NFS4.2 have support to synthetic backup, but it is necessary to use XFS under NFS share. NFS only provide possibility to use synthetic file system under share, we support XFS as Synthetic FS.

The same error you have in XCP-ng.

Regards

Hello!
Thank for your post.

It looks, like you created Synthetic Backup Destination on file system, which not support it. We use XFS as synthetic file system.

You could use classic File System, or recreate Backup Destination on XFS file system.

Kindly regards

Hi!

Did you try use that KB? There are few additional steps.

KB10025

Regards
Krzysztof

Hi!
Thank you for the post!

Could you tell me more about your infrastructure?

Which version of VMWare (and VMware VDDK) do you have?

Regards

Hi!

Thank for your post.

Could you tell me which user do you use to connect to your KVM host?

Regards

Hi @pradeep
Thank you for your ask.

Could you tell me something about your Infrastructure. Which Strategy Backup do you use? Some of Backup Strategies need to have an node/proxyVM inside OLVM (please look at that Documentation page: https://storware.gitbook.io/backup-and-recovery/protecting-virtual-machines/virtual-machines/oracle-linux-virtualization-manager in example Disk Attachment need an proxyVM)

Please tell me, did you follow our guide in Documentation? https://storware.gitbook.io/backup-and-recovery/deployment/installation (You could use all in one, where configuration is minimal)

Regards
Krzyszof