On Wed, Jul 27, 2022 at 2:56 PM <markec...@gmail.com> wrote:
>
> Hi!
> Not really sure if this is right place to ask, but..
>
> I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1.
> I have been using it on version 4.4.10.7 and it works ok there.
>
> On Veeam Release page it says that supported OS is RHV 4.4SP1 (oVirt 4.5).
>
> When i try to do backup, this is what i get from Veeam backup.
> No errors in vdsm.log and engine.log..
>
> 2022-07-27 08:08:44.153 00039 [19545] INFO | [LoggingEventsManager_39]:
> Add to storage LoggingEvent [id: 34248685-a193-4df5-8ff2-838f738e211c, Type:
> BackupStartedNew]
> 2022-07-27 08:08:44.168 00039 [19545] INFO | [TaskManager_39]: Create and
> run new async task. [call method:'RunBackupChain']
> 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: New AsynTask
> created [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f', description:'',
> type:'BACKUP_VM_POLICY']
> 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: Prepare
> AsynTask to run [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f']
> 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Refresh
> VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b'
> 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Begin
> updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b'
> [forceRefresh = True]
> 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test
> connection to cluster [IP: engine.example.org, Port: 443, User:
> admin@ovirt@internalsso]
> 2022-07-27 08:08:44.189 00039 [19545] INFO | [TaskManager_39]: AsyncTask
> registered. [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f']
> 2022-07-27 08:08:44.371 00031 [19545] INFO | [RhevCluster_31]: Test
> connection to cluster success. Status: Success. Message:
> 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]:
> Refreshing the policies data...
> 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Begin
> updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b'
> [forceRefresh = False]
> 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of
> active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b'
> [forceRefresh = False]. Number of active VMs '1'
> 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]:
> Policies data has been refreshed.
> 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of
> active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b'
> [forceRefresh = True]. Number of active VMs '1'
> 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Found the
> '1' VMs to backup in policy '6e090c98-d44b-4785-acb4-82a627da5d9b'
> 2022-07-27 08:08:44.564 00031 [19545] INFO | [BackupPolicy_31]: *
> Parallel policy runner has started * for policy [Name:'test5', ID:
> '6e090c98-d44b-4785-acb4-82a627da5d9b'
> 2022-07-27 08:08:44.564 00031 [19545] INFO | [VeeamBackupServer_31]: Test
> connection to backup server [IP: 'veeambr.example.org', Port: '10006', User:
> 'rhvproxy']
> 2022-07-27 08:08:44.931 00031 [19545] INFO | [VeeamBackupServer_31]: Test
> connection to backup server [IP: 'veeambr.example.org', Port: '10006'].
> Connection status: ConnectionSuccess. Version: 11.0.1.1261
> 2022-07-27 08:08:45.423 00031 [19545] INFO | [BackupPolicy_31]:
> Successfully called CreateVeeamPolicySession for job [UID:
> '6e090c98-d44b-4785-acb4-82a627da5d9b'], session [UID:
> 'aafa22ac-ff2e-4647-becb-dca88e3eb67f']
> 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]:
> Successfully called RetainPolicyVms for job [UID:
> '6e090c98-d44b-4785-acb4-82a627da5d9b'] with VMs:
> 50513a65-6ccc-479b-9b61-032e0961b016
> 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Start
> calculating maxPointsCount
> 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: End
> calculating maxPointsCount. Result = 7
> 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Starting
> validate repository schedule. Repository [UID:
> '237e41d6-7c67-4a1f-80bf-d7c73c481209', MaxPointsCount: '7',
> IsPeriodicFullRequired: 'False']
> 2022-07-27 08:08:46.595 00031 [19545] INFO | [BackupPolicy_31]: End
> validate repository schedule. Result: [IsScheduleValid: 'True', ErrorMessage:
> '']
> 2022-07-27 08:08:46.597 00031 [19545] INFO | [SessionManager_31]: Start
> registering a new session[Id: 'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708']
> 2022-07-27 08:08:46.639 00031 [19545] INFO | [SessionManager_31]: Session
> registered. [Id:'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708']
> 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: Backup VM
> [id:'50513a65-6ccc-479b-9b61-032e0961b016'] starting...
> 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]:
> RetentionMergeDisabled: false
> 2022-07-27 08:08:46.640 00031 [19545] INFO | [TaskManager_31]: Create new
> async task. [call method:'DoBackup']
> 2022-07-27 08:08:46.640 00031 [19545] INFO | [AsyncTask_31]: New AsynTask
> created [id:'15a63192-f3d2-4e3a-af56-240f3733bded', description:'',
> type:'BACKUP_VM']
> 2022-07-27 08:08:46.640 00031 [19545] INFO | [AsyncTask_31]: Prepare
> AsynTask to run [id:'15a63192-f3d2-4e3a-af56-240f3733bded']
> 2022-07-27 08:08:46.661 00031 [19545] INFO | [TaskManager_31]: AsyncTask
> registered. [id:'15a63192-f3d2-4e3a-af56-240f3733bded']
> 2022-07-27 08:08:47.295 00031 [19545] ERROR | [BackupPolicy_31]: Backup VM
> [id:'50513a65-6ccc-479b-9b61-032e0961b016'] failed. Error ('test: VM
> UUID=50513a65-6ccc-479b-9b61-032e0961b016 was not found: * Line 1, Column 1
> Syntax error: value, object or array expected.
> * Line 1, Column 1
> A valid JSON document must be either an array or an object value.
> ')
>
> Are there any changes between version 4.5 and 4.5.1 that are preventing using
> this?
In general oVirt is always backward compatible. The only change that
may be a problem
is changing the user name from "admin@internal" to "admin@ovirt@internalsso" but
this is already fixed in your example.
The failure:
A valid JSON document must be either an array or an object value.
Typically happens when you use "http" instead of "https" or similar error
which is not related to the actual error.
> Any solution?
Maybe try to enable DEBUG log level in Veeam. Seeing the actual http
request and http response from ovirt engine will probably tell what is the
real issue.
Maybe Yuri knows more about this.
Nir
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6T4FSGVOIN6DXP2237WZLUIBL5XVYCNR/
