Description of problem:
When any migration is triggered from 3.11 to 4.x cluster, the migrations stuck at the Backup phase. It is being observed that the velero pod on 3.11 cluster is getting restarted and having errors.

Version-Release number of selected component (if applicable):
3.x -> 4.x

How reproducible:
Always


Steps to Reproduce:
1. Deploy django or any application on the source cluster
2. Create migplan from MTC UI and perform a migration.


Actual results:
Velero pod restarts and Migration stuck in UI


Expected results:
Migration should be successfully completed.

Additional info:

Controller logs:

openshift-migration migration-controller-77cdcf4674-56gj5 mtc {"level":"info","ts":1673532636.4577825,"logger":"migration","msg":"Initial Velero Backup is incomplete. Waiting.","migMigration":"ocp-24872-mssql-mig-1673526503","phase":"InitialBackupCreated","backup":"openshift-migration/ocp-24872-mssql-mig-1673526503-initial-mfc2b","backupPhase":"InProgress","backupProgress":"34/34","backupWarnings":0,"backupErrors":0}


Velero pod logs:

time="2023-01-12T14:14:01Z" level=error msg="Error getting backup metadata from backup store" backup=ocp-33393-bz1845569-mig-1663065481-initial-cssqf backupLocation=automatic-t6r8s controller=backup-sync error="rpc error: code = Unknown desc = storage: object doesn't exist" error.file="/remote-source/velero/app/pkg/persistence/object_store.go:289" error.function="github.com/vmware-tanzu/velero/pkg/persistence.(*objectBackupStore).GetBackupMetadata" logSource="/remote-source/velero/app/pkg/controller/backup_sync_controller.go:216"