@tib_aj Hi, We have our pa**er, file that you upload in web UI can even be foo.txt, but inside you need to have proper formatting including an EOL mark at the end of the config and keyring (just use enter on the end of the file)
Posts made by Argus
-
RE: Ceph keyring malformed when uploaded via Storware Backup & Recovery UI
-
RE: Synchronization task failed: OpenStackException: Cannot fetch local MAC addresses
@carl-ceriola Hi, what backup method do you use?
-
RE: OpenStack: user_data are not backup ?
@vguillard Hi, no Storware is not capable of backuping/restoring user-data yet.
-
RE: Store task failed: Server has encountered the runtime error (RUNTIME_ERROR)
Hi we are not supporting file level restore for XCP we cannot read filesystems in its backup files, it is a technical limitation
You can check what features we support or not for different entities here -
RE: Can not backup VM on OpenStack
@kienht Ah, sorry RAW block devices are not supported in the SSH Transfer method. Documentation mentioning only disk image files we will change this for better understanding.
-
RE: Direct Backup to S3
@KLM You can delete backups by removing VMs from the list in the Instances tab.
-
RE: Direct Backup to S3
@KLM Also if you selected the "backup destination for cloud" lever in the backup destination configuration it would be only visible for cloud instances.
-
RE: vMwareStrategyException
@benitowarez We are investigating but it looks like some error on the VMware side, did this error occur for particular VMs or all VMs ?
-
RE: Can not backup VM on OpenStack
Hi, For the libvirt strategy only, QCOW2/RAW files or Ceph RBD are supported as the backend.
-
RE: Direct Backup to S3
Yes, it is possible, did you choose node configuration for this backup destination? Can you give me your version of SBR?
-
RE: Warning: Incremental snapshot is not available
@Cristian-Eglue Yes I can see thank you. So in this configuration, you set 7 days and 14 versions to keep, but your scheduler is configured to make a backup every day. So after a week, you have 7 backups but you also set a time restriction so backups older than 7 days will be marked as expired and removed after the next backup cleanup job so you only get 7 versions, not 14. nevertheless, you should be able to restore from any of those 7 versions.
-
RE: vMwareStrategyException
@benitowarez oh so after the update you still get this DISK_HANDLER error?
-
RE: vMwareStrategyException
@benitowarez I checked your logs I see you have a version mismatch update vprotect-node package to the latest version and server to we have a new one
-
RE: vMwareStrategyException
@Argus Did you only update vprotect-server ?
-
RE: vMwareStrategyException
@benitowarez Can we get logs from this one also?
-
RE: Connect to OpenNebula
@kutajs Backup method you using require vprotect node proxy VM inside opennebula HV do you have one?
-
RE: vMwareStrategyException
@benitowarez I see slightly different error from vmware I will check this with our dev tomorrow
-
RE: Warning: Incremental snapshot is not available
@Cristian-Eglue The file appears to be broken
-
RE: vMwareStrategyException
@benitowarez Hi, we spoke on the mail, can you give me your vprotect version ? It is possible that this error was already fixed
-
RE: Warning: Incremental snapshot is not available
@Cristian-Eglue Hi, you can omit warn messages, but I would like to see your schedulers set in that policy.