Backup copy job fails due to object lock

[Moose]

We have several backup copy jobs (configured as a storage copy option between two HPE StoreOnce's) failing due to unable to delete a restore point. We have enabled immutability on both source and target repositories.

The actual error message we receive is as follows, "Failed to call RPC function 'PluginsHost.StoreOnceCreateEmptyFile': OSCLT_ERR_OBJECT_LOCK_FAILED. Err: -1909. Failed to delete Object |JOBNAME|RESTORE POINT OF A VM on Store CATALYST STORE.

Veeam Case#07815482
Support responded with the following action items
- Reboot StoreOnce
- Reboot associated Mount server
- Upgrade StoreOnce FW
- Make sure the StoreOnce is not being accessed at the same time by multiple backup jobs.

We responded by rebooting both StoreOnce and associated mount server and scheduling a different backup time. But we are still having the same issue.
Not sure of next steps.


Environment Information

HPE StoreOnce 5660
4.3.11-2515.50

Veeam B&R
12.3.2.3617

[PetrM]

Hello,

I don't think we can effectively troubleshoot this issue through forum posts, as it does not appear to be a well-known problem or something that can be quickly resolved. I believe it would be best to let our support team handle it. Since the error code is returned by the storage in response to our attempt to create a file, it's likely that the storage vendor's support team will also need to be involved. However, I will leave the decision on the best troubleshooting strategy to our engineers.

Additionally, you may want to try rebooting the Gateway server, rather than the Mount server.

Thanks!

[Moose]

Thanks for your response. Just a side note before we configured the Catalyst stores to be immutable, we were able to flag the particular corrupted restore point by choosing the forget option. Then upon a retry of the backup copy job, it completed successfully. Now when we encounter the same situation, we end up creating a new catalyst store and a new backup copy job to resolve.