Backup Copy - Change time between retries?

[mrholm]

Hi
We do a lot of bakcup copies over WAN to StoreOnce Catalyst. Sometimes a VM i failing in a job and Veeam retry that VM but StoreOnce then have the files locked and we get 1909 OSCLT_ERR_OBJECT_LOCK_FAILED and the job will fail after 5 retries.
Can we change the time between the retries as we can for backups? If yes how long will StoreOnce keep the file locks nowdays?

//Mats

[coolsport00]

Here is info ir: b/u copy job retries:
https://helpcenter.veeam.com/docs/backu ... tml?ver=95

These retry intervals are 'automatic' and are not configurable in the GUI. You may be able to make a change to this via Registry, but I'm not 100% sure. You may be able to get an answer from Veeam Support about that being a possibility or not.

Regards.

[foggy]

Hi Mats, in older StoreOnce versions the file lock period was indeed long. What SO version do you have?

[mrholm]

We're using 3.18.3 on our StoreOnce.
If it's like you say that the file lock is down to 20 min it's still long for 5 retries in Veeam copy. It must be a way to change the retry in copy as it is in backup jobs??

[foggy]

Please try the BackupSyncMaxRetriesPerOib registry value.

[mrholm]

I got the following from Support:

RepositoryWriteRetryTimeoutSec
Type: REG_DWORD
Default value: value in seconds

RepositoryWriteRetryCount
Type: REG_DWORD
Default value: vaule decimal count

[mrholm]

Foggy, what does the registry setting, you mentioned, change?

[foggy]

The number of data transfer retry attempts. Actually, there are several types of retries and which one you need depends on the reason of the initial job failure:

Sometimes a VM i failing in a job

[mrholm]

When doing copy to StorOnce we get OSCLT_ERR_SERVER_OFFLINE 1404 nd since Veeam tries a restart directly without timeout the next try get OSCLT_ERR_OBJECT_LOCK_FAILED.
We like to set a timeout between retries in copy job as I can for bakcup jobs

[foggy]

Have you tried the registry setting? Increasing the number of retries should help to cover the file lock period.

[mrholm]

Sadly the proposed workaround is not working and I open a new case 03247180.
This could not be such a "biggie" when it can be done in the bakcup jobs?
A big future request if this can't be fixed....

[foggy]

I'd also look for the ability to change the file lock period on the storage side, if possible.

[mrholm]

I do agree but changing the file lock period on StoreOnce is not something for me to handle, believ ethat it would be easier for Veeam+HPE to look into this and solve the mechanism around this.

[foggy]

Let's see what our engineers come up with after reviewing your log files.

[mrholm]

We seem to have solved the most WAN related errors so we see less of the errors associated with StoreOnce but I stil lthink that Veeam should be able to set intelligence on the backup copy since we point out that the repo is a StoreOnce Catalyst. Setting a timeout in the code or add the same possibility to set amount of retries and timeout between retries like in backup.

[foggy]

Thanks for the update, glad you've been able to mitigate the issue. And thanks for your feedback as well, it is always appreciated.

[foggy]

Btw, how StoreOnce is connected to Veeam B&R here - is it FC or iSCSI?